VPN server (lucky) and client (zz) are Win7. Computer names are known to each machine via LMHOSTS. UserIds and passwords are the same on both ends. I can successfully establish a VPN connection. From the server I can easily access the default shares on the client. For example, in Start, I type \\zz\g$ and, without further action, an Explorer window opens there. If I do the same from the client, say \\lucky\d$, I get a credentials box and my credentials are not accepted. Oddly, if I create a non-default share on the server (say \\lucky\d) then, from the client, I can connect to \\lucky\d without hassle. What's going on? And how can I get access to the VPN server's default shares? Thanks. - Vince

VPN server (lucky) and client (zz) are Win7. Computer names are known to each machine via LMHOSTS. UserIds and passwords are the same on both ends. I can successfully establish a VPN connection. From the server I can easily access the default shares on the client. For example, in Start, I type \\zz\g$ and, without further action, an Explorer window opens there. If I do the same from the client, say \\lucky\d$, I get a credentials box and my credentials are not accepted. Oddly, if I create a non-default share on the server (say \\lucky\d) then, from the client, I can connect to \\lucky\d without hassle. What's going on? And how can I get access to the VPN server's default shares? Thanks. - Vince The solution was to create, in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System a REG_DWORD value named LocalAccountTokenFilterPolicy, with data 1. I googled that, and don't remember Googling it before, or setting it on the client machine mentioned above. But it was set there. Is there a software way to do that?

Hi , I am glad to hear you have found the resolution. Set LocalAccountTokenFilterPolicy value to 1 is to disable UAC remote restrictions. More information about UAC remote restrictions, please see this link. http://support.microsoft.com/kb/951016Tracy Cai TechNet Community Support