locked
whs and remote access RRS feed

  • Question

  •  

    i have tried to access my xxxfamily.homeserver.com page with no sucess. i can get to it by web access,69.144.xxx.xxx. is there something i'm missing? i have a godaddy cert installed (i think). do i have to do some port forwarding?? if i do have to port forward will someone give me a step by step?  i have a ebr-2310 d-linkrouter.
    Friday, December 7, 2007 12:58 AM

Answers

  • What results do you get if you check the Domain Name Details?

     

    To do so...

    1. Launch Windows Home Server Console
    2. Enter Settings
    3. Select Remote Access tab
    4. Under Domain Name section, click Details button
    Friday, December 7, 2007 1:29 AM
    Moderator
  • If all of those results are coming out alright... then it should be accessible... and yet it’s not.


    Stupid question perhaps... are you sure you are typing the domain name properly? Exactly the same as what is shown on the diagnostics screen? Tried both with http and https?

     

    Have you also tried accessing your server using its domain name from outside of your network? If not and you’d like you can email me (address in profile) your domain and I’ll give it a remote try.

     

    Some routers (like mine) give different results when you hit the external domain internally or externally.

    Friday, December 7, 2007 4:34 AM
    Moderator
  •  Al Jarvi wrote:
    Can anyone else, ie. a family or friend, connect to you via your homeserver.com address?

     

    For note, hoeky emailed me his domain name and I can hit it just fine across the internet... leaving likely leaving DNS issues with his ISP or in his home or one wonkey router.

    Friday, December 7, 2007 10:07 PM
    Moderator

All replies

  • What results do you get if you check the Domain Name Details?

     

    To do so...

    1. Launch Windows Home Server Console
    2. Enter Settings
    3. Select Remote Access tab
    4. Under Domain Name section, click Details button
    Friday, December 7, 2007 1:29 AM
    Moderator
  • those results tell me that everything is working

     

    Friday, December 7, 2007 2:58 AM
  • If all of those results are coming out alright... then it should be accessible... and yet it’s not.


    Stupid question perhaps... are you sure you are typing the domain name properly? Exactly the same as what is shown on the diagnostics screen? Tried both with http and https?

     

    Have you also tried accessing your server using its domain name from outside of your network? If not and you’d like you can email me (address in profile) your domain and I’ll give it a remote try.

     

    Some routers (like mine) give different results when you hit the external domain internally or externally.

    Friday, December 7, 2007 4:34 AM
    Moderator
  • From a PC on your home network try the following...

     

    1. Log onto the http://www.whatismyip.com site and get your current public IP address.

    2. Then go to Start -> Run and type cmd at the command window.

    3. From the command prompt run the nslookup yourWHSname.homeserver.com command.

    4. Compare the reported IP addresses from Step 1 and Step 3. Do they agree?

     

    Where are you trying to remotely access your WHS from?

     

    Some folks, including myself, had problems accessing our WHS servers while staying at hotels. For some reason some hotel internet providers have DNS issues with homeserver.com names.

    Friday, December 7, 2007 12:14 PM
  • Hi Al

    in answer to your question---no the 2 web addresses do not agree.

     

    i'm trying to just type in the windows live address that was assigned to me from microsoft (xxxfamily.homeserver.com)

     

    from my home computer

     

    Friday, December 7, 2007 2:47 PM
  • What does your network configuration look like? Do you have multiple devices between the point where the wire comes through your wall and your server? What devices?
    Friday, December 7, 2007 5:11 PM
    Moderator
  •  hoeky_b wrote:

    Hi Al

    in answer to your question---no the 2 web addresses do not agree.

     

    i'm trying to just type in the windows live address that was assigned to me from microsoft (xxxfamily.homeserver.com)

     

    from my home computer

     

     

    Well, if they don't agree then that's the issue, ie. a DNS problem. Can anyone else, ie. a family or friend, connect to you via your homeserver.com address? If they do a nslookup yourWHSname.homeserver.com command do they report the correct IP, ie. what you see when you went to the http://www.whatismyip.com site?

     

    Just for information and as noted by Ken how is the WHS and your home network connected to the public internet, ie. what type of ISP (cable, DSL, dialup), are you behind a router, etc. Who is your ISP?

    Friday, December 7, 2007 9:56 PM
  •  Al Jarvi wrote:
    Can anyone else, ie. a family or friend, connect to you via your homeserver.com address?

     

    For note, hoeky emailed me his domain name and I can hit it just fine across the internet... leaving likely leaving DNS issues with his ISP or in his home or one wonkey router.

    Friday, December 7, 2007 10:07 PM
    Moderator
  • Hi Ken,

    my network is this--cable modem,4 port router(dlink ebr2310), 8 port switch,2 clients,a dell server running whs (oem)full version.and an hp printer.

    modem to router,server to router with static ip from router,clients(with static ip's) to switch,need router ports for other media,

     

    Sunday, December 9, 2007 4:03 PM
  • Having Trouble with Remote Access????

    For those of you that have issues with the remote access wiih your MediaSmart or Windows Home server, you can try these steps in the tutorial below to help figure out whats wrong.  I've helped several folks in the past few days and it's mainly been issues with Vonage routers or other VOIP routers being IN FRONT of the router that the mediasmart is connected to.

    Take a peek at our TROUBLESHOOTING REMOTE ACCESS FOR YOUR MEDIASMART OR WINDOWS HOME SERVER at http://www.myhomeserver.com/?page_id=22


    Sunday, December 9, 2007 4:24 PM