Slow getting "online" and synchronizing through VPN connection.

From: Hans Kristiansen (anonymous_at_discussions.microsoft.com)
Date: 05/13/04


Date: Thu, 13 May 2004 06:52:11 -0700

The last time I posted this it did not show up, so I'll
try again:

We are running a Windows 2003 Server (Standard) with
approx. 30 internal WinXP clients and five external WinXP
clients. On the server (dk-server1) we have a share
(share1) mapped out to all clients as a J: drive, and on
this share there are three folders: "Ekstern", "Intern",
and "Standards". All clients (external as well as
internal) have been entered into the domain (dk-
domain.local).

For the external clients we have made the "Ekstern"
folder on the J: drive available offline. When we
initially set this up we had the external machines
physically connected to the internal network, at which
point we synchronized the "Ekstern" folder. Later we
tested the configuration that the external machines would
use forth worth; namely an ADSL connection to the
Internet through which they establish a software Cisco
Systems VPN Client connection through which they
synchronize. This all worked fine, also when the external
machines arrived at their external locations.

A few days later, however (it may have been less, we're
not sure), problems arose with synchronizing. The problem
mainly manifests itself in that the machines take an
inordinate amount of time to figure out that they are, in
fact, "online" with the server once the VPN connection
has been established.

We previously had an identical setup running up against
an NT4 server. From this experience we found out that if
the clients open the VPN connection, then start Windows
Explorer and go to the J: drive, if they only see
the "Ekstern" folder then Windows does not yet realize
that it is online through the VPN connection. If they
then right-clicked on the "Ekstern" folder and
selected "Synchronize", the other two folders (which are
not available offline) would eventually pop up (after at
the most three tries or 30 seconds) and they could then
actually synchronize "Ekstern". The problem now is that
the other two folders take from 15 to 45 minutes to show
up, which is unacceptable. What is seems like we really
need is something that works like the "Work offline" menu
option available in Internet Explorer and MS Outlook:
Remove the checkmark, and Windows figures out that you're
online.

Restarting the Windows 2003 server does help, but only
for a short while, perhaps just a few hours: Initially
the clients get "online" almost immediately (as it should
be) but later it's back to it taking many minutes for the
WinXP clients to realize they are online. We are not
aware of anything that changes on the server (programs
loading, etc.) within this time.

We've implemented the hotfix mentioned in Knowledge Base
article no. 829074, to no avail.

If we connect an external machine directly to the
internal network there are no problems; it sees that it's
online straight away and syncs as it should.

Also, but this is not certain at this time, it looks like
once it finally gets started, the synchronizing is about
four times slower than it was up against the NT4 Server,
and we also get intermittent errors that the share is not
available while synchronizing.

Any help would be greatly appreciated.



Relevant Pages

  • Re: been hit by hacker, servudaemon installed
    ... Every single one of the web servers and internet server operating systems ... Windows, Apache, you name it. ... commands they entered in your IIS server logs. ...
    (microsoft.public.inetserver.iis.security)
  • Re: ISA Server Problems, please help
    ... > clients are unaffected, is it secureNAT clients which are affected? ... then checked Send the original host header to the publishing server instead ... > provided unrestricted internet access. ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA Server Problems, please help
    ... Based on the rules you have listed, SecureNAT clients should only be allowed ... The All access rule for SBS Internet Users ... Web Proxy and/or Firewall Client ... > header to the publishing server instead of the actual one. ...
    (microsoft.public.windows.server.sbs)
  • Re: been hit by hacker, servudaemon installed
    ... >Every single one of the web servers and internet server ... >Windows, Apache, you name it. ... >commands they entered in your IIS server logs. ...
    (microsoft.public.inetserver.iis.security)
  • Re: After installing SBS 2003 two IE 6.0.29 SP2 clients that cannot to companyweb
    ... Mozilla, and other clients can access the http://comanyweb, the SBS server ... Reset the Internet Explorer Settings to Default. ... DHCP was turned off in SBS 2003. ...
    (microsoft.public.windows.server.sbs)