Robert L
April 4th 03, 05:37 PM
1. for the security reason, some company vpn ip range and LAN ip range are
different. for example, our vpn ip is 192.168.1.0 and LAN is 10.0.0.0, if we
don't use default gateway on remote network, we can't browse the LAN.
2. both metrics are 1 that is OK. the router will know if you go 10.0.0.0,
the router will point you to 10.1.10.113; and others will go to 192.0.2.2.
For more information, go to http://www25.brinkster.com/ChicagoTech
Please don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.
Robert Lin, CNE & MCSE
Windows & Network Support, Tips and FAQs on
http://www25.brinkster.com/ChicagoTech
This posting is provided "AS IS" with no warranties.
"Sam Santiago" > wrote in message
...
> Robert, thank you for your help, that did the trick. The routing
table
> shows that all 10.x.x.x address are sent to the VPN connection
10.1.10.113.
> Any brief reasons why this works. The description says "When checked,
data
> that cannot be sent on the local network is forwarded to the dial-up
> network.". Sounds like you would want this option checked. Also, why
isn't
> the 10.x.x.x traffic sent to the 192.0.2.1 gateway when the first entry
has
> the same metric and starts with 0.0.0.0?
>
> Here's the routing table after that is checked:
>
>
================================================== =========================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x2 ...00 08 74 07 5e c3 ...... 3Com 3C920 Integrated Fast Ethernet
> Controller (3C905C-TX Compatible) - Packet Scheduler Miniport
> 0x10004 ...00 02 b3 c4 32 99 ...... Intel(R) PRO/Wireless LAN PC Card -
> Packet Scheduler Miniport
> 0x20005 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
>
================================================== =========================
>
================================================== =========================
> Active Routes:
> Network Destination Netmask Gateway Interface
Metric
> 0.0.0.0 0.0.0.0 192.0.2.1 192.0.2.2 1
> 10.0.0.0 255.0.0.0 10.1.10.113 10.1.10.113 1
> 10.1.10.113 255.255.255.255 127.0.0.1 127.0.0.1 50
> 10.255.255.255 255.255.255.255 10.1.10.113 10.1.10.113 50
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
> 192.0.2.0 255.255.255.0 192.0.2.2 192.0.2.2 30
> 192.0.2.2 255.255.255.255 127.0.0.1 127.0.0.1 30
> 192.0.2.255 255.255.255.255 192.0.2.2 192.0.2.2 30
> 207.215.205.17 255.255.255.255 192.0.2.1 192.0.2.2 1
> 224.0.0.0 240.0.0.0 10.1.10.113 10.1.10.113 50
> 224.0.0.0 240.0.0.0 192.0.2.2 192.0.2.2 30
> 255.255.255.255 255.255.255.255 192.0.2.2 2 1
> 255.255.255.255 255.255.255.255 192.0.2.2 192.0.2.2 1
> Default Gateway: 192.0.2.1
>
================================================== =========================
> Persistent Routes:
> None
>
> ________________________________
> Sam Santiago
>
> "Robert L" > wrote in message
> ...
> > If this is the case, make sure if you unchecked "use default gateway on
> > remote network" option in the properties of the VPN connection.
> >
> > --
> > For more information, go to http://www25.brinkster.com/ChicagoTech
> >
> > Please don't send e-mail or reply to me except you need consulting
> services.
> > Posting on MS newsgroup will benefit all readers and you may get more
> help.
> >
> > Robert Lin, CNE & MCSE
> > Windows & Network Support, Tips and FAQs on
> > http://www25.brinkster.com/ChicagoTech
> > This posting is provided "AS IS" with no warranties.
> >
> > "Sam Santiago" > wrote in message
> > ...
> > > Both network cards are currently using automatic metric and the output
> > below
> > > is with automatic. I had tried setting the wireless metric to 20
> > manually
> > > since that is what the standard network card was showing when I looked
> at
> > > the routing table.
> > > ________________________________
> > > Sam Santiago
> > >
> > >
> > >
> > > "Robert L" > wrote in message
> > > ...
> > > > the problem is wireless still using 0.0.0.0 0.0.0.0
> > > > 192.0.2.1 192.0.2.2 1 after vpn. try to setup automatic
metric
> > by
> > > > going to properties of tcp/ip>Advanced. post back with the result.
> > > >
> > > > --
> > > > For more information, go to http://www25.brinkster.com/ChicagoTech
> > > >
> > > > Please don't send e-mail or reply to me except you need consulting
> > > services.
> > > > Posting on MS newsgroup will benefit all readers and you may get
more
> > > help.
> > > >
> > > > Robert Lin, CNE & MCSE
> > > > Windows & Network Support, Tips and FAQs on
> > > > http://www25.brinkster.com/ChicagoTech
> > > > This posting is provided "AS IS" with no warranties.
> > > >
> > > > "Sam Santiago" > wrote in message
> > > > ...
> > > > > When I VPN into my office network from home I cannot access
any
> > > remote
> > > > > network resources via my wireless network card. But if I VPN
using
> my
> > > > > standard built-in network card I can access resources. My local
> > network
> > > > is
> > > > > addressed with 192.0.2.x addresses and the remote office network
> > > addressed
> > > > > with 10.1.10.x.
> > > > > When I examine the routing table it appears that the Interface
> > > Metric
> > > > is
> > > > > the same for both the remote gateway and the local gateway.
Whereas
> > > when
> > > > > the standard network card is used the metric for the local gateway
> is
> > > set
> > > > to
> > > > > a higher value. So it appears that with the Wireless card traffic
> for
> > > the
> > > > > 10.1.10.x addresses are routed locally. Is this correct
> > interpretation
> > > of
> > > > > the routing tables? And how can I resolve this problem. I tried
> > > > changing
> > > > > the initial metric of the wireless card to 20, but it gets reset
> when
> > > the
> > > > > VPN connection is established. Any assistance greatly
appreciated.
> > > > > Here are the routing tables:
> > > > >
> > > > > 1) With standard network card:
> > > > > Before VPN:
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > > Interface List
> > > > > 0x1 ........................... MS TCP Loopback interface
> > > > > 0x2 ...00 08 74 07 5e c3 ...... 3Com 3C920 Integrated Fast
Ethernet
> > > > > Controller (3C905C-TX Compatible) - Packet Scheduler Miniport
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > > Active Routes:
> > > > > Network Destination Netmask Gateway
Interface
> > > > Metric
> > > > > 0.0.0.0 0.0.0.0 192.0.2.1
192.0.2.4
> > 20
> > > > > 127.0.0.0 255.0.0.0 127.0.0.1
127.0.0.1
> > 1
> > > > > 192.0.2.0 255.255.255.0 192.0.2.4
192.0.2.4
> > 20
> > > > > 192.0.2.4 255.255.255.255 127.0.0.1
127.0.0.1
> > 20
> > > > > 192.0.2.255 255.255.255.255 192.0.2.4
192.0.2.4
> > 20
> > > > > 224.0.0.0 240.0.0.0 192.0.2.4
192.0.2.4
> > 20
> > > > > 255.255.255.255 255.255.255.255 192.0.2.4 192.0.2.
4
> > 1
> > > > > Default Gateway: 192.0.2.1
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > > Persistent Routes:
> > > > > None
> > > > >
> > > > > After VPN:
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > > Interface List
> > > > > 0x1 ........................... MS TCP Loopback interface
> > > > > 0x2 ...00 08 74 07 5e c3 ...... 3Com 3C920 Integrated Fast
Ethernet
> > > > > Controller (3C905C-TX Compatible) - Packet Scheduler Miniport
> > > > > 0x20004 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > > Active Routes:
> > > > > Network Destination Netmask Gateway
Interface
> > > > Metric
> > > > > 0.0.0.0 0.0.0.0 10.1.10.107
10.1.10.107
> > 1
> > > > > ***** VPN connection is lower metric.
> > > > > 0.0.0.0 0.0.0.0 192.0.2.1
192.0.2.4
> > 21
> > > > > 10.1.10.107 255.255.255.255 127.0.0.1 127.0.0.1
> 50
> > > > > 10.255.255.255 255.255.255.255 10.1.10.107
10.1.10.107
> > 50
> > > > > 127.0.0.0 255.0.0.0 127.0.0.1
127.0.0.1
> > 1
> > > > > 192.0.2.0 255.255.255.0 192.0.2.4
192.0.2.4
> > 20
> > > > > 192.0.2.4 255.255.255.255 127.0.0.1
127.0.0.1
> > 20
> > > > > 192.0.2.255 255.255.255.255 192.0.2.4
192.0.2.4
> > 20
> > > > > 207.215.205.17 255.255.255.255 192.0.2.1
192.0.2.4
> > 20
> > > > > 224.0.0.0 240.0.0.0 192.0.2.4
192.0.2.4
> > 20
> > > > > 224.0.0.0 240.0.0.0 10.1.10.107
10.1.10.107
> > 1
> > > > > 255.255.255.255 255.255.255.255 192.0.2.4
192.0.2.4
> > 1
> > > > > Default Gateway: 10.1.10.107
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > > Persistent Routes:
> > > > > None
> > > > >
> > > > > 2) With Wireless card:
> > > > >
> > > > > Before VPN:
> > > > >
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > > Interface List
> > > > > 0x1 ........................... MS TCP Loopback interface
> > > > > 0x3 ...00 08 74 07 5e c3 ...... 3Com 3C920 Integrated Fast
Ethernet
> > > > > Controller (3C905C-TX Compatible) - Packet Scheduler Miniport
> > > > > 0xd0002 ...00 02 b3 c4 32 99 ...... Intel(R) PRO/Wireless LAN PC
> > Card -
> > > > > Packet Scheduler Miniport
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > > Active Routes:
> > > > > Network Destination Netmask Gateway
Interface
> > > > Metric
> > > > > 0.0.0.0 0.0.0.0 192.0.2.1
192.0.2.2
> > 1
> > > > > 127.0.0.0 255.0.0.0 127.0.0.1
127.0.0.1
> > 1
> > > > > 192.0.2.0 255.255.255.0 192.0.2.2
192.0.2.2
> > 30
> > > > > 192.0.2.2 255.255.255.255 127.0.0.1
127.0.0.1
> > 30
> > > > > 192.0.2.255 255.255.255.255 192.0.2.2
192.0.2.2
> > 30
> > > > > 224.0.0.0 240.0.0.0 192.0.2.2
192.0.2.2
> > 30
> > > > > 255.255.255.255 255.255.255.255 192.0.2.2
3
> > 1
> > > > > 255.255.255.255 255.255.255.255 192.0.2.2
192.0.2.2
> > 1
> > > > > Default Gateway: 192.0.2.1
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > > Persistent Routes:
> > > > > None
> > > > >
> > > > > After VPN:
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > > Interface List
> > > > > 0x1 ........................... MS TCP Loopback interface
> > > > > 0x3 ...00 08 74 07 5e c3 ...... 3Com 3C920 Integrated Fast
Ethernet
> > > > > Controller (3C905C-TX Compatible) - Packet Scheduler Miniport
> > > > > 0xd0002 ...00 02 b3 c4 32 99 ...... Intel(R) PRO/Wireless LAN PC
> > Card -
> > > > > Packet Scheduler Miniport
> > > > > 0xe0005 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > > Active Routes:
> > > > > Network Destination Netmask Gateway
Interface
> > > > Metric
> > > > > 0.0.0.0 0.0.0.0 10.1.10.148
10.1.10.148
> > 1
> > > > > *****VPN and local have same metric.
> > > > > 0.0.0.0 0.0.0.0 192.0.2.1
192.0.2.2
> > 1
> > > > > 10.1.10.148 255.255.255.255 127.0.0.1
127.0.0.1
> > 50
> > > > > 10.255.255.255 255.255.255.255 10.1.10.148
10.1.10.148
> > 50
> > > > > 127.0.0.0 255.0.0.0 127.0.0.1
127.0.0.1
> > 1
> > > > > 192.0.2.0 255.255.255.0 192.0.2.2
192.0.2.2
> > 30
> > > > > 192.0.2.2 255.255.255.255 127.0.0.1
127.0.0.1
> > 30
> > > > > 192.0.2.255 255.255.255.255 192.0.2.2
192.0.2.2
> > 30
> > > > > 207.215.205.17 255.255.255.255 192.0.2.1
192.0.2.2
> > 1
> > > > > 224.0.0.0 240.0.0.0 192.0.2.2
192.0.2.2
> > 30
> > > > > 224.0.0.0 240.0.0.0 10.1.10.148
10.1.10.148
> > 1
> > > > > 255.255.255.255 255.255.255.255 10.1.10.148
3
> > 1
> > > > > 255.255.255.255 255.255.255.255 192.0.2.2
192.0.2.2
> > 1
> > > > > Default Gateway: 192.0.2.1
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > > Persistent Routes:
> > > > > None
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Sam
> > > > > ________________________________
> > > > > Sam Santiago
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
different. for example, our vpn ip is 192.168.1.0 and LAN is 10.0.0.0, if we
don't use default gateway on remote network, we can't browse the LAN.
2. both metrics are 1 that is OK. the router will know if you go 10.0.0.0,
the router will point you to 10.1.10.113; and others will go to 192.0.2.2.
For more information, go to http://www25.brinkster.com/ChicagoTech
Please don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.
Robert Lin, CNE & MCSE
Windows & Network Support, Tips and FAQs on
http://www25.brinkster.com/ChicagoTech
This posting is provided "AS IS" with no warranties.
"Sam Santiago" > wrote in message
...
> Robert, thank you for your help, that did the trick. The routing
table
> shows that all 10.x.x.x address are sent to the VPN connection
10.1.10.113.
> Any brief reasons why this works. The description says "When checked,
data
> that cannot be sent on the local network is forwarded to the dial-up
> network.". Sounds like you would want this option checked. Also, why
isn't
> the 10.x.x.x traffic sent to the 192.0.2.1 gateway when the first entry
has
> the same metric and starts with 0.0.0.0?
>
> Here's the routing table after that is checked:
>
>
================================================== =========================
> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x2 ...00 08 74 07 5e c3 ...... 3Com 3C920 Integrated Fast Ethernet
> Controller (3C905C-TX Compatible) - Packet Scheduler Miniport
> 0x10004 ...00 02 b3 c4 32 99 ...... Intel(R) PRO/Wireless LAN PC Card -
> Packet Scheduler Miniport
> 0x20005 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
>
================================================== =========================
>
================================================== =========================
> Active Routes:
> Network Destination Netmask Gateway Interface
Metric
> 0.0.0.0 0.0.0.0 192.0.2.1 192.0.2.2 1
> 10.0.0.0 255.0.0.0 10.1.10.113 10.1.10.113 1
> 10.1.10.113 255.255.255.255 127.0.0.1 127.0.0.1 50
> 10.255.255.255 255.255.255.255 10.1.10.113 10.1.10.113 50
> 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
> 192.0.2.0 255.255.255.0 192.0.2.2 192.0.2.2 30
> 192.0.2.2 255.255.255.255 127.0.0.1 127.0.0.1 30
> 192.0.2.255 255.255.255.255 192.0.2.2 192.0.2.2 30
> 207.215.205.17 255.255.255.255 192.0.2.1 192.0.2.2 1
> 224.0.0.0 240.0.0.0 10.1.10.113 10.1.10.113 50
> 224.0.0.0 240.0.0.0 192.0.2.2 192.0.2.2 30
> 255.255.255.255 255.255.255.255 192.0.2.2 2 1
> 255.255.255.255 255.255.255.255 192.0.2.2 192.0.2.2 1
> Default Gateway: 192.0.2.1
>
================================================== =========================
> Persistent Routes:
> None
>
> ________________________________
> Sam Santiago
>
> "Robert L" > wrote in message
> ...
> > If this is the case, make sure if you unchecked "use default gateway on
> > remote network" option in the properties of the VPN connection.
> >
> > --
> > For more information, go to http://www25.brinkster.com/ChicagoTech
> >
> > Please don't send e-mail or reply to me except you need consulting
> services.
> > Posting on MS newsgroup will benefit all readers and you may get more
> help.
> >
> > Robert Lin, CNE & MCSE
> > Windows & Network Support, Tips and FAQs on
> > http://www25.brinkster.com/ChicagoTech
> > This posting is provided "AS IS" with no warranties.
> >
> > "Sam Santiago" > wrote in message
> > ...
> > > Both network cards are currently using automatic metric and the output
> > below
> > > is with automatic. I had tried setting the wireless metric to 20
> > manually
> > > since that is what the standard network card was showing when I looked
> at
> > > the routing table.
> > > ________________________________
> > > Sam Santiago
> > >
> > >
> > >
> > > "Robert L" > wrote in message
> > > ...
> > > > the problem is wireless still using 0.0.0.0 0.0.0.0
> > > > 192.0.2.1 192.0.2.2 1 after vpn. try to setup automatic
metric
> > by
> > > > going to properties of tcp/ip>Advanced. post back with the result.
> > > >
> > > > --
> > > > For more information, go to http://www25.brinkster.com/ChicagoTech
> > > >
> > > > Please don't send e-mail or reply to me except you need consulting
> > > services.
> > > > Posting on MS newsgroup will benefit all readers and you may get
more
> > > help.
> > > >
> > > > Robert Lin, CNE & MCSE
> > > > Windows & Network Support, Tips and FAQs on
> > > > http://www25.brinkster.com/ChicagoTech
> > > > This posting is provided "AS IS" with no warranties.
> > > >
> > > > "Sam Santiago" > wrote in message
> > > > ...
> > > > > When I VPN into my office network from home I cannot access
any
> > > remote
> > > > > network resources via my wireless network card. But if I VPN
using
> my
> > > > > standard built-in network card I can access resources. My local
> > network
> > > > is
> > > > > addressed with 192.0.2.x addresses and the remote office network
> > > addressed
> > > > > with 10.1.10.x.
> > > > > When I examine the routing table it appears that the Interface
> > > Metric
> > > > is
> > > > > the same for both the remote gateway and the local gateway.
Whereas
> > > when
> > > > > the standard network card is used the metric for the local gateway
> is
> > > set
> > > > to
> > > > > a higher value. So it appears that with the Wireless card traffic
> for
> > > the
> > > > > 10.1.10.x addresses are routed locally. Is this correct
> > interpretation
> > > of
> > > > > the routing tables? And how can I resolve this problem. I tried
> > > > changing
> > > > > the initial metric of the wireless card to 20, but it gets reset
> when
> > > the
> > > > > VPN connection is established. Any assistance greatly
appreciated.
> > > > > Here are the routing tables:
> > > > >
> > > > > 1) With standard network card:
> > > > > Before VPN:
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > > Interface List
> > > > > 0x1 ........................... MS TCP Loopback interface
> > > > > 0x2 ...00 08 74 07 5e c3 ...... 3Com 3C920 Integrated Fast
Ethernet
> > > > > Controller (3C905C-TX Compatible) - Packet Scheduler Miniport
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > > Active Routes:
> > > > > Network Destination Netmask Gateway
Interface
> > > > Metric
> > > > > 0.0.0.0 0.0.0.0 192.0.2.1
192.0.2.4
> > 20
> > > > > 127.0.0.0 255.0.0.0 127.0.0.1
127.0.0.1
> > 1
> > > > > 192.0.2.0 255.255.255.0 192.0.2.4
192.0.2.4
> > 20
> > > > > 192.0.2.4 255.255.255.255 127.0.0.1
127.0.0.1
> > 20
> > > > > 192.0.2.255 255.255.255.255 192.0.2.4
192.0.2.4
> > 20
> > > > > 224.0.0.0 240.0.0.0 192.0.2.4
192.0.2.4
> > 20
> > > > > 255.255.255.255 255.255.255.255 192.0.2.4 192.0.2.
4
> > 1
> > > > > Default Gateway: 192.0.2.1
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > > Persistent Routes:
> > > > > None
> > > > >
> > > > > After VPN:
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > > Interface List
> > > > > 0x1 ........................... MS TCP Loopback interface
> > > > > 0x2 ...00 08 74 07 5e c3 ...... 3Com 3C920 Integrated Fast
Ethernet
> > > > > Controller (3C905C-TX Compatible) - Packet Scheduler Miniport
> > > > > 0x20004 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > > Active Routes:
> > > > > Network Destination Netmask Gateway
Interface
> > > > Metric
> > > > > 0.0.0.0 0.0.0.0 10.1.10.107
10.1.10.107
> > 1
> > > > > ***** VPN connection is lower metric.
> > > > > 0.0.0.0 0.0.0.0 192.0.2.1
192.0.2.4
> > 21
> > > > > 10.1.10.107 255.255.255.255 127.0.0.1 127.0.0.1
> 50
> > > > > 10.255.255.255 255.255.255.255 10.1.10.107
10.1.10.107
> > 50
> > > > > 127.0.0.0 255.0.0.0 127.0.0.1
127.0.0.1
> > 1
> > > > > 192.0.2.0 255.255.255.0 192.0.2.4
192.0.2.4
> > 20
> > > > > 192.0.2.4 255.255.255.255 127.0.0.1
127.0.0.1
> > 20
> > > > > 192.0.2.255 255.255.255.255 192.0.2.4
192.0.2.4
> > 20
> > > > > 207.215.205.17 255.255.255.255 192.0.2.1
192.0.2.4
> > 20
> > > > > 224.0.0.0 240.0.0.0 192.0.2.4
192.0.2.4
> > 20
> > > > > 224.0.0.0 240.0.0.0 10.1.10.107
10.1.10.107
> > 1
> > > > > 255.255.255.255 255.255.255.255 192.0.2.4
192.0.2.4
> > 1
> > > > > Default Gateway: 10.1.10.107
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > > Persistent Routes:
> > > > > None
> > > > >
> > > > > 2) With Wireless card:
> > > > >
> > > > > Before VPN:
> > > > >
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > > Interface List
> > > > > 0x1 ........................... MS TCP Loopback interface
> > > > > 0x3 ...00 08 74 07 5e c3 ...... 3Com 3C920 Integrated Fast
Ethernet
> > > > > Controller (3C905C-TX Compatible) - Packet Scheduler Miniport
> > > > > 0xd0002 ...00 02 b3 c4 32 99 ...... Intel(R) PRO/Wireless LAN PC
> > Card -
> > > > > Packet Scheduler Miniport
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > > Active Routes:
> > > > > Network Destination Netmask Gateway
Interface
> > > > Metric
> > > > > 0.0.0.0 0.0.0.0 192.0.2.1
192.0.2.2
> > 1
> > > > > 127.0.0.0 255.0.0.0 127.0.0.1
127.0.0.1
> > 1
> > > > > 192.0.2.0 255.255.255.0 192.0.2.2
192.0.2.2
> > 30
> > > > > 192.0.2.2 255.255.255.255 127.0.0.1
127.0.0.1
> > 30
> > > > > 192.0.2.255 255.255.255.255 192.0.2.2
192.0.2.2
> > 30
> > > > > 224.0.0.0 240.0.0.0 192.0.2.2
192.0.2.2
> > 30
> > > > > 255.255.255.255 255.255.255.255 192.0.2.2
3
> > 1
> > > > > 255.255.255.255 255.255.255.255 192.0.2.2
192.0.2.2
> > 1
> > > > > Default Gateway: 192.0.2.1
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > > Persistent Routes:
> > > > > None
> > > > >
> > > > > After VPN:
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > > Interface List
> > > > > 0x1 ........................... MS TCP Loopback interface
> > > > > 0x3 ...00 08 74 07 5e c3 ...... 3Com 3C920 Integrated Fast
Ethernet
> > > > > Controller (3C905C-TX Compatible) - Packet Scheduler Miniport
> > > > > 0xd0002 ...00 02 b3 c4 32 99 ...... Intel(R) PRO/Wireless LAN PC
> > Card -
> > > > > Packet Scheduler Miniport
> > > > > 0xe0005 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > > Active Routes:
> > > > > Network Destination Netmask Gateway
Interface
> > > > Metric
> > > > > 0.0.0.0 0.0.0.0 10.1.10.148
10.1.10.148
> > 1
> > > > > *****VPN and local have same metric.
> > > > > 0.0.0.0 0.0.0.0 192.0.2.1
192.0.2.2
> > 1
> > > > > 10.1.10.148 255.255.255.255 127.0.0.1
127.0.0.1
> > 50
> > > > > 10.255.255.255 255.255.255.255 10.1.10.148
10.1.10.148
> > 50
> > > > > 127.0.0.0 255.0.0.0 127.0.0.1
127.0.0.1
> > 1
> > > > > 192.0.2.0 255.255.255.0 192.0.2.2
192.0.2.2
> > 30
> > > > > 192.0.2.2 255.255.255.255 127.0.0.1
127.0.0.1
> > 30
> > > > > 192.0.2.255 255.255.255.255 192.0.2.2
192.0.2.2
> > 30
> > > > > 207.215.205.17 255.255.255.255 192.0.2.1
192.0.2.2
> > 1
> > > > > 224.0.0.0 240.0.0.0 192.0.2.2
192.0.2.2
> > 30
> > > > > 224.0.0.0 240.0.0.0 10.1.10.148
10.1.10.148
> > 1
> > > > > 255.255.255.255 255.255.255.255 10.1.10.148
3
> > 1
> > > > > 255.255.255.255 255.255.255.255 192.0.2.2
192.0.2.2
> > 1
> > > > > Default Gateway: 192.0.2.1
> > > > >
> > > >
> > >
> >
>
================================================== =========================
> > > > > Persistent Routes:
> > > > > None
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Sam
> > > > > ________________________________
> > > > > Sam Santiago
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>