Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)
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?
Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)
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.
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....
On Tue, 29 Jun 2004 10:51:46 -0400, "Michael A. Covington"
<look@www.covingtoninnovations.com.for.address> wrote:
>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!
>
>
>
>
Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)
Will do. Is it simple to do this? Anything tricky about it?
"Jeffrey Randow (MVP)" <jeffreyr-support@remotenetworktechnology.com> wrote
in message news:9564e0tqb36um3lk968ugolitt9mpumf6f@4ax.com...
> 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)
> jeffreyr-support@remotenetworktechnology.com
>
> 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 >
> On Tue, 29 Jun 2004 10:51:46 -0400, "Michael A. Covington"
> <look@www.covingtoninnovations.com.for.address> wrote:
>
> >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!
> >
> >
> >
> >
>
DHCP Relay Agent was already running on "Internal" but did not know the IP
address of our campus DHCP server. I told it...
This did not improve the performance of the VPN as far as I can tell.
Any other ideas?
"Jeffrey Randow (MVP)" <jeffreyr-support@remotenetworktechnology.com> wrote
in message news:9564e0tqb36um3lk968ugolitt9mpumf6f@4ax.com...
> 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)
> jeffreyr-support@remotenetworktechnology.com
>
> 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 >
> On Tue, 29 Jun 2004 10:51:46 -0400, "Michael A. Covington"
> <look@www.covingtoninnovations.com.for.address> wrote:
>
> >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!
> >
> >
> >
> >
>
Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)
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...
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....
On Tue, 29 Jun 2004 22:28:48 -0400, "Michael A. Covington"
<look@www.covingtoninnovations.com.for.address> wrote:
>I assume you mean the configuration procedure described here:
>
>http://support.microsoft.com/default.aspx?kbid=232703
>
>DHCP Relay Agent was already running on "Internal" but did not know the IP
>address of our campus DHCP server. I told it...
>
>This did not improve the performance of the VPN as far as I can tell.
>
>Any other ideas?
>
>
>
>"Jeffrey Randow (MVP)" <jeffreyr-support@remotenetworktechnology.com> wrote
>in message news:9564e0tqb36um3lk968ugolitt9mpumf6f@4ax.com...
>> 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)
>> jeffreyr-support@remotenetworktechnology.com
>>
>> 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 >>
>> On Tue, 29 Jun 2004 10:51:46 -0400, "Michael A. Covington"
>> <look@www.covingtoninnovations.com.for.address> wrote:
>>
>> >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!
>> >
>> >
>> >
>> >
>>
>
Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)
"Jeffrey Randow (MVP)" <jeffreyr-support@remotenetworktechnology.com> wrote
in message news:jdt6e0pio23fj1ka3pbptued8nrabr3tj7@4ax.com...
> That solved the problem on my end...
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...
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.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.