Bill; Paul's info was good, just incomplete because of some of the details you were missing.
The problem is what the VPN connection is doing to your routing table. It's likely telling your machine to look through the VPN "adapter" to find anything on the 192.168.1.0 network. Of course, your UD server isn't out there. Since, you can still connect properly to other external addresses it doesn't sound like it using the adapter as the default gateway (VPN connection, properties, TCP/IP properties, Networking, Advanced), but it is possible. I usually turn this off. You do have to be careful with which IP address it gives you as a client before turning it off. Not being a network guru, I haven't figured out a way to modify what a VPN does to your routing table. However, a quick and dirty fix may be to simply add a permanent route to tell your computer how to get to the UD server without going through the VPN. Something like (at the command prompt): ROUTE -p ADD 192.168.1.12 MASK 255.255.255.255 192.168.1.1 You may want to try without the -p flag first (which creates a permanent route) to make sure it works properly first. Notes: I am just guessing at the 192.168.1.1 address. A ROUTE PRINT (prior to the VPN connection) will show the correct address. Good luck Colin Alfke Calgary Canada >-----Original Message----- >From: Bill Haskett > >Paul: > >The VPN is going out the local network to 69.xxx.xxx.xxx. My >AccuTerm connection to UniVerse, on my local machine, is to IP >"MyMachine", which has a >"C:\Windows\system32\drivers\etc\hosts" entry of 192.168.1.51. > My AccuTerm connection to D3, on my local machine, is to IP >"127.0.0.1". >Another AccuTerm connection out of our network to >209.xxx.xxx.xxx is working. > >The VPN client mostly set itself up and now my AccuTerm >connection to the 69.xxx.xxx.xxx machine connects to >192.168.1.3 (I don't know if it knew there wasn't such an >address assigned to my internal network or not). > >Once the VPN is connected, I can telnet to 192.168.1.51 (my >machine) from anywhere on the network. I can telnet to >192.168.1.3 and I get to the machine on the other end of the >VPN. I just can't telnet to 192.168.1.12 (the UniData server). > >Am I missing something here within your explanation? > >As always, thanks, > >Bill ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
