Not accessible!please help!

[nuts2k]

I can connect to the VPN server, but I can not even access the VPN server.

Here's my connection:

192.0.0.18(VPN client)---->NAT--->internet----->NAT(port 809 TCP/UDP forwarding)----->192.168.0.100(VPN server)

On the Network tab of gatekeeper, i can see the workgroup of the server side(the client has the same workgroup name with the server), but all computers are not accessible.

I can't ping the 192.168.0.100 or telnet 192.168.0.100 809.

Please help me

[adrien]

Hi which version of WinGate / WinGate VPN are you running?

I'm not sure I understand the problem - are you not able to get a basic VPN connection?

can you test that the port forwarding is working from the router? I.e. try connecting to a port on the Server side, from its own local LAN, so you know the port is open. Then redirect a port on the firewall to that port, and try connecting in through the firewall. That will tell you if there is a redirect problem on your firewall.

Adrien

[nuts2k]

Hi which version of WinGate / WinGate VPN are you running?

I'm not sure I understand the problem - are you not able to get a basic VPN connection?

can you test that the port forwarding is working from the router? I.e. try connecting to a port on the Server side, from its own local LAN, so you know the port is open. Then redirect a port on the firewall to that port, and try connecting in through the firewall. That will tell you if there is a redirect problem on your firewall.

Adrien

thanks
I'm running wingate vpn 1.2.3

Yes, I got a basic VPN connection but no computer on the server side is accessible, even the server itself. Port forwarding on the server side is OK, I've tested it. Actually, I only tested TCP port, I don't know how to test an UDP port. I can telnet 192.168.100 809 from the local LAN of the server and telent 218.x.x.x(server side router ip) 809, it works.

Any suggestion for me? Thanks a lot.

[MattP]

Hi,

It looks like you have each end to the VPN on the same subnet, ie 192.168.0.*, this will cause a routing conflict with the resulting not accessible error.

Try changing the internal IP address of the client to a different subnet, eg 192.168.1.*, that should take care of it for you.

Regards,

Matt

[nuts2k]

Hi,

It looks like you have each end to the VPN on the same subnet, ie 192.168.0.*, this will cause a routing conflict with the resulting not accessible error.

Try changing the internal IP address of the client to a different subnet, eg 192.168.1.*, that should take care of it for you.

Regards,

Matt

they are not in the same subnet. One is 192.0.0.* and the other is 192.168.0.*

ps. I saw you have a test VPN server in another thread, can you email me the config file so I can make sure that I setup the client side correctly. Thanks.

[jono659]

Unless they have started a test server recently then you will be referring to my message. Click on my mail addy below and mail me.


JonO

[jono659]

Wow, have just seen a message that Qbik HAVE set up a test server.

Well done boys and girls, a great step forward


JonO

[MattP]

Hi Nuts,

I've just emailed you the config file for our test VPN.

192.0.0.* will be seen by WinGate as a public IP address by WinGate so it will be firewalled, please check your interface settings, you can check this by going to options>advanced and select the network interfaces tab, you should see your internal NIC as public no trusted yes.

Matt

[nuts2k]

Hi Nuts,

I've just emailed you the config file for our test VPN.

192.0.0.* will be seen by WinGate as a public IP address by WinGate so it will be firewalled, please check your interface settings, you can check this by going to options>advanced and select the network interfaces tab, you should see your internal NIC as public no trusted yes.

Matt

Thank you for your information. I can not connect the wingate test server, actually I can't even ping it. Maybe I should try it later. I've noticed that 192.0.0.* was treated as an external IP, so I disabled the firewall and mannually set it to be private and trusted on the NIC tab. Nothing happened. Maybe I should wait and see if I can connect your server later. Thanks again.

[jono659]

Hi,

You appreciate that Qbik support does as much as possible within the confines of time etc, this being the case if you would like talking through on my live Wingate VPN server then please mail me. It helps if you have MSN messenger as we can talk in real time while trying to get your VPN up.

Oh, and yes it's free.

Regards

JonO

(Wingate VPN self help group)

[MattP]

Hi Nuts,

Sorry about that, we were changing over IP addresses yesterday so the server was offline for a time.

Please try again,

Matt

[adrien]

Hi

We just found a problem with build 975 of the VPN when using non-standard ports. Basically if the VPN server (not the other end) is not using port 809 for the data connection, it won't work. We have now fixed this, and it will be in the next release.

Adrien

[mrbudman115]

Can you help me with this entire setup issue. I have a server with a smc Modem/Router cable(Dual) I tried to setup a vpn using two Linksys Routers. But the SMC will not allow me to bridge the two routers. So to avoid having to change all the settings back to original I thought of Wingate. I have installed it on the server and it shows all my users etc….. What I am concerned with is when we connect from outside the network the connection goes into the SMC router and then gets forwarded into the linksys. We have a static IP for our network but it forwards to the Linksys router from there to a wan/la nip and then to the server.. Make any sense to you????



Can you help?



Brian