[RESOLVED] Shared folders causing me problems again

I have a shared folder on a server and I want to map a network drive to it. I used to have this drive mapped, but last night I turned off my PC. Now when I try to map the drive, it wants an id and password but doesn't like what I am giving it and keeps prompting me.

I rarely reboot my PC and whenever I did I'd have this problem. So I documented what my id and password is instead of just relying on (my poor) memory. So I'm pretty sure I have that right, but then why won't it let me in?

I should also say last night we moved offices and the servers moved physically as did my PC (which is why I had to turn it off) so I don't know if some address changed that I am not aware of (our public IP changed, but if my PC and the server are internal, would that matter?). But I guess my basic question is how do you map a drive and how do you know what credentials it wants?

Thanks.

Try this

Click on Start~~>Run
Type the relevant IP +path as shown below

\\xxx.xxx.xxx.xxx\Pathname

and press enter. Now try the username and the password.

We will take it from there....

Your local network admins should be able to help you with this. Have you contacted them?

While mapping the network drive, provide the correct username and password by clicking that "different user name" link in that window. It won't ask for password after that after you reboot.
Attachment 75436

As for how to map a drive - open My Computer and go to Tools -> Map Network Drive. That will take you to the screen Pradeep has shown you.

But like Hack says, this is really the job of your network admins and ideally they should be deploying such mapped drives by logon script or group policy so that you users do not have to ever mess around mapping them yourself. It sounds like a bit of an odd setup you have got there though if you have to specify a username and password to access the share, normally the admin would just grant your windows account access to the share and that would be it. Also, it is pretty likely that the office move has something to do with it if suddenly stopped working since then.

I also believe the office move has something to do with it.

Thanks for all the replies. (I've been out the last few days but of course when I came back this was still here waiting for me).

As for the advice about contacting my administrator, yes, I wish I had one. I think it is me. We are a very small shop and since I am the web developer which has something to do with computers by default I am also the network administrator since that has something to do with computers (we have use of a network engineer at our boss's brother's company and he and I work together great, but the relationship is being severed because the companies are splitting, and I have been getting yelled at for calling him). Our company VP does a lot of the network stuff, but this is for Visual Source Safe, which I have set up because I wanted it, so I may be stuck as the one to fix it.

But I think I'll risk the yelling and asking the network engineer for help. Your ideas resulted in different results, none of which has gotten me in yet, but thanks, I feel I'm getting closer.

TBC...

I think I am getting somewhere. I at least got connected to the drive on the server which I mapped to the source safe folder. I found this advice on another forum which somebody else had asked:

You should try to connect from your client to the SourceSafe share and create a test file in the data directory.

If this works look at the explicit rights.dat file.

Otherwise check permissions on both the share and NTFS.

And I cannot create a test file. The error was

Unable to create the file 'New Text Document.txt'. Access is denied.

Do you know how I can grant myself the necessary access rights?

Right click the shared folder (on server) and select Properties.

In the properties window, go to Sharing tab.
click Permissions button.
Select Everyone and then tick mark the Full control (allow) checkboxes.
[Note that this will grant full control to anyone on your network. If you want it for yourself only then add your UserName to that users list and grant permissions.]

Thank you. Now I am able to create a test file. But I get the same error message. Which according to the advice in post #7 indicates that I need to "look at the explicit rights.dat file." Look at it and do what with it? And does that mean look at its properties, because I can't look at it, it's binary.

Thanks.

Have you tried opening it in Notepad?

Yes, that's how I did try it and saw that it was binary. So I don't know what I'm looking at.

Okay, if you click on enough things eventually you get it right.

What seemed to do the trick was the VSS folder, Properties, the Sharing tab, the Permissions button and I gave Full Control to Everyone. Which means I may not have done exactly what Pradeep suggested until just now, since that seems to be exactly what Pradeep said. But I think I first tried just me and that didn't work.

Thank you. I still don't know why this happened just from a simple move of hardware up the stairs...

I should say that when I first made Pradeep's change, I next got unable to open user login file. There wasn't one (data\loggedin\mmock.log) so I created a zero length one, then had other problems, then went back to Pradeep's advice with Everyone selected.

I'm sorry I can't recount the exact steps of what I did,but like I said, I clicked a lot of things!

The share permissions are not what Pradeep was talking about - there are NTFS permissions (which is what he was talking about) and Share permissions. I think he just forgot to mention the Share permissions (and I would have as well...). Generally we just grant Everyone full control on the share permissions and then restrict access via the NTFS permissions as you have more flexibility with NTFS permissions.