I have a client that I do IT work for. They have a 2003 server with active directory and is setup as their DC. The problem they are having that just started over the weekend, is that they are unable to see any of the shares on the server. This started from one computer at first, and then as they started rebooting computers, those computers started having the same problem. Not all computers are having this problem though. There were a couple that I rebooted and renewed their IP leases, and they are still able to find the network shares on this server.
When we browse out to "\server\" instead of getting a listing of the shares on the server, they get a listing for just one folder called "users" and this folder contains nothing. If we try to manually enter the share name in the UNC path it comes back with an error saying it could not be found and to check our spelling. If I browse to \server\ from the server itself, it of course can see all its own shares.
OK, here is where it gets weird, I can browse to the server using just its IP address "\x.x.x.x\" and then we can see all the shares. I know that would look something like the workstations don't have proper DNS server settings in their IP setup, but if I go to a command prompt and ping the server by the server name, it pings it just fine, and returns the proper address. They have other network shares setup to other computers using just the computer names and all those work fine.
I think it has something to do with DNS, but at this point I am not sure what. I have tried flushing the DNS cache on the workstations. I have even tried running winsockfix to try and repair any issues with the tcpip stack. In order to get them back up and running, I am having to remap all their network drives to this server using the ip address of the server.
Any suggestions or solutions would be greatly appreciated.