What are the issues with VPN and
Remote Desktop?

[ Post a follow-up to this message ]

In article <cs-dnVu9S7dJBwLbnZ2dnUVZ_rLinZ2d@comcast.com>, Rick Merrill wrote:
> What are the issues with VPN and
> Remote Desktop?

Not finding the machine you're trying to connect to due to DNS not resolving
the name to IP.

Mike

--
Posted via a free Usenet account from http://www.teranews.com

[ Post a follow-up to this message ]

Mike wrote:
> In article <cs-dnVu9S7dJBwLbnZ2dnUVZ_rLinZ2d@comcast.com>, Rick Merrill wr
ote: 
>
> Not finding the machine you're trying to connect to due to DNS not resolvi
ng
> the name to IP.
>
> Mike
>

Suppose I provide the IP and the port?

[ Post a follow-up to this message ]

In article <OYednR6Yl4-YTwLbnZ2dnUVZ_hzinZ2d@comcast.com>, Rick Merrill wrote:
> Mike wrote: 
>
> Suppose I provide the IP and the port?
>

The port is not important, but the IP is. Either supply the IP (and as the I
P
changes) or keep DNS through the vpn active and correct.

Mike

--
Posted via a free Usenet account from http://www.teranews.com

[ Post a follow-up to this message ]

Mike wrote:
> In article <OYednR6Yl4-YTwLbnZ2dnUVZ_hzinZ2d@comcast.com>, Rick Merrill wr
ote: 
>
> The port is not important, but the IP is. Either supply the IP (and as the
 IP
> changes) or keep DNS through the vpn active and correct.
>
> Mike
>

I know  the IP and it stays put, but I'm trying to access it via
a VPN created through SonicWall.

[ Post a follow-up to this message ]

In article < Guadnat6Wa3_pjzbnZ2dnUVZ_srinZ2d@comcast
.com>, Rick Merrill wrote:
> Mike wrote: 
>
> I know  the IP and it stays put, but I'm trying to access it via
> a VPN created through SonicWall.

My users have no issues connecting to RDP using mstsc across VPN. Are you ab
le to
connect to that box on your internal network without VPN? Is RDP enabled on 
that box?

Mike

--
Posted via a free Usenet account from http://www.teranews.com

[ Post a follow-up to this message ]

Mike wrote:
... 
>
> My users have no issues connecting to RDP using mstsc across VPN. Are you 
able to
> connect to that box on your internal network without VPN? Is RDP enabled on that b
ox?

That network has only the server and the system I'm trying to get to.  I
may have to take a laptop over and connect in order to address your
question about connecting without VPN.

I did enable Remote Desktop service (to the best of my so-called
ability) but I can't remember if I rebooted !8-)  Is there a
protocol/service/client that must be installed in the Local Area
Connector? (running Windows XP sp2 on both ends).  I will double
check those settings.

[ Post a follow-up to this message ]

In article <1c-dnXmgFt_7zD_bnZ2dnUVZ_judnZ2d@comcast.com>, Rick Merrill wrote:
> Mike wrote:
> ... 
>
> That network has only the server and the system I'm trying to get to.  I
>   may have to take a laptop over and connect in order to address your
> question about connecting without VPN.
>
> I did enable Remote Desktop service (to the best of my so-called
> ability) but I can't remember if I rebooted !8-)  Is there a
> protocol/service/client that must be installed in the Local Area
> Connector? (running Windows XP sp2 on both ends).  I will double
> check those settings.

You can check that RDP is active from another box by telnet'ing to
the windows box port 3389 (telnet $HOST 3389).

Mike

--
Posted via a free Usenet account from http://www.teranews.com

[ Post a follow-up to this message ]

Mike wrote:
> In article <1c-dnXmgFt_7zD_bnZ2dnUVZ_judnZ2d@comcast.com>, Rick Merrill wr
ote: 
>
> You can check that RDP is active from another box by telnet'ing to
> the windows box port 3389 (telnet $HOST 3389).
>
> Mike
>

Neat trick!

Sadly,
C:\>telnet 192.168.248.207 3389
Connecting To 192.168.248.207...Could not open connection to the host,
on port 3
389: Connect failed

answers to a ping however.

[ Post a follow-up to this message ]

Mike wrote:
> In article <1c-dnXmgFt_7zD_bnZ2dnUVZ_judnZ2d@comcast.com>, Rick Merrill wr
ote: 
>
> You can check that RDP is active from another box by telnet'ing to
> the windows box port 3389 (telnet $HOST 3389).
>
> Mike
>

Turns out that the "host" computer was running windows home!!!

[ Post a follow-up to this message ]