locked
Help: Can't connect via ***********.homeserver.com RRS feed

  • Question

  • I have ports forwarded on Apple Airport Extreme router, but can not acces my server via the internet?? Any idea what I am doing wrong?? I am on Charter Communications cable in Birmingham, AL.

     

    Remote access was my main reason for purchase.

    Monday, January 14, 2008 5:45 AM

Answers

  • It's possible that your ISP is blocking access to one or more of the ports used by Windows Home Server. Before you test that, though, can you confirm that you've set your router to forward ports 80, 443, and 4125 to the internal IP address assigned to your server (probably something like 192.68.xx.yy)? And are you doing your testing from inside your network or outside (i.e. Starbucks/internet cafe/public library/etc.)? If inside, try it from outside; many routers have issues looping back to their own IP address from inside the network.

    If everything is set correctly, you can use a site such as Shields Up! to test your network connection. You'll want to test ports 80, 443, and 4125. Let us know the results of the tests, but ports that come back as "stealthed" are blocked somewhere (probably your ISP).
    Monday, January 14, 2008 12:29 PM
    Moderator
  •  

    A couple of quick questions:

     

    1. are you connecting to http://****.homeserver.com/home  you need the home on the end.

    2. Did you try connecting to https://***.homeserver.com/home ? sometimes ISP's block port 80.

     

    Jim

    Monday, January 14, 2008 12:30 PM

All replies

  • It's possible that your ISP is blocking access to one or more of the ports used by Windows Home Server. Before you test that, though, can you confirm that you've set your router to forward ports 80, 443, and 4125 to the internal IP address assigned to your server (probably something like 192.68.xx.yy)? And are you doing your testing from inside your network or outside (i.e. Starbucks/internet cafe/public library/etc.)? If inside, try it from outside; many routers have issues looping back to their own IP address from inside the network.

    If everything is set correctly, you can use a site such as Shields Up! to test your network connection. You'll want to test ports 80, 443, and 4125. Let us know the results of the tests, but ports that come back as "stealthed" are blocked somewhere (probably your ISP).
    Monday, January 14, 2008 12:29 PM
    Moderator
  •  

    A couple of quick questions:

     

    1. are you connecting to http://****.homeserver.com/home  you need the home on the end.

    2. Did you try connecting to https://***.homeserver.com/home ? sometimes ISP's block port 80.

     

    Jim

    Monday, January 14, 2008 12:30 PM
  • While on your own home network, if you type http://servername into a browser does your site come up?

    Monday, January 14, 2008 12:34 PM
  • I checked from outside the network this morning and I can access the server remotely. Thanks!!!

    Monday, January 14, 2008 7:24 PM
  • @Auble what did you do to make this work for you. I am having the same problem. Couple of differences with my config: 1) FiOS is my ISP and 2) My actionTech router is set as a bridge and my AEB is the router.

    Any help is appreciated.

    Thanks.
    Monday, January 14, 2008 10:39 PM
  • Make sure that you are using HTTPS://*******.homeserver.com/home

     

    I was not putting the /home at the end of the URL.

     

    Also, follow the moderator's suggestions above and use SheildsUp to test your ports. From inside your network you can type http://servername to see if you can access internally.

    Monday, January 14, 2008 10:51 PM
  • Adaniali, FiOS is a product of Verizon. It's my understanding that Verizon blocks almost all ports to prevent customers from running servers on their network. You can use the Shields Up! site I linked earlier to determine (from your home) if your ports are blocked.
    Monday, January 14, 2008 11:02 PM
    Moderator