04-14-2010 05:31 AM - edited 04-14-2010 05:43 AM
I followed this thread.
You said that you are not able to connect to port 1706 using telnet.
I assume you did it as follows:
telnet servername 1706
Usually you should be able to connect to the server.
If this is not working the client firewall seems to be on or perhaps blocks outgoing access.
Are the client and the server in the same subnet?
Can you ping the server?
04-14-2010 06:15 AM - edited 04-14-2010 06:21 AM
Yes I can ping by both servername and IP. Both are on the same subnet/domain.
I was not able to telnet to the new SLX server with current firewall settings. After adding port 1706 UPD and TCP to the Windows Firewall excepction list I was able to telnet to it.
I was able to to telnet to our current SLX server but the response was a bunch of werid characters...
Through even with the port now open the connection from the client to the server still fails.
04-14-2010 06:41 AM
Mike Spragg has asked me to add the below on his behalf as he's out on the road
"The bunch of weird chars is correct - the server is active. On new server there must be a firewall/AV in the way and preventing it"
04-14-2010 06:47 AM - edited 04-14-2010 06:49 AM
Okay. I disabled the Windows Firewall completly.
I still am unable to connect/see the SLX server from the client. Same "Failed to connect to SLX Server..."
Anything else I can check/change?
04-14-2010 07:14 AM - edited 04-14-2010 07:22 AM
We opened the the follwoing ports on a customer's w2k8 server:
the sql port, if sql is installed on the same server
1706 (TCP and UDP
Hope this helps!
04-15-2010 09:08 AM
Thanks for all your help.
Basically a re install of SLX fixed this issue. It should be noted I installed SLX this time with the Firewall off. Perhaps Windows Firewall blocked something during the installation.
Thanks once again.