In a 10-27-2004 note, Mike Crom listed the "networks we VPN to Phila:"

10.224.2.0/24
10.224.5.0/30

10.224.10.0/23
10.224.20.0/23
10.224.30.0/23
10.224.40.0/23
10.224.45.0/24
10.224.50.0/23

10.224.164.0/24     tshuspaphimbx01.isinet.com = New e-mail Server = ...128

192.168.56.0/24

The above 10. and 192.168 networks, I don't mind.  But these networks, I would
have thought were external, Internet-addressable networks, but when you're in
the office or VPN'd in, these are not.

164.179.14.0/24

165.23.0.0/16 
165.78.200.0/24
165.78.204.0/24

# 167.68.0.0/16         my.thomson.com = 167.68.9.83
170.107.8.0/24        Thomson Healthcare (Ann Arbor?  Medstat?)

198.62.99.0/24        rs-mail = 198.62.99.81 (public = 199.x.y.z)

--------------------------------------------------------------------------------

When one VPN's in, there should be a few routes defined for clients.

- All of 10.x.y.z
- 198.62.99.0/24 for rs-mail.  Insure rs-mail resolves to the internally-routed
                               198.62.99.81, not the external 199.x.y.z address
                               (Or did Mike get confused?  www.isiremote.com is
                               199.4.155.31, which IS external.  I dunno.)
- Patolis 210.197.102.194 = ips01i
- Patolis 210.197.102.195 = ips06i

 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  netstat -r    or route print to show the routing table under Windows

 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

If you have "Use Default Gateway on Remote" box checked, your default route
goes through the VPN, which isn't what you want, 'cause then all your external,
Internet traffic (e.g. www.google.com or www.yahoo.com) will go through the
VPN and get routed out from the San Jose office, then back to you.  Awful.