Bill; The problem is that both networks use the same IP subnet. Think two cities with the same street numbers (or phone numbers with different area codes). The system needs some way to figure out which way to go. The problem is that MS makes it easy for the home (non-network) user by defaulting everything to use the "remote" network. I.e. the user dials an ISP to connect to the internet. I guess MS expects office (network) users to have someone that has paid MS for certification ;-) and knows how to figure this out.
The best way to solve this problem depends on your answers to the following questions: Are there any other resources on the remote network that you want to connect to after you make the VPN connection? Are there any resources on your office network that you want to connect to after you make the VPN connection? Is it possible to change the IP addressing schemes on either network? What is happening is that once the VPN connects is that it is saying that when your PC needs to connect to anything starting with 192.168.1. should use the VPN connection. Since your UD server is on that subnet it looks for it over the VPN (you may have noticed that your e-mail doesn't work as well). There may be a way to control the routes that are generated by the VPN - but it's way beyond my limited knowledge. Fortunately I've never hit the problem you have with the remote network using the identical subnet (which is odd as 192.168.1.0 is pretty standard). My quick and dirty solution was to add a route to tell your PC that when you want to connect to the 192.168.1.12 address to use your local network and not the VPN. Quick correction, try: ROUTE ADD 192.168.1.12 MASK 255.255.255.255 192.168.1.51 If that works you can add the -p flag so that you don't have to keep entering it. Hopefully that will override the routes the VPN creates. Another way would be to delete the routes that the VPN creates and add one for whichever (192.168.1.3?) server that you need to connect to on the remote network. Hence my questions on which network you need more access to. I would put all of the route statements in a bat file and run it after connecting. Hth Colin Alfke Calgary Canada >-----Original Message----- >From: Bill Haskett > >Paul: > >Telnet still doesn't work. Here's the "route print" results after I >unchecked the "Use default gateway on remote network" checkbox: > >BEFORE VPN CONNECTION: > >C:\Documents and Settings\wphaskett>route print >======================================================================= ==== >Interface List >0x1 ........................... MS TCP Loopback interface >0x2 ...00 12 f0 27 db bd ...... Intel(R) PRO/Wireless 2200BG Network Connection >- Packet Scheduler Miniport >0x3 ...00 11 25 ae af 75 ...... Intel(R) PRO/1000 MT Mobile Connection - >Packet >Scheduler Miniport >======================================================================= ==== >======================================================================= ==== >Active Routes: >Network Destination Netmask Gateway >Interface Metric > 0.0.0.0 0.0.0.0 192.168.1.1 192.168.1.51 1 > 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 > 192.168.1.0 255.255.255.0 192.168.1.51 192.168.1.51 10 > 192.168.1.51 255.255.255.255 127.0.0.1 127.0.0.1 10 > 192.168.1.255 255.255.255.255 192.168.1.51 192.168.1.51 10 > 224.0.0.0 240.0.0.0 192.168.1.51 192.168.1.51 10 > 255.255.255.255 255.255.255.255 192.168.1.51 192.168.1.51 1 > 255.255.255.255 255.255.255.255 192.168.1.51 2 1 >Default Gateway: 192.168.1.1 >======================================================================= ==== >Persistent Routes: > None > > >AFTER VPN CONNECTION: > >C:\Documents and Settings\wphaskett>route print >======================================================================= ==== >Interface List >0x1 ........................... MS TCP Loopback interface >0x2 ...00 12 f0 27 db bd ...... Intel(R) PRO/Wireless 2200BG Network Connection >- Packet Scheduler Miniport >0x3 ...00 11 25 ae af 75 ...... Intel(R) PRO/1000 MT Mobile Connection - >Packet >Scheduler Miniport >0x80005 ...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.168.1.1 192.168.1.51 1 > 69.xxx.xxx.xxx 255.255.255.255 192.168.1.1 192.168.1.51 1 > 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1 > 192.168.1.0 255.255.255.0 192.168.1.51 192.168.1.51 10 > 192.168.1.0 255.255.255.0 192.168.1.15 192.168.1.15 1 > 192.168.1.15 255.255.255.255 127.0.0.1 127.0.0.1 50 > 192.168.1.51 255.255.255.255 127.0.0.1 127.0.0.1 10 > 192.168.1.255 255.255.255.255 192.168.1.15 192.168.1.15 50 > 192.168.1.255 255.255.255.255 192.168.1.51 192.168.1.51 10 > 224.0.0.0 240.0.0.0 192.168.1.15 192.168.1.15 50 > 224.0.0.0 240.0.0.0 192.168.1.51 192.168.1.51 10 > 255.255.255.255 255.255.255.255 192.168.1.15 192.168.1.15 1 > 255.255.255.255 255.255.255.255 192.168.1.15 2 1 > 255.255.255.255 255.255.255.255 192.168.1.51 192.168.1.51 1 >Default Gateway: 192.168.1.1 >======================================================================= ==== >Persistent Routes: > None > >I'll have to read Colin's note a little more carefully, but >thought Windows >would spare me the trouble of digging in by hand. :-0 > >Bill Haskett >Advantos Systems, Inc. >"What Software can be." >4370 La Jolla Village Drive, Suite 400 >San Diego, CA 92122 > >* 360-923-4838 (WA) >* 760-944-5570 (CA) >[EMAIL PROTECTED] ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
