If you’re seeing this message today on your home server:
[Pic: usingwindowshomeserver.com]
then don’t worry, you’re not alone. Looks like this is a widespread issue, courtesy of Microsoft. Hold tight, don’t make any changes at your end. I’m sure Microsoft are aware of the issue and will have it resolved soon.
For the record, I haven’t had the warning appear myself, but many of our readers have.
Update: Received confirmation from Microsoft that they’re aware of the issue and are working on it now.
Update #2: Microsoft have informed us that the issue should now be resolved, but do post if you’re still receiving the error.
10. November 2009 at 9:52 pm
I´m having the problem here too, calling microsoft right now.
10. November 2009 at 9:54 pm
Thanks..I'm having the problem also! I thought it was my WHS again..
10. November 2009 at 10:23 pm
Its been going on for quite a while today now – we reported it about six hours ago :
http://usingwindowshomeserver.com/2009/11/10/tech...
Im not having the problem myself either but I know a lot of people are. And glad the screenshot was useful
Andrew
10. November 2009 at 10:29 pm
Apologies, Andrew – missed the source on the screenshot. Now fixed.
10. November 2009 at 10:26 pm
spent 4 hours to resolve this issue !!! thanks for the information.
But on my side i deleted and try to reconfigure my domain but i im not able anymore, hope microsoft will deliver a correction soon!!
thanks again
10. November 2009 at 10:41 pm
I've actually had this problem for months and blamed it on intermittent connectivity issues related to either a Vista or IE8 upgrade.
11. November 2009 at 5:52 pm
Yes same here for a few month's as well.
10. November 2009 at 10:42 pm
Notification disseapered here.. is it working again for you guys?
10. November 2009 at 10:46 pm
I'm getting the warning and my domain name isn't working. had to use the IP address to connect from work. I notice that Microsoft changed the name of their custom domains website today http://customdomains.spaces.live.com/ so they've probably stuffed something up along the way doing that.
10. November 2009 at 11:20 pm
Started for me around 6pm yesterday worked for a while last night and was not working again this morning. I can connect remotley now so I think it is working.
10. November 2009 at 11:41 pm
Glad to see I'm not the only one with this problem! It started about a week and a half ago for me.
11. November 2009 at 1:21 am
thanks for the update. I spent at least 3 hours trying to figure out what to do and I found this purly by accident. glad it wasn't just me
11. November 2009 at 1:58 am
Still dead in Georgia as of 9:00 EST….
11. November 2009 at 3:09 am
I only get it late at night, for the last two nights. I just restarted my server and the error went away for most of the day. Glad to know it's not an issue on my end.
11. November 2009 at 3:13 am
Whew, I have been checking configuration, firewalls, router. I wish Microsoft would have told me the problem is on their end. What a waste of my valuable time.
11. November 2009 at 5:19 am
Seems to be fixed now
11. November 2009 at 6:46 am
Yes, it's fixed.
11. November 2009 at 11:16 am
Appreciate the heads-up… I get so many nagging errors from my WHS, the signal-to-noise ratio is so bad I don't even pay attention anymore. Usually stuff about the last backup of (computer) failed, (computer)'s AV is out of date, (computer)'s having a heart attack, etc. I just ignored the domain update thing… figured it'd figure itself out.
But I've just got to point out (again)… for all the perfect grammar in the rest of the blog posts, the one glaring error keeps stabbing me in the eye time after time! "(Company) have…" is improper grammar… a company is a singular entity (like a "team"), so it should be "Microsoft has…". Sorry, it's just like fingernails on chalkboard to me! Had to mention it…
11. November 2009 at 1:19 pm
Slight language variations across the pond, re: the collective noun. See http://en.wikipedia.org/wiki/Collective_nouns for one explanation. Not a big deal to me, and I am A 'Murkin
LOL at the various panic messages from your WHS. I usually dismiss them, but keep a lookout for the radical "I'm bleeding to death" message…
11. November 2009 at 10:51 pm
I gave up on going to my server console each time WHS decides a computer has a problem and "Ignoring" the issue. My status is always "Critical" now and I just don't even care.
Hopefully – SERIOUSLY hopefully – the next version of WHS will have options to disable computer-related notifications. I really only want to know when the server itself is having issues. Then I might actually pay attention! I was hoping there was an add-on to correct this, but a quick topic said that no such add-on exists (sadly). Hopefully soon…
11. November 2009 at 2:44 pm
Strange. I posted a reply here a couple hours ago, and it doesn't see to have shown up. I hope it wasn't regarded as inappropriate.
In any case, I *think* subject-verb agreement in the case of collective nouns (such as Microsoft, HP, Ford, etc.) is considered gramatically correct when using the plural form in Britain. It's as if, when one says "Microsoft have released," you were to add "(The whizzywigs from) Microsoft have released…"
11. November 2009 at 8:10 pm
Ya know, the more I work with them thar Brits, the more I has began to wright like 'em.
There, have a field day with that sentance! BTW, there is a very distinct difference in how each side of the pond deals with "have" and "has".
One must realize that as a melting pot, US English has been "influenced" by so many languages, it is amazing that there are not more differences.
11. November 2009 at 9:37 pm
If it's any consolation, I now read/hear so much US media, my UK English gammar has gone to pot!
12. November 2009 at 6:29 pm
Oh Terry, you is so right ….
You are lucky, you doesn't have to learn Ebonics by Oakland school district (California)…. B)
11. November 2009 at 2:24 pm
Thanks for that info – was happening all day yesterday, so turned off remote access. Now seems fixed.
11. November 2009 at 2:46 pm
I'm still getting this error "Windows Home Server was unable to update Windows Live Custom Domains with your current IP address. Your Web site may not be available on the Internet." 11-Nov-2009 15:42 GMT+1. But it has been less error messages today than yesterday. But it's not solved.
11. November 2009 at 3:01 pm
My error got cleared again on 11-Nov-2009 15.55 GMT+1. I've now had 16 warnings and 16 cleared messages. The first warning came 10-Nov-2009 03:04 GMT+1.
11. November 2009 at 3:10 pm
The "official" word from MS:
"Today the Live DNS service had a hiccup that prevented updates for records on the .homeserver.com domain name. Thus if your WAN IP address changed on your router, the home server was unable to update this record, and remote access was not available. This may have been accompanied with an alert from the home server. If your WAN address did not change during the last 24 hours, remote access was unaffected.
This issue has been resolved as of 8:16pm Pacific Time."
DNS issues take time to filter thru the 'net, usually within 24 hours????
11. November 2009 at 4:13 pm
The DNS issues for this particular case should not take 24 hours. The Time to Live (TTL) on the homeserver.com domain name are very short. I would say about 10 minutes maximum you should be back online.
Thanks for your patience.
11. November 2009 at 7:10 pm
Seems to be working again here in Georgia….
11. November 2009 at 8:11 pm
When I try and log into my home server I get this after attempting to log in. I have rebooted the computer I am using and the home server.
Server Error in '/Remote' Application.
——————————————————————————–
Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".
<!– Web.Config Configuration File –>
<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>
Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.
<!– Web.Config Configuration File –>
<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>