Network issue involving database Server

Question

Network issue involving database Server

Barkingdog

SSCoach

Points: 18670
More actions
June 22, 2005 at 2:00 pm

#102606

We have a production sql 2K server running on Windows 2000 Server,SP4. All IP addresses (i.e. base machine config, DNS, etc.) are fixed, Everything was working happily until about 11am this morning.
Then we found that users running Windows 2000 Pro couldn't connect to the database server (as in "ping" <server> timed out) but at the same time Windows XP users could connect to the server and run their programs normally! We rebooted the server but that didn't resolve the problem, either. We were left scratching our heads. Fortunately, about 10 or 15 minutes later things returned to normal. I have no clue was happened. I checked the server event logs there was no sign of any trouble whatsoever.
Any thoughts on this one much appreciated.
TIA,

Bill

Viewing 4 posts - 1 through 3 (of 3 total)

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

Russell Shilling SSCarpal Tunnel Points: 4399 More actions · Answer 1

I'd suggest waiting 10-15 minutes.

The Win2K users could be having trouble authenticating to the network, and are using "cached" logons. I don't know of a way to check this, but the best option is to look in the event logs for failed logons, or other anomolies.

So long, and thanks for all the fish,

Russell Shilling, MCDBA, MCSA 2K3, MCSE 2K3

David A. Long SSCrazy Eights Points: 8421 More actions · Answer 2

One thing to check is the Windows 2000 MDAC version, XP service packs update MDAC, and since Windows 2000 doesn't you may have to deploy a MDAC update.

Another that may just be "old school", is that SQL Server service packs no longer update the ODBC and OLE DB procedure level to that of the latest MDAC. Why I do not know, or even if this is still required. So one of my normal tasks after rebooting the SQL Server after service pack and verification that no events are generated, is to run the instcat.sql from the C:\Program Files\Microsoft SQL Server\MSSQL\Install folder.

Andy

sswords SSCrazy Eights Points: 8207 More actions · Answer 3

I don't know. If they couldn't even ping the server, then to me that points to a network or connectivity issue. Are all of the workstations on the same lan segment? If it were me, I'd be asking the network admins if there was either a switch, DNS server or some other connection issue that they saw during this time. You might get some clues as to whether or not this was the case if you check both the server and Windows 2000 client event logs. Hope this helps.

My hovercraft is full of eels.