locked
Router port forwarding issues - Westlink 327 DSL router RRS feed

  • Question

  • I am at a deadend, and need some help.

    I had the evaluation version of WHS, and had no problems with the automatic configuration WHS did on the router, and was able to access my website, and use Remote Desktop.

    I had a hard drive failure, and replaced the hard drive, and while I was at it I purchased the OEM version of WHS.

    Now the router won't allow me to access my website or remote desktop.

    I am using AT&T DSL;  same ISP, same router (all hardware is the same, except for the new hard drive)

    I manually forwarded ports 80, 443 and 4125, I have went to Shields Up!, and checked to make sure these port are open, and all showed as open except for 4125, which didn't show up at all on Shields Up!

    i have unconfigured, reconfigured, manually forwarded ports, etc..but to no avail

    everything works fine on my LAN, but can;t seem to gain access from the outside.

    Any thoughts? Suggestions?
    Thursday, October 16, 2008 5:00 PM

Answers

  • Hello,
    maybe, the IP address of your server is not the same as before, and you still try to use the old address for forwarding?
    Did you redo the Remote Access features via WHS console?
    Please check, what is the result of
    ipconfig /all
    entered in a command prompt on the Windows Home Server desktop.
    Validate, if this is the address, to which you did the forwarding.

    Can you access your WHS from one of your clients via
    http://server:55000 (replace server with the name you gave to your WHS)?

    Would https://server/home/default.aspx?gotodefault=true work (after clicking continue at the certificate warning)?
    If both commands work, this means, that the Internet Information service of your WHS seems to be ok.

    A more simple reason:
    It seems there is currently an issue with Windows Live Custom Domains registration (since some hours registration fails for me), so if your router got a new IP address since last registration, this can not work.

    Workaround: If your router supports Dynamic DNS, create an account at www.dyndns.org, register a free site and configure your router to propagate itself against dyndns with that site/account.
    Best greetings from Germany
    Olaf
    Thursday, October 16, 2008 7:25 PM
    Moderator

All replies

  • Hello,
    maybe, the IP address of your server is not the same as before, and you still try to use the old address for forwarding?
    Did you redo the Remote Access features via WHS console?
    Please check, what is the result of
    ipconfig /all
    entered in a command prompt on the Windows Home Server desktop.
    Validate, if this is the address, to which you did the forwarding.

    Can you access your WHS from one of your clients via
    http://server:55000 (replace server with the name you gave to your WHS)?

    Would https://server/home/default.aspx?gotodefault=true work (after clicking continue at the certificate warning)?
    If both commands work, this means, that the Internet Information service of your WHS seems to be ok.

    A more simple reason:
    It seems there is currently an issue with Windows Live Custom Domains registration (since some hours registration fails for me), so if your router got a new IP address since last registration, this can not work.

    Workaround: If your router supports Dynamic DNS, create an account at www.dyndns.org, register a free site and configure your router to propagate itself against dyndns with that site/account.
    Best greetings from Germany
    Olaf
    Thursday, October 16, 2008 7:25 PM
    Moderator
  • Olaf,
    Thanks for your help.
    here are the results:

    ipconfig/all results in the same IP address I have the ports forwarded to.

    I can access WHS from my client with http://server:55000

    I can access my webpage from https://server/home/default.aspx?gotodefault=true from my client

    It is possible that my router got a new IP address since last registration, and my router does support dynamic DNS, but I am unfamiliar with how to set up router to propagate itself against dyndns







    Friday, October 17, 2008 12:39 AM
  • Ok,
    I am now able to access website from the WAN, and gain remote access from there.
    Still can;t connect through remote desktop.

    What I did was to unconfigure my website, configured new website, with new name, basically re-registering with with Windows Live custom domains.

    So obviously my router has been assigned a different IP address, which is why my website wasn't working.

    Now if I could figure out the RDP issue, i'd be set!

    Thanks again
    Friday, October 17, 2008 12:56 AM
  • Hello,
    what do you mean with RDP issue?
    Do you try to use Remote Desktop to your WHS from outside and it doesn't work?
    In this case (which is also an unsupported scenario) you need to forward port 3389 to your server and change the Firewall settings on your WHS for Remote Desktop to allow connections from outside the local subnet.

    Best greetings from Germany
    Olaf
    Friday, October 17, 2008 6:31 AM
    Moderator