Roaming profiles not connecting to mapped drive

[rico42]

Hello,

I recently moved to new servers, and ever since i did, my users have been having a problem. I was able to transfer active directory fine. and my User Profile Path is pointed to the right place. example:

User Profile
Profile Path: \\fire\Users$\JamesM\Profile

Home Folder
Connect: U: to: \\fire\Users$\JamesM

Usually we will get a prompt saying that the U: drive cannot be found, logging on with a local profile nothing will be saved. We will open up my computer and U: will not be mapped. We can usually just Map U: to \\fire\Users$\JamesM and all their icons will come up again. Sometimes, the computer will not connect to fire, we can also try to map it to \\fire.lhsoc.local\Users$\JamesM and that will work. Again even when we thought we beat it, every once in a while neither will work. Other times it map the drive, only it wont map all the way. It will map U: to \\fire\Users$ So we get the same issues of people not being able to save things.

Any thoughts?

 

[snootalope]

That's odd.. If it were me, I'd change your share "Users$" to a simple share rather than an administrative share. that's just me though.

 

[Gazzieh]

To me this sounds like a server connection error. Something worth checking is your NIC, because our new servers were set to let the NICs go to sleep when trafic was low and they wouldn't wake up even on traffic. This required a quick driver fix.

 

[rico42]

I will give that a try and let you guys know, thanks for the help so far.

 

[rico42]

ok chekced it without an admin share and we had the same problem.

Checked on the NIC's going to sleep and that wasnt the problem. Threw on some new drivers just for a test, but we are still getting the same problem.

My only other thought would be a domain controller issue. maybe it didnt like the promotion or something.

If anyone can think of something else please let me know.

 

[snootalope]

One more thought...

Take their profile out of their Home directory. Create a new share and put the profile's in there.

 

[Gazzieh]

You have checked the security for the share?

The admin share is fine but I do agree with separating out documents from the profile. Not because I believe it will solve the issue but because once it is running you can easily delete a corrupted profile without losing documents, and having it as part of the documents folder simply will allow your users to edit/delete their own profile. With all the headache that would cause.

 

[w33mhz]

Have you verified that there are no other mappings to \\fire\Users$ that the users have mapped. I have had issues when trying to map 2 drives with in the same share whether it be an admin share or not. Being an admin share really won't have much to do with it unless the user doesn't have access to the admin share. The permissions go with most restricted so its always a good idea for the share perms to be full control everyone, then tighten secutrity at the NTFS perms.

Another note is that you need to allow SYSTEM full control of the profile folder, otherwise you will have issues with corupt profiles more often.