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 -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Hamrick Sent: Friday, October 20, 2006 9:47 PM To: [email protected] Subject: RE: [U2] UD and VPN >From the results you are getting it sounds like both networks are using the same IP scheme (for example 192.168.1.x). This would cause the telnet request to fail as the request would stay local and never cross the VPN. When the remote PC opens a VPN connection the VPN server passes a static IP for its network to the remote VPN client PC, in this case the IP scheme past is the same as your remote network. So when you telnet to the UD server, for example at 192.168.1.10, that IP scheme is the same as your local remote network; your remote PC tries to answer the telnet request itself (locally). Chances are there is not a UD server running locally at 192.168.1.10 so it fails. It never goes to the UD server on the other side. So to see if this is the case, change the IP scheme on the remote network to 192.168.100.x, set your PC to 192.168.100.1 and then connect via VPN. Try then the telnet...the network IP schemes should then be different and the telnet will work. The other servers you are connecting to probably have a different network IP scheme and that is why they are working. Paul H. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Haskett Sent: Friday, October 20, 2006 9:21 PM To: [email protected] Subject: [U2] UD and VPN When I open a VPN connection, from my Windows XP client, to another Windows 2003 server, I cannot connect (via telnet) to UniData on separate Windows 2K3 server. If I already have a telnet connection open, when the VPN connection opens the UniData telnet session is severed. I have UniVerse on the same Windows XP client and it doesn't seem to be affected. If I'm telneting to another D3 server it doesn't seem to be affected. If I telnet from a command line to another server on the internet this connection doesn't seem to be affected. I've searched through the documentation and UniAdmin and can't seem to find anything referencing this behavior. If anyone can tell me what I need to adjust to make this work I'd appreciate it. Thanks, Bill ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
