Link to home
Create AccountLog in
Avatar of tucktech
tucktech

asked on

How to troubleshoot SQL network resolution

Hello Experts,

I have a network that has a Win Server 2008r2 with SQL 2008r2 AND a Win Server 2008r2 for a DC.  The environment has worked well until this morning.

There is an application that connects to the database and for some reason some workstations cannot find the database while others can.  Then the ones that cannot will work and then will have a problem again.  I looked at the server and I don't see any bad events.

From the workstation, I can ping the SQL server, perform an NSLOOKUP to the server and can sometimes telnet (telnet servername 1433) to the server.

What can I do to pin point the problem?

The clients are win xp and win7
ASKER CERTIFIED SOLUTION
Avatar of Megan Brooks
Megan Brooks
Flag of United States of America image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of tucktech
tucktech

ASKER

I found the problem.  I assumed I would be able to ping the server name.  I could not, the ip address was not ping-able.   I have two nic cards in the server and I had to disable the NIC card that was the secondary IP address.  Using Windows 2008r2 so I don't see a NIC teaming option.
Giving all of you credit because you started down the correct path of debugging...  I also ran across this web page that I found helpful..

http://social.technet.microsoft.com/wiki/contents/articles/2102.how-to-troubleshoot-connecting-to-the-sql-server-database-engine.aspx
This helped...
http://social.technet.microsoft.com/wiki/contents/articles/2102.how-to-troubleshoot-connecting-to-the-sql-server-database-engine.aspx

Thanks for your infomraiton and fundamental question, it always go back to fundamentals!