policy manager can not be accessed in fsecure 12.4 (administration module - a connection with the server cannot be established)

Highlighted
Aspirant

policy manager can not be accessed in fsecure 12.4 (administration module - a connection with the server cannot be established)

I have problems in acessing the policy manager. I tried to reconfigure port as shown, restarted the services but the problem persists. Any Ideas ?

fsecure.png

 

1 ACCEPTED SOLUTION

Accepted Solutions
Aspirant

Re: policy manager can not be accessed in fsecure 12.4 (administration module - a connection with the server cannot be established)

As i tried it from the server only .. localhost and dc01... where the same machine but i forgot that they do not use the same ip 127.0.0.1 is definetly not 192.168..... shame on me

of course you are right ... as i am on the server via rdp i do not need to administer anything on an other maschine.

So one thing remains ... some previous version has worked with https://localhost while it has to read https://localhost:8085. Im pretty sure about it as i initialy made the setup with the modified ports. Maybe the Hosts File or a meanwhile changed switch had some information that translated the ip.

Anyhow i guess i'll never  find out about that part.

 

Thank you for your help and consider this case as solved

13 REPLIES 13
F-Secure Product Expert
F-Secure Product Expert

Re: policy manager can not be accessed in fsecure 12.4 (administration module - a connection with the server cannot be established)

Hi, 


can you confirm that port 8087 is not used by any other service?
Did you try changing the port already?



Best Regards

-Ben

_________________________________

Has somebody helped you? Say thanks by giving likes. Has your issue been solved? Mark the post using "Accept As Solution" button to let others know.
Aspirant

Re: policy manager can not be accessed in fsecure 12.4 (administration module - a connection with the server cannot be established)

same problem here on different portdx.png

Aspirant

Re: policy manager can not be accessed in fsecure 12.4 (administration module - a connection with the server cannot be established)

sorry for the long replie time .. been busy on other customers,

Yes, stated above and again below i can confirm that the ports are not in use and i tried as well changin g them from former 8085 to 8087. A quick try on 80 and 81 for the administartion module also archieved nothing.

Superuser

Re: policy manager can not be accessed in fsecure 12.4 (administration module - a connection with the server cannot be established)

Having an other look at your screenshots, all look nice, except that I do not see
1) if the firewall is open for 8085 (8087)
2) You status it rying to connect to DC01 instead of 127.0.0.1.. the port is not bound to the external IP.
So rerun the setup and chose "change settings" to allow administration from other PC.

Remenber these:
12.40 is introducing https so by default you need 80, 443, 8080 and 8081

80 and 443 ar for Host-> Server communication. Ports must be open at Firewall of the Server

8080 is by default limited to local access and is used for PMC -> PMS communication
8081 is WebReporting


So please try to connect to these ports using a standard browser with proxy settings = none.
e.g. https://<ip of server>:443. What is the output?

 

Changing port 443 is a bit tricky, as Clients need to learn about that change through the policy, which they might expect to receive on Port 443. Try to stick with that port.

Matthias
----------
perComp is a Platinum Partner of F-Secure since 1994. Any advice or help given by me in this forum is voluntarily and to my best knowledge based on working with the products since 1997. Direct contact for customers please check our homepage http://www.percomp.de

F-Secure
F-Secure

Re: policy manager can not be accessed in fsecure 12.4 (administration module - a connection with the server cannot be established)

Hello Matthias, noknowhow,

 

Small correction. Default HTTPS port is 443.

 

Best regards,

Vad

Superuser

Re: policy manager can not be accessed in fsecure 12.4 (administration module - a connection with the server cannot be established)

changed that to 443. thanks for the correction.

Matthias
----------
perComp is a Platinum Partner of F-Secure since 1994. Any advice or help given by me in this forum is voluntarily and to my best knowledge based on working with the products since 1997. Direct contact for customers please check our homepage http://www.percomp.de

F-Secure

Re: policy manager can not be accessed in fsecure 12.4 (administration module - a connection with the server cannot be established)

Hello noknowhow,

Could you please check jetty.request.log in c:\Program Files (x86)\F-Secure\Management Server 5\logs\

Requests from the Status monitor should be logged like:

127.0.0.1 - - [date:time +offset] "GET https://localhost:8087/fspms/version HTTP/1.1" 200 11 "-" "FSMS_STATUS_QUERY"

127.0.0.1 - - [date:time +offset] "GET https://localhost:8083/web-reporting/version HTTP/1.1" 302 0 "-" "FSMS_STATUS_QUERY"

127.0.0.1 - - [date:time +offset] "GET /fsms/fsmsh.dll/?FSMSCommand=GetVersion HTTP/1.1" 200 - "-" "FSMS_STATUS_QUERY"

127.0.0.1 - -[date:time +offset] "GET /fsms/fsmsh.dll/?FSMSCommand=GetVersion HTTP/1.1" 200 - "-" "FSMS_STATUS_QUERY"

 

Please copy-paste it here.

Also you can check what is the status code for the https://localhost:8087/fspms/version request (200 in my example) and check other logs for exceptions happened same time. If this entry does not exist in the log, that might be firewall issue.

Also, one idea is to set RestrictLocalhost to 0 in the registry (with PMS service restart) and try again. Status monitor might reach Policy Manager via external interface while according to your registry only connections from localhost are allowed.

Regular Member

Re: policy manager can not be accessed in fsecure 12.4 (administration module - a connection with the server cannot be established)

Hi,

 

try a telnet on the specified port when the PM services are not running.

If you get a connection the port is already used by a differnet application

 

format:

telnet fqdn portnumber

 

 

 

Aspirant

Re: policy manager can not be accessed in fsecure 12.4 (administration module - a connection with the server cannot be established)

as a result i get in the last jetty_2017_11_05.request.log.1 some lines like the following 2 lines

192.168.100.88 - - [05/Nov/2017:23:07:58 +0100] "GET https://dc01.elora.intern:8082/host-module/fsms/fsmsh.dll?FSMSCommand=GetPackage&Type=4&Identity0=50... HTTP/1.1" 304 0 "-" "F-Secure Network Request Broker"
192.168.100.88 - - [05/Nov/2017:23:07:58 +0100] "POST https://dc01.elora.intern:8082/host-module/fsms/fsmsh.dll?FSMSCommand=UploadPackage&Type=5&Identity0... HTTP/1.1" 200 8 "-" "F-Secure Network Request Broker"

 

i switched to 8085 meanwhile and even restarted the whole maschine ...

doing a https://localhost:8085/fspms/version comes up with a nearly white page showing only

13.00.83038
as i updated from version 12.4 to 13 ... but still output of polcy manager is
the same as above

Administation Module
HTTP Pport : 8085
Status : a connection with the server cant be established