Re: Remote office logon script - Long Delay

I belive the AD site and subnets are configured correctly. Nothing is showing
in the logs and replication is occuring regularly and without error.

DHCP is working correctly and seems to be keeping to it's assigned subnet
for each location.

I do not have WINS configured for the remote site, only the primary
location. I thought most apps aren't using WINS for anything much anymore.
Should this be configured?

Intersite messaging is set to Auto, I think I had to do this initially to
get the replication to work.

I don't push apps out to the clients and other than GPOs I don't do much but
serve files to the clients and mail. So setup.exe may not be needed?


--
Sean


"kj [SBS MVP]" wrote:

Sean wrote:
My first thought was DNs, but no erros or problems browsing/accessing
netwoprk resources. Users are on the systems at the moment, so I'll
post an IPConfig log as soon as I can.

This remote server was built using connect computer script, and is a
GC/AD server with DNS and DHCP for it's area.


Ah, that makes a *big* difference, or at least it can.

Is the remote server (DC) setup as a seperate AD site with the subnets
properly defined?

Is your intersite replication working properly? (you need to change the
Intersite Messagind service on the SBS server to "Startup: Automatic")

Do you have a second WINS server and if so, is it configured for push/pull
replication to the SBS one?

With a second DHCP server and scope, are the remote workstation getting DNS
only from the local server or is the SBS server set as #2?

Setup.exe isn't a large file but it may be generating a fair amount of
network traffic in it's execution. If everything else is configured and
working properly and you don't plan on the SBS server distributing
applications (from the SBS server) you might want to configure the login
script not to do this for the remote site.


Copying large files can be a real burden to the network, but no more
than I would expect for the bandwidth that is available.

Is there anything that can be done for setup.exe to improve it's
performance? Copy the folder?



Sean wrote:
I am running SBS 2003 (not premium) and have a remote server (win
2003) at a remote office. The offices are link through two Sonicwall
devices through a VPN tunnel. The remote office connection is a 640K
DSL and is slow, but works for the 3 employees.

I am experiencing an extremely long delay running the logon script
file. Seems the setup.exe file may be the culprit. My script has
only two lines but takes almopst 10 minutes to complete.

\\SERVER\Clients\Setup\setup.exe /s PHXSERVER
\\SERVER\ezaudit\ezstart /auto

I can watch the scripts progress and the setup line is the long
delay. No error messages are displayed, just seems to take too long.


Any guidance on how to improve performance? My local systems are
done in 10-15 seconds.

Thanks in advance.

Well my first take would be that the remotes might be having trouble;

a) resolving "PHXSERVER" back to the SBS server.
-or-
b) the clientsetup program "setup.exe" is passing suffecient data
across the link to slow things down.

....and I suppose it could be a combination or something else
altogether.

How did you setup (/connectcomputer?) the remote clients? Can you do
a ipconfig/all from a local client and one from the remote and post
the results?

--
/kj

--
/kj



.

Relevant Pages

  • Re: DNS Forward lookup problem - now having problems with a period
    ... How did you set the replication scopes in the zone's properties in DNS on ... > each DNS server? ... to the remote 10.0.2.3 server, which runs on cable (we are working on ...
    (microsoft.public.windows.server.dns)
  • Re: Advice Needed: Asynchronous Replication/Mirroring to central o
    ... Looking for a SQL Server replication book? ... field offices return data to the central office so some of this "advanced" ... geographically-dispersed remote locations. ...
    (microsoft.public.sqlserver.replication)
  • Re: Advice Needed: Asynchronous Replication/Mirroring to central o
    ... Looking for a SQL Server replication book? ... geographically-dispersed remote locations. ...
    (microsoft.public.sqlserver.replication)
  • Re: what new 2008 AD features may I want to consider for this?
    ... If you have large numbers of users at remote sites or if your vpn connection is unreliable, then this is a perfect candidate for a dc at the remote location. ... If you have remote dc's setup then you need to ensure the bandwidth is available for replication and while setting this up the DS replication doesn't consume the bandwidth available. ... this active directory deployment is only to support a deployment system, which is using WDS and DFS-R, both of which require active directory. ... There is a 'central' server where all edits to anything will be done from, each other location will have a deployment server with a replica of this file share. ...
    (microsoft.public.windows.server.active_directory)
  • RE: VPN (RRAS) ON SBS 2003 SP1
    ... SBS Server via VPN cannot access other internal servers/clients, ... "Remote Access Wizard": ... mark) on both the SBS Server and the remote client, ...
    (microsoft.public.windows.server.sbs)