tomcatuk.net

It's a guess, but I would thinkk whatever it is that is preventing you from logging into the administrator account is the cause. It would probably be a hardware issue of some kind - if it was me, I would try disconnecting hardware until I could get into the administrator account. Do I take it from your fisrt post that you're installing a printer? If it's connected, try disconnecting it, then log in and install the software.

This might sound obvious, but are you attempting the install from a restricted account and using the "Run As..." and selecting administrator, or actually logging onto the machine as the admin and doing it? I'd try the second option if you haven't yet.

Don't you just hate it when people don't post the solution? Got to the bottom of it today: By default it seems Small Business Server 2003 had set the DNS server properties with forwarders to the DNS servers at our ISP. Removed them and bingo! all sites with content provided by Akamai display correctly & MSN Search is available again. Here's what it looks like WORKING: The thing I don't get is why this problem only showed up 4 days ago out of the blue - possibly someone here logged onto the server and messed with the settings but I kind of doubt it. Windows Update perhaps? Or a change to Akamai's (quite frankly strange) method of dealing with DNS? If anyone has any possible reasons why this might have happend I'd like to know

Hi, I'm having trouble with Akamai - for those that aren't familiar with Akamai here's a very brief summary - Akamai provide localised content distribution for major websites. MSN search are a good example - when you run a search through MSN, the Akamai system directs you to one of their servers that is geographically close to you. Try pinging search.msn.com and you'll more than likely be presented with a different IP address to the one I get (84.53.134.200) in much the same way that the google.com you get is dependant on your location. Hope that part makes sense. Go to Akamai.com if you want to read up on them - apparently they handle a huge percentage of all internet traffic. For some reason we don't get served any content by the Akamai servers. I have tried using some different DNS servers so we get different Akamai machines when resolving search.msn.com but to no avail. No matter which of Akamai's servers we request data from, the result is the same. For MSN search we get the "This service is currently unavailable". If we try and view images hosted by them we get a "DNS Failure" from the web browser. It occurred to me that our IP address might have been banned in some way, but if that was the case (as I understand it) we wouldn't be able to ping the IP address, but we can, and get great respoonse times. Have spoken to Akamai and had them query the relevant IP addresses and they assure me that the servers at the IP addresses I gave them do belong to them, and are running correctly. It's not a local network problem, our ISP seems to be the point at which the problem exists as I've spoken to their techies and they have the same issue - no search.msn.com for them either! Stumped - any help appreciated!

Microsoft has this to say: You may experience problems in Windows Explorer or in the Windows shell after you install security update MS06-015 Interesting....this patch brought down my Small Business Server 2003, resulting in 10 memebers of staff screaming at me as to why they couldn't connect to either the Exchange Server or the Internet. We're basically an "Internet" company so net access is kind of important. It took 2.5 hours to fix as I had to.... 1) Set the most important client machines to connect directly to the net so at least some people could get some work done 2) Re-run the install routine on my SBS2003 machine as it was stuck in an unrecoverable reboot loop. This swallowed 3 hours of my day, and let's face it we all have more interesting things to do than install operating systems (if you haven't, ask yourself what you are actually achieving every day!) This happened Tuesday morning - which meant I was left with a SBS installation nagging me to apply the critical updates until today when I'm finally able to identify which patch was the culprit for bringing down my server! Here's where I first heard what I was looking for My Webpage