Follow the instructions in the alert box to accept the certificate as certified. If using Firefox or Mozilla, you will receive a security alert.Once you have returned to the security alert box, select the "Accept" option. Follow the instructions to install the certificate. Select it, and then select the ïnstall certificate" option. You will be given an option to view the certificate. If using Internet Explorer, you will receive a security alert.The procedure to trust the certificate depends on the browser: This is normal users have to accept the HTTP/S plugin certificate as a trusted certificate to allow the encryption of communications. Users connecting for the first time to the login page of the Web server will receive a security alert from their browser. Users have the ability to request everything available from their account, until the time allocation expires or the "logout" option from the "Account" menu is selected. Note that the default HTTP port number used for ECaccess is 9080.īy giving an ECMWF user identifier and a passcode, the user is authenticated and routed to a personal page a user context is maintained for the subsequent operations from his browser. No popup, no warning, no nothing - it just doesn't work.Īny suggestions/help would be most welcome!ĮDIT: Just added two wireshark pcap files.Assuming that the Member State ECaccess gateway (see Ecaccess concepts) runs on the server "", users connect to the application by pointing their Web browser at "" and will be redirected to the login page. So the big question: What is the firewall doing during the connection phase? All required ports are open, there are no log entries or anything. The firewall runs in interactive mode (always has), all components of NX NoMachine have been granted full access to LAN and Internet. Obviously I don't want to disable the firewall everytime I need to connect to the Linux computer, which is why I'm trying to find a solution. Enabling the firewall after the NX client has successfull connected doesn't break it either. The interesting thing is: If the firewall is disabled, it connects just fine. The initial connection (encrypted) always goes through port 22 (SSH), afterwards it also uses a port between 5000-5200 if the rest of the traffic is unencrypted, otherwise it just uses port 22. I'm having the same issue with my Laptop, so it's definitely Smart Security. It used to work perfectly for almost two years, but it just stopped one day. Hello everyone, I'm having a tough problem with Smart Security 4, it's firewall component to be precise, and the NX NoMachine Windows client.Ĭan't say exactly which day it happend, but roughly two month ago Smart Security 4 started blocking NX NoMachine whenever I try to connect to a Linux computer across my LAN.
0 kommentar(er)
