Re: Access cluster from FE server

Shaine

If you open a remote admin connection to the frontend box and then try to
access the backend owa on the cluster does it work?

Nue
"processendnow" <shainefisher@xxxxxxxxxxx> wrote in message
news:1138718746.223620.130220@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Did a quick check, host headers are setup on the FE server for www and
> www.domainA.com, there are 3 virtual servers setup in system manager
> (default, www, and www.domainA.com) all use the cluster IP address, in
> IIS manager on the active cluster node there are 3 websites (one for
> each vserver) all are started.
>
> New error 500 internal server error, can't find it in the logs, but
> here are the IIS logs, see what you can make of this.
>
>>>From the active cluster node IIS logs last failure
>
> #Software: Microsoft Internet Information Services 6.0
> #Version: 1.0
> #Date: 2006-01-31 14:28:41
> #Fields: date time s-sitename s-ip cs-method cs-uri-stem cs-uri-query
> s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus
> sc-win32-status
> 2006-01-31 14:28:41 W3SVC102 10.0.1.240 GET /exchange - 80
> DOMAINA\Administrator 10.0.1.1
> Exchange-Server-Frontend-Proxy/6.5+Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727)
> 500 0 0
> 2006-01-31 14:30:25 W3SVC102 10.0.1.240 GET /exchange - 80
> DOMAINA\Administrator 10.0.1.1
> Exchange-Server-Frontend-Proxy/6.5+Mozilla/4.0+(compatible;+MSIE+6.0;+Windows+NT+5.2;+SV1;+.NET+CLR+1.1.4322;+.NET+CLR+2.0.50727)
> 500 0 0
>
> As you will know, 10.0.1.1 (www) is the address of the FE server (the
> cluster is 10.0.1.249 (myCluster))
> I was on a windows 2003 machine and I wanted to get to the exchange
> directory using the addresss http://www.domainA.com/exchange
>
> That's all I can tell you for now, at least I know that the request is
> reaching the cluster, just failing when it gets there.
>
> Hope this helps
> Shaine
>


.

Relevant Pages

  • Re: NLB Cluster - Ping fails or long time to reply from outside local subnet - SOLVED
    ... Windows Server 2008 Readiness Team ... cluster on a separate DLink card in multicast mode. ... I thought that the litmus test was that the router functions fine ... member of the NLB cluster, setup NLB on it, plug the NICs ...
    (microsoft.public.windows.server.clustering)
  • Re: NLB Cluster - Ping fails or long time to reply from outside local subnet - SOLVED
    ... Once again, ARP is an RFC standard, if you are having to make static entries in unicast mode, then your network device is not in compliance. ... Windows Server 2008 Readiness Team ... I was feeling nervous about our teaming-capable adapter as I read it might be sending out heartbeats, so I disabled it AND configured the cluster on a separate DLink card in multicast mode. ... I thought that the litmus test was that the router functions fine when no NLB is installed, but when it is, things start going screwy. ...
    (microsoft.public.windows.server.clustering)
  • Re: NLB Cluster - Ping fails or long time to reply from outside local subnet - SOLVED
    ... One server with no cluster configured - all works ok. ... When static ARP mappings are added all works ok. ... I thought that the litmus test was that the router functions fine when ...
    (microsoft.public.windows.server.clustering)
  • Re: NLB Cluster - Ping fails or long time to reply from outside local subnet - SOLVED
    ... Windows Server 2008 Readiness Team ... NLB is installed, but when it is, things start going screwy. ... The servers are a couple of switches away from the router so I ... 'exterior' to the NLB cluster itself. ...
    (microsoft.public.windows.server.clustering)
  • Re: NLB Cluster - Ping fails or long time to reply from outside local subnet - SOLVED
    ... ARP is defined by RFC. ... Windows Server 2008 Readiness Team ... The servers are a couple of switches away from the router so I would have thought that any duplicate MAC info. or similar would have been come irrelavent/concealed at the router. ... If you run the command 'wlbs query' and the node it is run on says it is converged with all of your nodes in the cluster, that basically says the NLB configuration is correct and the nodes are talking to each other. ...
    (microsoft.public.windows.server.clustering)
Loading