We have one project group with a different subnet and a different VLAN. All the machines in the same project group are able to ping a remote machine, which is in U.S., through our VPN tunnel. Latency has been found to be normal, but when we add a new machine on the same subnet, the ping response is showing high latency. We have connected the one machine from the same subnet (which is showing normal latency) and given it a new IP address that shows high latency. We have checked the vulnerabilities, sniffer analysis and ethereal analysis on the new machine, which is showing high latency. It was not showing any other traffic other than ICMP (because we are pinging it).
This problem only happens when we add new machines with new IP addresses on the same subnet. We are using Windows 2000 Professional and Windows XP. Can you please help us?
QUESTION POSED ON: 06 OCT 2005
QUESTION ANSWERED BY: Howard Plumley, Jr.
At a machine that is operating normally, go to the command prompt and type
'nbtstat –c (lowercase is important). You will find the system attached to through the VPN is listed in your NetBIOS Table (routing). The new machines do not have that entry and, because XP (Pro) deprecates the NBT cache, are slow to acquire it. Add the route (path) LMHosts, and it should resolve the differences. This DOES require an update of the table or a restart of the system.
|
|
|
