Re: WinXP. Unable to map home drive. Map's to root of share only.

There is something very strange going on. Consider this:

- Your user's name is 00026260.
- The command net use x: \\server\home$ generates this mapping:
X: \\Server\data$
- The command net use y: \\server\home$\%UserName%
is expected to create this mapping:
Y: \\Server\data$\00026260
but instead it creates this maping:
Y: \\Server\data$\0\00026260

What's the extra "0\" doing in there? Does this folder exist?
What is its purpose? When you execute the command
net share home$ on the server, where does it point to?

Perhaps your share definition for the home$ share is corrupt.
I would run these commands on the server:
net share home$ /del
net share home$=d:\SomeFolder\SomeSubFolder

Your question about my second batch file is justified. It should
have read
net use y: \\server\%UserName% instead of
net use y: \\server\home$\%UserName%

Does the corrected command work? Every time?


"Mick Reynolds" <MickReynolds@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4FF33B50-9FC5-4A87-AC82-2ACFE7B4775A@xxxxxxxxxxxxxxxx
> Sorry for the slow reply (and thanks for your help)
>
> I have run the scripts as you requested and attached them below.
>
> I don't quite understand the 2nd script because its mapping to the
original
> share and not the share that you asked me to create on the server. As you
can
> see the when I run your script it works ok but this has always been the
case
> when done after logon. My original login scripts do work but occasionally
> fail to the root map (I have also attached net use to show you how
sometimes
> they work and sometimes they dont - look at the F: drive mapping).
> **********somtime don't work sometimes work:
> New connections will be remembered.
>
>
> Status Local Remote Network
>
> --------------------------------------------------------------------------
-----
> OK F: \\Server\data$ Microsoft Windows Network
>
> The command completed successfully.
>
>
>
> New connections will be remembered.
>
>
> Status Local Remote Network
>
> --------------------------------------------------------------------------
-----
> OK F: \\Server\data$\0\00026260 Microsoft Windows Network
>
> The command completed successfully.
>
> **********Test1.txt
> 05/10/2005 14:31:45.79 user=00026260
> The command completed successfully.
>
> The command completed successfully.
>
> New connections will be remembered.
>
>
> Status Local Remote Network
>
> --------------------------------------------------------------------------
-----
> OK F: \\Server\data$ Microsoft Windows Network
> OK X: \\Server\data$ Microsoft Windows Network
> OK Y: \\Server\data$\0\00026260 Microsoft Windows Network
> The command completed successfully.
>
> Volume in drive X is Data
> Volume Serial Number is 8E42-75BC
>
> Directory of x:\
> **********Test1.err
> File Not Found
> **********Test2.txt
> 05/10/2005 14:36:27.50 user=00026260
> The command completed successfully.
>
> The command completed successfully.
>
> New connections will be remembered.
>
>
> Status Local Remote Network
>
> --------------------------------------------------------------------------
-----
> OK F: \\Server\data$ Microsoft Windows Network
> OK X: \\Server\data$ Microsoft Windows Network
> OK Y: \\Server\data$\0\00026260 Microsoft Windows Network
> The command completed successfully.
>
> Volume in drive X is Data
> Volume Serial Number is 8E42-75BC
>
> Directory of x:\
> **********Test2.err
> File Not Found
>
>
> "Pegasus (MVP)" wrote:
>
> > OK, time to run some tests. Please run the following batch file
> > on the problem workstation, then post the contents of c:\test*.txt
> > and c:\test*.err.
> >
> > @echo off
> > echo %date% %time% user=%UserName% 1>c:\test1.txt 2>c:\test1.err
> > net use x: \\server\home$ 1>>c:\test1.txt 2>>c:\test1.err
> > net use y: \\server\home$\%UserName% 1>>c:\test1.txt 2>>c:\test1.err
> > net use 1>>c:\test1.txt 2>>c:\test1.err
> > dir x:\ 1>>c:\test1.txt 2>>c:\test1.err
> >
> > Now hop onto the server and run this command from a
> > Command Prompt:
> > net share xxx=d:\yyy\xxx
> > where xxx is the user's logon name (as above) and d:yyy is the
> > physical location of \\server\home$. Check your handiwork by
> > running this command:
> > dir \\server\home$\xxx
> > You must also set the ***share*** permissions for xxx to
> > "Full Control for Everyone". You can do this in Explorer.
> >
> > Now run the following batch file from the same workstation
> > as before:
> >
> > @echo off
> > echo %date% %time% user=%UserName% 1>c:\test2.txt 2>c:\test2.err
> > net use x: \\server\home$ 1>>c:\test2.txt 2>>c:\test2.err
> > net use y: \\server\home$\%UserName% 1>>c:\test2.txt 2>>c:\test2.err
> > net use 1>>c:\test2.txt 2>>c:\test2.err
> > dir x:\ 1>>c:\test2.txt 2>>c:\test2.err
> >
> > The results should be interesting.
> >
> >
> > "Mick Reynolds" <MickReynolds@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
> > news:F30FE4C0-4874-45D8-8D20-1EEE35961BF1@xxxxxxxxxxxxxxxx
> > > Sorry if I'm not explaining myself very well...
> > > we are trying to map root a folder to \\server\home$\%username% and
most
> > of
> > > the time it works i.e. root map to the home folders user account, but
> > > sometimes it only maps the drive to the share i.e. \\server\home$
> > >
> > > when it fails net use s: \\server\home$\%username% only returns the
same
> > > mapping of \\server\home$ and doesn't map to the users home folder
i.e. no
> > > error message but the wrong drive mapping
> > >
> > >
> > > "Pegasus (MVP)" wrote:
> > >
> > > > You previously wrote:
> > > > "I have also mapped drives manually after login using the net use
> > command
> > > > but this still fails."
> > > >
> > > > You then wrote:
> > > > "We don't get an error message - We get a drive mapping only to the
> > share
> > > > i.e.
> > > > \\server\home$ not \\server\home$\"username"
> > > >
> > > > These two statements are at variance with all my networking
experience.
> > > > Either something works, or else I get an error message.
> > > >
> > > > If you wish to map drives manually for testing purposes then
> > > > you must do it from a Command Prompt:
> > > > net use s: \\server\home$
> > > > net use t: \\server\home$\%UserName%
> > > >
> > > > After resolving any problems surrounding these commands,
> > > > put them into your netlogon batch file, followed by a "pause"
> > > > command, until they work or until you see the exact error
> > > > message.
> > > >
> > > >
> > > > "Mick Reynolds" <MickReynolds@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
> > message
> > > > news:8D5F16C6-F967-4C2A-82AE-2BFEEB2E7701@xxxxxxxxxxxxxxxx
> > > > > We don't get an error message - We get a drive mapping only to the
> > share
> > > > i.e.
> > > > > \\server\home$ not \\server\home$\"username"
> > > > >
> > > > > "Pegasus (MVP)" wrote:
> > > > >
> > > > > > What is the exact error message you see when the
> > > > > > command fails?
> > > > > >
> > > > > >
> > > > > > "Mick Reynolds" <MickReynolds@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in
> > > > message
> > > > > > news:D3C1FB95-D43E-40E0-9B9F-31575AEA123F@xxxxxxxxxxxxxxxx
> > > > > > > Thanks for you reply
> > > > > > >
> > > > > > > I have tried mapping the path as stated below i.e.
> > > > > > > \\server\users$\%username% within the login script. The login
> > script
> > > > runs
> > > > > > ok
> > > > > > > with no errors but still get random failure (Please note these
> > login
> > > > > > scripts
> > > > > > > and drive mappings have been working for 2-3 years with no
> > problems -
> > > > it
> > > > > > is
> > > > > > > only since we upgraded to Windows XP SP2 that the problem
started
> > and
> > > > it
> > > > > > > seems to be very random)
> > > > > > >
> > > > > > > Do you still recommend getting rid of the home folder entry in
the
> > > > users
> > > > > > > profile even though I am running the scripts as you suggest (I
> > have
> > > > approx
> > > > > > > 20,000 users)
> > > > > > >
> > > > > > > I have also mapped drives manually after login using the net
use
> > > > command
> > > > > > but
> > > > > > > this still fails.
> > > > > > >
> > > > > > > I have also tried disabling the ADS group policy in User
> > > > > > Configuration\Admin
> > > > > > > Templates\System\User Profiles
> > > > > > >
> > > > > > > Mick
> > > > > > >
> > > > > > > "Pegasus (MVP)" wrote:
> > > > > > >
> > > > > > > >
> > > > > > > > "bowser325" <aaronmccall@xxxxxxxxxx> wrote in message
> > > > > > > >
news:1127399620.234487.148850@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > > > > > > > > Under user properties - Profile Tab - Home Folder -
Connect S:
> > To:
> > > > > > > > > \\server\users$\%username%
> > > > > > > >
> > > > > > > > You are relying in inbuilt mechanisms which can be
> > > > > > > > hard to debug. I would use an external mechanism
> > > > > > > > that is completely visible and easy to debug. Get rid
> > > > > > > > of the home folder entry in the user's profile and place
> > > > > > > > this instruction into your logon script instead:
> > > > > > > >
> > > > > > > > net use S: \\server\users$\%UserName%
> > > > > > > > pause
> > > > > > > >
> > > > > > > > Remove the "pause" commend when you see that
> > > > > > > > things work OK.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >


