Logon script command (net use x: /home) fails with system error 53

I'm hoping someone can help shed some light on a problem I'm having. Here's the situation:

We've got a W2K3 network with two DCs and about 25 or so users running XP Professional clients. For each user's profile, the Home folder is specified as drive H: via the Connect option and points to \\server\user.name, and each user's logon script contains the net use H: /home /y command.  Also, each DC has a Users folder which in turn contains home folders for some of the users. (The servers used to handle seperate divisions (different OUs) in different locations prior to a company consolidation.)

Here's the problem. When users with home folders on DC01 login to the domain, they get their H: drive. But when users with home folders on DC02 login, they don't get it-- instead, while other drive mappings to DC02 work OK, the net use /home command fails with Error 53, network path not found. For the users with home folders on DC02, I can manually map their home folder via net use \\server\user.name as well as in Windows Explorer.

Anyone have any ideas as to why the \home command works for one group and not the other? Could this have something to do with OU settings or how permissions are configured on the respective Users folders?

Any insights would be greatly appreciated!

Regards,

Joe


 

Joe2009Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SysExpertCommented:
Possibly.

also, I would make sure you do a delete of the H: drive before mapping it in the login script.

I hope this helps !
0
samsixtyCommented:
Odd that it works for one group but not the other yet you are doing the same thing.

Personally I use group policy to redirect users home folders, and a logon vbscript to to map drives depending on which group the user is in. (see code snippet for example)

These links may be helpful:

Folder redirection best practices, http://technet.microsoft.com/en-us/library/cc739647%28WS.10%29.aspx

Implementing folder redirection using group policy, http://www.tech-faq.com/implementing-folder-redirection-using-group-policy.shtml


On Error Resume Next
 
Set objSysInfo = CreateObject("ADSystemInfo")
Set objNetwork = CreateObject("Wscript.Network")
 
strUserPath = "LDAP://" & objSysInfo.UserName
Set objUser = GetObject(strUserPath)
strUserName = objNetwork.UserName
objNetwork.MapNetworkDrive "N:", "\\Servername\Private\" & strUserName
 
For Each strGroup in objUser.MemberOf
    strGroupPath = "LDAP://" & strGroup
    Set objGroup = GetObject(strGroupPath)
    strGroupName = objGroup.CN
 
    Select Case strGroupName
        Case "Accounts"
			objNetwork.MapNetworkDrive "R:", "\\Servername\Common"
			objNetwork.MapNetworkDrive "J:", "\\Servername\Accounts"
 
 
 
	Case "Engineering"
			objNetwork.MapNetworkDrive "R:", "\\Servername\Common"
			objNetwork.MapNetworkDrive "H:", "\\Servername\Engineer"
 
 
    End Select
Next

Open in new window

0
Joe2009Author Commented:
Thank you for the links.

Since I didn't set up this network originally, I want to avoid making any wholesale changes until I better understand how things are configured. Plus I'm a little rusty (OK, a lot) and don't have much experience with Group Policy.

What I don't understand is why the \home variable doesn't work when I can map to the specific folder by name. Is there any way this can be an NTFS/sharing  permissions issue?
 
Joe
0
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

samsixtyCommented:
How about trying 'net use h: \\server\%username%' instead of 'net use H: /home' in your logon script, that is not much of a change and may work.
0
johnb6767Commented:
Are you using the %homeshare% variable in thier AD properties??
0
DonNetwork AdministratorCommented:
0
Joe2009Author Commented:
Sorry for the delayed response-- I've been away.

I can make the drive mapping work by using \\server\%username% instead of /Home in the logon script. I have also noticed that by changing the Connect path from \\server\username to \\server\\users\username, a new home folder for the user is created, which then maps perfectly.  

For the users whose mappings don't work, it apparently never worked. I suspect the home folders were not created via ADU&C but were set up in advance and then had the path added to the profile. It's the only explanation I can think of for why the exact same logon script and folder path works for some users and not others.

I'm guessing the home folder file/and or share permissions are messed up on affected users, but it's not obvious to me what the problem is.

Anybody know of a decent doc that explains optimal home folder permissions?



0
johnb6767Commented:
0
DonNetwork AdministratorCommented:
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
OS Security

From novice to tech pro — start learning today.