F-secure Policy Manager Http Server Error
Contents |
for may have been moved or the
F-secure Policy Manager Console
URL may be incorrect Contents Sub Topics Related Topics Search Results 2016 F-Secure. All rights reserved. Terms & Conditions English Change Version Use this menu to view the product's documentation for a different version Next Change Platform Use this menu to view the product's documentation for a different platform Next View other content Use this menu to see more content that is available for this product Next Change Language To view the documentation in a different language, select the available languages from this menu Close
narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean Home Help forums How-to & FAQs Change language: EN FI F-Secure Community / Business Security Knowledge Base / Article Options Article History Subscribe to RSS Feed Bookmark Subscribe Email to a Friend Printer Friendly Page Report Inappropriate Content Unable to connect to the Policy Manager Server after upgrading to Policy Manager 12.10 by Khairul_A 27-07-2016 12:18 PM - https://help.f-secure.com/product.html?business/policy-manager/12.00/en/concept_D46BE213762C4338AB0448CD17728616-12.00-en edited 27-07-2016 12:41 PM (1,285 Views) Labels: Policy Manager for Windows 12.x Symptoms 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." Diagnosis This may be a TCP port conflict. Policy Manager https://community.f-secure.com/t5/Business/Unable-to-connect-to-the-Policy/ta-p/85137 12.10 introduces a new port for the client and Policy Manager communication which is supported by newer clients (e.g. Server Security 12.00, Client Security 12.10). The default listening port is 443. 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. Solution If you suspect that you have a service running on port 443, run the following command in command prompt (run as administrator) to check: netstat -anb > ports.txt. 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. 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] 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
narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean Home Help forums How-to & FAQs Change language: EN FI F-Secure Community / https://community.f-secure.com/t5/Business/Policy-Manager-11-on-Windows/td-p/28084 English / Business Security / Business Security / Policy Manager 11 on Windows Server 2008 R2 - firewall rules for communication? Reply Topic Options Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page « Message Listing « Previous Topic Next Topic » fossehs Aspirant Posts: policy manager 13 Registered: 11-07-2013 Policy Manager 11 on Windows Server 2008 R2 - firewall rules for communication? Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Permalink Print Email to a Friend Report Inappropriate Content 11-07-2013 11:08 AM Since we can now no longer download the latest Client Security versions installer from F-Secure website, I haverecently installed Policy Manager 11 secure policy manager on a Windows Server 2008 R2 server which didn't have any existingsoftwareusing any of the ports 80, 8080 or 8081 prior to F-Secure Policy Manager being installed.I have imported the Client Security 11 fscs-11.00-332-rtm into Policy Manager and exported the msi installer fscs-11.00-332-rtm-exported using the latest installation keycode and the fqdn of the policy manager server: http://servername.domain.localI have performed the installation of fscs-11.00-332-rtm-exported.msi on my Windows 8 Enterprise computer which installed successfully and appears to be getting the updates from the F-Secure website.Two issues:1)The computer does not appear in the Policy Manager console which I suspect ports need to be opened for the Windows Server 2008 R2 firewall? Please confirm inbound and outbound ports required to be opened on the server.2) On the default policy of the exported msi versiondoes not allow F-Secure client to unload as it used to do on the standalone version. What settings need to be set to allow this feature to exist and apply the policy to the first computer I am testing on?Kind Regardsfossehs Message 1 of 3 (6,376 Views) Report Ina
be down. Please try the request again. Your cache administrator is webmaster. Generated Sat, 15 Oct 2016 12:11:39 GMT by s_ac15 (squid/3.5.20)