MOSS 2007 farm installation issue

Hot Topic

InfoPath Forms do not open in a browser after contact control is added..
Extending list with custom field
Loading User Controls into page
Physical seperation of layers - business layer -> data layer?
O/R Mapping
Impact on performance while using session service
RollBackTask
Architecture for Notification based application
Sharepoint Services 3.0 and AD Security Groups?
O/R Mapping and visual controls

SharePoint Products

WebServices or SQL replication
Multi-tiered Application with client Server Architecture
Objects with many child object relations - Need design help!
Database Design
Accessing a SQL Server table using sql authentication as opposed to windows authentication
Left Navigation - Sub Menu Items
Change the default theme applied to new sites
Developing a new feature? Or is there a better way?
Identity Manager - Tools and Utilities
ADAM and MOSS2007

MOSS 2007 farm installation issue

We have installed MOSS 2007 Farm setup having 4 servers in total as
follows.

1. SRV1 - Acting as SQLServer

2. SRV2 - Acting as SSP Server and hosting Admin site, search
and indexing services

3. WEBFRONT01 - Web frontend server running 'Web Application
Service'

4. WEBFRONT02 - Web frontend server running 'Web Application
Service'

When I create a web application and site collection through Admin site,
the site gets created on both the web frontend servers, which is fine.
But only one of the web frontend servers is able to serve incoming
request. i.e. If I try http://WEBFRONT01 I get to the page, but when I
try http://WEBFRONT02 I automatically get redirected to
http://WEBFRONT01 and I get to see the page.

If I switch off (web application service) on WEBFRONT01 and try
http://WEBFRONT02 I get 'Page cannot be displayed' message.

Q1: Can anyone in our team explain this behavior Is this the right
behavior of MOSS How can I make both the web front end servers serve
the same content, even if one of them is down.

Madhur


Answer this question

MOSS 2007 farm installation issue

  • tasleemarif

    No. Its the configuration just after installation.


  • ACCOUNTINGONLINE.US

    Your problem is simply the access mappings.

    When you hit SharePoint it inspects your hostheader (the address you used to access the site) and if it doesn't match anything it knows, it'll determine your zone (i.e. internet, intranet etc) and redirect you to url it believes it the correct one.

    To make your current setup work:
    Go the central admin / operations / alternate access mappings
    Add server1 address to one of the zones (just choose one)
    Add server2 address to one of the zones (just choose custom).
    Add your nlb address (when you have one) to the default zone

    Btw: If you still see the problem, use another browser to test it. In case of problems IE will not display the site it was actually redirected to, just the error message.
    Firefox will at least tell you what site it is hitting.

  • eman1975

    Bob,
    I am away from the setup for couple of days. As soon as I get back, I will get back to you with
    the results.
    Thanks




  • WolfgangEngel

    Are you using any Load Balancing

  • scottmonte

    What happens when you log into the WebServer2 and try to hit the site....

  • JinMengcheng

    When you created your web app you had to give it a "load balanced URL." If you used the name of a server (webfront01) rather than a DNS alias w/round robin or a truly load balanced VIP then you will get this behavior.

    Chris Fields
  • MOSS 2007 farm installation issue
Answer this question