A Real Remote Desktop Stumper

"Is this over your local LAN?" - Yes it is. I will close the port however it
wasn't working either way which is why I tried opening 3389. If I recall
correctly it was set up with the port open prior to my firmware upgrade and
was working fine, but I'm not 100% sure on that - it may not have been open.

"Of course you need to configure any software firewall installed on the RDP
host to allow incoming RDP requests." - I've double, triple and quadrouple
checked.

"What OS is running on the host and client?" - Both are on XP Pro

"Have you tried reflashing the router firmware?" - Does that mean holding in
the reset button on the router for 2min after the firmware upgrade? If so,
I've done that. I've also removed power for a minute and then started it up
again.
 >> Stay informed about: A Real Remote Desktop Stumper 

"Everett H. Leaper" <EverettHLeaper.TakeThisOut@discussions.microsoft.com> wrote in
message news:EF574530-8770-4840-BA4B-8BFF66681CA3@microsoft.com...
> "Is this over your local LAN?" - Yes it is. I will close the port however
> it
> wasn't working either way which is why I tried opening 3389. If I recall
> correctly it was set up with the port open prior to my firmware upgrade
> and
> was working fine, but I'm not 100% sure on that - it may not have been
> open.
>
> "Of course you need to configure any software firewall installed on the
> RDP
> host to allow incoming RDP requests." - I've double, triple and quadrouple
> checked.
>
> "What OS is running on the host and client?" - Both are on XP Pro
>
> "Have you tried reflashing the router firmware?" - Does that mean holding
> in
> the reset button on the router for 2min after the firmware upgrade? If so,
> I've done that. I've also removed power for a minute and then started it
> up
> again.
>

OK....

So your calling the correct IP address for the host?

Is Remote Desktop enabled on the host?

Can you connect to the host from another PC on the same LAN?

Can you connect to a different host from the client?

Is Remote Desktop actually listening on the host on TCP Port 3389?

http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetup...Trouble

--

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...
 >> Stay informed about: A Real Remote Desktop Stumper 

"So your calling the correct IP address for the host?" - Yes

"Is Remote Desktop enabled on the host?"- Yes

"Can you connect to the host from another PC on the same LAN?" - Don't have
one

"Can you connect to a different host from the client?" - Don't have one

"Is Remote Desktop actually listening on the host on TCP Port 3389?

http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetup...Trouble"
" - Yes, I ran the test, it seems to be listening.

However, on that last question I followed another link on the page to a
telnet test microsoft has posted...
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q187628

I think this mayhave told me something, I'm just not sure what to make of it.

All points below pertain:
1) I get no error when I telent to the host and when "tserv" is the host
name. However nothing shows up on the host computer.

2) I do get an error and I guess therefore CANNOT telnet when "tserv" is the
ip address

3) I CAN telnet when "tserv" is both the ip address and the (intended)
client name.

Note: When i try to remote into the intened client from the intended host
(therefore switching them temporarily) it looks like I can log in but I only
get a blank black screen.


I hope I was able to quantify all of that well enough for a response...
 >> Stay informed about: A Real Remote Desktop Stumper 

Sorry... let me add. Point #3 (above) was conducted from the intended Host
(BBOffice) and telneting into the intended Client (LLOffice).

#1 & #2 are done from LLOffice into BBOffice, which is how I ultimately need
the remote desktop to work.
 >> Stay informed about: A Real Remote Desktop Stumper 

"Everett H. Leaper" <EverettHLeaper.TakeThisOut@discussions.microsoft.com> wrote in
message news:303A316F-E9E8-4B0B-B176-6455F2848368@microsoft.com...
> Sorry... let me add. Point #3 (above) was conducted from the intended Host
> (BBOffice) and telneting into the intended Client (LLOffice).
>
> #1 & #2 are done from LLOffice into BBOffice, which is how I ultimately
> need
> the remote desktop to work.
>

Lets straighten up the names first...

The PC you want to remotely access and control is the "host" and the PC your
connecting from is the "client". So in your example you want to eventually
access and control BBOffice (the RDP "host") from LLOffice (the RDP
"client").

When you run the telnet test from LLOffice to BBOffice you can get using the
BBOffice name but not the IP.

If you telnet into LLOffice from BBOffice you can get in using both the name
and IP address.

In your previous comment you said "Yes, I ran the test, it seems to be
listening". Well, either its listening or not...

Looking at the firewall on each machine make sure the port exception for
Remote Desktop is set for "My network (subnet) only" or "Any computer". If
you have it set for a "Custom address list" then you may be blocking the
wrong address for the client. See the "Adding the port exception" section on
this page...

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

Are you running any type of software on either machine like NAV worm
protection, any anti-trojan software, OneCare Live, etc that may be blocking
incoming Remote Desktop connections?

--

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...
 >> Stay informed about: A Real Remote Desktop Stumper 

Correct on the PC names and host/client references.

The port is listening. I also verified it with a netstat command.

