Post reply

Trying to connect to a Database

  • February 3, 2011 at 12:00 pm

    #388776

    Hi,

    I was not sure if this is the right place to put this question but here goes!

    We have two servers running Windows Server 2003 which have two separate instances of SQL Server 2000 (I know I know). Everything has always worked fine.

    Then we started to update the client PC's to Windows 7 (from XP).

    Now on the test PC we can connect to the database on one of the servers but not the database on the other even though they are the same version of SQL Server and are set up the same.

    I have switched off the firewall, can ping the server but just cannot connect to the SQL Server database (I get the unable to connect error - Msg 17, Level 16, State 1 - Microsoft ODBC SQL Server Driver DBNETLIB SQL Server does not exist or access denied).

    I am stumped (largely because I am new to SQL server but very keen to learn). It cant be the ODBC driver as I can connnect to the other database and the user is OK as they could connect on an XP system.

    Any ideas would be very warmly received

    Thanks

    P

  • February 3, 2011 at 2:23 pm

    #1282165

    This might be a good place to start

    http://support.microsoft.com/kb/827422

    __________________________
    Allzu viel ist ungesund...

  • February 7, 2011 at 11:03 am

    #1283318

    Hi,

    Thanks for your reply.

    The article was very interesting and useful

    I have got a little confused though. In the Client Network Utility on the General Tab for the Network Protocol Default Value Setup the Default Port is 1433.

    There are two servers being connected to. The first has a Default Port in Server Network Utility of 1433 the other of 1355.

    If the default port on the Client is 1433 how can I be connecting to both using Query Analyser???

    1) If you use a default port always dynamic i.e. does it try to resolve it on each connection.

    2) Should we set up named instances with specific ports on each server and on the client set up an alias to connect to these specific ports.

    3) Would this make all connection more stable

    4) If the same dll is used for two network libraries i.e DBNETLIB used for TCP/IP and NWLinkIPX/SPX would this cause any problems

    Thanks for your help.......it is always appreciated

    P

  • February 7, 2011 at 8:34 pm

    #1283515

    When you have two instances on the same system one will be the default and other will be the Named instance unless you specifify both to be Named Instance.

    Default instance always listen to 1433 port and Named instance will listen to other port which is available in your case it is 1355. By making the port to static for named instance will easy your work.

    You can create an alias in the Client network utility for Named instance with the port information . You can use the alias name to connect either from GUI or QA.

    "More Green More Oxygen !! Plant a tree today"

  • February 8, 2011 at 6:52 am

    #1283645

    Hello,

    But on each server we only have one instance.

    The odd thing is the instance on one server has a default port of 1355.

    The instances on the other two servers (again, there is only one instance on each server) have default ports of 1433.

    On the client PC's the default port in Client Network Utility is 1433

    I would expect not to be able to connect to the first server and the instance on it in query analyser but I can.

    I thought it might be using the secondary protocal (named pipes) so I disabled it....and I could still connect!!!

    Then I disabled TCP/IP so there were no enabled protocols. I got a message that "Super Socket Net Library will use the default protocol" (not sure what that meant) but I could still connect.

    This seems strange as there seems to be no way I can not connect to the server and the database on it. This might not seem like a problem (!) but occassionally I get a "Unable to Connect" error and have to restart the server (the one with the first instance on it - 1355 default port) to clear it, so I wanted to understand and troubleshoot the connections in order to ensure this doesnt happen again

    But it seems no matter what I do the client always connects to the servers and the individual instances on them so I cant re-create the problem!!

    Any help!

    Thanks

    P

  • February 18, 2011 at 11:22 am

    #1288967

    Any ideas anyone????

    Im completely stumped!!

    Thanks

    P

Viewing 6 posts - 1 through 5 (of 5 total)

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