We help IT Professionals succeed at work.

RDP stopped working after reboot....

wlandymore asked
Medium Priority
Last Modified: 2010-08-05
I have an ISA 2004 firewall and everything was working perfectly for a long time until the other day when I gave the box a reboot. Now everything is still working except for the RDP from my workstation into the ISA firewall itself.
I have tried RDP from external computers to internal ones and that works, RDP works into my own machine, it's just the firewall.

The rule I have for that is still there. The system policy still allows it and has my IP address, my IP address hasn't changed.....what else could be making this happen???
Watch Question

I assume the RDP service is running on the ISA itself? Just something to check out. It could be that on the reboot a dependancy service failed to start in time and didn't allow RDP to get fired off. Just a long shot.


Is that in the regular services in admin. tools?

I don't see anything there for RDP....


yeah, I can't see any service running for it and doing a netstat doesn't show 3389 as listening.

How can I re-enable that to open the port for me?
Right click on my computer
choose manage
go into services/applications
go into services
scroll down till you see TERMINAL SERVICES
right click on it and choose START
that should get you going .


yeah, that service was already started. I thought you were saying that there was a specific RDP service which I said I hadn't heard of it.

The only thing I can get from the firewall itself is when I do the logging. It shows an 'initiated' connection and then right after it just closes the connection. Like I said, I seem to have everything up and running, I'm allowed to access it via RDP as far as rules are concerned, but I don't seem to be able to get in.

I have a recent backup of the firewall configuration....maybe I should just try a restore. I really didn't want to do that though so I was hoping it was something easy I was missing.
If that service is running then your netstat -a should show 3389 listening. Your firewall logs are your only course of diagnosis at this point, from what I can tell.

(I tested the netstat -a 33889 listening on my ISA 2k4 running on Windows 2k3)

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts


Yeah, I did the restore after hours and everything came back. I don't know why this just happened after the reboot but everything's gravy now.

thanks for the help.

(I'm giving you the points since you provided good suggestions and there wasn't much of a way to predict that the restore would clear up a problem like this)
Just dang glad it worked for you. I have had issues similar with a paticular rule. I could remove the rule and re-add it and all was well. Strange in deed.
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.