Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Net Use login script failure

Status
Not open for further replies.

Mokil

Programmer
Joined
Jun 7, 2001
Messages
15
Location
GB
Hi there, hope someone can help!

I'm running a small network (about 10 PCs), all of which login to a server running Windows 2000 Advanced Server. Have SP3 and all latest security patches on this machine.

Network is a mixture of Win 98/Win 2000/Win XP.

Each user has a login script, which uses NET USE commands to provide mapped access to network shares. All shared data resides on the server.

The server was recently rebooted after installation of SP3. Since then, none of the Windows 98 PCs can see one of the shares! The XP and 2000 PCs still see the share. But the Win 98 PCs do not even execute the NET USE command for this share when logging in.
More bizarrely, if I add new shares and new mappings to the login scripts (on any PC), the command is not executed. That is, the NET USE command for that share is not executed.

I'm currently trying to solve this problem - any help is greatly appreciated!

Thanks,
Mokil.
 
A colleague of mine had the saem issue, he removed all service packs and went back to SP2......that sorted it for him.....Id try that. 'A world without donuts is like a donut without a hole.......wait that would mean more donut! I'm a Genius' Homer Simpson
 
Cheers for the reply Rath!

I've tried removing SP3 but this hasn't helped. If I run the script manually, there is no problem - it executes fine.

Regards,
Mokil.

 
Have you reinstalled SP2?? 'A world without donuts is like a donut without a hole.......wait that would mean more donut! I'm a Genius' Homer Simpson
 
Yup, SP2 reinstalled - still no luck!

Putting SP3 back on.

Think it might be order of precedence - have a firewall and a backup file server - they may have been booted up in incorrect sequence.

Cheers!
 
Sorted!

I was right - the backup server had taken precedence and login scripts were running from there. The login scripts on the backup server were old, hence the missing share.

Anyway thanks for all your help Rath.

The morale of this story is make sure your servers boot up in the correct order (I didn't know they had been booted up incorrectly).

Best regards,
Mokil.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top