Remote operation



Jayso
07-10-2005, 12:28 AM
Does anybody know how to connect remotely to a computer that is BEHIND a
router (as in my internal IP is 10.0.0.1 and my external is something else)

I have tried by using the Windows Remote Desktop thingy and a program called
Real VNC

I believe the problem might resolve in the port number which gets changed by
the router

Thankyou for ur replies
--
Jayso

Rick \Nutcase\ Rogers
07-10-2005, 12:28 AM
Hi Jayso,

The router must be configured to forward the listening port from the
external link to the internal IP of the destination machine. For Remote
Desktop this is 3389 by default.

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP
http://mvp.support.microsoft.com/
Associate Expert - WindowsXP Expert Zone
www.microsoft.com/windowsxp/expertzone
Windows help - www.rickrogers.org

"Jayso" <jayso_chinnery@hotmail.com(nospam)> wrote in message
news:40633785-28E6-4A1E-9657-4D72ADE8578B@microsoft.com...
> Does anybody know how to connect remotely to a computer that is BEHIND a
> router (as in my internal IP is 10.0.0.1 and my external is something
> else)
>
> I have tried by using the Windows Remote Desktop thingy and a program
> called
> Real VNC
>
> I believe the problem might resolve in the port number which gets changed
> by
> the router
>
> Thankyou for ur replies
> --
> Jayso

R. McCarty
07-10-2005, 12:28 AM
Rick's right -

One other helpful solution is to have the Host machine use a
fixed IP address from the router range (192.168.1.10), then setup
the router to use persistent port forwarding on Port 3389 to the
fixed IP. Many times you'll have to have the Host machine user
get their WAN (Internet) IP and either include it in the message
field of the ticket. Then have the Guest recipient edit the ticket to
use the WAN IP.
You can get the WAN IP from the Router's Web Interface or
just use IE and go to WhatIsMyIP.Com.

"Rick "Nutcase" Rogers" <rick@mvps.org> wrote in message
news:e$WQ2dUWFHA.3620@TK2MSFTNGP09.phx.gbl...
> Hi Jayso,
>
> The router must be configured to forward the listening port from the
> external link to the internal IP of the destination machine. For Remote
> Desktop this is 3389 by default.
>
> --
> Best of Luck,
>
> Rick Rogers, aka "Nutcase" - Microsoft MVP
> http://mvp.support.microsoft.com/
> Associate Expert - WindowsXP Expert Zone
> www.microsoft.com/windowsxp/expertzone
> Windows help - www.rickrogers.org
>
> "Jayso" <jayso_chinnery@hotmail.com(nospam)> wrote in message
> news:40633785-28E6-4A1E-9657-4D72ADE8578B@microsoft.com...
>> Does anybody know how to connect remotely to a computer that is BEHIND a
>> router (as in my internal IP is 10.0.0.1 and my external is something
>> else)
>>
>> I have tried by using the Windows Remote Desktop thingy and a program
>> called
>> Real VNC
>>
>> I believe the problem might resolve in the port number which gets changed
>> by
>> the router
>>
>> Thankyou for ur replies
>> --
>> Jayso
>
>

Leythos
07-10-2005, 12:28 AM
In article <e$WQ2dUWFHA.3620@TK2MSFTNGP09.phx.gbl>, rick@mvps.org
says...
> Hi Jayso,
>
> The router must be configured to forward the listening port from the
> external link to the internal IP of the destination machine. For Remote
> Desktop this is 3389 by default.

That should come with a warning - we see hundreds of attempts per IP to
connect to 3389 every day. If running RD on a computer, and exposing it
through a router/firewall, change the default port to something not as
commonly scanned for.

VNC is a great tool and it's simple for the users to change the
listening port on, and it can use a NON-OS Account password for
authentication. As an example, you could setup VNC (or TightVNC) to
listen on port 58700 (which we never see scanned) and to use a strong
password (which is not the same password of the Windows user) and then
the person would still have to logon to the Windows station with a valid
password - that's three levels to get through before the intruder can
get to the machine.

--
--
spam999free@rrohio.com
remove 999 in order to email me


Remote operation