Home folder problems for a few users

[agiuliano]

Let me start off by saying this is not a new installation it has been in place for years and no changes have been made to the servers:

 

I'm having a strange problem with 3 users on my network all my users have a mapped Home Directory Drive "Z" via the home path variable in the profile tab.

Occasionally I would have a user lose their "z" drive and a simple restart would suffice. Some people earlier this year experienced a persistent loss of their "z" drive and I changed the path from:

\\Server\Users\"Username"

 

to

 

\\S11KNOX.knoxschool.local\users\"Username"

 

However after a power loss on the Server room (3) users haven't been able to get their "z" drive back - no matter where they login, although others have no problem logging in on the same machine.

I have looked at past posts and tried the "delete the desktop.ini file and it will restore it to its former state." = No luck

 

The only relation they all share is their offices are located in the same area of the building (but other users in the same area and or office are fine).

 

Any ideas?

[synaesthesia]

Is there otherwise full network connectivity? Are they able to log on elsewhere, can other users log on to their PCs?

[victory2012]

have you tried the ip address of the server to rule out dns issues,, e.g //10.0.0.1/users/%username%

[jklight]

For windows xp clients, look in C:\WINDOWS\Debug\UserMode\userenv.log it is where windows logs this sort of stuff.

[agiuliano]

"z" drive back - no matter where they login, although others have no problem logging in on the same machine.

I have looked at past posts and tried the "delete the desktop.ini file and it will restore it to its former state." = No luck

 

The only relation they all share is their offices are located in the same area of the building (but other users in the same area and or office are fine).

Any ideas?

They all have full conectivity

[agiuliano]

All the affected system are Win 7 (1) 32bit & (2) 64bit I have a Winxp user in the area, but they a not experiencing any problem.

[agiuliano]

have you tried the ip address of the server to rule out dns issues,, e.g //10.0.0.1/users/%username%

trying that right now - also there was a mention in a port about creating a Dword in the registry "Formatdatabase" but that did't work either.

[agiuliano]

The ip address trick failed to work... it looks like a definite account issue.

[free780]

Have you checked the permissions both ntfs and share on the server.

[synaesthesia]

So, to reiterate what I said originally - can they log on elsewhere, can others log onto those stations? Basic checks first...

[agiuliano]

Yup like I said in the OP "(3) users haven't been able to get their "z" drive back - no matter where they login although others have no problem logging in on the same machine"

[agiuliano]

Have you checked the permissions both ntfs and share on the server.

Yes rechecked them.... although nothing on the server has been changed, I am the sole IT person on staff.

[synaesthesia]

Yup like I said in the OP "(3) users haven't been able to get their "z" drive back - no matter where they login although others have no problem logging in on the same machine"

 

Ack, my apologies!

 

How are those drives mapped, via GPO/GPP or script? If GPO/GPP what does gpresult throw out?

[ricki]

Have you rebooted the switch that the servers are plugged into. Have you checked the dns records on all of the dns servers. Have you checked if the servers are replicating. Have you checked the servers are regosteted in dns. Have you checked the time on the clients and servers.

 

Richard

[ricki]

Dont forget mapped drives dont work well with scripts on windows 7 use the gpo intead.

 

Richard

[agiuliano]

The Drive is mapped via the home path variable in the profile tab of the users account on AD. I'm going to remotely restart the servers and switches tonight. I did notice on one of the machines that the dns forwarder reverse lookup were acting funny the assigned IP was 192.168.0.129, but the client would respond to Nslookup commands but not ping requests. I deleted the DNS forward and reverse records for the client and rebooted the computer, still the problem persisted until i manually changed the IP and rebooted it responded to pings and Nslookup correctly but the main problem still persists, I even took off the domain, removed it from the AD computers list and put it back on the domain. still no luck.

[Homeland]

I realise it might be a stupid comment but you said that you lost power to the server room at one time, have you tried deleting the user account and recreating it in case its beome corrupted for some reason ???

[agiuliano]

Good news I logged in remotely and restarted all my servers and switches (and restarted a few switches in another part of the building this morning.) all 3 users have there Drive back. Thanks for all the assistance with fixing this problem.