Re: network home folder not mapped correctly
- From: "Per Hagstrom" <poh@xxxxxxxxxxxxxxxxx>
- Date: Wed, 13 Sep 2006 15:12:07 -0500
"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OVvV$jz1GHA.4924@xxxxxxxxxxxxxxxxxxxxxxx
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
Hey!
There is a ton of people out there with this very same annoying problem. It
always seem to happen to people after they installed SP2 on Win XP.
I have the very same problem as well.
After reading a bunch of different forums with this problem, I haven't found
one solution to fix this specific problem. Only solutions are workarounds
with VB scripts etc...
So seems like this must be a bug? Could somebody contact Microsoft tech
support and find out why this is happening, and if there is a fix, without a
workaround?
Many thanks in advance!!
/ Per
ps. Somebody suggested to enable this GPO; Computer Config-Administrative
Templates-System-Logon-Always wait for network at computer startup and logon
Haven't had time to check if that is the actual problem? What do you think?
.
- 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: Devldr32.exe issue
- Next by Date: Re: Remote Access and Account Lock Windows XP Pro
- Previous by thread: Re: network home folder not mapped correctly
- Next by thread: Re: network home folder not mapped correctly
- Index(es):
Relevant Pages
|
