Welcome to ISAserver.org

Strange behaviour when implementing TS publish rule

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 General ] >> Server Publishing >> Strange behaviour when implementing TS publish rule

Page: [1]

Message

<< Older Topic Newer Topic >>

Strange behaviour when implementing TS publish rule - 29.Mar.2005 1:44:00 PM

janguas

Posts: 1
Joined: 29.Mar.2005
From: Barcelona
Status: offline

Tom,

Thanks for your article.

I just wanted to explain a weird behaviour we experienced on our ISA Server:

We are configuring a trihomed ISA Server, wrote a server publish rule to allow TS from an IP in the External network to a machine in our Perimeter network as you describe in your article.

But it did not work. We found these messages in the event viewer:

"
Event Type: Error
Event Source: Microsoft Firewall
Event Category: None
Event ID: 21174
Date: 3/28/2005
Time: 7:44:20 PM
User: N/A
Computer: GATEWAY
Description:
Server publishing rule [Expose TS rom EXT-DEV to External] failed because there was no valid network listener. For requests to reach the published server there must be a network relationship between the selected listener networks and the published server. Location 325.955.4.0.3439.50.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 0d 00 07 80 ...?
"

And then without any intervention:

"
Event Type: Information
Event Source: Microsoft Firewall
Event Category: None
Event ID: 14161
Date: 3/28/2005
Time: 7:46:56 PM
User: N/A
Computer: GATEWAY
Description:
Server publishing rule [Expose TS rom EXT-DEV to External] that maps 192.168.120.34:3389 TCP to 192.168.120.34:3389 for protocol [RDP (Terminal Services) Server] was applied successfully. This rule previously failed, but now completed successfully.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
"

(note that the IPs are not right, in fact its the same ip)

And it worked from then on!

Thank you,

Joaquim.