Having to log in to shared Win 7 computer each time

Posted on 2011-02-16
Last Modified: 2012-05-11
I have set up a small Win 7 Pro network for the customer.  Computer WS2 has it's C drive shared, where they have some files accesed by other computers.  Then, I have connected Computer WS9 to WS2 and mapped it as drive F.  While I was doing the connection, it required me to log in to WS2, so I did so, using a login name of 'Main' and a password of 'mara'--which is the system login on WS2--and it worked fine.  I also told it to automatically reconnect WS9.

The problem is this: Anytime I reboot WS9, it does not automatically reconnect to WS2.  I can click on the shortcut to "C on WS2", but it makes me login again as 'Main' and 'mara'.  I have repeatedly checked the box saying to remember my credentials, but it doesn't help.

The box actually says something like:  

Windows Security
Enter your password to connect to WS2

It also shows "Domain: WS9"...but of course I'm not using a domain.  This is just a simple file sharing setup with two Win7 computers.

I DID notice that if WS9 is up and running and connected to WS2, and then I reboot WS2, I can still access the WS2 share from WS9 without having to rekey my credentials.  But if I REBOOT WS9, that's when I have to rekey credentials to access WS2.

What am I missing here?  Is there a Win 7 setting I can do on WS2 and/or WS9 to make it remember my credentials?

Question by:sasllc
  • 4
  • 3

Accepted Solution

CrowaX earned 500 total points
ID: 34906922
I would suggest mapping the network drive with a bat file that enters the password on boot. Here is an example.

Type in notepad:

net use \WS2\sharename mara /user:Main
net use z: \\WS2\sharename

Just replace sharename with whatever your shared folder is called. Then save the file as network.bat, or something, then stick it in your startup folder. This should clear the drive, then remount it on every startup.

There may be an easier way, but this works great for me.

Expert Comment

ID: 34906983
I didn't take into account which computer is being specified in the login processes, the "domain" as you say. If the above works, that is good. If it wouldn't, replace the second and third line with this line:

net use Z: \\WS2\sharename /user:WS2\Main mara

If that doesnt work, then change the /user:WS2\Main part to  /user:WS9\Main

It depends which computer the actual username is a part of. For example, if you created the username "Main" on WS2, then you would use WS2. If you created it on WS9, then you would use WS9.

Author Comment

ID: 34913216
I ended up using the first example, lines 1 and 3, and that 'saved the day' while I was on-site, thank you.

Is all this 'normal' with Win 7 Pro networks?  Is there a setting in Win 7 Pro that will prevent the need to log in each time--for the other computers connecting with the shared computer?  

I've seen something on the web about a 'credentials manager' in Win 7 that may address this issue--but I can't tell for sure if it will solve the problem, nor exactly how to use it in a case like this one above.  Any idea?

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.


Expert Comment

ID: 34917188
It's not normal for domain based networks which the logged in user has rights to the computer. It is normal when trying to log onto a computer that your username does not have rights to. I've even seen this in XP which is where my first script came from.

I've never tried the 'credentials manager' before, but I added our computer name and password, and it still prompted for a password when logging in. But the box was different, as it had the credential name already filled in.

Author Comment

ID: 34926547
One more thought--that I can't easily test at the customer site without taking a chance of messing things up.

What about the idea of adding a user named WS9 on the WS2 computer?  Would doing this make the WS2 computer always think that WS9 was legit--and solve the login credentials problem?  

I would hate to have to add a user on WS2 for each computer that would ever log in, only because the WS2 operator would have to pick from a list of users--and find WS2--when starting up the computer (I assume).  But, if by adding all the user(s) it would negate the need for the batch file in startup, then it might be worth it.

So does this sound workable, and are there any downsides to doing it this way?


Expert Comment

ID: 34927385
I dont think that would be a problem. On my home Media Center computer, I could not access the media for some reason, so I made a second user on there with the same name and password as my computer username and I got access. But I did not use it to map drives. It is certianly worth a shot and seems like it would work.

Author Comment

ID: 35898872
FYI, I found that my last suggestion did work.  I added a "user" on WS2 for every computer that was going to connect.  The downside, of course, is that ALL the users I set up appear on the WS2 desktop when they log in in the morning.

Featured Post

Ransomware-A Revenue Bonanza for Service Providers

Ransomware – malware that gets on your customers’ computers, encrypts their data, and extorts a hefty ransom for the decryption keys – is a surging new threat.  The purpose of this eBook is to educate the reader about ransomware attacks.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Today, still in the boom of Apple, PC's and products, nearly 50% of the computer users use Windows as graphical operating systems. If you are among those users who love windows, but are grappling to keep the system's hard drive optimized, then you s…
When you try to share a printer , you may receive one of the following error messages. Error message when you use the Add Printer Wizard to share a printer: Windows could not share your printer. Operation could not be completed (Error 0x000006…
This Micro Tutorial will teach you how to the overview of Microsoft Security Essentials. This is a free anti-virus software that guards your PC against viruses, spyware, worms, and other malicious software. This will be demonstrated using Windows…
The Task Scheduler is a powerful tool that is built into Windows. It allows you to schedule tasks (actions) on a recurring basis, such as hourly, daily, weekly, monthly, at log on, at startup, on idle, etc. This video Micro Tutorial is a brief intro…

860 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question