-I am not familiar with VPN from windows to windows.  We do VPN from Windows
XP Pro to our Cisco PIX.  One thing I always check when people are having
VPN issues is that they have actually established the VPN connection.  We
have one user who connects (clicks on the VPN link and logs in) but always
has difficulty accessing applications.  

When I have him run an "ipconfig" command from a DOS prompt, he never has an
IP address associated with the VPN connection.

He should have two separate IP addresses:

1 - His local PC address (either static or DHCP assigned)
2 - His VPN address (taken from the office DHCP server)

After he tries the connection a few times, he gets and address and
everything works.

Could it be that you are not getting an IP address for you VPN connection?

-The other issue that I have found sounds like part of your second problem.


We have had some users change the default configuration on their VPN
settings.  

In the VPN connection box -> Click Properties -> Click Networking -> Select
TCP/IP -> Click Properties -> Click Advanced -> on the General Tab -> check
(or uncheck) the Use default gateway on remote network box -> OK, OK, OK

I have found that sometimes having this box checked helps and other times I
need it unchecked???  May be someone else can tell us why? 

-The other part of your problem, loosing the connection may be related to
your cable company.  I have Comcast cable at home and they sent out a notice
a few years ago that they do NOT want home users using VPN connections.  For
that type of usage I would have to upgrade to a business class service at
over twice the price!  (I never did upgrade so I only use VPN occasionally)
I don't know if the "no VPN" rule is still enforced or not.

I hope some of this helps! 
-Bryon

-----Original Message-----
From: pctech-bounces@xxxxxxxxxxxx [mailto:pctech-bounces@xxxxxxxxxxxx] On
Behalf Of Dan
Sent: Wednesday, September 07, 2005 1:50 PM
To: PC Technical Discussion for iSeries Users
Subject: [PCTECH] Remote Desktop and VPN issues

Using Microsoft's Remote Desktop (RD) at home to connect to my PC at work. 
Work PC is WinXP Pro SP2 + all updates. Have cable internet, and use VPN to 
connect.

Home PC #1 is Win98SE with the RD software downloaded and installed. RD 
works fine.
Home PC #2 is a brand-spanking new XP Home (SP2 + all updates) box 
(finally!). VPN makes connection, but ...

a) RD never connects. VPN connection status shows it is active, but trying 
to logon to RD gives the following error:

The specified remote computer could not be found. Verify 
that you have typed the correct computer name or IP 
address, and then try connecting again.

Cause: The name or IP address of the remote computer is 
incorrect. This might be a typing error.

Solution: Try typing the name or IP address of the 
remote computer again. If you receive the same message, 
contact the server administrator to be sure you are using 
the correct name or IP address for the remote computer.

This seems strange, since I made the VPN connection, and I am using the 
exact same configuration that I'm using on my Win98SE box

b) Browsers will intermittently lose connection
("www.google.com<http://www.google.com>not found...") and the VPN
connection dialog box will appear. Since I'm not
trying to connect to work, I "cancel", but I still can't reach other web 
sites. When I do the VPN logon, I can again reach other web sites. I can 
"disconnect" the VPN and, strangely, still surf for awhile, but eventually 
the VPN connection dialog box will appear again, and nothing can be found 
until I log on again.

Assistance, gentle RTFM's, links would be GREATLY appreciated.

- Dan

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.