Re: 1 way remote desktop

From: Sooner Al (SoonerAl_at_somewhere.net.invalid)
Date: 08/28/04 

Date: Sat, 28 Aug 2004 08:21:50 -0500

When you test this over your local LAN, make sure your calling using the private LAN IP of the PC
your trying to connect to, NOT the public IP of the router.

Yes you should see TCP Port 3389 LISTENING in the netstat -a listing...Do you? If not, is Remote
Desktop enabled on the desktop PC? If you run services.msc from the "Start -> Run" command line is
the Terminal Services service running?

Forget about using the web based method until you get the normal RDP link working over your local
LAN.

Are you running any other personal firewall software on the desktop?

Note that port forwarding on the router has no bearing on connecting over the local LAN. 

-- 
    Al Jarvi (MS-MVP Windows Networking)
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...
<anonymous@discussions.microsoft.com> wrote in message 
news:1c1601c48cfc$daa218c0$a601280a@phx.gbl...
> Firstly response:
> I have tried with the xp provided firewall on and off on
> both pc's.  when I had it on, I selected an exception for
> remote desktop to let it through, but no luck either way
>
> Secondly response:
> both machines are behind the router I believe.  I have to
> go through the router to get to the internet from
> either.  But I have to go thru the router to get from 1
> machine to the other.  Not sure if that is what you meant
> below??
>
> Do not believe I have changed the listening port on the
> pc. should I see listening on port 80, 3389 if I do a
> netstat -a in console window ?
>
> Lastly response:
> I have port forwarding set in router to go to the ip of
> the desktop (192.168.0.2)
>
> I am not offsite.  I am trying to use my LAN to go from
> laptop to desktop and run desktop from another room in
> house.  I tried both the desktop pc name and ip address
> (above).  I do not have a static public ip address
>
> The error msg is as follows:
> The client could not connect to the remote computer
>
> Remote connections might not be enabled or the computer
> might be too busy to accept new connections
> It is also possible that network problems are preventing
> your connection
>
> Please try connecting again later.  If the problem
> continues, contact your administrator
>
>
>
> Unfortunately that is me and I don't know how to fix !
>
>
> Thanks
> Bob
>
>
>>-----Original Message-----
>>nayborbob wrote:
>>> I have 2 wxp pro pc's - 1 laptop, 1 desktop.  I have
>>> netgear mr814 wireless router connected to desktop and
>>> wireless usb adapter for laptop.  Have set up a network
>>> and can share files and get to internet from laptop.
>>>
>>> I can remote desktop from the desktop to the laptop (ie
>>> run the laptop from desktop), but cannot go the other
>>> way, which is what I want !
>>>
>>> I notice I cannot ping the desktop from the laptop, but
>>> can ping the laptop from the desktop !
>>>
>>> I am thinking its not a router problem, but something
> on
>>> the desktop network setup.  I did set up port
> forwarding
>>> for 3389 and 80 on the router, but does not seem to
> help.
>>>
>>> Any advice would be greatly appreciated.
>>> Getting desperater
>>
>>First off, I assume that either the firewall on the
> desktop is either off or
>>configured to allow port 3389 traffic through (should be
> a checkbox in the
>>XP firewall - SP1 or SP2.)
>>
>>Secondly, I assume that you have tried this with both
> machines behind the
>>router - so that you don't have to worry about the 3389
> forwarding.  Also -
>>you have not changed the listening port on the desktop..
>>
>>Lastly, I assume that you have the port forwarding on
> the router pointing to
>>the desktop system and the laptop is off-site and you
> are trying to remote
>>into the router's public IP address (not machine name or
> private IP).
>>
>>Are those assumptions correct?  What error message do
> you receive, if any?
>>
>>-- 
>><- Shenan ->
>>-- 
>>The information is provided "as is", it is suggested you
> research for
>>yourself before you take any advice - you are the one
> ultimately
>>responsible for your actions/problems/solutions.   Know
> what you are
>>getting into before you jump in with both feet.
>>
>>
>>.
>>

Relevant Pages

  • Re: what to do with local and remote users for a SBS Network?
    ... First with no real firewall I would at least use two NICs and use RRAS. ... routers at least have some limited port blocking and I would forward ... available I would put External NIC in DMZ or replace Router with inexpensive ... I would setup User 1's Laptop with Outlook over Htttp which gives him his ...
    (microsoft.public.windows.server.sbs)
  • Re: Remote works at one local...not the other
    ... the ISP and a Dynamic was assigned by the router or DHCP server. ... What I see from your network is the laptop taking ... My SMC ... SMC range of 10.1.10.10 through 253 and then port frwrd that address into the ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Remote works at one local...not the other
    ... its best to use a static IP address if you use port forwarding. ... Can you connect to the laptop using RDP from another PC on the same LAN? ... address in the SMC Router range, ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: 1 way remote desktop
    ... both machines are behind the router I believe. ... Do not believe I have changed the listening port on the ... The client could not connect to the remote computer ... >> wireless usb adapter for laptop. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Remote desktop only working with one pc
    ... if you can connect to each PC over the local LAN from another PC on ... or the DSL modem. ... If the test fails then you need to resolve the port forwarding issue. ... You can isolate further by removing the router and connecting each PC ...
    (microsoft.public.windowsxp.work_remotely)