ADSL Router / ISA 2000 / Windows 2003 R2 (Terminal Services – Application Mode)
ADSL Interface: IP: 10.0.0.254/8 External Interface on ISA: IP: 10.0.0.1/8 Internal Interface on ISA: 192.168.0.1/24 Windows 2003 SP1. ISA 2000 SP2.
I’ve Publish the TS Server using Microsoft’s KB294720.
Windows 2003 R2, Terminal Services configured in Application Mode.
Accessing the Terminal Server from with in the LAN works fine with out any problems. Trying to access the Terminal Server from the Internet is where the problem starts. I’m able to connect for about 5 secs and them suddenly the session hangs and after about 30 sec I am disconnected.
I’ve deleted and recreated the “Access Rules” on the ISA box and problem maintains. Changed the RDP default Port 3389 à 5000 (reg changed) recreated the access rules and I still land up with the same result.
I am having pretty much the same issue. I have 2 Windows 2003 R2 servers, one runs ISA 2000 SP2 and the other is a Domain Controller in Remote Admin mode.
I publish RDP (3389/tcp) on the ISA server to the DC and it worked OK. THen we upgraded the ISA server. I used the ISA Import/Export tool from MS (available on isatools.org).
NOW on the NEW ISA server we can't RDP to the DC, it tries to connect and then hangs. Occationally you get the full login window but it still hangs.
We have tried recreating the RDP protocol rule and server publishing rule. We have tried changing the RDP port and making an all new rules, same thing. I have checked that RDP on the ISA server is NOT on. We've tried service and server restarts.
I have tested the MTU as per KB 314825 incoming and out going to look for black hole routes.
Other Server publishing rules work OK. Just RDP doesn't work. If I disable the rule I get no connection as expected, and if I re-enable it all I get is the initial connect (or perhaps just the yellow bar at the top). I have tried publishing a different server with RDP and it still doesn't work.
If I connect internally (LAN side) to the DC it works 100%. I believe it to be a problem with ISA. Short of a complete uninstall, and manual reconfig any suggestions?
Any one have any suggestions? Anyone know where ISA 2000 keep its rules and definitions (file or registry)? It still happened when I changed the RDP port -- does ISA do RDP filtering of some kind? Is there a way to "repair" ISA?
If I enable RDP on the ISA server (setting it so it only responds on it's Internal network card) and then change the RDP publishing rule to point to its OWN Internal network card: IT WORKS!
Since other published servers, like Radmin, on port 4899, work OK and I can connect from the ISA server's desktop via RDP to the Domain Controller with no problem this leads me to believe that ISA is doing something to RDP traffic that causes it to fail when it publishes the server.
I'm not sure if I'm any closer than I was before but I thought it was worth mentioning.