Accedi
Microsoft.com
 
Microsoft
 
 
 
Microsoft >
> 
> 
When configuring Domain Name - error 80000190 received

Odpovědět When configuring Domain Name - error 80000190 received

  • lunedì 8 settembre 2008 18:24
     
     
    Registrati per votare
    0
    Hi,
     
    Can anyone tell me what the above error means - I'm following the wizard to create a domain for remote access...

    Filled in live id details
    entering or selecting previously entered registered name

    then receiving error:

    The following error occured during Domain Name Setup:

    An unexpeced error has occured communicating with the Windows Live Domains service. 80000190


    Does this mean that the MS server is currently down, or does it mean that I've done something wrong!

    Thanks
    Tony
     

Tutte le risposte

  • lunedì 8 settembre 2008 18:36
    Moderatore
     
     Con risposta
    Registrati per votare
    0
    Tony,

    Probably means that the Microsoft site is having problems as this has been reported before, and usually clears after a few hours.

    As this 'homeserver.com' domain becomes more important to users, I think it needs to be possible for users to check it's on-line status.

    Colin
    If anyone answers your query successfully, please mark it as 'Helpful', to guide other users.
     
  • lunedì 8 settembre 2008 20:44
     
     
    Registrati per votare
    0
    Hi Colin,

    thanks for your response - I'll keep trying, maybe one time I'll be lucky :-)

    Thanks
    Tony
     
  • lunedì 8 settembre 2008 22:20
     
     
    Registrati per votare
    0

    This error will also occur if the Internet Service Provider you are with is blocking the common ports such as 25, 80, 110, etc.
    With spam being so rampant, many ISPs block ports on residential/consumer accounts and unblocked service requires business/server accounts.

     
  • sabato 3 dicembre 2011 17:48
     
     
    Registrati per votare
    0

    This error will also occur if the Internet Service Provider you are with is blocking the common ports such as 25, 80, 110, etc.
    With spam being so rampant, many ISPs block ports on residential/consumer accounts and unblocked service requires business/server accounts.


    So what is the Solution...................
     
  • sabato 3 dicembre 2011 19:09
     
     
    Registrati per votare
    0

    This error will also occur if the Internet Service Provider you are with is blocking the common ports such as 25, 80, 110, etc.
    With spam being so rampant, many ISPs block ports on residential/consumer accounts and unblocked service requires business/server accounts.


    So what is the Solution...................

    The easiest solution is to change your ISP or look at their business account offerings. Failing that, you need to read up on advanced porf Forwarding.

     

    Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.
     
  • mercoledì 25 gennaio 2012 15:52
     
     
    Registrati per votare
    0

    Having set up a new server over Xmas, as my HP Storageworks X510 had started to give problems, I have been trying to get my domain name set up on the new server since early January and had the 80000190 error every time. I know all the ports from the ISP are open as I can access using an alternative domain name. I also have a fixed IP and I have changed ISP during this period. 

    I know there are occasional outages on the Live Domains service, but I am not aware of it going on for about 3 weeks. I am trying about three times per day at present. I have had this homeserver.com domain since the original beta of WHS v1, but just to confirm I used an alternative Live ID to create a new domain name and that gives the same error. I am clearly communicating with the Live Domains service as it offers up the domain name associated with the respective Live ID's.

    Can anyone confirm if the homeserver.com Live Domains system is working or not.

     

     

     
  • giovedì 26 gennaio 2012 01:05
    Moderatore
     
     
    Registrati per votare
    0
    Dave, make sure your server is fully updated: use the Windows Home Server console application to check repeatedly for updates until none are found.
    I'm not on the WHS team, I just post a lot. :)
     
  • giovedì 26 gennaio 2012 11:34
     
     
    Registrati per votare
    0

    Does your Live ID password contains any "special characters"?

    Refer to this: http://onlinehelp.microsoft.com/en-us/windowshomeserver2011/windows-live-dns-support-2.aspx

    It states there that "The server does not support use of the characters $, /, ', and %."

    Luc.

     
  • sabato 28 gennaio 2012 10:10
     
     
    Registrati per votare
    0

    After many attempts and re-imaging the OS more times than I can count, I finally brough my Acer H340 back from the valley of death. Let me save everyone the drama and just share you the highlight - maybe it will help some of you out there.

    1) After almost three years of services, one of my data drives (Seagate) reported errors in late November. I ignored for a few weeks, until the WHS started crushing and files gone missing. So I purchased three drives to replace all of the original drives.

    2) After backing out the drives and insert the new drives, system still crashed. So I had no choice, but to reimage the OS.

    3) After multiple failed attempts, finally brought the OS up, but can't get domain and backup working. So selected the "restore to factory setting". Still no luck with domain.

    4) One more try with "restore factory setting" and install all the hot fixes (including power pack 3. BTW: if you can see your desktop as in my case, you will see a pop-up dialog window after the system comes up after installing power pack 3 telling you the system will reboot in 30 secs. That dialog window might looks familiar to you if you experienced Code Red worm before, but don't panic. Just let the system reboot)

    5) Install one more security hotfix, then I was able to get my domain back.

    This is has been a very frustrating experience.

     
  • domenica 6 maggio 2012 20:58
     
     
    Registrati per votare
    0

    Ken's suggestion worked for me.

    After a server restore I was trying to configure my HP MediaSmart to use my previous homeserver.com domain, but the '80000190' error kept showing up. I thought the server was up-to-date, but you really have to repeatedly check for updates (this may require several server restarts) until the 'No more updates available' dialogue window is shown. After that, the domain configuration completed successfully.

    Thanks for your post, Ken. 

     
  • giovedì 10 maggio 2012 22:57
     
     
    Registrati per votare
    0

    I kept getting this error on my machine. farked around with my routers ports all night trying to forward them. Turns out I just needed to update my home server after i reinstalled it. Stupid me. After updating my server completely I was able to finish the domain name wizard and now can access my server from outside of my network. 

    Thank you

    • Modificato Unreal2k12 giovedì 10 maggio 2012 22:59
    •  
     
  • martedì 25 settembre 2012 18:02
     
     
    Registrati per votare
    0
    Didn't work for me. I spent all day today trying to get my homeserver
    domain back up after a full reinstall - what a nightmare. That 80000190
    error just won't let me. Updated to the hilt too - any idea's for a fix ayone? Or is the domain down for everyone?
     
  • martedì 25 settembre 2012 18:31
     
     
    Registrati per votare
    0

    There is a Microsoft problem at the moment which has not been resolved - you will need to wait.

    See here:

    http://social.microsoft.com/Forums/en-US/whs2011/thread/8140a905-419d-4ee9-bb7c-898df26e4530

    From a Wasp!

    Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.

     
  • venerdì 26 ottobre 2012 21:04
     
     
    Registrati per votare
    0

    Ken,

    Thanks, this worked for me.  I had to restart 6 or 7 times after a fresh install.  It took me better part of a day.