Robynsveil, I can not promise it has the resource you need but something was recently posted which gives much of the functionality of the Group Policy Editor to 32-bit Home Premium and it may help with this setting you need.I read GopherBaroque's link. In it he says:
"Fixing the problem requires editing the group policies. ..."
But then, he explains how to fix the issue for Win7 Pro users using gpedit.msc. Since I'm on Win7 Home Premium, I don't have gpedit.msc, so I'll need to edit my registry by hand. The article only gave a warning that editing the registry might be dangerous: it didn't actually explain what changes to make.
Is there a resource for this information anywhere?
Perfect. Thank you very, very much for sharing this link. I registered on this forum just to say thanks.See also the network security policy tweak at:
Thank you.I just signed up so I could post the simplest solution:
- Go to: Control Panel > User Accounts and Family Safety > Manage Windows Credentials
- Expand each device listed by clicking the down arrow
- Delete all the credentials by selecting "Remove from vault"(to make things simple)
- Create new credentials for each network by entering the IP address of the device you're trying to connect to. For example, most internal IP addresses start with 192.168.1.xx. The last two digits vary with each device. It could be 192.168.1.1, 192.168.1.16, etc. Enter this address in the "Internet or network address" field.
- Enter your username and password (don't have to enter computer name, slashes, etc)
- Try to connect to the network. It will now work.
- To double check, restart your computer. The credential will still be remembered.
I tried to write down the simplest instructions. Obviously, there is more depth to this and alternative solutions, but this one works. The issue is 1.You either did not enter your credential in the correct format or 2.You have corrupted/duplicate credentials. There is no sequence required. We usually think that if something works, the sequence must have mattered.
5 years of this symptom, typing the darn user/pwd for the NAS share, checking the useless "remember my password" box...oh so many keystrokes....but tonight I came across this fix, posted back in 2009, and yet never listed in my dozens of google searches.I had the same problem for a long while, but tonight I seem to have solved it. This is how I did it. Hope it works for you and many others. My network storage is Buffalo Linkstation LS-CHL (I will call it LS-CHL below).
Sign-in your network storage device manually as before.
Go to Credential Manager under Control Panel-User Accounts. Look for your network storage device under windows credential and open it. Then select Edit. Replece the domain name in front of your user name (LS-CHL, in my case). Save.
Log off from you Windows account and then log in again. Windows will again say it cannot connect network drive. Open Credential Manager again and you will notice that your device is not there under windows credential.
Now connect your device again manually. Then in Credential Manager click "Add a Windows Credential": enter device name (LS-CHL, in my case) as internet/network address, user name (without domain name) and password. Save.
That is it. Log off window and then log back on, your device should be connected automatically.
The sequence is important.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.
|Does Windows 7 "Windows Update" scan "my" computer for updates or does…||1|
|Windows does not continue starting up||2|
|Windows Update doesnt work after a Clean Install od WIN 7 64 bit SP1||2|
|Autoplay does not appear in Windows 7||1|
|Bought new Windows 7 disc, doesn't seem to start||0|
|Windows 7 doesn't boot...||1|
|Windows 7 64bit Screesaver doesn't work||1|
|Screensaver windows 7 doesn't come on||11|