Re: RD Quit

Tech-Archive recommends: Fix windows errors by optimizing your registry

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

Date: Sat, 2 Oct 2004 17:11:27 -0500

So...Using the regular Remote Desktop client, ie. not the web based method...

1. Can you connect to the target PC from another PC on your local LAN using the target PCs LAN IP or
its network name?
2. If so, then RD is working Ok.
3. If not, the RD is not setup correctly or a personal firewall is running on the target PC or
something else is going on.

4. If you can connect in step 1 above, then does the telnet test work from a remote location? 

-- 
    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:%23sp$LKMqEHA.3936@TK2MSFTNGP10.phx.gbl...
> Try the telnet test while the laptop is connected to the dialup. Check forwarding on the 
> router...etc...etc...etc...
>
> -- 
>    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...
>
> "EllenR" <EllenR@discussions.microsoft.com> wrote in message 
> news:9C06193F-62A6-4FBC-AF89-D273A4856D72@microsoft.com...
>> ok--I connected via dialup and still cannot get in.  However, I HAVE been
>> connecting via the dyndns alias when I was not at a remote location--i.e.,
>> sitting in the same seat under all of the same conditions, clicking the same
>> buttons.  That is what makes this so strange.  Tuesday morning it worked,
>> Tuesday afternoon it didn't.
>>
>> "Sooner Al" wrote:
>>
>>> If your trying to test from a PC on your local LAN to another PC on the same LAN, you can *NOT* 
>>> use
>>> the public IP or dyndns alias of the router. Testing on the local LAN only works using the 
>>> private
>>> LAN IP or the PC name. To test using the public IP or dyndns alias you must be at a remote 
>>> location.
>>> You could use a dial modem on a laptop for example, connect into your ISP by dialup and then 
>>> connect
>>> via the broadband Linksys routers public IP or dyndns alias...
>>>
>>> -- 
>>>     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...
>>>
>>> "EllenR" <EllenR@discussions.microsoft.com> wrote in message
>>> news:F4543FD9-32BB-41B5-903A-DDABB6582ABA@microsoft.com...
>>> > Not exactly--I am on a wireless laptop at home trying to connect to my
>>> > desktop downstairs.  The regular Remote Desktop
>>> > (Start/Programs/accessories/communications/Remote Desktop Connection) is what
>>> > used to work but has stopped.  I need to get it fixed before I leave town
>>> > again.
>>> >
>>> > "Sooner Al" wrote:
>>> >
>>> >> Ok...so you are trying to connect to a work PC from home through a Linksys router and using 
>>> >> the
>>> >> web
>>> >> based method, is that correct?
>>> >>
>>> >> Since the telnet test works, from your home PC to the work PC, then does the regular Remote
>>> >> Desktop
>>> >> client work, ie. don't use the web based method, from home?
>>> >>
>>> >> -- 
>>> >>     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...
>>> >>
>>> >> "EllenR" <EllenR@discussions.microsoft.com> wrote in message
>>> >> news:6B4D3E6C-5912-49AA-A465-E8F84FEB1314@microsoft.com...
>>> >> >I tried the telnet test and it worked (using the port # (my birthday) that I
>>> >> > port-forwarded long ago for this purpose).  Also, I am not at a work location
>>> >> > (I am at home trying to get it to work, so a change at work is NA.
>>> >> >
>>> >> > "Sooner Al" wrote:
>>> >> >
>>> >> >> I forgot to add... Run this telnet test to see if you can pinpoint the problem
>>> >> >>
>>> >> >> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q187628
>>> >> >>
>>> >> >> Also, if your trying to connect from a work location to your home its always possible your
>>> >> >> employer
>>> >> >> has started blocking TCP Port 3389 outbound. You need to check with your work/office 
>>> >> >> network
>>> >> >> administrators about that issue... One way to test that is to try Remote Desktop from a
>>> >> >> friends
>>> >> >> house. If you can connect then that pretty much points to work blocking the port 
>>> >> >> outbound...
>>> >> >>
>>> >> >> -- 
>>> >> >>     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:OqCNQoHqEHA.1164@TK2MSFTNGP10.phx.gbl...
>>> >> >> > So you can connect over your local LAN from another PC on the LAN by both IP and name? 
>>> >> >> > If
>>> >> >> > so...
>>> >> >> >
>>> >> >> > What Linksys router?
>>> >> >> > Have you tried a simple power reset of the router?
>>> >> >> > Any changes made in the routers port forwarding that you don't know about?
>>> >> >> >
>>> >> >> > -- 
>>> >> >> >    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...
>>> >> >> >
>>> >> >> > "EllenR" <EllenR@discussions.microsoft.com> wrote in message
>>> >> >> > news:4CC1978C-4176-4DC9-B655-E12CB5E1BAE1@microsoft.com...
>>> >> >> >>I have been using RD for months, connecting using Remote Desktop Connection.
>>> >> >> >> Suddenly I get msg "the client could not connect...."   I am running XPpro
>>> >> >> >> SP1 on both machines.  Host is on a network using a linksys router.  I do
>>> >> >> >> have a dynamic ip, but use a proxy name thru dyndns (but have checked current
>>> >> >> >> ip and it doesn't work either).  I do not use NIS, just Norton AV.  I can
>>> >> >> >> connect using Remote Desktop Web Connection (entering
>>> >> >> >> http://192.168.1.101:nnnnn/tsweb/) but, not totally understanding everything,
>>> >> >> >> think I get in because I am within reach of my wireless home network.  To my
>>> >> >> >> knowledge, the only thing that has changed was my download of Firefox browser
>>> >> >> >> on the Host.  Even though it was not my current browser, I uninstalled it and
>>> >> >> >> reverted to a previous restore point.
>>> >> >> >
>>> >> >>
>>> >> >>
>>> >>
>>> >>
>>>
>>>
>
Quantcast