Posts: 107
Joined: 26.Feb.2004
From: UK
Status: offline
Hi there
I had to re-install a ISA 2004 Firewall machine and for various reasons went back to Windows 2003 without SP1 i have since installed SP1 and all is well except i can no longer RDP to the ISA server to administer it. I know there is a fix for this but i can't find the KB article, can anyone help by pointing me in the right direction?
I am certain i found the article on here a year or two back but lol the ISA server HTTP filter stops me from using the search facility for the forums.
Posts: 107
Joined: 26.Feb.2004
From: UK
Status: offline
Hi there
Thanks for that i'll take a look at the TSC settings next time on site (although it worked fine before) also from memory does this now mean i can only have RDP on one of the Network interfaces? I just had a funny feeling a registry hack was required to fix this the last time a i had the problem.
Hi, i was just wondering if you had found a solution to this problem as I am in the same boat w2k3 sp1 and isa 2004 sp2 and I am not able to rdp to the server. If it helps, I did realtime logging and received "FWX_E_Abortive_shutdown"
Obviously not enough sleep, I did assign the listener to my nic, in the "live" logs I noticed the same "...abortive_shutdown" as well as an attempt to RDP to the external nic
Posts: 2187
Joined: 10.Aug.2004
From: fort frances.on.ca
Status: offline
TSC = Terminal Services Configuration unless you are publishing it for access from the internet, I would think the listener should be applied to the internal NIC.
If not published, why would the request show up on the external NIC? Do you have a DNS entry for the external NIC?
_____________________________
The School of Hard Knocks is a mean teacher. She gives the exam before the lesson.
Hi, I have selected the internal nic exclusively, yet I still get attempts on the external. There is no DNS entry for the external nic. I have tried the following troubleshooting ideas: I have been able to telnet on 3389 to the server I have modified the sytem rule for mmc to allow connections from "internal" as well as my defined enterprise network I have created an array Firewall rule to allow RDP to no avail
I am able to remote from the ISA to any other server in the network, and of course to itself. but I still get the same "...abortive_shutdown" error when attempting from other servers - even those with supposed "all outbound" set to "allow" So far, sol... thanks for your help