VPN Host problems
Mar 30 04 4:47 am
I've looked around the forums here but I haven't seen any solutions to my problem.
I'm using the latest Wingate VPN to host VPN on my box, using Windows XP SP1. So far I've set up the options correctly and people from the Internet can connect to me (they to use Wingate VPN). However, we cannot ping each other, we cannot browse each other’s networks, and we can't see ourselves in any LAN based games.
Other details: The host is behind a router, and successfully forwards port 809. Again, clients connect, jus that there isn't any logical link between us.
I've used other programs before like OpenVPN and they worked, but I liked the administrative capabilities and ease of use with Wingate VPN.
I'm using the latest Wingate VPN to host VPN on my box, using Windows XP SP1. So far I've set up the options correctly and people from the Internet can connect to me (they to use Wingate VPN). However, we cannot ping each other, we cannot browse each other’s networks, and we can't see ourselves in any LAN based games.
Other details: The host is behind a router, and successfully forwards port 809. Again, clients connect, jus that there isn't any logical link between us.
I've used other programs before like OpenVPN and they worked, but I liked the administrative capabilities and ease of use with Wingate VPN.
Mar 30 04 5:32 am
Which address are you pinging? If not the nat translated local ip then it may be an mtu problem look here
http://www.vpn.serveftp.net/php/viewtopic.php?t=11
and here
http://forums.qbik.com/viewtopic.php?t=1104
Otherwise, do you have any firwall software running (xp or other)
Regards
JonO
http://www.vpn.serveftp.net/php/viewtopic.php?t=11
and here
http://forums.qbik.com/viewtopic.php?t=1104
Otherwise, do you have any firwall software running (xp or other)
Regards
JonO
Mar 30 04 5:52 am
Since we're both on cable, we're using an MTU of 1500. I can ping his internet IP, but his internal IP that displays in Wingate cannot be pinged (request timed out). Does the MTU have to be changed for all of us? I'm kind of reluctant to change it because of the degradation of performance. More importantly, if all my friends and subsequent users of the system wish to login, I would hate to have to explain to them about changing their network settings just to get it to work.
Yes the host is using a firewall, Sygate, however it has been configured to allow Wingate to pass though. Alternatively, the Wingate firewall was disabled.
Here's a sample of my setup. I ping the user's 192.168.2.167 IP with no results. And of course their MS Network is inaccessible
Yes the host is using a firewall, Sygate, however it has been configured to allow Wingate to pass though. Alternatively, the Wingate firewall was disabled.
Here's a sample of my setup. I ping the user's 192.168.2.167 IP with no results. And of course their MS Network is inaccessible
Mar 30 04 2:29 pm
Did you forward 809 for TCP and UDP ?
Mar 30 04 2:59 pm
"Did you forward 809 for TCP and UDP ?"
- Yes, both protocols are being forwarded to the computer. Also, outbound 809 connectivity to connected clients seem to be working too
- Yes, both protocols are being forwarded to the computer. Also, outbound 809 connectivity to connected clients seem to be working too
Mar 30 04 3:01 pm
Hmmm. Pings fail, correct ? I have a basic trouble-shooting document, which might be of interest to you. Can I email that to you ? (Approximately 2.8 MB)
Mar 30 04 3:11 pm
--- edit ----
Last edited by TheGhost on Mar 30 04 4:40 pm, edited 2 times in total.
Mar 30 04 3:12 pm
Not yet, but I'll put it on my site and send you a download link.
Mar 30 04 4:08 pm
Actually, I'm starting to wonder if the problem lies in the routing table. Wingate VPN is set to send and receive new routes, but the routing table isn't updating. For example, my friend who is on the 192.168.2.X network isn't added in my routing table. Could this be the cause? I tried adding in some static routes but still had no success. Perhaps I'm missing something important along these lines.