We have a SharePoint2007 server running on a Windows Server 2003 Box. The box itself is quite old but has not experienced any weird issues.

Recently SharePoint has begun to show some strange behavior. One of the most annoying things is that once in a while, the sharepoint sever stops responding to requests outside our network. Internally, you can still browse everything that has to do with sharepoint but outside, nothing. If i reset the server it will start responding again. I am just not sure what makes it stop responding to users on the outside in the first place. Resetting the WWW publishing service does no good.

link|improve this question

feedback

1 Answer

Anything in the event logs? What happens if you try an iisreset or bouncing the firewall service?

link|improve this answer
just to make sure I am clear, doing a reset through the IIS console is the equivelant of iisreset on the CLI, right? If so, I have tried that. I have also reset the WWW publishing service. I have not tried bouncing the firewall service and will try that the next time I see a failure on outide traffic. – Cliff Racer Nov 23 '09 at 19:46
The one type of error I see a ton of in the App logs is event id 2436. In short its an access denied error. Which is another unnerving thing since the account that SP uses should have all the proper permissions. On top of that the other type of error I see is 8214, which is is some sort of Topology error in SharePoint – Cliff Racer Nov 23 '09 at 19:54
1  
Here's the answer for the Event 2436/Access Denied error: support.microsoft.com/kb/971382 (it's actually a pretty common problem that is easy to fix). Not sure if resolving that will fix your main issue, but it certainly wouldn't hurt to fix it and may clear up some noise in the event logs about your original problem. As far as the IISReset, yes, I believe it is the same as restarting IIS in the management console. – Sean Earp Nov 23 '09 at 20:28
Thanks! I tried what the article suggested and the first option did not work for me so I took the second suggestion and disabled loopback alltogether. That appears to have stopped those errors. – Cliff Racer Nov 24 '09 at 18:17
feedback

Your Answer

 
or
required, but never shown

Not the answer you're looking for? Browse other questions tagged or ask your own question.