Tunnel connecting, but unable to ping remotes

[Christopher]

My situation has a good tunnel connection, plus I can "see" the machines at either end, but I cannot connect nor ping them.

Host: Server 2000 192.168.3.xx [Static DSL - NAT]
Remote: Server 2003 192.168.2.xx [T1 - NAT]

Firewalls are turned off on WingateVPN and no OS firewalls are running. The routers are running their firewalls with both UDP & TCP port 809 forwarded.

Local Participation is set for Local Network on both ends.
RIP 2 has been activated on both routers.

I had these babies seeing each other last week, with just an issue with opening a large folder on the host. MTU adjustments didn't seem to help, but I was not finished testing. Now they will not even connect. I've reset all settings, uninstalled Wingate VPN and reinstalled with no luck. Help

[MattP]

Hi Christopher,

If you can ping the other end of the VPN then you either have a routing problem or there is a firewall blocking the connection.

What IP addresses do the NICs have between the server and the internet connection? This isn't on the same subnet is it? Do the servers have a default gateway set pointing at the internet connection?

Can you access our test server? You can download the config file here, username=test, password=1234.

[Christopher]

The server subnets are...

Host: 192.168.3.xx 255.255.255.0 >> 10.0.0.xx 255.255.255.0 >> Internet
(This network has our router on a DMZ connection on the DSL router)

Remote: 192.168.2.xx 255.255.255.0 >> Internet

Default gateway's the servers point to the router each one is connected to.

I will try your connection this afternoon when I get to the remote office.

[Christopher]

*Update* 1:00pm EST

I can connect and enter the Walrus network and I see the Walrus server. If I try to open it asks for a user/pass. This connection attempt is from the remote network.

[MattP]

When you get prompted for the username and password use the same credentials as you did for the VPN, test and 1234. You should then be able to get in and browse the shared directory.

[Christopher]

I'll try that. In the mean time I have to admit that I got more done in 1 minute with your host than the hours I've been working on mine.

[MattP]

Do you want to create a support ticket and send us the VPN config file, then we'll try to connect to your VPN and see what happens?

We'll need a username and password to connect with, and a username and password to browse the server when we get connected.

[Christopher]

Give me some time. I've got the network broken down now since I cannot stop them from working. Plus I want to change a couple of things on the host end.

BTW thanks Matt!

[Christopher]

Since my last post I've removed a secondary router from the host end and now have only one private subnet in place at that location (192.168.3.xx).
The remote location has not changed and sits on a seperate subnet (192.168.2.xx). I have cleaned up the published routes in an attempt to get rid of the ones tagged as "Ignored/Conflict", but connectivity is not real stable. At some points all machines are listed as connected, then I'll loose one network all together (Not connected) or one or two machines will not connect. Pinging is also random.
I would like to try this new driver if possible, before I continue.

Host is a 2000 Server & Remote is a 2003 Server

Chris at nbsva dot com

[MattP]

Hi Chris,

Drivers sent.

[Christopher]

Hi Chris,

Drivers sent.

Didn't recieve...My filters may have rejected connection, which means you'll see an error. I'm unable to reach my email server at this time.

Can you send to secondary?

nbsva at comcast.net