First i noticed that my Home Drive set in my AD Profile path as \\server\username$ was missing after log on to the domain. So I tried a manual mapping to the hidden share... Path not found.Other logon script mappings work fine to NON-hidden shares. My Home drive still is accessible from XP machines.This issue was not evident in the Beta or RC.Network discovery turned offUAC set to defaultRunning the machine with a restricted rights (not admin group) account.Hidden share is on a NAS. I will test today to see if I can map to hidden shares on a W2K3 server.

Tested on a 2K3 server... No problem mapping to a hidden share. So I went back to the NAS and tried the IP address instead of servername... (\\123.456.789.001\username$) No problem!... Mapping went fine.BUT... Some of my other scripted mappings are to the same NAS server and they work fine... so how can it be a name resolution issue?Very bizarre.

Is Windows Live Sign-in Assistant installed? If it is try uninstalling it.Kerry Brown MS-MVP - Windows Desktop Experience

No... I do not see "Windows live Sign-in Assistant" in my Programs and Features list but I did have an issue where the Adobe Bonjour service was killing my DHCP connection because it would throw in a 0.0.0.0 Default gateway address ahead of my proper gateway address. Think there is any relationship???I have since stopped and disabled the Bonjour service and /released, /renewed my DHCP reservation and rebooted a few times... My DHCP issues are resolved but I still cannot resolve this hidden Home drive Profile path.

This issue can be caused by the incompatible Kerberos encryption types. How does it work if you access the NAS from a Windows Server 2003 computer via IP address? I suggest that you make the following changes on the Windows 7 computer: 1. Open gpedit.msc. 2. Find the policy Windows Settings -> Security Settings -> Local Policies -> Security Options ->Network Security: Configure encryption types allowed for Kerberos 3. Configure the policy. If it is not configured, actually both DES cipher suites are disabled. I suggest that you enable all the suits. Then please check the result. If the issue persists, please change the NTLM type in Windows 7. You may refer the following article. Network security: LAN Manager authentication level Please change the level to Send LM & NTLM - use NTLMv2 session security if negotiated. If the issue still occurs, please capture network trace data and send to me. 1) Download NetMon3.3 from the following website and install it on the computer NetMon3.3 2) Launch NetMon3.3.3) In the Microsoft Network Monitor 3.3 window, click Create a new capture tab 4) In the new tab, select all the Network Adapters in the Select Networks window.5) Go to sync time page. Then, switch to Network Monitor, press F5 to start NetMon.6) Try to sync time.7) Go back to the NetMon window and press F7 to stop the NetMon.8) Press Ctrl+S to save the Netmon file named test. Please upload the file to the following path. Microsoft Service File Transfer Password: zHMiOioS7lZx-YCArthur Xie - MSFT

I tried the local policy ideas... No change. I cannot install netmon in this environment

Problem solved - was caused by creating a "default profile" using unsupported methods. (Copying thea "user"directory and renaming it "default".)Any mappings made by subsequent logged on users were trying to be made with the credentials buried in the default profile.