Strange behavior with clustered IIS server

I have IIS running on a Windows 2003 failover cluster. I realize that
it is not recommended that to do it this way but the server is
clustered for other reasons and I needed it running a web site as
well.

The website works fine if I browse directly to the computer that is
the active node. However, when I browse using the cluster name, I can
browse the root but not any subfolders.

Example:

http://Server1/ ' Works if node1 is active
http://Server2/ ' Works if node2 is active
http://Cluster/ ' Works with any node
active
http://Server1/SubFolder/ ' Works if node1 is active
http://Cluster/SubFolder/ ' DOES NOT WORK

By not working I mean that I get a 404 error saying the resource
cannot be found.

Not sure if this is an IIS issue or a cluster issue.

Thanks
Karl

Re: Strange behavior with clustered IIS server

On Dec 3, 11:14 am, karlman wrote:
> I have IIS running on a Windows 2003 failover cluster. I realize that
> it is not recommended that to do it this way but the server is
> clustered for other reasons and I needed it running a web site as
> well.
>
> The website works fine if I browse directly to the computer that is
> the active node. However, when I browse using the cluster name, I can
> browse the root but not any subfolders.
>
> Example:
>
> http://Server1/ ' Works if node1 is activehttp://Server2/ ' Works if node2 is activehttp://Cluster/ ' Works with any node
> activehttp://Server1/SubFolder/ ' Works if node1 is activehttp://Cluster/SubFolder/ ' DOES NOT WORK
>
> By not working I mean that I get a 404 error saying the resource
> cannot be found.
>
> Not sure if this is an IIS issue or a cluster issue.
>
> Thanks
> Karl

I am narrowing this down. Looks like it is a cluster issue and I am
pretty sure it is something I did wrong...

The main admin cluster network name and IP that is in the original
group with the Quorom works fine. The new one I created does not. It
does not even show up in the available list of IPs on the IIS admin
general page.

I will play with it more to see if I did something wrong.

Thanks
Karl

Re: Strange behavior with clustered IIS server

On Dec 3, 11:33 am, karlman wrote:
> On Dec 3, 11:14 am, karlman wrote:
>
>
>
>
>
> > I have IIS running on a Windows 2003 failover cluster. I realize that
> > it is not recommended that to do it this way but the server is
> > clustered for other reasons and I needed it running a web site as
> > well.
>
> > The website works fine if I browse directly to the computer that is
> > the active node. However, when I browse using the cluster name, I can
> > browse the root but not any subfolders.
>
> > Example:
>
> >http://Server1/ ' Works if node1 is activehttp://Server2/ ' Works if node2 is activehttp://Cluster/ ' Works with any node
> > activehttp://Server1/SubFolder/ ' Works if node1 is activehttp://Cluster/SubFolder/ ' DOES NOT WORK
>
> > By not working I mean that I get a 404 error saying the resource
> > cannot be found.
>
> > Not sure if this is an IIS issue or a cluster issue.
>
> > Thanks
> > Karl
>
> I am narrowing this down. Looks like it is a cluster issue and I am
> pretty sure it is something I did wrong...
>
> The main admin cluster network name and IP that is in the original
> group with the Quorom works fine. The new one I created does not. It
> does not even show up in the available list of IPs on the IIS admin
> general page.
>
> I will play with it more to see if I did something wrong.
>
> Thanks
> Karl- Hide quoted text -
>
> - Show quoted text -

Problem resolved. It was an issue with not having both servers fully
updated with the latest ASP code.

Sorry, I am a moron!