Always get the same response header even if contacting a different server
Greetings.
We have a Sharepoint-farm (MOSS 2007) with several Web Frontends (WFE).
We currently have a problem and wanted to trace it. During that we found out that no matter which WFE we call, we always get the same "Servername" in the "Response Header" which is the name of the first WFE.
Example:
Let's say our first WFE is called "server1" and the other are server2 to server4. When we access server1, the response header says "servername: server1". If we contact server2, it also says "servername: server1". It never actually displays the real name.
We find this a little weird. We found some clues that due to caching and HTTP 1.1-features, Sharepoint may generate his own custom response header. My current theory is that the response header is generated once (during the configuration of the first WFE
probably) and then replicated to the other WFE's (maybe stored in the Config-DB).
Is that correct or am I totally wrong here? And if so, why do we always get the same response header even if we're absolutely sure we're contacting a different server?
Thanks!
June 7th, 2010 4:10pm
Do you use MS NLB?
You can use a trick. Create a test.htm file for every WFE server with server name as <html>SERVER1</html>. Copy test.htm into C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS for
every server. To get a real server that response you just open url
http://nlb_url/_layouts/test.htm
Oleg
Free Windows Admin Tool Kit Click here and download it now
June 7th, 2010 6:04pm
Yes, we use MS NLB.
Adding another file would be a little problematic, as this is a live production environment for many-many-many users and we are only part of the support team. Getting something like that approved would take a lot of time, if it were approved at all.
Is there something else we can try?
June 8th, 2010 10:54am
I do not have enought information about your environment to make a suggestion. But I guess it maybe some configuration issue with AAM. This article may help
http://technet.microsoft.com/en-us/library/cc288609(office.12).aspx.
Oleg
Free Windows Admin Tool Kit Click here and download it now
June 8th, 2010 5:31pm
Hi,
Have you tried using a local host file, which will override your DNS settings. You can then point your browser to which ever SharePoint server you wish.Regards, Aaron www.aaron-rendell.co.uk
June 8th, 2010 6:33pm
Hi Aziegler,
Can you drainstop Server1 in your Windows NLB console and test if you still reach a box (because this serves existing sessions, but doesn't allow new ones, you'd need to login as a user without a current session)? If so, what the response header looks like?
It may be possible you're seeing the same header due to single-client affinity being set.
Netmon traces will help. If you're looking at your header through a Netmon, is there a chance you can post selections of the header information you're seeing here?
Depending on the version of IIS Manager (if you have 7 or above) you can enable Failed Request Tracing in IIS to look for client traffic (or, maybe even more helpfully, simply check the IIS Logs for user access on each of the SharePoint boxes).
Thanks!
Free Windows Admin Tool Kit Click here and download it now
June 10th, 2010 6:42pm
This topic is archived. No further replies will be accepted.
Other recent topics
