Welcome to ISAserver.org

Publish TSWEB over ISA Server

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 General ] >> Server Publishing >> Publish TSWEB over ISA Server

Page: [1]

Message

<< Older Topic Newer Topic >>

Publish TSWEB over ISA Server - 13.May2008 5:56:18 AM

tanzie

Posts: 4
Joined: 12.Jun.2007
Status: offline

hi all

I have 2 network cards for Internal and External network and its configured accordingly.

The problem that i sit with is that i have published an internal RDP server using TSWEB over ISA, but when i connect from an external client, it keeps on giving me the following error.

VBScript: Remote Desktop Disconnected, The client could not connect to the remote computer.

and when i click the ok button it just returns me back to the tsweb page where i enter details to connect to terminal server.

And i looked in ISA and it seems that it bombs out with the following error code: 0x80074e21 fwx_e_abortive_shutdown and it does not give me a comprehensive answer to were i should look to solve this problem.

one other thing should i NAT the terminal server, because the ISA firewall connects to my cisco pix. but the relevant rules are already applied onto it.

as per the article on: http://www.isaserver.org/tutorials/Publishing-Remote-Desktop-Web-Connection-Sites-ISA-Firewall-Part3.html

So what's up? What's causing the failed connection? The key is the entry in the Result Code column. Here you see that Result Code for the Closed Connection entries is 0x80074e21. If you look up this result code you'll see that it means that either the client or the server closed the connection with a TCP RST. OK, so what is a TCP RST? A TCP RST is a TCP segment (notice that TCP messages are segments, NOT packets, which is a common misuse of the language among network admins) which indicates something is wrong with the connection. A RST is sent when:

A SYN arrives for a non-existent server.
TCP wants to abort the connection.
A segment is received for which a connection doesn't exist.

The problem in our case is related to the first reason. The "non-existent server� is the absence of the RDP listener being enabled on the terminal server or remote desktop connection server (like Windows XP). When you enable terminal services listener on the terminal server, or enable remote connections to a published remote desktop server (for example, Windows XP Professional or Windows Server 2003 Admin RDP) everything will work as expected.

Can someone please explain to me more in detail, because internally the RDP listener works fine. Can it be because i have a virtual NIC for my server.

Any assistance will be highly appreciated.

regards,
tanzie