Re: How to Access Any Computer in a LAN by Remote Desktop
From: rhu (anonymous_at_discussions.microsoft.com)
Date: 05/10/04
- Next message: fahlis: "Mapped Printer Sessions remain in Printers and faxes after logout??-Win 2003!"
- Previous message: Lance: "RE: client access license could not be upgraded or renewed"
- In reply to: hallstein: "Re: How to Access Any Computer in a LAN by Remote Desktop"
- Next in thread: rhu: "Re: How to Access Any Computer in a LAN by Remote Desktop"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 10 May 2004 09:35:12 -0700
Thank you very much. Your message is very informative
and right on the point. I'll try it later and share the
results here.
rhu
>-----Original Message-----
>Hi,
>
>as I read your original post, I was surprised by the
responses you got,
>as people did not seem to get affected by the word "LAN"
(which indeed
>point out that you are behind some kind of NAT(network
address
>translation) , which makes all your clients share one IP
on the internet).
>
>Solution
>=======
>
>Finding the local port on client(s)
>
>You need to 1st check out how to define your registry.
>HKEY_LOCAL_MACHINE\SYSTEM\ControlSet\Control\Terminal
>Server\WinStations\RDP-Tcp
>Here you will find Portnumber d3d which is hex
for "3389". (this port
>is tcp)
>
>
>How one can make the NAT gateway listen for remote
desktop
>
>The NAT gateway is by default not listening for any
traffic, unless it's
>specified in the routing tables. So you have to read the
manual of the
>router, and see how you can add a port redirection for a
NAT service.
>It's usually telnet'ing to your router and use
>set nat entry add [local IP] [port] [external IP]
[port] [tcp/udp]
>
>so if my public IP is 123.123.123.123 and my local
remote desktop is
>192.168.1.2 running on port 3389
>set nat entry add 192.168.1.2 3389 123.123.123.123 3494
tcp
>
>Now, on the outside of this network, all one has to do
is to connect to
>remote desktop 123.123.123.123:3494 and you will
reach that client.
>You can define more entries on different ports.
>e.g.
>set nat entry add 192.168.1.5 3389 123.123.123.123 3496
tcp
>set nat entry add 192.168.1.6 3389 123.123.123.123 3497
tcp
>set nat entry add 192.168.1.7 3389 123.123.123.123 3498
tcp
>
>Good Google search words are: NAT Remote desktop 3389
(Your-router-name)
>Good luck.
>
>
>rhu wrote:
>
>> All my computers behind the router use local IPs, such
as
>> 192.168.x.x. This is exactly the question I am asking
>> about - how to access the computer in a LAN behind a
>> router or firewall.
>>
>> thx.
>>
>>>-----Original Message-----
>>>Hi,
>>>
>>>That sounds like a DNS issue. What happens if you
enter
>>
>> the IP directly?
>>
>>>--
>>>--Jonathan Maltz [Microsoft MVP - Windows Server,
>>
>> Virtual PC]
>>
>>>http://www.visualwin.com - A Windows Server 2003
visual,
>>
>> step-by-step
>>
>>>tutorial site :-)
>>>http://vpc.visualwin.com - Does <insert OS name> work
on
>>
>> VPC 2004? Find out
>>
>>>here
>>>Only reply by newsgroup. I do not do technical
support
>>
>> via email. Any
>>
>>>emails I have not authorized are deleted before I see
>>
>> them.
>>
>>>
>>><anonymous@discussions.microsoft.com> wrote in message
>>>news:a89901c435fe$638432f0$a101280a@phx.gbl...
>>>
>>>>Thank you, Jonathan. But why can I only access my
>>
>> server
>>
>>>>by entering the domain name in the login window?
Even
>>
>> I
>>
>>>>use my server's computer name (e.g.
>>>>server.mycompany.com), it can't make the connection.
>>>>
>>>>
>>>>>-----Original Message-----
>>>>>Hi,
>>>>>
>>>>>Enabling RD should be all (and if the clients are
>>
>> older
>>
>>>>than XP, install the
>>>>
>>>>>RD client)
>>>>>Enable RD:
>>>>>http://www.visualwin.com/Enable-RD/
>>>>>
>>>>>The RD Client:
>>>>>http://www.microsoft.com/downloads/details.aspx?
>>>>
>>>>displaylang=en&familyid=a8255ffc-4b4a-40e7-a706-
>>>>cde7e9b57e79
>>>>
>>>>>--
>>>>>--Jonathan Maltz [Microsoft MVP - Windows Server,
>>>>
>>>>Virtual PC]
>>>>
>>>>>http://www.visualwin.com - A Windows Server 2003
>>
>> visual,
>>
>>>>step-by-step
>>>>
>>>>>tutorial site :-)
>>>>>http://vpc.visualwin.com - Does <insert OS name>
work
>>
>> on
>>
>>>>VPC 2004? Find out
>>>>
>>>>>here
>>>>>Only reply by newsgroup. I do not do technical
>>
>> support
>>
>>>>via email. Any
>>>>
>>>>>emails I have not authorized are deleted before I see
>>>>
>>>>them.
>>>>
>>>>>
>>>>>"rhu" <anonymous@discussions.microsoft.com> wrote in
>>>>
>>>>message
>>>>
>>>>>news:a2de01c4357e$2f33eca0$a401280a@phx.gbl...
>>>>>
>>>>>>Hello,
>>>>>>
>>>>>>Is there any way to remotely access any computer in
>>
>> a
>>
>>>>LAN
>>>>
>>>>>>network by using Remote Desktop Connection and how?
>>>>>
>>>>>
>>>>>.
>>>>>
>>>
>>>
>>>.
>>>
>.
>
- Next message: fahlis: "Mapped Printer Sessions remain in Printers and faxes after logout??-Win 2003!"
- Previous message: Lance: "RE: client access license could not be upgraded or renewed"
- In reply to: hallstein: "Re: How to Access Any Computer in a LAN by Remote Desktop"
- Next in thread: rhu: "Re: How to Access Any Computer in a LAN by Remote Desktop"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|