Tunnel but noe network

Apr 18 05 3:30 am

I have 1 PC connected behind an ADSL Modem router with an ip address of 192.168.1.2, the second PC is connected via dial up. I can now get the tunnel to connect and ping in both directions. But there is not networking. The server (adsl connection) shows that the remote PC is there but its icon is yellow and has the text of "Testing" (for at least 30 mins. The remote shows the server and retests OK.
Niether PC will open or explore the PC on the other end of the VPN.
I have tried dropping the MPU as low as 1300 but this made no differance
I'm using 2,0,4

Apr 18 05 8:07 am

Are you sure that Microsoft Windows Networking is started on both PCs? In a lot of cases, with a single interface (Such as Dialup) in a machine it is not started because that would bind it to an external (public) interface. In these cases you should manually bind it to the dialup adapter. In that case, the WinGate VPN Firewall will still be protecting you against traffic coming in from the internet. I would recommend however that you then have the two bottom checkboxes in Extended Networking (Protect before startup and keep firewall up after shutdown)

Apr 18 05 10:46 am

The dial up PC is normally connected to the same network as the server via LAN, but this has been unplugged for testing purposes. I have already set the dial up adapter for file and print sharing, plus client for Microsoft networks

Also does tthe firewall play with windows security centre as it says there is no firewall

Apr 18 05 10:54 am

No, it is not registered in Security Center as a firewall. It is still 100% operational though.

Apr 18 05 11:15 am

Pascal wrote:No, it is not registered in Security Center as a firewall. It is still 100% operational though.

But what about the main problem :-)

Apr 18 05 11:21 am

Well, the tunnel is established. We know this because you've done the ping test and we know that traffic is being encrypted and shunted across the VPN tunnel. If you've done the ping tests correctly (With the non fragmentable flag and specified packet size set) and have adjusted the MTU using DrTCP (From dslreports.com) your system should also be setup correctly for Windows networking to work.

Which means, at this stage, it sounds like a Windows networking issue, rather than a VPN one.

Can you reach the machine by IP? E.g. \\192.168.0.1 ? Also, try running

nbtstat wrote:C:\Documents and Settings\pascalv>nbtstat -a 192.168.0.60

where 192.168.0.60 is the ip of the machine you are unable to reach. See what type of response it gives you back.