Re: Remote Desktop Control thru VPN, did work! Not now (sigh)...
From: Bill Sanderson (Bill_Sanderson_at_msn.com.plugh.org)
Date: 02/12/04
- Next message: deltu: "Re: Unable to Logon Interactively"
- Previous message: John: "Speed issues"
- In reply to: Doc: "Re: Remote Desktop Control thru VPN, did work! Not now (sigh)..."
- Next in thread: Doc: "Re: Remote Desktop Control thru VPN, did work! Not now (sigh)..."
- Reply: Doc: "Re: Remote Desktop Control thru VPN, did work! Not now (sigh)..."
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 12 Feb 2004 12:09:37 -0500
Pick whichever end of the link is easiest to change--perhaps your end, for
now, and change the subnet to a different one: Say, 192.168.2.x
"Doc" <pc-dc-doc@nospam.comcast.net> wrote in message
news:uubwu2W8DHA.1936@TK2MSFTNGP12.phx.gbl...
> Bill Sanderson typed this:
>> Are the addresses at the far end of the VPN tunnel on the same subnet as
>> those on your end?
>
> Absolutely! Private Scheme - 192.168.0.xxx / the subnets on both LANS are
> default
>
>> If your target host machine is the one terminating the VPN tunnel, I'd go
>> for whatever IP address is specified in the VPN connectoid (down by the
>> clock, status, details) as the "server ip address."
>
> Yes... that is right and what I am using.
>
>
>> You've got the right instinct--you want a single pipe to put you on the
>> lan at the far end, able to address any given machine with RD--and this
>> should be possible, if you can get the IP addressing right.
>
> I'm hoping I can get it running. As I mentioned, can VPN by itself. Can
> Remote Desktop by itself, can't mix 'em. Think this could be MTU?????
>
>
>> Since this is all private addressing we are talking about (if not, why
>> not just leave off the last part if the addresses)--it'd be easier for me
>> to visualize if you could just tell us straight out what the addresses
>> are--those given out by DHCP at the host end, those you've specied for
>> the VPN use at the host end, and those in use at the client end--and
>> those that actually appear in properties of the tunnel when it's open.
>
> Sure the "client" or controlling PC is 192.168.0.XXX
> The "host" or server PC is 192.168.0.xxx
> The 'VPN' provided addresses are not DHCP selected, but manually
> entered and DO show up in the 'connectoid' in the lower right , both
> are Class C, private scheme (192.168.0.x - and NONE of the provided
> VPN IP addresses are IN USE at either end - but I AM double checking
> that!)...
>
> Many thanks... head has big bruise from beating it against the wall. If
> I come up with the answers it will be posted here. Thanks again.
>
>
>
>>>It was going so well...
>>>I've been able to setup VPN.
>>>I've been able to setup Remote Desktop Connections
>>>I've been (at one location) able to 'tunnel' the RDC thru the VPN.
>>>
>>>BUT another SITE is giving me fits. I can VPN and get connected.
>>>I can Remote Desktop Connect and have full control over the desktop
>>>behind the Netgear RP614v2 -
>>>With VPN, I've port forwarded to the defualt PORT (1723, although in
>>>the Netgear it is a preconfigured PPTP setting - but it works as VPN
>>>and I connect VPN from the remote computer instantly.
>>>
>>>UNLIKE the other setup, I CANNOT gain remote control over the desktop
>>>thru the VPN. I can get RDC to work by just bypassing VPN and opening
>>>the default port (but I will be RDC to three others and I wanted to
>>>just come thru the ONE PIPE, VPN_)...
>>>
>>>Perhaps I don't understand the TWO in combo (and it was just dumb
>>>luck that got the first one running at a different location)...
>>>I've followed the VPN client and server setup and it works.
>>>I've setup the 'server' (in the VPN chain) to "AlLOW REMOTE DESKTOP
>>>CONTROL" and used a single USER (who, BTW, is the same NAMED user
>>>and SAME given P/W as the user at the "client" end of the VPN tunnel)
>>>
>>>The Remote Desktop Connection efforts are just not connecting.
>>>I have entered several different IP addresses (in an attempt to
>>>see if ANYTHING will connect)...
>>>I initially used ONE of the ASSIGNED IP addresses that I name in
>>>the 'server side' setup for VPN - they are the same class exactly
>>>as the 'server' side LAN and, being private, the same CLASS SCHEME
>>>as the DHCP assigned 'client' IP address (provided by that end's
>>>ISP setup of that Modem/router - it is using DHCP and only three
>>>IPs are leased out). All thru the VPN, no VPN? Works nicely thru 3389.
>>>
>>>I could not connect. So tried the IP address of the "server" PC as
>>>it IS given in that LOCAL LAN - no go.
>>>I tried the OTHER (called the Client IP) address provided in the
>>>VPN server setup, no go.
>>>
>>>I did even try the IP address (static) of the WAN side of the
>>>MODEM/Router (I know, I know) and it wouldn't go.
>>>
>>>Any help is GREATLY appreciated..
>>>Thanks.
>>>--
>>>Rich "Doc" Colley
>>>
>>>mailto: pc-dc-doc@nospam.comcast.net
>>
>>
>>
>
>
> --
> Rich "Doc" Colley
>
> mailto: pc-dc-doc@nospam.comcast.net
- Next message: deltu: "Re: Unable to Logon Interactively"
- Previous message: John: "Speed issues"
- In reply to: Doc: "Re: Remote Desktop Control thru VPN, did work! Not now (sigh)..."
- Next in thread: Doc: "Re: Remote Desktop Control thru VPN, did work! Not now (sigh)..."
- Reply: Doc: "Re: Remote Desktop Control thru VPN, did work! Not now (sigh)..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
