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]
Visit: www.advantos.net
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Paul Hamrick
Sent: Monday, October 23, 2006 2:46 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] UD and VPN
Bill,
In a follow-up response from Colin, he suggests a route is being added to
your local routing table (route print) when you connect that is throwing
everything off. Let's eliminate that route during the connection of the VPN
and see what the results are?...To prevent the new default route from being
created, select Internet Protocol (TCP/IP) on the Networking tab for the
properties of the VPN connection. Click Properties, and then click Advanced.
In Advanced TCP/IP Settings, on the General tab, clear the Use default
gateway on remote network check box. Reconnect and test the telnet.
Paul H.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill Haskett
Sent: Monday, October 23, 2006 2:48 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] UD and VPN
Paul:
C:\Documents and Settings\wphaskett>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : asibill
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : pmsialaska.com
Ethernet adapter Wireless Network Connection 2:
Media State . . . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Intel(R) PRO/Wireless 2200BG
Network Connection
Physical Address. . . . . . . . . : 00-12-F0-27-DB-BD
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Mobile
Connecti on
Physical Address. . . . . . . . . : 00-11-25-AE-AF-75
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.51
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 4.2.2.2
PPP adapter Pmsi:
Connection-specific DNS Suffix . : pmsialaska.com
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.13
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 192.168.1.13
DNS Servers . . . . . . . . . . . : 192.168.1.2
Primary WINS Server . . . . . . . : 192.168.1.2
C:\Documents and Settings\wphaskett>ping 192.168.1.12
Pinging 192.168.1.12 with 32 bytes of data:
Reply from 192.168.1.12: bytes=32 time=50ms TTL=127 Reply from 192.168.1.12:
bytes=32 time=57ms TTL=127 Reply from 192.168.1.12: bytes=32 time=53ms
TTL=127 Reply from 192.168.1.12: bytes=32 time=58ms TTL=127
Ping statistics for 192.168.1.12:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round
trip times in milli-seconds:
Minimum = 50ms, Maximum = 58ms, Average = 54ms
C:\Documents and Settings\wphaskett>ping asiolywadev
Pinging AsiOlyWaDev [192.168.1.12] with 32 bytes of data:
Reply from 192.168.1.12: bytes=32 time=98ms TTL=127 Reply from 192.168.1.12:
bytes=32 time=51ms TTL=127 Reply from 192.168.1.12: bytes=32 time=49ms
TTL=127 Reply from 192.168.1.12: bytes=32 time=53ms TTL=127
Ping statistics for 192.168.1.12:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round
trip times in milli-seconds:
Minimum = 49ms, Maximum = 98ms, Average = 62ms
Thanks for your help on this.
Bill
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Paul Hamrick
Sent: Monday, October 23, 2006 9:23 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] UD and VPN
Bill, connect to the VPN and drop to DOS prompt and enter IPCONFIG /ALL and
report the results. Also, run PING 192.168.1.12 and report the results. The
IPCONFIG /ALL will tell us both the local IP assigned to your network card
and the IP address assigned to your PPP adapter (VPN adapter).
Thanks,
Paul H.
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill Haskett
Sent: Monday, October 23, 2006 11:22 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] UD and VPN
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: u2-users@listserver.u2ug.org
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: u2-users@listserver.u2ug.org
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
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
