Friday, December 05, 2008

Event ID 529

One of our employees here was unable to map a network drive to our file server. When they would try to connect the connection was successful through our firewall, however, the actual Windows Server 2003 R2 system would record event ID 529 in the Security log stating that the user's username or password were not correct, which they were. In the end, it turned out that the name they were using for the server was a synonym of what the actual server name is, meaning that the server name that the user was using was actually different from what the actual server name is on the system. So for example, the user referenced the server as "webserver" but the actual name on the system was "fileserver". To work around this I modified the users HOSTS file, inserted a new line with the actual name of the system, but using the external IP address (on the firewall) rather then the internal IP address of the system itself. I then did a NBTSTAT -R and IPCONFIG /FLUSHDNS and was able to successfully map the network drive.

No comments: