Welcome to ISAserver.org

Publishing Problems - ISA ignoring publishing rules

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA 2006 Publishing] >> Server Publishing >> Publishing Problems - ISA ignoring publishing rules

Page: [1]

Message

<< Older Topic Newer Topic >>

Publishing Problems - ISA ignoring publishing rules - 22.Apr.2008 4:44:47 AM

nowiresmatt

Posts: 2
Joined: 22.Apr.2008
Status: offline

Gudday Folks...

I'm having problems with server publishing specifically on SMTP in this case.

The problem occurs on both enterprise arrays and standard ISA 2006 servers.

The network is a little complicated with 4 NICS - one internal, two DMZ perimeter, one External. All are subnetted tightly with /27 or /29 masks as appropriate. Network relationships are NAT in both directions. While access rules work without problems publishing rules are completely ignored no matter if they are for SMTP, DNS, or LDAP.

I was looking for the following article for insight but cannot find it.
http://www.isaserver.org/articles/2004ignoreserverpub.html

The rules are created with the standard SMTP publishing wizard using the network interface address as the listener.

It should be noted that there is also a Web Listener on 443 (as opposed to 25) on the same address if this could cause problems. I've removed the web listeners but the problem is still present.

Any suggestions would be greatly appreciated.

Cheers

Batty Matty...

"Arguing with an engineer is like wrestling with a pig in the mud -- After a while, you realize that the pig is enjoying it."

Post #: 1

Featured Links*

RE: Publishing Problems - ISA ignoring publishing rules - 22.Apr.2008 7:45:30 PM

nowiresmatt

Posts: 2
Joined: 22.Apr.2008
Status: offline

OK this is getting interesting.

I've isolated the issue down to network rule sets.

The order of the network rules is:
1 internal route to all
2 external nat to internal
3 internal nat to external

In this mode publishing the internal on external works.

Changing the order to:
1 internal route to all
2 internal nat to external
3 external nat to internal

stops the internal publishing and publishes the external on the internal interface.
The error when stopping the other publishing rule is that there is no network relationship.

This is really bizare. Surely NATING both ways should work for the publishing rules in each direction?

Any thoughts.

(in reply to nowiresmatt)

Post #: 2