was
the
phone. with a dial !
Allen 'in 83 degree SoCal, light breeze and clear skies' Elwood
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
[EMAIL PROTECTED]
Sent: Tuesday, October 24, 2006 12:24
To: u2-users@listserver.u2ug.org
Subjec
Tuesday, October 24, 2006 12:24
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] UD and VPN
No problem. I wish we had one too. I've learned from the school of hard
knocks. The number of methods that we use to connect is silly.
Everything from straight telnet, Remote Desktop, RAS, propri
No problem. I wish we had one too. I've learned from the school of hard
knocks. The number of methods that we use to connect is silly.
Everything from straight telnet, Remote Desktop, RAS, proprietary
dial-up, PcAnywhere, various VPN's (MS, Cisco, Novell, Nortel,
Contivity), Citrix, Webex, GotoMyP
, October 24, 2006 6:49 AM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] UD and VPN
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
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 ev
s.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 lo
elnet.
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 Confi
um = 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 an
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 se
,
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
hing 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 ge
>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
f
12 matches
Mail list logo
