Welcome to ISAserver.org

Web Publishing Issues

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA 2006 Publishing] >> Web Publishing >> Web Publishing Issues

Page: [1]

Message

<< Older Topic Newer Topic >>

Web Publishing Issues - 6.Feb.2008 2:30:12 AM

bobh

Posts: 3
Joined: 23.Jan.2008
Status: offline

Hi all, Hate to post "one of those" questions, however, I just don't know where to look.

I had an ISA 2004 standard install working , publishing several websites for years.
It was on a VERY old machine, but it worked fine due to the low usage.
I needed to reboot it maybe every two weeks.

As internal usage increased, I found myself needing to reboot more often, so time to upgrade to ISA 2006.

First question. There is no ISA 2006 Standard that I could find, correct?

OK, So I built a new machine, w2k3 r2 Enterprise and installed ISA 2006 on it.
I fiddled for quite some time trying to get the old rules imported before giving up and simply re-creating the rules manually. I only have about 8 websites total, all of which are user review websites for clients.

I have been concentrating on one site only and cannot get it to publish. I can make it alternate between 403's and 404's.

I have run live log runs and see the requests coming in.
I have run netmon on the target webserver ( all of which are Host header name setups ) and see the requests come in from the source IPs, but they have no Host header name and they are not HTTP but are TCP requests.

Everything worked great under 2004, but I must be seriously missing something fundamental somewhere.

Links to a good basic web publishing primer for isa 2006 would be appreciated, as well as any other suggestions.

Is there just something fundamentally different between ISA 2004 standard and ISA 2006 enterprise that I am missing?

BTW, I noticed several other posts, although a lot shorter, with the same issue.
If this is a known issue, is there a way to post a sticky on the problem in the forum?

Searching is dicey unless you hit on the right set of keywords, and I didn't find anything useful browsing the first four pages of this forum.

Thanks in advance for any suggestions.

Bob

< Message edited by bobh -- 6.Feb.2008 2:32:01 AM >

Post #: 1

Featured Links*

RE: Web Publishing Issues - 7.Feb.2008 2:22:25 AM

bobh

Posts: 3
Joined: 23.Jan.2008
Status: offline

Well, as is usual when one asks a stupid question, there are two outcomes.

A. You Get a response telling you where you missed the Train.
B. You have a Late Night Moment, due to Kids Cold, or Your Cold or Some Other Epiphany.

Unfortunately, this was a LNM ( KC ) resolution.
Could also be classified as LNM ( SOE ) but I'm giving it to my sick daughter....

Perhaps this will direct others who have had the same general issue to find a solution?

I somehow doubt it....

As EMBARRASING as it might be, I hate to post questions and then find my own solutions, but not post a response to my own question giving the details of said solution....

So, swallowing away, in the hope it helps someone else:

When you move from one ISA server to a NEW one, and you change your gateway IP, so that the move will be ( theoretically ) painless, Be sure to change the gateway IP on all machines that are statically assigned.

Especially your web servers.

You see, it's a little bit difficult for your web server to get a request and then try to send the response out on a gateway IP that has since been turned off.
( Like the OLD ISA server...., capish? )

Lesson learned?

Put a BIG OL' task on your todo list:
Convert from static IP assignments to DHCP if you are a small shop, NO MATTER HOW MUCH TROUBLE IT MIGHT BE.
It will be LESS TROUBLE in the long run, after a couple years have gone by, and you forget how you have set up your network.
Heck, you might even want to manage this in a larger shop using DHCP, not sure, network management is Obviously Not my speciality...

In Brief, Simply changing the gateway IP addr on the web server to the new ISA server solved the issue.
*sigh*
GOD I hope this helps someone else...

SO Embarrasing..

(in reply to bobh)

Post #: 2