Re: VPN Routing Problem

Bill Gribble, <BillG@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>, the scorched,
overjealous chode doctor, and brewer and seller of beer without a license,
plagued:

> 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

Ok. Bye.

.

Relevant Pages

  • Re: VPN clients unable to connect to other resources.
    ... gateway matches the IP of the remote client, and DNS and WINS point to the ... remote (although it takes close to a minute to connect, ... This is just regular Windows VPN, ... VPN server, remote routing and access running on the SBS 2003 server ...
    (microsoft.public.windows.server.sbs)
  • RE: Problems with connectcomputer and active directory
    ... I understand that you would like to join a remote client to the domain. ... If you have hardware VPN tunnel setup using Linksys or others, ... In this scenario you have to configure the SBS Server computer to enable ... Create a VPN connection to ISA/RRAS on the Internet ...
    (microsoft.public.windows.server.sbs)
  • RE: Remote connectivity problems
    ... do you mean you have added a remote client to SBS ... If you have hardware VPN tunnel setup using Linksys or others, ... In this scenario you have to configure the SBS Server computer to enable ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN clients unable to connect to other resources.
    ... Are you saying that an XP Home PC wouldn't be able to connect to a server share over VPN? ... Can ping the SBS but not the client PCs on the same network. ... gateway matches the IP of the remote client, ...
    (microsoft.public.windows.server.sbs)
  • Re: Secure VPN access
    ... with it's security option for the client. ... After getting the VPN connection I check the Ip settings and found the ... point to the head ISP's DNS server. ... > Computer certificates for L2TP/IPSec VPN connections ...
    (microsoft.public.windows.server.sbs)
Loading