Why the delay after connecting to VPN?

  • Thread starter Thread starter Michael A. Covington
  • Start date Start date
M

Michael A. Covington

We have a VPN hosted by a Windows 2003 (formerly 2000) server; the clients
are Windows XP.

It works fine except for one minor inconvenience.

After connecting to the VPN, it's usually 30 to 120 seconds before I can
browse the network or access paths such as \\servername\sharename (where
servername is on the VPN).

During that 30- to 90-second interval, it's as if the VPN weren't connected
yet, even though it is.

I presume this has something to do with network browsing. Is there anything
I can do to eliminate the delay?


Thanks!
 
Make sure you install/enable the DHCP Relay Agent on the Windows 2003
RRAS server to get your WINS/DNS server addresses passed to your VPN
clients... This will eliminate the network broadcast resolution
delay.

Jeffrey Randow (Windows Networking & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
 
That solved the problem on my end...

How different are the networks on the two ends? If they are in the
same general address range (i.e., 192.168.2.x), then this could also
be a problem...

Jeffrey Randow (Windows Networking & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
 
Jeffrey Randow (MVP) said:
That solved the problem on my end...
Click to expand...

And in fact it may have helped somewhat on my end, but not completely.
How different are the networks on the two ends? If they are in the
same general address range (i.e., 192.168.2.x), then this could also
be a problem...
Click to expand...

It was quite a problem during a brief period a while back when I tried
setting it up that way :)

The VPN now has its own range of assigned addresses to give out, completely
different from what anyone's home DHCP server might be giving out.
 
Back
Top