Re: network home folder not mapped correctly


"Doug P" <DougP@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:041F7B49-2473-4D8C-A144-E572E35BA22F@xxxxxxxxxxxxxxxx
My domain is currently in flux. I have a new 2003 DC but have not yet
removed
my 2000 DCs. The 2003 server is primary. The problem happened before the
2003
server was installed so that's not the issue.
The 2003 server is the logonserver whether the drive is mapped correctly
or
not.
I have not been able to recreate the problem with a reboot. During my
testing today, I can only recreate it after a complete shutdown. If I log
off
and log on, it works fine. If I reboot, it works fine. I can't say for
sure
that it never happens on a reboot. I can say for sure that log off and log
on
always fixes it.
Here's the weird part: When the mapping is incorrect, homeshare is
\\server\share and homepath is username. When the mapping is correct,
homeshare is \\server\share\username and homepath is \.
When the mapping is incorrect, net use z: /home reconnects the same
incorrect path. Net use z: \\server\share\username does work when done
manually after logon but I haven't tried it yet in a logon script.

Since it only happens on a complete shutdown, could it be due to some
default machine policy that only gets overwritten from the domain after
the
first log on?



"Lanwench [MVP - Exchange]" wrote:

In news:1ECB8E12-F857-47D8-BBC4-D4004E43A49D@xxxxxxxxxxxxx,
Doug P <DougP@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
I use a login script to map all other network drives.
Their home drive letter is done through the AD.

Are you using a W2k domain? I've seen this before but don't recall the
resolution...

Do you have the same problem if you use something like

net use z: /home ?
and/or
net use z: \\server\home\%username% ?

....presuming you're using a batch file? (I like to append /persistent:no
as
well)


All users have Full Control to their own home directory.
All Domain users have List Folder contents to the root home directory.
Everyone has Full Control to the home share.

That should be fine.

It can't be a permissions issue if it works sometimes but not others.

Agreed.

When this error occurs, what path do you see specified in the the
%homeshare% variable (type 'set' in a command prompt)?
How many DCs do you have, and does it make any difference which DC
authenticated them? (you can see this in Set as well).

As mentioned, I've seen this before - I've searched and found a couple of
people with the same problem. This looked interesting:
http://www.pcreview.co.uk/forums/thread-2150236.php





"Lanwench [MVP - Exchange]" wrote:

In news:AA622A73-B9C2-4468-B13C-E93B35AABD1C@xxxxxxxxxxxxx,
Doug P <DougP@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
All users in my Active Directory domain have a home folder
configured in AD to automatically attach their z: drive to
\\server\home\username where home is the name of the share on the
server.
Frequently when clients login to the domain from XP Pro computers
that have just been rebooted, their z: drive gets mapped to
\\server\home instead of \\server\home\username. If they logout and
login again, the mapping is correct. This only happens on XP. All
2000 Pro clients always get mapped correctly.
Any ideas?

Do you use a login script?
What permissions do your users have on the "home" share, and what
permissions do they have on their own subfolder





Doug,

I had the exact same problem as you are. And I also noticed the same
homeshare/homepath problem.

I have now been testing the GPO change for a while, and so far I haven't had
one single problem since.

This is the GPO you have to enable:

Computer Config-Administrative Templates-System-Logon-Always wait for
network at computer startup and logon

Give that a try and let me know if it fixes it for you too. Doesn't really
make "sense", but if this fixes it, it tells me this is a Microsoft bug or
flaw...
Don't forget to run GPUPDATE on the workstation after you have done the GPO
change.

Thanks!

/ Per

ps. Additionally, Microsoft does have documentation that you have to enable
this GPO to make sure the Group Policy Software Pushouts are going to work
correctly.



.

Relevant Pages

  • Re: network home folder not mapped correctly
    ... I just tried out this policy setting and it has worked so far. ... When the mapping is incorrect, homeshare is ... I have now been testing the GPO change for a while, and so far I haven't had ...
    (microsoft.public.windowsxp.general)
  • Automatic Updates options are greyed out, SBS 2003 and WSUS
    ... The SBS server is the DC ... GPO: Default Domain Policy ... Computer Setting: 50 ... GPO: Default Domain Controllers Policy ...
    (microsoft.public.windows.server.sbs)
  • Re: SCW question.
    ... Created a new Server and installed IIS. ... and saw that the default rights for IUSR and IWAM users are there. ... Server to the domain without and GPO's applied...Local Security policy ... rights (which coincides with my Member server GPO settings). ...
    (microsoft.public.windows.server.security)
  • RE: IE Security Group Policy
    ... username and password to access the Companyweb and the GPO did not apply on ... In the Security filtering of the GPO, please select the user account or ... Step 2: Check the IIS settings on the SBS Server: ...
    (microsoft.public.windows.server.sbs)
  • Re: Getting desperate: GPO applying incorrectly, PLEASE HELP ME!!
    ... > the exception of placing the TS machine account into the security settings ... > I think you are on to something with the linking of the GPO. ... >> OU to which the loopback GPO is linked, ... >> OU you placed the TS server, and you set loopback on in replace ...
    (microsoft.public.windows.group_policy)