Some time ago our server crashed (ironically just a couple of days after I was promoted to Network Manager). Up until that time this department didn’t have ANY IT personnel. So guess what? Nobody was ever backing up the server.
I pulled a machine they had bought to replace the server but never implemented out and set it up with Windows Server 2003. For a short while, life was good again.
Then I discovered that within the network, one office had their own Win2K File Server. This Win2K File Server was set up to received an address via DHCP from the server I had replaced. Still, everything seemed to work normally. Everyone who was in that office still could access their file server.
The problem started when I tried to add a new employee in that office as a member of their Win2K Server’s domain. It worked ok…for a single day. After that she can’t access the Win2K server. The only way to get her back on is to unjoin her from the domain and then rejoin here. This solution though only lasts for one day.
I believe it has something to do with me replacing the old Win2K Server that crashed with the Win2K3 Server, but I can’t put my finger on what’s going on here. Any insight anyone can offer me would be greatly appreciated.
BTW, the Win2K3 Server is DHCP, DNS, WINS, and file serving.