Category ISA 2006

PROBLEM:

• When installing Isa 2006 on Server 2003 R2 the install fails on ADAM install. The error is: “setup failed to install ADAM”. This error pops up towards the end of the ISA install. This occurs if you have a server 2003 R2 with SP2 installed.

SOLUTIONS:

• Work Around 1 – Copy the contents of the ISA 2006 disc on the local hard drive...

I ran into an issue with my recently deployed ISA firewall. It was blocking
any STMP incoming traffic. This made it so my Exchange users could send 
email just fine but could not receive any incoming email. I checked the 
Event Viewer and saw this:

Event Type:        Warning
Event Source:    Microsoft Firewall
Event Category:                None
Event ID:              14090
User:                ...

My clients on my network could access FTP servers behind our ISA 06 firewall but they could not create or delete anything on that FTP. I checked to make sure the permissions on the FTP were setup correctly. I narrowed it down to ISA blocking Incoming FTP traffic coming back from the FTP servers. I did some searching and there are many issues out on this. Others issues vary slightly but I did find something that worked for me. I setup the below rule on ISA.

ISA FTP rule:

• Action: Allow
• Protocols: FTP (21 TCP Outbound /FTP Filter Disabled) – FTP Server (21 TCP Inbound /FTP Filter enabled)
• From/Listener: Internal
• To: External
• Condition: All Users

I hope the above ISA rule is useful for someone else as well. Here is some more useful information when Troubleshooting Outbound FTP Access in ISA Server: http://technet.microsoft.com/en-us/library/bb794745.aspx

The Issue:

We requested a new certificate for our website from a CA. We applied the certificate on the Internal IIS6 web server. I then exported the certificate including keys and imported onto our ISA 2006 firewall.

I then went into the publishing rule for our website and updated it with the new certificate.

When external users went to our website using https they got the following error:
Error Code: 500 Internal Server Error. The target principal name is incorrect. (-2146893022)

Issue Analysis:
When I looked at the rule I noticed it was set to an IP under the To tab.
I opened up a command prompt and tried to ping my web server. It returned a different IP. I then tried to Ping domain.com it returned a different IP then the one that was listed in on the To tab of the publishing rule.

I knew from this MS Technet article (http://technet.microsoft.com/en-us/library/cc302619.aspx#CommonIssues) the name on the To tab had to match the common name on the Web site certificate. When a client sends a request ISA sends it to the name on the To tab therefore if ISA cannot resolve this it will produce that error.

What I did to resolve ...