why don't the login scripts work some time?

[Guest]

Some times, for some users, the maped network drives that are configured on
the login script don't work. Can anyone make any guesses on why is this
happening?

Could the high CPU utllization on the server that the scripts are stored
affect the proper functioning of the scripts?

Thanks

Christos

 

[Pegasus \(MVP\)]

Some times, for some users, the maped network drives that are configured on
the login script don't work. Can anyone make any guesses on why is this
happening?

Could the high CPU utllization on the server that the scripts are stored
affect the proper functioning of the scripts?

Thanks

Christos

I recommend that you collect some data in order to home in on
this issue, by modifying your logon script like so:

@echo off
echo %date% %time% User=%UserName% PC=%ComputerName% >> c:\logon.txt
echo %date% %time% User=%UserName% PC=%ComputerName% >> c:\logon.err
net use p: \\YourServer\JSmith 1>> c:\logon.txt 2>>c:\logon.err
net use >> c:\logon.txt

When you get the next failure, have a look at the two log files.
The answer is likely to be right there.

 

[Guest]

I have exactly same problem as Christos.

Login script sometimes doesn't want to map network drive.
Message is always the same:
-----
"System error 53 has occurred.
The network path was not found."
------
Sometime it helps to execute manually script several times, but sometimes it
just doesn't want to map the drive.
If you browse drive through "My Network Places" or type UNC it will open
shared drive without problems. If you execute script immediately after
browsing drive it will map for 100%.

In 90% cases I have problem with the same share?! I checked permissions and
they are just fine. I even moved share to FreeBSD-Samba server and it behaves
absolutely the same?!!. In 90% will also be same users, including myself
(admin).
This share was DFS share while ago.....but not anymore...maybe..?

Any idea?

This is output from

 

[Pegasus \(MVP\)]

This message suggests that your PC was unable to locate
the machine where the shares reside. This could be a DNS
problem: net.exe looks in all the wrong places for your
server, and sometimes it times out. Ask your network
administrator to check your DNS settings.

 

[Guest]

DNS settings are just fine, I checked that already.
We have other shares on the same server accessed without a problem.
It is just this particular share that give us trouble. In case we have a
problem with DNS resolution it will affect all shares on this server not only
one of them.