Connected to VPN server but cannot see shares

[mansol]

I have my client joining the VPN, and can then see the VPN server and its domain. I cannot access any of the shares on the server.
The VPN is local machine only.
The server is 192.168.0.2, my client is 192.168.100.23
If I try to browse \\192.168.0.2 then it asks for a username & password, then (eventually) says it is not accessible.

Any suggestions appreciated
Archie Campbell

[MattP]

Hi Archie,

If you're getting a pop-up authentication box asking for a username then it sounds like the VPN side of things is working. When you enter a username and password does it accept it?

When you see the not accessible message are you still able to ping the remote machine?

What OSes are you running at each end of the VPN?

Is file and print sharing enabled on the adapters of these machines?

[mansol]

When client connected to the VPN, I can see
Local network of SERVER [Master]
Microsoft Windows Network
<domain name>
Server
If I try to open or explore Server, after a long pause I get a window with "\\server is not accessible. The remote procedure call failed".

The username and password are definiteley valid on the host domain. I have tried joining the VPN on engine startup as suggested in the Help file

VPN host User Database is set to use remote user database (Active Directory) on \\server. The Active Directory User properties - Dial In - Remote Access Permission as set to Allow Access.

Ping from host to client is OK.
Ping from client to host times out (tracert goes 15 hops then times out)
Telnet from host to client can't open connection to port 809
Telnet from client to host connects.

The VPN host is running Win 2000 Server
The client is Win 2000 Pro, but I get the same result on XP Pro.

File and print sharing is enabled at both ends.

[mansol]

After looking at nearly every setting in the software, I finally managed to connect to the server share.
I think the key points were
1. User database linked to Active Directory.
2. In Active Directory user properties, set Dial In Remote Access Permission to allow access.
3. Turning down the MTU on the network adapters from 1500 to 1000 (it stops working again above 1000).

Still have to configure another 3 laptops though, and it's quite hard to type while keeping fingers crossed.