new added drive on netlogon not working on client machine

Hi experts,

I have a problem connecting to a drive that i have added to the netlogon script. It is working on the server when i login, but on client machine it is not working.

I already did logoff and restart but still it is not working.
ragotAsked:
Who is Participating?
 
JohnConnect With a Mentor Business Consultant (Owner)Commented:
Try mapping it manually from the client. Open a command prompt and type:

NET USE X: \\server\folder name

What error or message do you get?

Also, on the client, open a command prompt and type NET USE . Do you see all your regular drives as expected?  Any other drives?  Still on the client, for each drive, type:

NET USE DRIVE: /PERSISTENT:NO
NET USE DRIVE: /DELETE

Do this for all drives and make sure all are deleted. Now restart and see if all reconnects.

... Thinkpads_User
0
 
JohnBusiness Consultant (Owner)Commented:
Did you add a line in an existing (and working) script? That is a normal way to add a drive. And simple logoff / logon always fixes that.

So, is the line typed properly (double check)? Does the drive properly exist (same server, same subnet, same domain, etc)? Overlapping drive letters? Last drive letter?

Have you turned persistence off and restarted?

... Thinkpads_User
0
 
ragotAuthor Commented:

 Thanks Thinkpads_User for the fast reply.

 The shared folder is mapped automatically via the script when i logon to windows server.. but on clients it is not working..


 Yes i added a line in an existing and working script. the drive exist same server, subnet, domain.
 no overlapping drive letter. i assigned it as "X"

 i havent turned the persistence off and restarted. This i will do on server or on client?
0
Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

 
JohnBusiness Consultant (Owner)Commented:
The steps I outlined about persistence are for the client. Persistence is a client issue and the server should be fine with handing out scripts.

I change existing scripts without issue on Server 2003.

Another thing to check is the user(s)' properties on the server. There should be a tab where the home folder is set. Make sure it is accomodating your new drive letter.

... Thinkpads_User
0
 
ragotAuthor Commented:

 the home folder connects to common user folder on remote site which is fine. you mean i need to change it and connect to the new shared folder that i want to map to users?
0
 
JohnBusiness Consultant (Owner)Commented:
No. I just wanted you to check the settings in there. The home folder will assign a drive letter and have a script that runs. You just need to make sure that the home folder letter is not X, for example. ... Thinkpads_User
0
 
ragotAuthor Commented:

 yes the home folder is not X
0
 
ragotAuthor Commented:

 i tried including persistent off into the line of the new folder into the script.. restarted machine.. still X drive is not mapped
0
 
ragotAuthor Commented:

 mapping drives manually from the client i have no issues. i just want to map it to all users here automatically when they logon.
0
 
JohnBusiness Consultant (Owner)Commented:
OK, but now I would like to answer my questions on persistence. You have some issue of drive lettering, or at least so it appears. ... Thinkpads_User
0
 
ragotAuthor Commented:
i tried net use, i saw all the network drives on My Computer, and the drive letter X is not yet taken by other drives
0
 
JohnBusiness Consultant (Owner)Commented:
Also, just to test: Try your script with a different drive letter. Also, remark out one line in your script and replace it with the new drive you wish to map. ... Thinkpads_User
0
 
ragotAuthor Commented:

 I tried different drive letter on my script, I tried having a rem on one line. Still cannot automatically map that folder that i want
0
 
JohnBusiness Consultant (Owner)Commented:
Can you list out your server script here please? Change the server name to just server to protect privacy, but otherwise. list out your script.

Also does the script live in C:\WINDOWS\SYSVOL\sysvol\mbc.local\scripts ?

Then in Active Directory -> Users , select a user and then properties of the user. In the Profile tab, is your script in there? and what does the Home folder say? What drive letter? and does it point the the user's folder.?

... Thinkpads_User
0
 
ragotAuthor Commented:

 i cannot see the mbc.local folder.
 In the Profile tab, is your script in there?  Yes
and what does the Home folder say?  folder of the user profile
What drive letter?  to another letter
and does it point the the user's folder.?  Yes
0
 
JohnBusiness Consultant (Owner)Commented:
It was an example and should look like C:\WINDOWS\SYSVOL\sysvol\yourserver\scripts .

So it would now help if you could find the script and it should be in sysvol. I don't know where else.

... Thinkpads_User
0
 
ragotAuthor Commented:
thanks. I found the scripts on that folder. but the only problem is that certain drive is not automatically mapped into users machine
0
 
JohnBusiness Consultant (Owner)Commented:
Can you list the script there (change the server name) ?

You have said "yes" to everything I have suggested. You say the folder is on the same server, same subnet, same domsin). You have suggested there are no overlapping drive letters or drive letters beyond "last drive".

The only things you have not done is (a) conclusive say you set "persistent:no" on the client drive and restarted and (b) list out the script.

A question I have not asked is: Did you share the new folder properly? Compare the sharing properties of the new folder to the sharing properties of an existing shared folder.

... Thinkpads_User
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.