July 2, 2007 at 1:54 pm
I've got a SQL 2005 Enterprise (64-bit) server running on WIN2K3 64-bit. The server is set up for Remote Logins on both TCP/IP and Named Pipes and the SQL Browser is running. I have a Named Instance running against port 1433. However, I can not get SSMS to register the server. I have checked EVERYTHING. Any suggestions?
July 2, 2007 at 1:56 pm
can you change the "named" instance port ?
1433 should be used for the "default" instance.
* Noel
July 2, 2007 at 3:07 pm
Unfortunately no... the SysAdmin-types don't want to change the port number.
July 3, 2007 at 8:00 am
Just a crazy throught.. can you ping the servername? ie the "Myserver" part of Myserver\SQLinstance ? if so can you telnet to the IP on port 1433? If you cannot ping the servername the DNS isn't set up.. or perhaps there is an alias issue. Can you register with IPAddress\SQLInstance?
July 3, 2007 at 10:15 am
Yeah, I could ping the server and even ping to resolve the DNS. It just wasn't passing the port. For some reason... this goofy thing did not set the port in the Configuration Manager Tool. It had 1433 registered for the Native Client protocols, but failed to register the port for the Network Configuration - Protocols for [MyServer\Instance]. I went into the advanced tab of the TCP/IP protocol and set the port for the TCP connection associated with the Static IP. I was then able to register the server remotely (after stopping and restarting the DE Service and Browser Service).
Thanks for the Help Rich and Noel
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply