 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
SQL Server Forum / Programming / SQL / December 2008At my Wits end with this one
Hi, I hope someone may be able to offer some suggestions here The scenario I have installed two instances of SQL Server 2008 64bit on a 2008 server. The default instance and one called MSSMLBIZ. The default instance is configured to listen on port 1433 and the named instance is configured to listen on 5356. In the Windows firewall I have configured both ports 1433 and 5356 to permit traffic (TCP & UDP) from within my subnet (see attachment). I have checked that there are no other rules for port 5356 that might override my rule for SQL If I try to connect to the default instance I succeed. If I try to connect to the named instance I fail. However if I turn off Windows Firewall completely on the 2008 server I can connect. If anyone can offer advice on this it would be most appreciated Regards, Nigel Ainscoe. Full error message below. I have of course taken all the steps recommended by the web link in the message (which are for SQL 2005 despite both the client and server being 2008) TITLE: Connect to Server ------------------------------ Cannot connect to JDUK006\MSSMLBIZ. ------------------------------ ADDITIONAL INFORMATION: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1) For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer& EvtID=-1&LinkId=20476 Try connecting via <ipaddress>,<portnumber> instead of instance name. xxx.xxx.xxx.xxx,9999 > Hi, I hope someone may be able to offer some suggestions here > [quoted text clipped - 40 lines] > For help, click: > http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer& EvtID=-1&LinkId=20476 Yeah, I was about to say the same thing: http://www.connectionstrings.com/sql-server-2005 Search for "1433" and you'll find the most anal of the connection strings. IP Address and Port Number as Eric wrote. > Try connecting via <ipaddress>,<portnumber> instead of instance name. > xxx.xxx.xxx.xxx,9999 [quoted text clipped - 51 lines] >> For help, click: >> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer& EvtID=-1&LinkId=20476 PS You can also look at this key in the registry to see if anything weird is going on: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo I wouldn't change anything manually, but it will show you how Sql Server stores some of the info. If there isn't anything at that key, then go to: COntrol Panel / Admin / ODBC / System DSN (tab) Add a temporary ODBC source. Use Sql Server, and put parameters in. Make sure you click "Client Configuration" button and put in a IP address (under "Server Name" and port number (uncheck the "dynamic port" thing). The ODBC thing is a cheap way to experiment with how you're connecting to the database. If you add a ODBC connection, you can delete it later. But if you add something, it should show up in the registry under the above key. Just some tidbits from years past. > Yeah, I was about to say the same thing: > [quoted text clipped - 62 lines] >>> For help, click: >>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer& EvtID=-1&LinkId=20476 Now that is interesting Eric - and thanks to you too Sloan It connected straight away, which suggests to me that it is some sort of DNSy type of name resolution problem. I will look at the registry settings that Sloan mentioned and see if that gives me any clues. I'll let you know. Regards, Nigel Ainscoe > Try connecting via <ipaddress>,<portnumber> instead of instance name. > xxx.xxx.xxx.xxx,9999 [quoted text clipped - 51 lines] >> For help, click: >> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer& EvtID=-1&LinkId=20476 > Now that is interesting Eric - and thanks to you too Sloan > [quoted text clipped - 3 lines] > > I'll let you know. To be able to translate the instance name to a port, you need to have contact with the SQL Brower Service. This service must be running, and you must have UDP port 1434 open.  SignatureErland Sommarskog, SQL Server MVP, esquel@sommarskog.se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx Erland, yo da maan (as a stereotypical American cousin might say), connection by name is working a treat. You learn something new every day. Not one of the online articles I have googled has mentioned that the browser service listens on 1434 - or maybe I just didn't see it.. :-( Thanks a lot Nigel Ainscoe >> Now that is interesting Eric - and thanks to you too Sloan >> [quoted text clipped - 8 lines] > contact with the SQL Brower Service. This service must be running, and > you must have UDP port 1434 open. |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2010 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.