November 1, 2012 at 6:43 am
Here's a strange one.
A server in a different data center than where I am based listens on 1633 instead of 1433. I cannot connect to the server with SSMS. I specify the server by either "name:1633" or "IP Address:1633", and neither is successful from my location.
The server is a two-node cluster and has SQL Browser service running.
I can connect with RDP, ping, and Telnet to "servername 1633" from my location.
I can connect with SSMS to the server from another server in the same data center by just using the name of the SQL cluster, no port specification.
Since I can telnet to the server from my location I know that the routing is right and FW port is open.
The only thing I can think of is maybe the server cannot talk back to my client port from its location to mine, but I am not sure of the blank screen I get from telnet proves or disproves that.
Any ideas?
Thanks,
Chris
Learning something new on every visit to SSC. Hoping to pass it on to someone else.
November 1, 2012 at 7:29 am
instead of the colon (:) try a comma before the port number.
November 1, 2012 at 11:09 am
That worked. Thanks. Wish I could have found that in BOL.
Thanks,
Chris
Learning something new on every visit to SSC. Hoping to pass it on to someone else.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply