Domain access

Tutte le risposte

• venerdì 18 luglio 2008 11:48

  Moderatore

   

   
  

  0
  Please test from some location other than your home network. Many routers cope poorly with looping back to an internal machine through the WAN address.
  
   
• venerdì 18 luglio 2008 21:52

   

   
  

  0
  I was using my friend's home connection to log back into the home server
  
   
• sabato 19 luglio 2008 02:12

  Moderatore

   

   
  

  0
  Okay, you hadn't said.
  
  What error are you seeing?
  
   
• domenica 20 luglio 2008 05:09

   

   
  

  0
  There isn't any special error meesgae, just like the link (https://xxxx.homeserver.com) doesn't exist..........
  
   
• domenica 20 luglio 2008 05:30

  Moderatore

   

   
  

  0

  eaout wrote:

  There isn't any special error meesgae, just like the link (https://xxxx.homeserver.com) doesn't exist..........

   

  Did you try it without the s?  Does everything show up with a green check mark in the Router and Domain Name tabs?  If not, which ones don't?

   
• domenica 20 luglio 2008 15:25

  Moderatore

   

   
  

  0
  In the Windows Home Server console, what do you see when you click Settings → Remote Access → Details... (under Router)? What is shown under Domain Name on that same page? What about when you click Details... under Domain Name?
  
   
• lunedì 21 luglio 2008 06:36

   

   
  

  0
  I have checked again and everything is green.....
  
  That's why I don't understand how come it is not working?????
  
  Anyone can help......
  
   
• lunedì 21 luglio 2008 15:51

   

   
  

  0
  It is possible that your router is not set properly, even when UPnP should be working. You may need to go to your router's configuration and manually forward ports to your WHS machine.
  
   
• lunedì 21 luglio 2008 22:13

   

   
  

  0
  I have forwarded ports 80, 443 and 4125 to the WHS already.
  
   
• martedì 22 luglio 2008 00:59

  Moderatore

   

   
  

  0

  eaout wrote:

  I have forwarded ports 80, 443 and 4125 to the WHS already.

   

  You can try going to Shields Up! and check those ports to see what it shows the status of those are.

   
• martedì 29 luglio 2008 09:34

   

   
  

  0
  I have done the shields up test and all 1056 ports are stealth. Is it a good thing?? But I have forward port 80, 443 and 4125, so I expected those 3 ports are shown as opened.....
  
  Is it something to do woth my router???
  
   
• martedì 29 luglio 2008 12:08

  Moderatore

   

   
  

  0
  If the ports that Windows Home Server uses are reported as STEALTH by Shields Up!, then your ISP is blocking them. You'll have to contact your ISP to find out what you can do about it.
  
   
• martedì 29 luglio 2008 13:19

   

   
  

  0
  Please correct me if I'm wrong, but he said that he could connect fine by using his WAN IP, only when he tried his xxx.homeserver.com domain it failed, so it sounds like a DNS issue to me and not a problem with the port-forwarding
  
  Regards, Alex
  
   
• mercoledì 30 luglio 2008 03:21

   

   
  

  0
  Did you take a look at this thread.
  http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=1730579&SiteID=50