Windows 7 needs to log on again after every boot

My Cloud OS 3 Personal & Network Attached Storage My Cloud
1

As per title. Each time I boot my PC I need to type user name and password to access it. I always check remember me, and in the Windows 7 control panel credential manager I’m remembered yet still need to do it again after each boot. 

Any way of making logging on automatic upon booting? 

2

Hope you have Windows 7 Pro, as you need access to the Group Policy Editor. There are workarounds available if you have W7 Home, available on the net.

This looks a bit long winded but only takes a minute or so. Assuming you have W7 Pro, in the Windows Run dialog, type  gpedit.msc

Once the Policy editor is open, in turn, click Computer Configuration - Windows Settings - Security Settings - Local Policies - Security Options.

Right click on “Network Security:LAN Manager authentication level” item and from the pop-up menu, select “Properties”

Select yje “Local Security Settings” tab and then in the dropdown box, select “Send LM&NTLM - user NTLMv2 session security if negotiated”

Click OK and close the window. Should all now work for you.

3

Are you trying to access shares through mapped network drives?

Did you create these mapped network drivers through Windows on your local LAN or through the Wd2go.com interface?

4

Just a point to note. Enuthing less than NTMLv2 is a security vulnarability.

Network security: LAN Manager authentication level

This security setting determines which challenge/response authentication protocol is used for network logons. This choice affects the level of authentication protocol used by clients, the level of session security negotiated, and the level of authentication accepted by servers as follows:

Send LM & NTLM responses: Clients use LM and NTLM authentication and never use NTLMv2 session security; domain controllers accept LM, NTLM, and NTLMv2 authentication.

Send LM & NTLM - use NTLMv2 session security if negotiated: Clients use LM and NTLM authentication and use NTLMv2 session security if the server supports it; domain controllers accept LM, NTLM, and NTLMv2 authentication.

Send NTLM response only: Clients use NTLM authentication only and use NTLMv2 session security if the server supports it; domain controllers accept LM, NTLM, and NTLMv2 authentication.

Send NTLMv2 response only: Clients use NTLMv2 authentication only and use NTLMv2 session security if the server supports it; domain controllers accept LM, NTLM, and NTLMv2 authentication.

Send NTLMv2 response only\refuse LM: Clients use NTLMv2 authentication only and use NTLMv2 session security if the server supports it; domain controllers refuse LM (accept only NTLM and NTLMv2 authentication).

Send NTLMv2 response only\refuse LM & NTLM: Clients use NTLMv2 authentication only and use NTLMv2 session security if the server supports it; domain controllers refuse LM and NTLM (accept only NTLMv2 authentication).

Important

This setting can affect the ability of computers running Windows 2000 Server, Windows 2000 Professional, Windows XP Professional, and the Windows Server 2003 family to communicate with computers running Windows NT 4.0 and earlier over the network. For example, at the time of this writing, computers running Windows NT 4.0 SP4 and earlier did not support NTLMv2. Computers running Windows 95 and Windows 98 did not support NTLM.

Default:

Windows 2000 and windows XP: send LM & NTLM responses

Windows Server 2003: Send NTLM response only

Windows Vista, Windows Server 2008, Windows 7, and Windows Server 2008 R2: Send NTLMv2 response only
5

Thanks for the replies. I think I know what’s going on. 

The shares were set up on the WD drive, and my wife (and other) pc’s can log onto the shares without having to do the log on. On my PC I run a backup utility that I have used for a wile and like (so I’m sticking with it) and this needs to have the WD drive mapped, so I set that up on my PC. If I remove the mapping I can log on after a reboot but the backup don’t find files, if I map the drive I have to log on after rebbot.

Now I know what’s causing it I will simply log on after boot. 

Cheers