wlandymore
asked on
RDP stopped working after reboot....
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???
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???
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.
ASKER
Is that in the regular services in admin. tools?
I don't see anything there for RDP....
I don't see anything there for RDP....
ASKER
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?
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 .
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 .
ASKER
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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)
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)
Thanks.
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.
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.