Welcome to ISAserver.org

New protocol - new rule, not sticking

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA 2006 Publishing] >> Server Publishing >> New protocol - new rule, not sticking

Page: [1]

Message

<< Older Topic Newer Topic >>

New protocol - new rule, not sticking - 10.Jan.2008 4:46:19 PM

sbaldridge

Posts: 15
Joined: 2.May2004
Status: offline

I have a newly-installed ISA2006 Enterprise on Win2003sp2. From a test workstation on the external network I attempt to connect to a random port from command prompt:

telnet [ISA's external IP] 1206

As expected I see on the ISA log we are DENIED attempting to connect on "Unidentified IP traffic". No problem, I make a new protocol called TEST TCP 1206 inbound, I make a server publishing rule to publish/allow this new protocol inbound and run the test again. Still denied, still it is "Unidentified IP traffic". If I change my new publishing rule to a known protocol, say NNTP server, the rule works correctly. It will not work with any user-created protocol but will work with any existing protocols. I have rebooted this ISA server. If I look in the protocol list under user-defined protocols I see the new protocol which contains inbound port 1206. *frustrating*

I have another 2006 ISA (Std) server that works perfectly with the exact same test. This server is to be replaced with the new one so all configurations, networks, etc are the same. Creating new protocols and publishing them is flawless.

How can I troubleshoot why the new ISA 2006 will not identify a user-created protocol as anything but "Unidentified"? It's as if the information is not being written to a config.

Thanks for your help,

Scott

Post #: 1

Featured Links*

RE: New protocol - new rule, not sticking - 28.Jan.2008 10:41:53 AM

sbaldridge

Posts: 15
Joined: 2.May2004
Status: offline

Solved: This was all caused because the network relationship messed up. The perimeter network needs to route, I had it set on NAT which must be the default. Talk about cryptic error messages.

(in reply to sbaldridge)

Post #: 2