W7 VPN connected but cannot access network or map network drive

But just one small hiccup.

I set up another connection to this VPN from a friend's PC (only real difference is different logon name and password)
The connection connected fine but then from the friends PC
- I could see the server on the network
- If I tried to access the PC to see its shares I got something along the lines of ""Logon does not have correct permissions"
- If I tried to set up a network drive to \\server\share I got a different message but meaning something similar.
the share's permissions include 'everyone' and the VPN user logon so I am confused

I have to set up a PC to replicate this so I can fiddle but do you have any initial ideas?

Do you mean you were able to setup 2 vpn connections at the same time?

No. When I use it from overseas I may be on a strange PC so I disconnected one VPN, set a VPN up on another PC that was (I think) identical to see if that worked. Apparently not!!

post a screenshot please. You just want to list all shares of PCSERVER?

I want the same access as we have managed to achieve during these exercise. I thought that logging on through the VPN meant any user logged on in this way had the access rights defined by the VPN username. The exercise with a friends PC suggests this might not be the case so but I have to set up a PC here to replicate the situation.

If that works, I have to get the friends PC back to check everything.

Excellent English as with all Dutch people
The VPN network is a work network
I've set password protected sharing to off (it was on)

But I dont think that is the problem. The new client PC cannot find the server by name or IP number (.1.67)
It can ping 78.86.160.148 (the external IP of the server) but that is all
It cannot PING .11.21, .1.1 or .1.67
IPCONFIG below

This is information emailed from the new client (a different location) so further information will be hard.
I do not now have much time for this until Tuesday of next week - maybe a sporadic hour or so - so during that time I will set up an XP machine; create a new user ; set up the VPN and see what happens but it wil lbe nothing much until next week.
Thanks for all your support

C:\Documents and Settings\Fain>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : FainsLaptop
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network Connection
Physical Address. . . . . . . . . : 00-1B-77-06-5F-D0
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.23
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 194.168.4.100
194.168.8.100
Lease Obtained. . . . . . . . . . : 13 March 2014 19:10:39
Lease Expires . . . . . . . . . . : 13 March 2014 20:10:39

PPP adapter Sam:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.11.27
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.1.1

Actually, I think I'll give up at this stage. I've learned a lot about networks (and even more about what I dont know about networks). You've helped me to get it to work and with a bit of patience I reckon I can make it work elsewhere.
Thanks again for all you help
dank u wel en tot zeins (which about exhausts the dutch I picked up in 4 years working in Holland!!)

The vpn tunnel is 192.168.11.27 now! But router on server side routes 192.168.11.* to 192.168.167 so no problem.

This is because of the subnet mask I presume?

If they can't ping 192.168.1.67.... client has to select "use the default gateway on remote network"

This doesn't (like much of this stuff!) make any sense. It was not necessary when we got got working the first time so why now
And (I presume) it means their internet connection is routed through the VPN.which is not desirable