On the computer you want to remotely connect/access go to the
http://www.canyouseeme.org site and run the test for TCP Port 3389. Does it
pass? If not then something is blocking incoming Remote Desktop connections.

--

Al Jarvi (MS-MVP Windows - Desktop User Experience)

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
How to ask a question
http://support.microsoft.com/KB/555375

"Coin-coin le Canapin" <canapin2@gmail.com> wrote in message
news:uHDYw$KyIHA.3968@TK2MSFTNGP04.phx.gbl...
> Hello again.
> I read attentively your link. I checked all things described in this page,
> and all is well configured on my computer.
> But the remote access still doesn't work.
> When a friend tries to connect to my computer, there is no event in the
> log viewer.
> It just... Doesn't work. Nothing, no error message. :/
>
> Sooner Al [MVP] wrote:
>> The home PC, ie. the Remote Desktop [RDC] host/server, must have RDC
>> enabled. If the PC is behind a router or a firewall or both then you also
>> need TCP Port 3389 open/forwarded on the router/firewall. You call using
>> the public IP of the home PC if its directly connected to the internet or
>> the public IP of the router. So...
>>
>> What type of internet connection do you have at home, ie. cable or DSL or
>> dialup? Keep in mind many DSL modems are also routers so you either need
>> to forward TCP Port 3389 or put the device in a bridge/pass-through mode.
>>
>> Are you calling the correct address?
>>
>> Have you forwarded/opened TCP Port 3389?
>>
>> See this page for help, etc...
>>
>> http://theillustratednetwork.mvps.or...eshooting.html