Home / server / Questions / 255493
In Process
Philippe
Asked: 2011-04-05 07:28:50 +0800 CST

net use mapping not working in batch files but works in cmd

  • 772

Ok so here's the problem :

I've got users using logon script in the domain (username.bat). The script simply lists 4 or 5 (net use letter: \\SERVER\directory\). However, when they open their session, the logon script doesnt work and returns system error 53 or 67 for all of them. I tried running the script after the profile has loaded and evrything is running, and it still gives me the error.

I've then tried to run the same command in the cmd.exe. Everything mapped correctly. It also works fine if I map the drives using the "Tools > Map network drives" utility.

Is there anything that can prevent a command to work when ran in a batch-file but works correctly when typed in manually?

login batch-file windows-command-prompt logon-scripts mapping

4 Answers

  1. Two options:

    1) Use Process Monitor (SysInternals) with its boot logging option, filtering on CMD.EXE and System. Monitor the logon process and script execution.

    2) Add a small test to the user's logon script, which uses ROBOCOPY's TBD switch to wait for the server/share to be available, i.e.:

    setlocal
set LOG_FILE=c:\temp\foo.log
echo %DATE% %TIME% >%LOG_FILE%
%SystemRoot%\System32\robocopy.exe \\server\directory c:\temp\test /tbd /eta /log+:%LOG_FILE%
echo %DATE% %TIME% >>%LOG_FILE%
endlocal

    Check the log file to see if ROBOCOPY does have to wait for the server/share to be available.

    • 1

  2. I ran into the same problem. For me, the solution was this:

    • I couldn't map a the root directory of a network share to a letter.
    • I couldn't use a trailing backslash in the mapped path.

    So:

    net use B: \\MYSERVER didn't work and resulted in error 53 right away.

    net use B: \\MYSERVER\Components\ didn't work and resulted in error 53 after a pause.

    net use B: \\MYSERVER\Components did work.

    • 1

  3. A few things you might try.

    1. Try using the fqdn for the server name see if you get better results that way.

    2. You might also try disabling any anti virus software on the server for testing it. I've seen McAfee take 1-3 minutes to load before it will let any kind of network connection to occure. When asking McAfee about that, they said it's setup to make sure McAfee is fully loaded before it will let any tcp/ip connection connect.

    • 0

  4. Without the script - If your batch file contains ifmember statements on for Windows 7 you could run into an issue. I have been using Group Policy to map drives as I find it a lot easier and flexible with security groups if that is something needed.

    • 0