Re: VPN Routing Problem
- From: Samuria <samuria@xxxxxxxx>
- Date: Sat, 20 Aug 2005 00:36:44 +0100
On Fri, 19 Aug 2005 16:03:16 +0100, Bill Gribble
<BillG@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
First what subnets are you using on the vpn etc?
>From the client do a tracert to the ones you cant connect to.
What is needed is a default gateway setting on the client so it knows
to goto these ip via it or the other way is to add the correct route
to the clients pc by using route print from a cmd window. Do a route
print /? for a list of the commands.
If you sned a copy of things like ipconfig /all and tracert we can
better understand whats going on. The subnet could be the key. In very
simple terms the subnet is a address were the pc's shout out I am
here. If you are on the same subnet you then know were everyone is. If
its on another subnet it will never get found. It is more complicated
than that as it set the host etc but it does give you the idea.
>Kadaitcha Man <nospam@xxxxxxxxxxxxxxxxxxxx> writes
>>Bill Gribble, <BillG@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>, the errhine,
>>all-round howler monkey, and employee who makes items for sale from vacuum
>>cleaner dust-bag emptyings, moralised:
>>
>>> Been pulling my hair out trying to set up VPN access from a remote PC
>>> to my company's LAN using Kerio Winroute Firewall 6 and the VPN
>>> server and client that comes with it. The support people at Kerio are
>>> doing their best to help out, but we're not getting anywhere
>>> particularly fast, so I thought I'd ask here, as although it might be
>>> a problem with the Kerio software, it could also be an issue with the
>>> network setup on the two Windows XP Pro machines concerned....
>>>
>>> I can connect the VPN client to the VPN server successfully, and
>>> browse network resources on the server machine. I can resolve the
>>> private IP addresses from machine names of machines on the LAN from
>>> the client, but I can't ping them or connect to them to browse shares
>>> and the like.
>>> I think it's a routing problem.
>>>
>>> From the client side, the VPN server name resolves to a 172.26.79.0
>>> range ip address, which is part of the ip range allocated by the VPN
>>> server to itself and its clients. Machines on the remote LAN correctly
>>> resolve to 172.16.200.0 range ip addresses.
>>>
>>> If, from the VPN client, I ping a 172.26.79.0 address, it routes
>>> correctly through the VPN connection. If, however, I ping a
>>> 172.16.200.0 address, it (incorrectly, I believe) routes out through
>>> the client machine's default gateway (ie. The local Internet
>>> connection) and, of course, fails to reach it's destination (and my
>>> ISP's routers are probably laughing at me for trying to ping a
>>> private class ip address through the Internet).
>>>
>>> Any ideas?
>>
>>Talk to your network admins. You may need to setup LMHOSTS.
>
>I think it's a routing problem, not a name resolution problem.
>
>As I understand it, LMHOSTS would, in the absence of a working DNS,
>resolve the machine names for me to their correct IP addresses, as does
>the existing HOSTS file on the VPN Server at present, and if that
>doesn't have the answer, the DHCP lease file.
>
>But the problem is not resolving the ip addresses from their machine
>names but rather finding a route between the 172.26.79 addresses of the
>VPN client and server and the remote 172.16.200 network that the VPN is
>supposed to link the client machine to. Does LMHOSTS have a role to play
>in this?
.
- Follow-Ups:
- Re: VPN Routing Problem
- From: Bill Gribble
- Re: VPN Routing Problem
- References:
- VPN Routing Problem
- From: Bill Gribble
- Re: VPN Routing Problem
- From: Kadaitcha Man
- Re: VPN Routing Problem
- From: Bill Gribble
- VPN Routing Problem
- Prev by Date: Re oops ! (silent sound ) update
- Next by Date: Re: VPN Routing Problem
- Previous by thread: Re: VPN Routing Problem
- Next by thread: Re: VPN Routing Problem
- Index(es):
Relevant Pages
|
