pzozulka
asked on
User logging in through VPN reports "A Duplicate Name already Exists on the Network" error
Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 7/18/2008
Time: 9:43:36 AM
User: N/A
Computer: WS100213
Description:
Application popup: Windows - System Error : A duplicate name exists on the network.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
This is a message one of users is getting when trying to connect to our VPN. We have made no changes for the past couple months to the VPN or the VPN Server. Users reported no errors in the past few months. The server is sitting on our LAN and I checked all the NAT settings are fine.
What can be causing this? Where do I look for hints? Not too familiar with "Routing and Remote Access" on the VPN server, but I was digging in there and all looks fine.
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 7/18/2008
Time: 9:43:36 AM
User: N/A
Computer: WS100213
Description:
Application popup: Windows - System Error : A duplicate name exists on the network.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
This is a message one of users is getting when trying to connect to our VPN. We have made no changes for the past couple months to the VPN or the VPN Server. Users reported no errors in the past few months. The server is sitting on our LAN and I checked all the NAT settings are fine.
What can be causing this? Where do I look for hints? Not too familiar with "Routing and Remote Access" on the VPN server, but I was digging in there and all looks fine.
Last Comment
Qlemo
For some reason Windows detects the computer's name WS100213 to be already in the network (NetBIOS / NetBT name). Maybe it's right here? You can ping that name while VPN connection is not active to find out.
ASKER
I tried pinging, but all seems normal. "Request timed out". This user continues to get kicked of the VPN and continues to receive same error messages that "Host already on network".
If you can preclude duplicate IP addresses, it could be a problem with DNS / WINS registering of the client. When you ping the name while VPN off, the name can be resolved anyway - that is strange, it should be deregistered after disconnect.
Compare the assigned IP (which client sees when he's connected) with that you get from ping.
Additionally you could call a nbtstat -c and nbtstat -n and nbtstat -r on any computer to get all known active names.
Compare the assigned IP (which client sees when he's connected) with that you get from ping.
Additionally you could call a nbtstat -c and nbtstat -n and nbtstat -r on any computer to get all known active names.
ASKER
The remote notebook is connected via VPN right now. I looked at the VPN settings, and machines get a static IP address in the range between (10.81.65.10-10.81.65.250 NETMASK: 255.255.255.0)
Our DHCP pool is set to only 10.81.32.10-10.81.32.250, and DNS also reflects that.
I searched for WS100213 or 10.81.65.19 (ip ws100213), in DHCP & DNS. No records set anywhere.
Keeping that in mind, WS100213 can pint us, so then I tried pinging WS100213, and here is the response:
C:\Program Files\Windows Resource Kits\Tools>ping ws100213
Pinging ws100213.bcr.local [10.81.65.19] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.81.65.19:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
Our DHCP pool is set to only 10.81.32.10-10.81.32.250, and DNS also reflects that.
I searched for WS100213 or 10.81.65.19 (ip ws100213), in DHCP & DNS. No records set anywhere.
Keeping that in mind, WS100213 can pint us, so then I tried pinging WS100213, and here is the response:
C:\Program Files\Windows Resource Kits\Tools>ping ws100213
Pinging ws100213.bcr.local [10.81.65.19] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 10.81.65.19:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
ASKER CERTIFIED SOLUTION
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Windows Server 2003
Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).
129K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
TRUSTED BY
