SQLState: 'HYT00' error "Timeout Expired", relating to Primary DNS

[knightwork]

Recently we had our secondary DNS server crash, we decided to turn the server off, when we did that there were a number of applications that quit working. Our quick fix was to remove the DNS entry from the client PCs, but that isn't a good solution.

After it calmed down I started trying to determine what the problem was, I am able to recreate the problem by putting a bogus IP address as my primary DNS server, then I attempt to setup an ODBC 'System DSN' connection using the 'SQL Server' driver. We use Windows NT authentication, and with the checkbox for obtaining the default settings from the server, I found that on 5 of our 14 servers I encounter the following error.

--------------------------------------------------
Microsoft SQL Server Login

Connection failed:
SQLState: 'HYT00'
SQL Server Error: 0
[Microsoft][ODBC SQL Server Driver]Timeout expired
--------------------------------------------------

The way I understand DNS, on Windows 2000 if the server doesn't reply it is supposed to go to the secondary DNS server, until the computer is either rebooted or the secondary no longer replies. If DNS fails entirely then it goes to WINS, and so on.

I'm at a loss for where to go with this issue, I have seen similar issues described, and some people suggest adding the addresses to the hosts file, but I'm looking for a fix that either doesn't need to be deployed to 1000 desktops or that doesn't have to change when server addresses change.

 

[LMRollins]

I'm having the same problem. Have you found a solution?

 

[ahollister]

having simailer problem but with out dns issues, can ping to netbios name of server, also we are using the sql authentication , at suggestion of application vendor going to format and clean install system, will post results...

ahollister

 

[LMRollins]

I finally got my problem fixed. My client connection was using named pipes instead of TCP/IP. You have to be using TCP/IP in order to make an ODBC connection to SQL Server.

 

[knightwork]

All of our connections are already setup as TCP/IP, we don't use named pipes. But now we are not having the problem anymore. If I determine what happened that made it start working I'll post it.