windows 7 admin question

[lozina]

So I used to have windows XP on my server and it was so easy accessing its hard drives from my other machines - I'd open up file explorer, type in \\server\j$ for one of them for example and if this was the first time I ever did it I have to enter credentials, check to save and that's it.

I recently had to install windows 7 on that machine and it's really annoying.

I'd put in \\server\j$ like before, enter credentials like before and get access. great. But then if I close that file explorer and open it again later - it asks me for credentials again (oddly) and then this time it denies access with some message about not allowing multiple connections. wtf?

What do I have to do to eliminate this annoyance, so I can freely open and close file explorer windows and access these shares like I used to?

 

[bonehead123]

lookie here:

Control panel > User accounts > manage credentials, or "change Account control settings"

enjoy

 

[JoeBleed]

reboot then map the drive properly for repeated use.

if you do this from time to time just checking something on other computers and it messed up once. you will need to delete it in the command prompt to re-access it or just simply reboot.

to delete it from the command prompt just type:
net use

after hitting enter, it list the drives that are currently mapped. you'll likely see the problem path with no drive letter. you need to delete that one and re do it.:
net use delete \\your\fileshare

should do it.

if you don't see it there, then run the command prompt as administrator and try the above again. depending on how you tried to access the share thorough the explorer shell determines where that stuck map gets placed and visible.

 

[xSauronx]

share a folder and map a drive or create a UNC shortcut to it. that is what you should do.

or create a bat file [with aforementioned NET USE commands] that can reconnect it when you need it to

 

[Mushkins]

Take everyone's advice. You can't do it the old way anymore because the old way was woefully insecure. If you access it frequently map it properly to a drive letter and tell it to save the credentials.

 

[BonzaiDuck]

Take everyone's advice. You can't do it the old way anymore because the old way was woefully insecure. If you access it frequently map it properly to a drive letter and tell it to save the credentials.

Ditto, :thumbsup: and +1 to that . . .

I once used workstation OSes for a peer-to-peer server setup, and the OP can do that. SOME (not all) of the remaining options are a tad expensive since $50 reseller OEM WHS-2011 install discs disappeared.

The belated lesson I learned: The Windows 7 "Homegroups" feature assumes a sort of "communist" share-everything-equally view of the fam-damn-ily. Little Timmy can access your tax and investment archives or business files; Wifey can look at your depraved CLUB Magazine scans. And then she'd figure out that Timmy could do the same -- familial and security outcomes you might have hoped to avoid completely. You can't exclude users from subfolders ("Deny") if they inherit the parent security; weird things begin to happen with access; and you find yourself adding "HomeGroup" to the access privileges again -- only to find that there's "no security."

And WHS doesn't properly inform the user about security under HomeGroups when it asks if you want to join the Home Group. Once we expunged Homegroups, we mostly had to mod the security settings on each shared folder, giving "Full Control" to CREATOR_OWNER, SYSTEM, the Administrator or Admin group, and the individual for whom some folder or subfolder was exclusive. The latter person would also be given "Ownership."

The workstation logon surprise was similar to the OP's. And the answer to that could be found in Credentials Manager.