locked
Home Server Remote Access Problems RRS feed

  • Question

  • Recently I installed home server on a computer that has been lying around

     

    When i configured remote access, due to my routers lack of UPnP support (even though it says there is) i was unable to configure it

     

    So i went and configured it myself, forwarding all the ports required

    80

    443

    4125

    Even though i forwarded it

    i was stopped at the step, checking remote website on the internet,

    So i thought maybe the ports were blocked and changed them to alternates

    Still did not work

    Can anyone please help?

     

     

    • Moved by Miles Li Monday, October 11, 2010 8:04 AM (From:Small Business Server)
    Sunday, October 10, 2010 2:06 PM

All replies

  • I'd ask them here.

    http://social.microsoft.com/Forums/en-US/category/WindowsHomeServer/

     

     

     


    Regards, Dave Patrick .... Microsoft Certified Professional -Microsoft MVP [Windows]
    Sunday, October 10, 2010 2:12 PM
  • See here for the FAQ on Remote Access problems.  (By Tom Ziegmann)
     
     
    BTW, the FAQ
     
     
    is a good first place to start when experiencing problems.  Most likely, someone else has experienced the problem and it will be covered there.
    --
    _________________
     
    BullDawg
    In God We Trust
    _________________

    I'd ask them here.

    http://social.microsoft.com/Forums/en-US/category/WindowsHomeServer/

     

     

     


    Regards, Dave Patrick .... Microsoft Certified Professional -Microsoft MVP [Windows]

    BullDawg
    Monday, October 11, 2010 10:10 AM
  • You need port 3389 also.
    Wednesday, October 20, 2010 11:41 PM
  • You need port 3389 also.


    No.

    Windows Home Server uses port 3389 only inside your local network; there is no need to forward that port from your router to your server.


    I'm not on the WHS team, I just post a lot. :)
    Thursday, October 21, 2010 1:08 PM
    Moderator
  • This might be a silly question, but is your cable or DSL modem acting as a NAT device? This is a problem I ran into initially because the DSL modem was handling PPoE/authentication with its own router/firewall. I fixed the problem by configuring the DSL modem as a bridge (e.g. it’s a dumb pass-through device now) and configuring a LinkSys router to handle PPoE and authentication with the DSL provider.
     
    You might also check to determine if your ISP is blocking incoming ports. If this is the case, you might search for a set of ports that are open and have your router port forward from the open ports to 80/443/4125 internally.
     
    "mliyanagamage" wrote in message news:9ce5ba3e-2459-4ae6-b939-06f03dc57501...

    Recently I installed home server on a computer that has been lying around

     

    When i configured remote access, due to my routers lack of UPnP support (even though it says there is) i was unable to configure it

     

    So i went and configured it myself, forwarding all the ports required

    80

    443

    4125

    Even though i forwarded it

    i was stopped at the step, checking remote website on the internet,

    So i thought maybe the ports were blocked and changed them to alternates

    Still did not work

    Can anyone please help?

     

     

    Wednesday, January 5, 2011 12:24 AM