Can't set up a New Folder on a mapped drive

Hello All.

This is a bit difficult to describe - please bear with me.

Using Windows Explorer on my laptop...

I have Drive S mapped to Drive D on my server.

On Drive D on the server is a Folder called "Woodroyd CS Data."

On my laptop I have Drive X mapped to the folder "Woodroyd CS Data" within Drive D on the server.

So as you can see I can access "Woodroyd CS Data." either directly through Drive X or by drilling down through Drive S.

Here is the problem.

Using Drive X I can create a new folder on Drive X - That’s OK
BUT using Drive S if I attempt to create a new folder I get an error saying that I need permission.

So I can create a new folder in "Woodroyd CS Data." providing I access it through Drive X but not when I access it through Drive S.

For clarity: Drive S on the laptop is mapped to Drive D which is the root directory. Drive X is mapped to a sub folder in that directory.

I have searched through all the permissions on the server but can't find anything that I can see that would cause this to happen.

This would not be a problem except that I am attempting to use a backup routine that backs up some folders on the laptop to drive S; but this fails because it can't create new folders when required.

If I access these folders actually on the server - no problem.

The laptop is running Windows 7 and the server SBS 2003.

I hope my explanation is clear and that someone has a clue about this.

 

Might try remapping Drive S to see if that corrects the problem.
If you still can't create the folder, you could try remapping the drive but "Connect with different credentials" in the process. For example, use the server credentials.

 

Thanks for your advice lbmest

This brought up a startling result.

As I was reconnecting to the D drive on the server I noticed that I had TWO D Drives listed.

One was listed as: Network / Woodroyd-Local / D drive on server

The other was listed as: Network / Woodroyd-Local / D drive on SBS server.

I will need to investigate this tomorrow when I can get access to the server, but by mapping S to Network / Woodroyd-Local / D drive on SBS server - all is well – it’s working

I tried remapping to the other one but that did not solve the problem.

Thanks again Ibmest

 

Also on the server where the share is you may have
S - with read only permissions
And the folder shared as "Woodroyd CS Data" you may have read/write/create - 'full access'.
You might ask the admin what your permissions are.

 

Unfortunately, foogoo, I am the administrator – that is probably a big part of the problem.

My company is not very big – indeed having a “proper” server is probably overkill – a workgroup would possibly be more appropriate. But we did install the server before the recession set in when we had a much larger staff.

But in spite of my lack of network knowledge I had checked permissions and shares. They were all OK – there should have been no difficulty there.

I have not yet had time to find out why there were two drive D’s showing under Networked drives.

 

One thing to note is that you typically have share permissions and NTFS permissions and they both need to be set correctly to get the desired access.

Remember that when it comes to calculating network share permissions the least permission dominates.

Read (Share) + Full Control (NTFS) = Read (Effective Permission)
Full Control (Share) + Modify (NTFS) = Modify (Effective Permission)

As far as the two 'D' drives showing up it could be that the first drive may have been disconnected when the second one created? I'm not too sure because Windows typically does not allow two drives of the same letter.

I haven't used SBS only the Windows Server editions so SBS may work things different.

 

As I said in an earlier post: from the laptop under Network / Woodroyd-Local / in Windows Explorer, I could see two instances of the D drive on the server. One named “D drive on SBS server” and the other “D drive on server.”

The permissions on the first were all set OK. What was not clear to me was that when I went into Properties on the server I was only seeing the share for “D drive on SBS server” – I had not spotted the drop down which enabled me to select the alternative named share. Frankly I had not thought that there could be more than one share anyway. As you might now guess the shares on the alternative name (“D drive on server.”) were not set for full access. So naturally using that name from the laptop could not possibly work.

This should now clear up this thread unless someone has something to add, so thanks again to all who have contributed, your advice has been noted and has brought fresh information to my understanding of network shares and share names.