Re: Access to remote ISA 2004 server via RDP no longer working
- From: "Anthony" <anthony@xxxxxxxxxxxxxxxxxxxx>
- To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
- Date: Sun, 19 Feb 2006 14:02:15 -0700
Rob,
I sent you a response on this earlier today, however, in sorting through my
desk I have found the article that was relevant to my case: Microsoft KB
Article ID 555382.
Anthony
----- Original Message -----
From: "Rob Moore" <RMoore@xxxxxxxx>
Sent: Friday, February 17, 2006 8:30 AM
Subject: Access to remote ISA 2004 server via RDP no longer working
Hello all--
I have a remote ISA 2004 server (on Win2k3 SP1, was ISA SP1, now is ISA
SP2) at a colocation facility. I also have an ISA 2004 server (on Win2k3
SP1, ISA SP1) here in the building. Behind the remote ISA server is a
web server. There is a VPN connection between the two ISA servers.
Up until this week, I have been able to RDP from here to both remote
servers. I could RDP to both servers over the VPN or without it, for
those times when the VPN has broken.
I don't know exactly when I stopped being able to RDP. I first
discovered it this week, right after I applied the latest MS security
patches to my computer. I was then going about applying them to my
servers. I got into and applied them to the remote web server. But I
couldn't get into my remote ISA server. I can still RDP to the remote
web server, both over the VPN and not over the VPN. When I try to RDP to
the ISA server, I get this error at my workstation:
"Remote Desktop Disconnected
The client could not connect to the remote computer.
Remote connections might not be enabled or the computer might be too
busy to accept new connections. Blah blah blah."
So this morning I went over to the colocation facility. I monitored
attempts to get in via RDP. Then I tried applying all the MS updates
(except for ISA SP2) and rebooting. RDP attempts got the same result.
Then I tried applying ISA SP2. RDP attempts yielded the same result.
Examining the logs on the remote ISA server shows me that it is NOT now,
nor was it before, denying the connection. Instead I'm getting the
result code "0x80074e21". When I Google that, I get to a Microsoft web
page with lots of error codes, including that one on ISA, and it says "A
connection was abortively closed after one of the peers sent a RST
segment."
Does that sound familiar to anyone? Any ideas about how to approach this
problem? It's complicated by the fact that, now that RDP to the ISA
server isn't working, I have to take a 30-minute trip to the colocation
facility if I want to get my hands on the server.
One thing I didn't think of trying until I'd left the facility was
RDPing from the web server to the ISA server.
Thanks,
Rob
Other related posts:
