Post reply

Error connecting to a sql server

  • September 20, 2007 at 6:56 am

    #120494

    I KNOW this has got to be something real stupid.  But...

    I have 2 SQL 2005 servers

    DATA1

    DATA2

    I have a named instance on DATA1 called IMGSQL

    RPC is running, SQL Browser is running, Instance is set up for remote connections.

    I can NOT use SQL Management studio on DATA2 to open the instance on DATA1.

    The weird thing is that I CAN from my laptop which has SQL 2005 workstation components installed.

    I can't connect to ANY of my instances through MGT Studio remotely from DATA2 to DATA1.

    Another weird thing is that I have applications that are able to connect to the instances with no problems.

    Any insight would be helpful.

    Thanks

    Ron

  • September 20, 2007 at 9:29 am

    #734977

    Hi Ron,

    1 Please, go to Configuration Manager on DATA1 and check TCP/IP ports for all your instances in SQL Server 2005 Network Configuration -> TCP/IP Properties -> IP Address tab. Also check what is enabled: Named Pipes or TCP/IP

    2. Next, go to your laptop, connect to DATA1, go to Manegement -> Activity Monitor on DATA1 and in the Net Library field check what protocol is used for your connection from your laptop.

    3. Next, go to DATA2, open the command prompt and type the following. It will help you to determine if appropriate ports are open. If the port is open, then you will see the black window, if the port is closed, you will get an error message.

    telnet DATA1 1433 

    (1433 should be replaced with the real port that your instance is using and you got this number is step 1)

    telnet DATA1 445

    The above line is for Named Pipes.

    telnet DATA1 1434

    The above line is for SQL Browser port

    If the port is not open from DATA2 to DATA1 on both TCP/IP SQL Server Instance port and Named Pipes port, you will not be able to connect. If only port 1434 is closed, you will not be able to connect to instances by browsing, but you can create an entry in Client Network Utility on DATA2 or in SQL Server Client Configuration in Configuration Manager on DATA2 where you UNCHECK Dynamically Determine Port (this is for Client Network Utility)and Explicitly specify your instance port.

    4. Check if you can connect using IP Address of the server, but not the name, this means name resolution issues.

    Do all of above and let us know the result.

    Regards,Yelena Varsha

Viewing 2 posts - 1 through 1 (of 1 total)

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