Re: Remote Desktop and VPN issues, part II

Sorry; didn't see this until just now.

\\myworkpcname would have to be in the DNS you're using for it to
properly resolve.  If you can "ping myworkpcname" and see it resolve to
the correct address, then the DNS is OK.  It doesn't have to
successfully do the ping; just the address resolution.  Many times
pinging will be blocked but the address resolution should always work.
If the name doesn't resolve to the address, you can either fiddle with
your DNS settings or just add an entry for your work PC to your hosts
file (windows\system32\drivers\etc\hosts.).

Now, even if the resolution works, there's no guarantee that remote
desktop connection (RDC) will work.  If your work network uses Network
Address Translation (NAT) the NATted address may not be routed even for
VPN users.  For that matter, they may not even allow VPN connections to
route to user-PC subnets.  There are lots of ways this can be blocked.

So trying \\my.work.pc.ipaddress may or may not work either.

But as I recall you mentioned you have a W98 PC as well and it VPNs
fine.  Does it do the RDC?  If so, does it work by name, IP, or both?

Are there other services you can access while at work or via VPN and
aren't available over the Internet in general?  An Intranet, or iSeries
Access for example?  Those may prove better tests for access than RDC.

John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787 F: +1-312-601-1782
john.jones@xxxxxxxxxx

-----Original Message-----
From: pctech-bounces@xxxxxxxxxxxx [mailto:pctech-bounces@xxxxxxxxxxxx]
On Behalf Of Dan
Sent: Thursday, February 23, 2006 3:36 PM
To: PC Technical Discussion for iSeries Users
Subject: Re: [PCTECH] Remote Desktop and VPN issues, part II

On 2/23/06, Jones, John (US) <John.Jones@xxxxxxxxxx> wrote:
>
> http://www.smallnetbuilder.com/Sections-article49-page1.php
>
> 500 for IPSec; 1723 for PPTP.
>
> AFAIK your comm will all flow over the VPN port.  The 3389 stuff will 
> be encapsulated & encrypted over the VPN tunnel and will become 3389 
> again on 'the other side' at your office.


Will check this out when I get home tonight.

BTW, FWIW, the VPN seems to "connect" fine.  I bring up the status
window, and it shows send & receive traffic.  I realize that this might
not necessarily mean anything other than my home PC "sees" my office PC.

Also, after VPN connects, I click Start/Run and enter: \\MyWorkPCname
and eventually get "Computer (???or server???) not found" message.
Could I also try using my work PC's IP address?

- Dan
--
This is the PC Technical Discussion for iSeries Users (PcTech) mailing
list To post a message email: PcTech@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/pctech
or email: PcTech-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/pctech.


This email is for the use of the intended recipient(s) only.  If you have 
received this email in error, please notify the sender immediately and then 
delete it.  If you are not the intended recipient, you must not keep, use, 
disclose, copy or distribute this email without the author's prior permission.  
We have taken precautions to minimize the risk of transmitting software 
viruses, but we advise you to carry out your own virus checks on any attachment 
to this message.  We cannot accept liability for any loss or damage caused by 
software viruses.  The information contained in this communication may be 
confidential and may be subject to the attorney-client privilege. If you are 
the intended recipient and you do not wish to receive similar electronic 
messages from us in future then please respond to the sender to this effect.