Login Scripts - net set time batch file takes long time

[Guest]

Hi,

i am in the main office with 5 other offices connected to it via Frame
Relay. The users in the remote offices login script work well except when the
following script has to execute it takes up to a minute to execute.

This is what a typical login script will look like:

NET USE H: \HOME
NET USE G:\\SERVERNAME\SHARES
NET USE I:\\SERVERNAME\INFO
NET TIME /SET /YES - when it gets to this bad boy it takes up to a minute.

Any ideas??

Thanks

 

[Herb Martin]

NET USE H: \HOME

NET USE G:\\SERVERNAME\SHARES
NET USE I:\\SERVERNAME\INFO
NET TIME /SET /YES - when it gets to this bad boy it takes up to a minute.

Does it work? (Set time) Especially if not, consider making
it a STARTUP script so it can work under the computer account
(with sufficient privileges) and consider spawning it off in a
separate batch with "start /separate /min cmd...."

/B may help or hurt with the start command.

Does net time work from the command line AFTER the use
is logged on? Is there a delay?

You may actually have a name resolution (even NetBIOS problem)
that requires DNS or even WINS server/client proper configuration.

 

[Lanwench [MVP - Exchange]]

Hi,

i am in the main office with 5 other offices connected to it via Frame
Relay. The users in the remote offices login script work well except
when the following script has to execute it takes up to a minute to
execute.

This is what a typical login script will look like:

NET USE H: \HOME
NET USE G:\\SERVERNAME\SHARES
NET USE I:\\SERVERNAME\INFO
NET TIME /SET /YES - when it gets to this bad boy it takes up to a
minute.

What's the client OS?
This shouldn't be necessary on Win2k/XP....they should sync with the DC (PDC
emulator) automatically anyway.

Also, unless that's a typo, "net time..." needs to be 'net time \\servername
/set /yes' or something....
WinNT and 9x need the net time command - but on NT-based OSes, only those
with local admin rights can set the system time.

 

[Herb Martin]

Herb, thanks for that

Yes, it works perfectly. I've been using it for years and it works fine in
the main office, there is not that long delay when my login script kicks in.

I suspect I have a DNS problem but not really sure how to troubleshoot it.

DNS is easy but NOT obvious at first.

If I look the all clients settings their primary DNS is the correct server's
DNS Address.

Clients should all be set to INTERNAL DNS server(s) ONLY.

Primary/Secondary are NOT client side concepts and irrelevant
there generally. Clients PREFERRED DNS server shoud be the
closest (network close).

Do NOT try to set clients to a combination of internal-exteranal
DNS server but rather let the internal DNS server(s) forward
if you need external resolution.

NOTE: Servers, especially DCs and even DNS servers are
DNS CLIENTS too!


Also:
DNS
1) Dynamic for the zone supporting AD
2) All internal DNS client NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2

Restart NetLogon on any DC if you change any of the above that
affects a DC.

 

[Enkidu]

What's the client OS?
This shouldn't be necessary on Win2k/XP....they should sync with the DC (PDC
emulator) automatically anyway.

Also, unless that's a typo, "net time..." needs to be 'net time \\servername
/set /yes' or something....
WinNT and 9x need the net time command - but on NT-based OSes, only those
with local admin rights can set the system time.

Yes, I was wondering why the need for it.

Cheers,

Cliff