About once every three weeks, remote users find that they cannot connect to our WinNT file server (\\FILESERV). The users dial in to their ISP, connect to our network through Win2k VPN, and find that their network drives are not mapped or accessible. They still have access to all other resources as long as it's not on FILESERV.
Remotely, I can ping the dns of all servers except FILESERV, but I can ping FILESERV's IP address. A tracert to the IP will still list the name "FILESERV".
Once I reboot the file server, everything is fine. Is there any way I can fix this without the reboot? We have a firewall and a NAT router, but those configurations have not changed at all. What specifically gets reset on the file server that fixes the dns resolution problem?
Remotely, I can ping the dns of all servers except FILESERV, but I can ping FILESERV's IP address. A tracert to the IP will still list the name "FILESERV".
Once I reboot the file server, everything is fine. Is there any way I can fix this without the reboot? We have a firewall and a NAT router, but those configurations have not changed at all. What specifically gets reset on the file server that fixes the dns resolution problem?