Post reply

cant connect to named instance

  • June 16, 2004 at 9:26 am

    #65203

    I have a named instance of SQL 2000 on windows 2003 server that I need to connect to from a different facility on a windows 2000 machine. The connection is through a SQL account. It is a different domain but the netowk guys tell me there is a wide open connection between sites.  I can ping the server successfully although only by IPaddress and not by DNS name. I can connect through enterprise manager to a default instance of sql 2000 but when I try to connect to a named instance (111.22.33.44\instance) it tells me the server is unavailable.  I know the server is up and I can connect to the instance when at the home site.  I have upgraded the client tools to SP3 as well as the MDAC but still no luck.

     

    Any suggestions would be great.

  • June 16, 2004 at 10:56 am

    #510686

    What happens if you connect using just 111.22.33.44?

    I have two instances on my server. I set my ODBC connection to the IP only (no instance). Permissions on SQL Server do the rest. When I do this with Enterprise Manger, I make the connect to the IP address, then it gives me the choice of all the instances that I have access to.

    -SQLBill

  • June 16, 2004 at 11:48 am

    #510704

    I am not using ODBC for the connection.  I am using native SQL drivers and I have an alias set, using the Client Network Utility, that points to 111.22.33.44\instance.  If I dont include the instance it looks for the default instance.

  • June 16, 2004 at 12:01 pm

    #510706

    How about this way,

    First, get the port number that instance is using. If you don't know, you can get into the box and open the "SQL Server Network Utility" and on Enabled protocals, click the TCP/IP and check the properties.

    Second, from "Client Netowork Utility", create an Alias by using TCP/IP with that port number. You can name anything you want.

    Third, use that to register from EM or SQL Analyzer.

    Hope that works.

  • June 16, 2004 at 12:05 pm

    #510708

    The reason why you cannot ping the host name and ping the I.P. is becuase it is in  a different domain. Your domain does not recognize the host name and hence that is not an issue. Can you try to create a telnet session on the port on which the named instance listens on the server 111.xx.xx.xx ?

  • June 16, 2004 at 12:45 pm

    #510713

    Sa24 is more than likely right on with your issue, you can see the server through Ping as Ping does not require domain access nor DNS resolution, and because your logon credentials will not register on the other domain, the server is not granting you access. You should have your “network guys” either setup your credentials correctly for cross domain authentication, or see if they will setup a remote for your access.

    Either way should get you in.

  • June 16, 2004 at 1:00 pm

    #510717

    I asked like above because the golfer wrote that "I can connect through enterprise manager to a default instance of sql 2000". That means at least network either already opened the right port or only those ports that the default instance is listening to. (i.e. TCP port 1433 and UDP 1434 for default but you might change for your system).

    So before you go and ask network guy to do the magic, first find out what ports that the instance is running and try it and if still doesn't work then ask network dude to open the port for you.

    my 2 cents

  • June 16, 2004 at 1:08 pm

    #510718

    The other thing is to make sure that 1434 is open, if it's blocked you'll not be able to find the instance.


    Shamless self promotion - read my blog http://sirsql.net

  • June 16, 2004 at 1:19 pm

    #510719

    Good Point! Sorry for any misdirection. I was thinking the other way toward DNS because of the named instance possibly not being resolved, since he could connect to the default instance, I was thinking the port should be open. Although as you have stated he could have the instance in question set to a different port, which could be the more likely cause.

    Sorry again for any misdirection.  

  • June 17, 2004 at 9:06 am

    #510869

    Thanks guys.  You have saved me a lot of pain.

    I was attempting to connect to 111.22.33.44\instancename and had no luck.

    iLoveSQL suggested I get the port number for the instance on the server and use that in the connection string.  Voila, it worked.  I now have an alias set to 111.22.33.44,1234.

     

    Thanks very much to all that helped.  This is by far the best site for advice.

Viewing 10 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic. Login to reply