I do not have NAV worm, anti-trojan, OneCare, or anything of the sort. The
machines are using only the windows firewall which is configured for RD. One
has a BRAND NEW (OS) and the other is ran very tightly and clean.

I'm baffled that I still can't get this to work.


> Lets straighten up the names first...
>
> The PC you want to remotely access and control is the "host" and the PC your
> connecting from is the "client". So in your example you want to eventually
> access and control BBOffice (the RDP "host") from LLOffice (the RDP
> "client").
>
> When you run the telnet test from LLOffice to BBOffice you can get using the
> BBOffice name but not the IP.
>
> If you telnet into LLOffice from BBOffice you can get in using both the name
> and IP address.
>
> In your previous comment you said "Yes, I ran the test, it seems to be
> listening". Well, either its listening or not...
>
> Looking at the firewall on each machine make sure the port exception for
> Remote Desktop is set for "My network (subnet) only" or "Any computer". If
> you have it set for a "Custom address list" then you may be blocking the
> wrong address for the client. See the "Adding the port exception" section on
> this page...
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;875357
>
> Are you running any type of software on either machine like NAV worm
> protection, any anti-trojan software, OneCare Live, etc that may be blocking
> incoming Remote Desktop connections?
>
> --
>
> 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...
>
 >> Stay informed about: A Real Remote Desktop Stumper 

Also: the port exception for Remote Desktop is set for and "any computer"
 >> Stay informed about: A Real Remote Desktop Stumper 

"Everett H. Leaper" <EverettHLeaper.TakeThisOut@discussions.microsoft.com> wrote in
message news:32688EDB-15BE-43D3-9E4B-1E66B48066D8@microsoft.com...
> Also: the port exception for Remote Desktop is set for and "any computer"

Is either PC a laptop? If so can you bring it to a friends or family members
house and try to connect to a different PC with RDP?

Any chance you have a friend or family member with a laptop that they can
bring over to your place and test from their machine?

Are both computers connecting wirelessly to the router or just one? Have you
tried connecting both via wired Ethernet connections and retesting?

--

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...
 >> Stay informed about: A Real Remote Desktop Stumper 

well both computers can connect to my office via RD. Granted the host at my
office is a server 2003 and not a regular PC, also it's not on my local
network... but both can connect. Wouldn't that suggest that it's either the
host computer with a fault or my network?

LLOffice is a wireless notebook. BBOffice is a wired & wireless desktop.


"Sooner Al [MVP]" wrote:

> "Everett H. Leaper" <EverettHLeaper.TakeThisOut@discussions.microsoft.com> wrote in
> message news:32688EDB-15BE-43D3-9E4B-1E66B48066D8@microsoft.com...
> > Also: the port exception for Remote Desktop is set for and "any computer"
>
> Is either PC a laptop? If so can you bring it to a friends or family members
> house and try to connect to a different PC with RDP?
>
> Any chance you have a friend or family member with a laptop that they can
> bring over to your place and test from their machine?
>
> Are both computers connecting wirelessly to the router or just one? Have you
> tried connecting both via wired Ethernet connections and retesting?
>
> --
>
> 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...
>
 >> Stay informed about: A Real Remote Desktop Stumper 

"Everett H. Leaper" <EverettHLeaper.DeleteThis@discussions.microsoft.com> wrote in
message news:1294A08E-8895-4FA5-8162-92DF2E4F7B24@microsoft.com...
> well both computers can connect to my office via RD. Granted the host at
> my
> office is a server 2003 and not a regular PC, also it's not on my local
> network... but both can connect. Wouldn't that suggest that it's either
> the
> host computer with a fault or my network?
>
> LLOffice is a wireless notebook. BBOffice is a wired & wireless desktop.
>
>
>
Well, I would try...

1. Connect the LLOffice notebook to the router via a wired Ethernet
connection and its wireless NIC is disabled.
2. Make sure the BBOffice PC is connected to the router via a wired Ethernet
connection and its wireless NIC is disabled.
3. Test Remote Desktop both ways.

If you still can't make a connection I would reflash the Linksys router with
the newest firmware available. Its possible the firmware is hosed.

--

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...
 >> Stay informed about: A Real Remote Desktop Stumper 

I tried this both ways. The results are the same.

The most quanitfied status I can give...

When I ping from the host I can ping bytyping in the client's ip or computer
name.

When I ping from the client I have to type the host's computer name. The ip
does not work.

Lastly, when I try to remote into the host (using the host's computer name)
I see the computer name at the top of the screen but recieve only a
blank/black screen. It does not connect at all using the IP.



> 1. Connect the LLOffice notebook to the router via a wired Ethernet
> connection and its wireless NIC is disabled.
> 2. Make sure the BBOffice PC is connected to the router via a wired Ethernet
> connection and its wireless NIC is disabled.
> 3. Test Remote Desktop both ways.
>
> If you still can't make a connection I would reflash the Linksys router with
> the newest firmware available. Its possible the firmware is hosed.
>
> --
>
> 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...
>
 >> Stay informed about: A Real Remote Desktop Stumper