Community
User Guides
Support
Community
Help Forums
English Forum
General
About our Community
General Discussion
News and Feedback
Products
F-Secure SAFE
F-Secure FREEDOME
F-Secure KEY
F-Secure SENSE Router
F-Secure ID PROTECTION
Other products
Beta programs
Feature Requests
Finnish Forum (Tukifoorumi)
Tuotteet Kotiin
F-Secure SAFE
F-Secure FREEDOME
F-Secure KEY
F-Secure SENSE Router
F-Secure ID PROTECTION
Muut tietoturvatuotteet
Support Articles
Language
English
Suomi
Deutsch
Français
日本語
Svenska
Dansk
Italiano
Nederlands
Norsk
Polski
中文 (繁體)
Products & Services
F-Secure TOTAL
F-Secure SAFE / Internet Security / Anti-Virus
F-Secure FREEDOME
F-Secure KEY
F-Secure SENSE Router
F-Secure ID PROTECTION
Other products
Common topics
User Guides
Support
Login
|
Register
Unable to connect to the Policy Manager Server after upgrading Policy Manager - F-Secure Community
<main> <article class="userContent"> <p> </p>Unable to connect to the Policy Manager Server after upgrading Policy Manager <h3>Symptoms </h3> <p>Policy Manager Console prompts an error message: "Cannot connect to the server: localhost:8080. Check that the host name and port number are correct. Port number 8080 is used by default." </p> <h3>Diagnosis </h3> <p>This may be a TCP port conflict. Policy Manager has a port for client and Policy Manager communication which is supported by the clients. The default listening port is 443. </p> <p>If you already have a service running on this port, this prevents Policy Manager Server from starting, thus not allowing you to login using Policy Manager. </p> <h3>Solution </h3> <p>If you suspect that you have a service running on port 443, run the following command in command prompt (run as administrator) to check: </p><pre class="code codeBlock" spellcheck="false">netstat -anb > ports.txt</pre>. This redirects the output to a file called ports.txt. Open the file to view the information. Below is a partial sample of the output. <pre class="code codeBlock" spellcheck="false">Proto Local Address Foreign Address State TCP 0.0.0.0:135 0.0.0.0:0 LISTENING RpcSs System] TCP 0.0.0.0:443 0.0.0.0:0 LISTENING someapplication.exe]</pre> <p>In this case, we already have an application listening on port 443 (someapplication.exe). Note that the default listening process in Policy Manager is java.exe. As both applications are configured to use the same port, there is a conflict. To fix the issue, two options are available. </p> <ol><li> Change the conflicting port used by someapplication.exe <ol type="a"><li>Consult the documentation for someapplication.exe to find out how to change the port. </li> <li>Once the port is changed, restart Policy Manager server using an elevated command prompt; <p></p><pre class="code codeBlock" spellcheck="false">net stop fsms</pre> <p></p><pre class="code codeBlock" spellcheck="false">net start fsms</pre> </li> </ol></li> <li> Change the conflicting port in Policy Manager Server <p>In this example, we are changing the port from TCP 443 to TCP 444. </p> <ol type="a"><li>Open <strong>Registry Editor</strong>. </li> <li>Browse to <strong>HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Data Fellows\F-Secure\Management Server 5</strong>. </li> <li>On the right pane, locate <strong>HttpsPortNum</strong>. Change the value from decimal 443 to 444. </li> <li>Restart Policy Manager Server using an elevated command prompt: <p></p><pre class="code codeBlock" spellcheck="false">net stop fsms</pre> <p></p><pre class="code codeBlock" spellcheck="false">net start fsms</pre> </li> <li>Start <strong>Status monitor</strong> in the Policy Manager program group, and change the default HTTPS port from 443 to 444. </li> <li>Go to the <strong>Advanced mode</strong> in Policy Manager Console, and navigate to <strong>F-Secure Managerment Agent</strong> > <strong>Settings</strong> > <strong>Communications</strong> > <strong>Protocols</strong> > <strong>HTTP</strong> > <strong>HTTPS Port</strong>. </li> <li>Change the default value from 443 to 444, and click the <strong>Force value</strong> to lock the settings. </li> </ol></li> </ol> </article> </main>