Problem with RDT on Windows 2003 Server

Having a rather strange problem with Windows 2003 server allowing connections via RDT on the local network. It's actually happening on both of the customers servers which makes it even stranger.

I've checked System\Remote and indeed Remote Desktop is enabled on both machines. Selected Remote Users is also valid (I even created a dummy user, turned on Remote access for that user and added them to the list...no dice). Services also seem to be running properly. In addition I checked and firewall is definitely turned off on both servers.

I'm fairly sure this isn't a routing issue, but I'll briefly describe the customers network in case someone gets some inspiration here. Both servers are dual connected...they are using an RFC 1918 (10.1.0.0/16 network) address on the users side and an RFC 1918 (192.168.0.0/23) that connects to their WAN network. I'm attempting to access the servers via RDT from the 10 network side, though I'm getting the same problem when I put a machine on the 192.168.0.0 side as well. Some additional information: one of the servers is running ISA 2004 and something called Websense (I assume it's content filtering software of some kind). This server also seems to have all of the user shares on it for some odd reasons. It's using SP2. The other server is the only domain controller and is using SP1. They are also using Sophos AV system, though they still have the stub hooks for Symantec's Corporate AV.

It's the standard error message when you attempt to connect of 'The client could not connect to the remote computer'.

Any thoughts or help on this would be most appreciated.

-XT

 

Hi

Can you ping remote computer you want to remote?

Aidas

 

Yes, they are fully accessible...from each other and from independent work stations. I can ping them, I can open up shares on them, etc etc...I just don't seem to be able to RDT into either machine.

-XT

 

Ok, try few more options:
1. Start>Run type mstsc. try to use RDC to localhost. Is it working on both servers?
2. try to telnet to port 3389 from one server to another

I guess there is no hardware firewall between these server that can block TCP 3389 port? Or any IPsec policies?

Aidas