RDC not working

  • Thread starter Thread starter tony
  • Start date Start date
T

tony

Here's the scenario:

Machines A & B & C - Z, all on same LAN. A is a Win
Server 2003 Standard (test machine - I'm admin of this
network and am getting ready to migrate most / all
servers to Win2003, but that's *only* relevant because
one of the two working machines is running Server2003).

B can remote to A.
A can remote to B.
Any machine C - Z can remote to B *or* A.

No machine C - Z can remote to any other machine C - Z,
and neither A nor B can remote to any machine C - Z.
This makes no sense, am I right? I've set all the XP Pro
sp1 workstations to allow remote connections, etc.
etc....what the heck can this be?

No router, so no 3389 issues. The only thing I can
possibly think of is a terminal svcs licensing issue, but
I didn't apply any licenses to machine B (the XP Pro sp1
machine that can remote to the server, and that can be
remoted to from any machine C - Z).

I hope that the scenario is clear and that I haven't made
it confusing by trying to be detailed <grin>.

Thanks for any thoughts,
tony
 
It wouldn't be a license issue - you would get an error message that
would say so...

Have you re-verified the network subnet masks on each of the machines?
This has solved the issues for others who had weird connectivity
problems.

Jeffrey Randow (Windows Net. & Smart Display MVP)
(e-mail address removed)

Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....

Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Smart Display Support - http://www.smartdisplays.net
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
 
disconnect the 2003 server, set it up as before with just
2000 servers, and see if that will work...
 
Thanks for the reply. Unfortunately, I think my use of
the term "migration" was misleading...I'm migrating from
Netware <g>. No Win2k boxes anywhere...

Should be able to RD from any, to any, WinXPPro machine
on same network, right??? Even if there were no servers
at all and all you had was IP's in the same network, no?

thanks again,
tony
 
Thanks for the reply!

Yep, I'd think the msg would ref. the license if that
were the issue, but having never seen that situation,
thought it might be a possibility...

Very small network...every machine is /24, zero
variation. Can ping from any, to any, machine on the
network--e.g. I can ping 192.168.1.103, but when I plug
that in as the RDC computer, no dice. Also, if I go into
the drop-down and choose <Browse for more...>, not a
single machine shows up--not even the ones I *can* RDC
to...very odd.

Thanks again for the reply,
tony
 
Yep, and it's often the simple solution that eludes us...I don't think so
this time, though...

Everything checks out like so:

192.168.1.35 can remote to 192.168.1.7
192.168.1.7 cannot remote to 192.168.1.35
192.168.1.7 can ping 192.168.1.35 successfully
Both 7 and 35 are set to "Allow users to connect remotely to this computer."
Both 7 and 35 are connected to ports on the same switch. Putting each
machine on the other's port makes no difference (don't laugh; you never
know).
Neither has ICF enabled.
When I bring up the Remote Desktop Connection client (on either 7 or 35),
<Browse for more...> shows no other machines. Usually not an issue because I
just type 192.168.1.7 in directly, but it's odd that it doesn't display any.

Am I right in my assumption, which is that RDC *should* work if all I had
were two XPPro workstations connected to a switch? No servers, no nothing?
The fact that I can *also* remote to 192.168.1.3, which is a Win2003 Server,
is irrelevant, right?

I disabled RDC on 192.168.1.7 and 192.168.1.35, then re-enabled just to be
sure that it was enabled on both

This is really driving me nuts.

Thanks for any help anyone can offer...

tony
 
Browsing for RD enabled boxes only works in a domain environment or if you perform a registry hack
for PCs in a work group environment.

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

Yes, I use RD all the time to administer two other XP Pro boxes on my home LAN work group
environment, one of which is my headless ICS/ICF/VPN box. No "servers" in the classic sense, ie.
2003 or 2000 for example.

Have you checked to see if RD is actually listening on TCP Port 3389 on 192.168.1.35 for example?
See if RD is actually listening on TCP Port 3389. On the target XP Pro machine go to "Start -> Run",
type 'cmd' (without the quotes). At the command line type the command 'netstat -a' (without the
quotes). Look for a line like this.

TCP <Your PC>:3389 <Your PC>:0 LISTENING

For example on my XP Pro desktop, Ashtabula, the line looks like this using the default port 3389.

TCP ashtabula:3389 ashtabula:0 LISTENING

The line should be present...If the Remote Desktop host is not running, then you will not see a line
like that and you will not be able to connect. If you run services.msc on the target machine is the
"Terminal Services" service started? Also, check the Event log to see if anything stands out when
you try to connect.

You might also try the 'telnet' test...It may tell you something...ie. is something blocking TCP
Port 3389 on the target PC for example.

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

--
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...
 
Back
Top