Link to home
Start Free TrialLog in
Avatar of patfsteele
patfsteeleFlag for United States of America

asked on

H drives not mapping correctly

In my workplace the DC is running on Server 2003 and we seem to be having an intermittant issue, if the user clicks on their mapped H drive (mapped through their profile, not a drive map policy) it will sometimes send them to their H drive, and sometimes it sends them to the users folder.  I initially thought that the fact that there was also a simple logon script which mapped the H drive along with some other drives and that it was conflicting somehow but after removing the H drive from that script the issue persists.  This seems to be happening randomly to mutiple people/computers.  The client stations are mostly Windows XP although I'm not sure if anyone is encountering this problem with Windows 7.  Any ideas where this problem stems from?
ASKER CERTIFIED SOLUTION
Avatar of Netman66
Netman66
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of patfsteele

ASKER

Thanks, but I must apologize that I was mistaken, it's running on server 2000, not 2003 and that option is not available, aside from using local policy on the PCs is there another way to do this with server 2000?
It should be available in Server 2000.  Try loading up the Adminpack and GPMC on a Windows XP machine then opening the Default Domain Policy from that machine.

New resolution for problems with Kerberos authentication when users belong to many groups
http://support.microsoft.com/kb/327825

Just suggesting this as an off chance solution. It does have known issues with drive mappings... Haven't see it around much though in a minute...
netman66 - sorry I was off site and didn't have access to it but I just confirmed that you are correct, it is an available option in server 2000.  Thanks.
Anytime.
Upon inspecting closer I did notice that while it does show in the template it does say that it only applies to server 2003 family or above.  I'll still give you the points, but wanted to list my alternate, logon script, based solution for windows xp / server 2000:

@echo off
Reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\current version\winlogon"
if errorlevel 1 goto fastlogonfix
goto end
:fastlogonfix
regedit /s -------(path to reg key)------- fastlogonfix.reg
:end
cls

***with the following reg keys:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\current version\winlogon]
"syncforegroundpolicy"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
"syncforegroundpolicy"=dword:00000001