"Error 53" with local LAN machines after VPN session on server
Posted
by
tim11g
on Server Fault
See other posts from Server Fault
or by tim11g
Published on 2012-03-25T20:44:52Z
Indexed on
2012/03/25
23:32 UTC
Read the original article
Hit count: 243
I have a Windows 2000 server with a Windows 7 client that occasionally gets "error 53" when accessing the server by name (net view \\server). It still works by IP address (net view \\192.168.0.1).
The server's primary IP address (as shown in "routing and remote access" as "Gigabit Ethernet" is 192.168.0.1. There is also a secondary IP address shown as "Internal" which is 192.168.0.50
The server also supports VPN. When a VPN user connects, it gets an address in the range of 192.168.0.51 to .59.
Normally (when there is no error), when the local LAN client runs "ping server", it resolves to 192.168.0.1. When the Error 53 problem happens, "ping server" resolves to 192.168.0.50.
This problem seems to be related to when a user connects or has recently connected to the server VPN.
Is there some connection between the VPN services on the server and the DNS services on the server that could cause a local LAN client to become confused about which IP address to use for the server? Or is there a misconfiguration in the VPN or DNS?
© Server Fault or respective owner