Peer to peer

[wmj24601]

I'm using Wingate VPN with the Peer 2 Peer license.

I have set up using your instructions. When I try to connect I receive a message that says connection refused by remote host or a time out error.

I am trying to connect an XP to an ME machine. Both machines are using Sprint DSL to connect to the internet and both are using DNS2GO for the DNS name.

What is the most likely reason that the machines will not connect to each other?

Is it a matter of user names/passwords on each of the computers?

Both computers have Panda Titanium antivirus running on them, could that be a problem?

Thanks for the help!

[adrien]

Does the Sprint DSL also do network address translation (NAT)? If so, then you will need to get into the DSL router and set up what are known as pinholes.

There should be some documentation that came with them to show you how to do that.

Adrien

[wmj24601]

Yes the router does support NAT. I put in 809 for the port and it asks for an IP address. I'm not sure what to put in there. Can you help with that?

Thanks.

[wmason]

You need to enter the IP address of the machine which is hosting the VPN gateway. If the IP address of your gateway machine is 192.168.1.100, then that is the address you enter for packet forwarding. The router will then forward packets over port 809 from your router's public IP address to the Wingate VPN software on the gateway machine.

Be certain that you enable forwarding for BOTH TCP and UDP packets on port 809. WINGATE VPN needs both types of packets. Your router documentation should show you how to do this, if it is not obvious.

[wmj24601]

I've set-up the router to open port 809 with the ip of the computer. The computers now seem to be connecting but I get a message saying "access denied".

I assume the user name/password isn't right. What user name/password do you use on the computer trying to log in? Is it the Wingate vpn user name/password or the networks user/password?

Thanks!

[wmj24601]

Ok I've set-up to user name and password and now am connecting.

I see the tunnel set-up ok.


I see the network of the computer I am connecting to. This is what is see:

Microsoft Network:
Name_Of_Network(testing)...

It just sits there doing that.


Under Published Routes I see:

Behind NAT/Translated

192.168.1.33/255.255.255.255(In Conflict)


I am not sure how to fix this conflict. Any ideas?

I've tried changing the IP address to Port 809 but no luck.

Thanks for any help!

[adrien]

Having a route in conflict means you are using the same IP addresses on each end of your VPN.

Each branch of the VPN needs to be on its own logical subnet, that means they need different ranges of IP addresses - e.g. 192.168.0.x, 192.168.1.x etc.

Adrien

[wmj24601]

I've changed the subnets that one of the dsl routers sets to 192.168.2.33 and kept the other one at 192.168.1.33.

It seems to connect now with no conflicts. But when under Microsoft Networks I do not see any shared drives.

any ideas?

Thanks for the help!

[overtheclockdivx]

Having a route in conflict means you are using the same IP addresses on each end of your VPN.

Each branch of the VPN needs to be on its own logical subnet, that means they need different ranges of IP addresses - e.g. 192.168.0.x, 192.168.1.x etc.

Adrien

ok but in windows vpn connections you can connect 192.168.0.x to another 192.168.0.x. Windows assign a network connection to the client machine like 200.0.0.1. And both machine can see eche other with no problem.

Real Situation.
CPU 1 VPN server WIN XP PRO, get 192.168.0.2 from router 1
CPU 2 VPN client WIN XP PRO, get 192.168.0.10 from router 2

When connection
CPU 1 makes server of VPN at 200.0.0.1
CPU 2 takes another connection with ip 200.0.0.7