Re: Can't establish remote desktop

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

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


Date: Thu, 11 Nov 2004 06:44:16 -0600

I forgot to add... Concerning the browse issue... Normally, in a work group environment you can not
browse for RDP hosts... If you really want/need to do that look at this registry hack...Reboot the
PC once the change to the registry has been made.

READ THESE TWO KB ARTICLE FIRST!!!!!!

http://support.microsoft.com/default.aspx?scid=kb;EN-US;256986
http://support.microsoft.com/default.aspx?scid=kb;EN-US;322756

The registry hack...

http://support.microsoft.com/default.aspx?scid=kb;en-us;281307

-- 
    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...
"Sooner Al" <SoonerAl@somewhere.net.invalid> wrote in message 
news:egbj8V%23xEHA.1204@TK2MSFTNGP10.phx.gbl...
> If you want to use TCP Port 82 for IIS did you also configure IIS for the new port? This old 
> thread has help for changing the IIS port to something other than the default TCP Port 80...
>
> http://groups.google.com/groups?hl=en&lr=&c2coff=1&frame=right&th=94cb220b2a08b3da&seekm=uFR9NbFVEHA.3692%40TK2MSFTNGP09.phx.gbl#link3
>
> Use the form http://PC_Address:82/tsweb/
>
> ...to call...
>
> Once you get this working over the private LAN, then be aware you also need to forward both the 
> new IIS port, TCP Port 82 in your case, and TCP Port 3389 through the router. See this page for 
> help with that...
>
> http://www.portforward.com/routers.htm
>
> Personally, I see no advantage in your case to using the web based access method. It simply 
> complicates the issue, IMHO. Try connecting with the normal Remote Desktop client to make sure 
> that works then, if you still want to, try the web based method...
>
> -- 
>    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...
>
> "Tracy" <Tracy@discussions.microsoft.com> wrote in message 
> news:EFF98141-24CB-464D-AA31-1C60C335AE4B@microsoft.com...
>>I have CPU1 (work) XP PRO on LAN with router & DSL modem, laptop @ home
>> (running XP Home) using dial-up. I have red everything applicable to my issue
>> posted here & still haven't gotten Remote Desktop working AT ALL.
>>
>> I HAVE done the following to the HOST (work) computer:
>> -Checked the box in System Properties to Allow users to connect to this
>> (HOST) computer.
>> -Selected Remote Desktop Users (complete with passwords)
>> -Used Windows Add/Remove programs to add Internet Information Services
>> Remote Desktop Web Connection
>> -Logged onto router and port forwarded 3389 to host 192.168.0.2 (host on LAN)
>> -Also port forwarded 82 to same (NOT 80 for "security")
>>
>> I HAVE done the following on the LAPTOP (client) computer:
>>
>> When I try to connect using the ip of the router (confirmed with
>> "Whatsmyip.com"), what I get is the standard "The client could not connect to
>> the remote computer. Remote connections might not be enabled or the computer
>> might be too busy..."
>>
>> When I try to connect on the LAN using the "Browse for Computers" I get
>> The WORKGROUP domain/workgroup does bot contain any Terminal servers.
>>
>> I have been working on this for 4 days now, day 2 I could log onto RD while
>> on LAN, but not internet. Tonight I added IIS and can't do squat (except get
>> remarkably frustrated).
>>  Ideally I would like to connect with dial-up from laptop directly to
>> dial-up modem in host (work) computer and use RD, but don't know if that's
>> supported. Ultimately use RD to utilize faster web access through DSL @ work.
>> Thanks in advance for all of your help and expertise.
>> Tracy
>>
>> "Russ" wrote:
>>
>>> I have set up my Office computer for remote desktop. It is using LAN and
>>> proxy. I am trying to connect from home (dial up) but no sucess. I tried to
>>> ping my office computer but no reply back. ( I have set up all the necessary
>>> settings on both computers)
>>>
>>> Any help appreciated
>>>
> 


Relevant Pages

  • Re: Cant establish remote desktop
    ... If you want to use TCP Port 82 for IIS did you also configure IIS for the new port? ... Once you get this working over the private LAN, then be aware you also need to forward both the new ... > posted here & still haven't gotten Remote Desktop working AT ALL. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Newbie to Remote Desktop.
    ... first of all you don't need to use a VPN in order to use Remote Desktop. ... You do need TCP Port 3389 open on the router and if you want to use the web based ... method then TCP Port 80 (IIS) must also be open. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Cant establish remote desktop
    ... So can you access the desktop from the laptop over the local LAN using the regular (not the web ... >> If you want to use TCP Port 82 for IIS did you also configure IIS for the new port? ... Try connecting with the normal Remote Desktop client to make sure ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Authentication does not work
    ... My host computer is connected to a router. ... From my router, I've already enabled Remote management port 8080 from any IP ... What am I doing wrong and what else should I be tweaking to make remote desktop connection work behind a router? ... If your trying to use the web based Remote Desktop method you need TCP Port ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Private LAN, Zone Alarm & Setting Up Remote Desktop - Sorta Stuck
    ... Just call the Remote Desktop (RDP) host from the RDP ... the router's hardware firewall and Zone Alarm software firewalls on ...
    (microsoft.public.windowsxp.general)