.

Relevant Pages

  • Re: log off command
    ... I simply execute the batch file and let them play... ... If it's by the hour you don't need a script. ... You can logoff a sessionname or a session ID in each case you have to ... Is it possible to issue the command from user1's logon to logoff ...
    (microsoft.public.windowsxp.basics)
  • Re: log off command
    ... I simply execute the batch file and let them play... ... If it's by the hour you don't need a script. ... You can logoff a sessionname or a session ID in each case you have to ... Is it possible to issue the command from user1's logon to logoff ...
    (microsoft.public.windowsxp.basics)
  • Re: Command or setting to force monitor on?
    ... Keystrokes vbs script? ... But the same symptoms as without cscript, monitor not waking up, when I ... I set up a batch file containing the commands to first start IE, ... could move to the keystrokes command. ...
    (microsoft.public.windowsxp.general)
  • Re: Scheduled script problem
    ... A vbs script that sets up a command to run a batch file, calls EXEC on the ... until the scheduler stops the script after the maximum allowed time to run. ...
    (microsoft.public.windows.server.scripting)
  • Re: Scheduled script problem
    ... A vbs script that sets up a command to run a batch file, calls EXEC on the ... until the scheduler stops the script after the maximum allowed time to run. ...
    (microsoft.public.windows.server.scripting)