XP Users don;t executer scripts when logging in on NT Domain

[Pete Halasovski]

Hi,

I have a problem which affects _most_ of my users. We'r in the process of
migrating from NT to XP workstations and NT to W2K servers. I have set up a
test XP box for my users to have a play with, unfortunately for many of them
the drive mappings given in login scripts do not work. Sample is:

net use S: \\server1\sshare1$ /persistent:no > NUL

Seems to work if the user issues this from a dos box although there is no
onscreen feedback; doesn't say 'Command completed successfully' even though
it did. I have also seen a variation where entering the server name does not
work but entering the server's IP address does.

The Domain is still run by NT. We did have issues with browse master
elections but this seems to be solved. Just not sure which tree to bark up
at the moment...

Thanks in advance,

Pete

 

[Invisible]

Sample is:

net use S: \\server1\sshare1$ /persistent:no > NUL

Seems to work if the user issues this from a dos box although there is no
onscreen feedback; doesn't say 'Command completed successfully' even though
it did.

Take out the "> NUL" bit and it should give the on-screen confirmation. (The
"> nul" bit turns off all screen output for a single command.)

I have also seen a variation where entering the server name does not
work but entering the server's IP address does.

Implies some kind of name-resolution problem (wither DNS or WINS, as
appropriate).

Hope that's at least *some* help to you...

 

[Gary Davis]

Make sure if you are using a NT4 server that the NT4 server is at Service
Pack 6a

 

[Michael Giorgio - MS MVP]

Disable the computer browser service on all
W2k or higher machines the only affect of this
is to take them out of the browse election process.
Server manager uses the browse list to populate
the list as long as view / show domain members
only is disabled. It's common for W2k machines
in an NT 4.0 domain to force a browse election
in order to become the master browser and win
because of it's OS criteria. In an NT 4.0 domain
the PDC is always the DMB or domain master
browser responsible for gathering the domain
wide browse list along with the SMB or segment
master browser responsibility on it's local subnet.
The SMB gathers the local list and passed it on
to the DMB/PDC which merges the list and passes
back to all SMBs. Note it takes as long as 51 minutes
for the browse list to refresh

 

[Plato]

I have a problem which affects _most_ of my users. We'r in the process of

MS OS's are designed to be installed fresh.

 

[Guest]

Dont forget, the same script(s) should have been set up on both PDC and BDC(s)...

 

[Lanwench [MVP - Exchange]]

Haven't seen the original post, but scripts should be replicated
automatically to all DCs...if they aren't being replicated, there's
something wrong.