Re: network home folder not mapped correctly
- From: Doug P <DougP@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 14 Sep 2006 13:20:01 -0700
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
- Follow-Ups:
- Re: network home folder not mapped correctly
- From: Per Hagstrom
- Re: network home folder not mapped correctly
- References:
- Re: network home folder not mapped correctly
- From: Lanwench [MVP - Exchange]
- Re: network home folder not mapped correctly
- From: Lanwench [MVP - Exchange]
- Re: network home folder not mapped correctly
- Prev by Date: Re: software not included
- Next by Date: Re: Windows XP - Startup List
- Previous by thread: Re: network home folder not mapped correctly
- Next by thread: Re: network home folder not mapped correctly
- Index(es):
Relevant Pages
|
|