connect to Windows 7 PC w/o login work around.

[El Cabot]

perhaps next week my problem returns

It lasted only a day. I am disapoint.

[fozo]

Tried all of these suggestion (which surprised there is no official tech support from the manufacture) and still not working.

[idynamitei]

I found the following steps on http://answers.microsoft.com/en-us/w...9-e17bc0626beb

I got the PBO working with Windows 8 (should work for Windows 7 as well) after completing the first part:

•Click the start button and type secpol.msc in the search function.
•Browse to "Local Policies" -> "Security Options". Now look for the entry "Network Security: LAN Manager authentication level" and open it. Click on the dropdown menu and select "Send LM & NTLM - use NTLMv2 session security if negotiated". Apply the settings.
•In the Advanced sharing settings page of Network and sharing center, you need to have it set as Work/Home profile. Try
◦Enable network discovery
◦Turn on file and print sharing
◦Turn off password protected sharing
◦Use user accounts and passwords to connect to other computers

•Please check related policies. ◦Enter “gpedit.msc” in the Start Search box.
◦Open “Computer Configuration”/Windows Settings/Security Settings/Local Policies/Security Settings.
◦In the right pane, enable the following policies:
◾Network access: Allow anonymous SID/name translation
◾Network access: Let Everyone permissions apply to anonymous users

◦Also please disable the following policies.
◾Network access: Restrict anonymous access to Named Pipes and Shares
◾Network access: Do not allow anonymous enumeration of SAM accounts
◾Network access: Do not allow anonymous enumeration of SAM accounts and shares

•Reboot PC to activate the new policy



•If the above still does not work, edit the following settings in Registry ◦Click Start button and type regedit in Search box and select regedit.exe to execute
◦Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Lsa and change the value as follows ◾Right click on "LimitBlankPasswordUse", select Modify and change the value data to 1
◾Right click on "NoLmHash", select Modify and change the value data to 0
◾Right click on "everyoneincludesanonymous", select Modify and change value data to 1

◦Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\servic es\LanmanServer\Parameters, right click on "restrictnullsessaccess" select Modify and change the value data to 0
◦Reboot the PC again

[takagari]

Doesnt Work.

I can not believe Win7 has so little support.

Bah

[idynamitei]

Doesnt Work.

I can not believe Win7 has so little support.

Bah

After all the above, try adding in your shared folder names to the following:

gpedit.msc -> Computer configuration -> Windows Settings -> Local Policies -> Security Options -> Network access: Shares that can be accessed anonymously

Also, try enabling the built-in Administrator account and create a password for it.

[idynamitei]

If you read my deleted post, please try the technique with discretion as it is a security risk.

[dtclxy64]

I'm running Win7 Home Premium, just uninstalled Windows Live Essentials, fixed the problem. However, I think before uninstalling, be sure to have the right network sharing setup as stated in the first post though.

[weezypenguin]

so if you have to delete windows live what are you supposed to do with WIndows 8. Come on Patriot this is shocking that you have not come out with some firmware to fix this....

[Eron]

After all the above, try adding in your shared folder names to the following:

gpedit.msc -> Computer configuration -> Windows Settings -> Local Policies -> Security Options -> Network access: Shares that can be accessed anonymously

Also, try enabling the built-in Administrator account and create a password for it.

I've tried everything suggested here to get my PBO core to see windows 8 file shares.. No go... aarrrrgh..

[snappy46]

I've tried everything suggested here to get my PBO core to see windows 8 file shares.. No go... aarrrrgh..

A new SMB protocol is shipped with windows8 and this probably related to the issues you've been having. The SMB client on the PBO is quite old and does not support the latest SMB protocol. Here some interesting info: http://blogs.technet.com/b/josebda/a...le-server.aspx Long story short a new samba client will probably be required or a change in the server end.