Welcome to ISAserver.org

RDP

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 Firewall] >> Management >> RDP

Page: [1]

Message

<< Older Topic Newer Topic >>

RDP - 26.Jun.2006 2:49:53 PM

mbassie

Posts: 36
Joined: 23.Mar.2005
Status: offline

Hi,

Installed a bunch of Windows updates on my ISA server this weekend. This involved at least one reboot. Since that reboot, I'm no longer able to create an administrative RPD session to my ISA server. My machine is still present in the 'Remote Management Computers' group, nothing else changed.

Remote management through MMC works
Remote Computer Management works
Remote Desktop Connection fails with the following message:
RDP (Terminal Services) Initiated Connection Allow remote management from selected computers using Terminal Server 0x0 Internal Local Host - DFT-ISA-003 Firewall
RDP (Terminal Services) Closed Connection Allow remote management from selected computers using Terminal Server 0x80074e21 FWX_E_ABORTIVE_SHUTDOWN Internal Local Host - DFT-ISA-003 Firewall
Remote Desktop Connection to other machines

Server:
Windows Server 2003 Std, SP1
Isa Server 2004 EE + SP2 (though product version still lists 4.0.3439.50)

Binding Terminal Services to a single interface does not appear to help. I'm going to try rebooting the machine, perhaps that helps. Anything else I could try?

-M

Post #: 1

Featured Links*

RE: RDP - 26.Jun.2006 8:28:42 PM

Ashokk001

Posts: 232
Joined: 6.Oct.2005
Status: offline

mbassie,

Check to see if the "TCP/IP NetBIOS Helper" service is started on the isa server. I had this disabled and just could not get RDP to the server. Do you get the screen come up to login to isa via RDP session??

HTH,

Ashok.

(in reply to mbassie)

Post #: 2

RE: RDP - 27.Jun.2006 1:49:21 PM

mbassie

Posts: 36
Joined: 23.Mar.2005
Status: offline

TCP/IP Netbios Helper service is running, doesn't seem to be causing problems.

What's odd is that one of my users is reporting immediate connection resets to a limited number of sites - sites other users can reach without any problem.
I guess I should reboot at the end of the day. Maybe I'll get lucky :).

-M

(in reply to Ashokk001)

Post #: 3

RE: RDP - 12.Jul.2006 11:43:13 PM

jonsauter

Posts: 66
Joined: 8.Jul.2005
From: Dallas, TX
Status: offline

M,

Did you ever get a resolution to this problem? I've noticed the problem as well on a number of our servers. All of our servers this is happening on are Windows Server 2003 SP1 or R2 but it is not happening on all SP1/R2 servers. Not sure what's causing the problem, but its existed since day one on the ISA servers that were built as R2. Another server was just recently upgraded from pre-SP1 to R2, the problem began immediately following the reboot.

On the server that was upgraded we are now seeing an information event in the application log. Event: 5050, Source: IAS. To my knowledge, IAS (RADIUS) isn't installed on this server so I'm not sure why an event would be coming from that source. You seeing this error too, or is that just mine?

Anyone has any insight into this that'd be great!

(in reply to mbassie)

Post #: 4

RE: RDP - 26.Oct.2006 3:24:49 PM

mbassie

Posts: 36
Joined: 23.Mar.2005
Status: offline

Shouldn't really be ressurecting this, but the solution was annoyingly simple. In my case, RDP was unable because:

- Terminal Server on the ISA server listened on all IP addresses
- I was publishing RDP for a few hosts through the ISA server

Simply configuring the ISA server Terminal Server listener to listen only on the internal IP address -did- fix this problem when I had time to go back to it, last month. Pretty sure it's a known pbcak :)

-W

< Message edited by mbassie -- 26.Oct.2006 3:25:59 PM >

(in reply to jonsauter)

Post #: 5