Strange RDP client issue

[JohnB]

I'm the new admin at this company, the last guy was terminated, so I'm
having to figure out how they did some things on my own.
They have 3 different servers that users can RDP into. A mix of 2000 and XP
clients. Most clients have no problems. But I've found a few that get this
message: "the computer cannot connect to the remote computer".

It always seems to be the same server. I'll call it ServerX.
- PCs that can't connect to ServerX can connect to ServerY and ServerZ
- those PCs are at the same OS level as clients that CAN connect: XP Pro
SP3 (all the latest updates)
- ServerX OS=2003, ServerY OS=2003 and ServerZ OS = 2000
- I do not know of any problem connecting via RDP to ServerY or ServerZ.
Only ServerX

The only thing that seems consistent is that some PCs can't connect to this
one server. But a PC that can't connect is identical to a PC that can.

This is one of the odd things that I've found: I CAN connect with a
problematic PC if I use the WAN IP address to get in.
The network was setup to allow users to RDP into all 3 servers remotely. So
someone apparently created port mappings, so that you have to use a non-RPD
standard port to get into 2 of the servers remotely. So if I go to a PC on
the LAN, that can't connect to ServerX via RDP, and enter the WAN address,
colon, port number, they can connect. Makes no sense to me.... how can this
possibly be a client issue? They can remote in that way, remote into other
servers, using just an IP.
How can it be a client permissions issue? They can remote into other
servers?
Can't be a server issue, others are remoting in Ok.

Any ideas?
TIA

 

[JohnB]

I figured it out. Someone edited the registry on the terminal server, to
listen on a port other than the default 3389. Don't know why they'd do
that.


"JohnB" wrote in message
news:u3wUBe7NKHA.4700@TK2MSFTNGP05.phx.gbl...
> I'm the new admin at this company, the last guy was terminated, so I'm
> having to figure out how they did some things on my own.
> They have 3 different servers that users can RDP into. A mix of 2000 and
> XP clients. Most clients have no problems. But I've found a few that get
> this message: "the computer cannot connect to the remote computer".
>
> It always seems to be the same server. I'll call it ServerX.
> - PCs that can't connect to ServerX can connect to ServerY and ServerZ
> - those PCs are at the same OS level as clients that CAN connect: XP Pro
> SP3 (all the latest updates)
> - ServerX OS=2003, ServerY OS=2003 and ServerZ OS = 2000
> - I do not know of any problem connecting via RDP to ServerY or ServerZ.
> Only ServerX
>
> The only thing that seems consistent is that some PCs can't connect to
> this one server. But a PC that can't connect is identical to a PC that
> can.
>
> This is one of the odd things that I've found: I CAN connect with a
> problematic PC if I use the WAN IP address to get in.
> The network was setup to allow users to RDP into all 3 servers remotely.
> So someone apparently created port mappings, so that you have to use a
> non-RPD standard port to get into 2 of the servers remotely. So if I go
> to a PC on the LAN, that can't connect to ServerX via RDP, and enter the
> WAN address, colon, port number, they can connect. Makes no sense to
> me.... how can this possibly be a client issue? They can remote in that
> way, remote into other servers, using just an IP.
> How can it be a client permissions issue? They can remote into other
> servers?
> Can't be a server issue, others are remoting in Ok.
>
> Any ideas?
> TIA
>