On trying to remove a old server from the directory (2003 server in a 2003 forest) I received this error
Failed to configure the service NETLOGON as requested “the wait operation timed out.”
The root problem was that this domain controller had a DNS entry to another domain controller that no longer existed. It was trying to contact it but couldn’t. Removing that entry and running dcpromo.exe again solved it.
I see a lot of people saying they are getting auth prompts for public anonymous content on SharePoint sites. Once you have anonymous enabled in Central Admin and in the site collection, you’d expect it to be all good right?
I discovered one more resaon beyond the obvious permissions problems. If you put a graphic or something embded in a page, then publish that page but NOT the embeded object (i.e. it’s still draft or unapproved) you’ll get an auth prompt when the page loads.
On a busy (lots of stuff) page it can be tough to find what’s the issue. The quickest way I’ve found to discover the problem (99% of time an image) is to cancel out of auth prompts, then look for broken stuff on the page. An image you can right click the broken icon and find the location of it… then jump to that library and check the file. My bet is it’s never been published.
Also seen as:
Problem:
Windows Server 2003 SP2 and newer (Windows Server 2008) have a Anti Denial Of Service feature that prevents the server from accessing itself via different names (that’s the simple answer).
Fix (assuming you want to keep your custom URL’s):
Further Info:
Rant:
In the KB Microsoft basically says “don’t turn it all off unless your lame”, so your left with “edit the registry every time you add a website”. This is a cumbersome workaround for something that happens out of the box default. Most SharePoint boxes will want more then one web site name and best practice says to NOT make production sites the server name. IMO SharePoint should be updating the reg key itself and keep in sync with the host headers created/managed by central admin. Or, the localhost loopback “new feature” should be looking at iis host headers and allowing them.
Update 6/22/09: KB972041 is out with a hotfix that resolves this issue. I guess you install it before, or in lieu of KB967831.
OK so this blog post explains it well but it has gotten worse since that post a month ago. Here’s an update and shorter version of what’s going on:
There’s a optional monitoring feature of OCS that many small shops likely won’t install. That’s fine, cus it’s optional right? Well turns out it’s now required (actually just part of it, the MSMQ service) for a hotfix to successfully install. That hotfix is now on Microsoft Update and is likely already on your box, WSUS, SCCM, SMS, etc: (KB967831). The patch is not smart enough to either:
So it leaves you a nice broke server to repair in the morning. Front-End and Edge Services service stopped, with cryptic misleading Event Log messages. So multiple boxes are down. Crazy thing is this happens in a “default install” scenario as if no one full tested the patch or something. I would give a pass for a hotfix, but a MU patch… fail!
Quick fix: install MSMQ (even though you don’t need it unless you setup RtcQmaAgent for OCS Monitoring) via this script (win2003 servers), then re-run the update either via MU or downloading and running it manually.
Only a handful of software that isn’t a game could end up on the “fun to use” list. I think Windows 7 is on it. I’ve been using it as the main OS on an increasing amount of computers since the pre-release of the public beta (build 7000) since December 08. I’ve now got 5 out of 7 work/home machines using it, most on build 7077 (which isn’t perfect). Waiting on RC build this month. It’s so enjoyable to use (compared to XP and Vista) that I have that “can’t wait” feeling for RTM.
From the responsiveness of the interface, awesome boot and return-from-sleep times, to the overall look, the new “best taskbar eva”, to little things like knowing the difference between a “default audio device” (speakers) and your “default communications device” (headset or webcam/mic)…. it’s got a lot going for it. I’m starting to get more comfortable with the “library” concepts (old 
habits of caring exactly where your file is located on disk die hard). Though, I’m still not a huge IE8 fan compared to Firefox (and now my new fav: Chrome… yes I said it. Just give it’s minimalism a week and you won’t miss the bloat of Firefox’s add-ins).
Just tried the “play to” option in Media Player to push music from my office to the living room PC, which is plugged into the house audio receiver. Couldn’t be easier. Love the simple and effective management window.
Next is to decide how I will implement a HomeGroup, which removes the need for me to manage share permissions, user passwords, etc. on the various home computers.
