I have been trying to remotely connect to our repository, which lives on our server in our office.
As required, we have to connect through Cisco AnyConnect VPN so that we can access the internal network. Remote Desktop works just fine. But when I try to open up the Monitor and connect it to our repository, it doesn’t work and give this error, even we already specified the certificate:
We have other machines in the office, and all of them are able to connect just fine. The issue only happens with remote connection through VPN. Not sure if it’s due to our network restriction, or I miss something here. Any tip?
Thank you
Hello @harry1511
The RCS listens for connections on port 4433 RDP works on a different port. It could be that firewall in your network is blocking the connection on port 4433.
What happens if the client machine is not connected to the VPN does it then connect with the RCS?
I think isolating from Deadline to check if the network is a problem should be the next step here.
You can do two tests:
- Try to telnet to the RCS machine from Deadline Client machine, run on cmd:
telnet <hostname/IP of RCS> 4433 << this should show you a blank screen with telnet [IP of the RCS] on the title. You will return to cmd if you hit enter. If you see any errors/timeouts?
- Get nmap: Download the Free Nmap Security Scanner for Linux/Mac/Windows << please check if you IT security allows it, if not then don’t perform this test simply run
tracert [IP of the RCS] from Deadline Client
– Then run nmap -p 4433 ip [IP of RCS]
Hi,
Without VPN, client machine obviously can’t connect with RCS.
With VPN, it is unfortunately the same, hence our problem.
I tried running telnet on 2 client machines: Machine A (outside of network, need VPN, and the one we are having trouble with), Machine B (inside of network)
Machine A:
- With and without VPN:
Connecting To 171.65.166.109...Could not open connection to the host, on port 4433: Connect failed
Machine B: connect instantly as expected
I also ran tracert
Machine A:
- With VPN: it hops only through 4 hops or so, and the rest just timed out. But the 1st hop is not the IP address of the machine we want to connect to.
- Without VPN: it hops more, but same thing
Machine B: only 1 hop and complete (obviously)
Not sure how to proceed from here.
Hello
From the results it seems like you have reproduced the connection issue outside of Deadline. The test also confirms that TLS is not a problem yet because the connection in the first place has failed. You will need to fix the connection between client and RCS.
Can you confirm is the RCS actually running on the machine whose IP you are using to connect Deadline Monitor?
Try using RCS machine’s hostname with fully qualified domain name in your telnet test. e.g. telnet hostname.FQDN 4433
