windows routing problem

Hi all,

I have trouble setting up routing on my laptop with Windows XP Pro. Im
not sure if Windows supports the kind of routing I would like to
accomplish at all - here's the situation:

I connect to a private corporate LAN using an on-board Intel NIC
(100Mb ethernet), this interface gets a private IP address (from a
range reserved by IANA for my employer).

Apart from this connection, I also connect to the Internet using a
HSDPA PCMCIA card (ie mobile internet access).
I connect to our customer's network using Cisco VPN client, which uses
the HSDPA connection - I can not use the corporate LAN to connect to
customer's VPN server.

Now the windows routing table looks like this:

Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 10.192.1.104
10.192.1.104 1
0.0.0.0 0.0.0.0 192.168.66.27
192.168.66.26 1
XX.138.109.0 255.255.255.128 XX.138.109.120 XX.
138.109.120 20
XX.138.109.0 255.255.255.128 192.168.66.27
192.168.66.26 30
XX.138.109.120 255.255.255.255 127.0.0.1
127.0.0.1 20
XX.255.255.255 255.255.255.255 XX.138.109.120 XX.
138.109.120 20
10.192.1.104 255.255.255.255 127.0.0.1
127.0.0.1 50
10.255.255.255 255.255.255.255 10.192.1.104
10.192.1.104 50
YY.209.212.132 255.255.255.255 10.192.1.104
10.192.1.104 1
127.0.0.0 255.0.0.0 127.0.0.1
127.0.0.1 1
192.168.66.26 255.255.255.255 127.0.0.1
127.0.0.1 30
192.168.66.255 255.255.255.255 192.168.66.26
192.168.66.26 30
224.0.0.0 240.0.0.0 XX.138.109.120 XX.
138.109.120 20
224.0.0.0 240.0.0.0 192.168.66.26
192.168.66.26 30
224.0.0.0 240.0.0.0 10.192.1.104
10.192.1.104 1
255.255.255.255 255.255.255.255 XX.138.109.120 XX.
138.109.120 1
255.255.255.255 255.255.255.255 10.192.1.104
10.192.1.104 1
255.255.255.255 255.255.255.255 192.168.66.26
192.168.66.26 1
Default Gateway: 192.168.66.27
===========================================================================

XX.138.109.120 is the IP address assigned to the Intel NIC, XX.
138.109.0 is the private corporate LAN with
XX.138.109.1 being the default gateway.

10.192.1.104 is the IP address assigned to the HSDPA interface by the
mobile network provider,
YY.209.212.132 is a IP address from his address space.

192.168.66.26 is the IP address of the Cisco VPN client interface,
192.168.66.27 is the default gateway for Cisco VPN.

Currently as soon as I connect to the Cisco VPN, all the traffic gets
routed through Cisco VPN and I cannot access the private network of my
employer.

what I would like to accomplish is the following:

1.) for reaching the customers network 10.21.240.0/24, make Windows
use the Cisco VPN interface with IP address 192.168.66.26,

2.) make the Cisco VPN connection use the HSDPA connection

3.) for everything else, use my employer's network with the default
gateway XX.138.109.1.

Is this kind of routing possible in Windows XP ?
Thanks for any information & suggestions,

regards,
fb
.

Relevant Pages

  • Re: windows routing problem
    ... I have trouble setting up routing on my laptop with Windows XP Pro. ... network using Cisco VPN client, which uses the HSDPA connection - I can ... Try the following command for this: ...
    (microsoft.public.windowsxp.network_web)
  • Win2K Pro - Why does the routing table contain web IPs
    ... I have been trying to troubleshoot some network issues and in the process ... discovered that the Windows (2k Pro and XP) routing table is updated with ... Why does windows ... keep these IPs in its routing table? ...
    (microsoft.public.win2000.networking)
  • Re: How to talk ethernet to windows
    ... It also has an ethernet port, and there is a windows xp professional ... internet by routing through to the linux box, ... the wireless network. ...
    (Fedora)
  • Re: Forwarding not work in FC9 but ip forward is turn on
    ... I have tried to eliminate that route with the command ... This also happens on Windows. ... missing in your routing table. ... Can't help but wonder what that's doing to routing to the>192.168.10 network on the machine. ...
    (Fedora)
  • Re: RRAS NAT Block Outgoing Port?
    ... Under NAT/Basic Firewall (assuming this is windows 2003), right click on the WAN and select Properties. ... Select Source network, ... In the Select Routing Protocol dialog box, click NAT/Firewall, and then click OK. ...
    (microsoft.public.windows.server.networking)
Loading