Making sure Syspeace can connect to the Syspeace backend server
If you can’t start up Syspeace, chances are that Syspeace can’t talk to the Syspeace backend server. If you are receiving a “No contact with the license server” message this is definitely the case.
Please start by verifying the following:
- The domain name s.syspeace.com (or s-sha1.syspeace.com for Windows Server 2003) can be resolved over DNS.
- The HTTP server at the above address is reachable on port 443. (If port 443 traffic or traffic in general is disallowed, you may need to make an exception for Syspeace’s IP addresses.)
- Using Internet Explorer on the server itself (to use the same proxy settings), you can go to https://s.syspeace.com/Ping (or https://s-sha1.syspeace.com/Ping for Windows Server 2003; you will receive a certificate error).
If using the Syspeace client works well but the Syspeace service does not start, it is possible that a proxy has been applied through a GPO (Group Policy Object) that uses Windows authentication to authenticate with the Active Directory domain account of the logged in user. The Syspeace service runs as a local System account and therefore it will not be able to authenticate with the proxy (this will be the case for everything running as a local account on this server not manually configured to have other proxy settings, and may affect operating system services and other programs). To resolve this situation, reduce the scope of the group policy object to not encompass the local System account.