locked
unable to view remotely RRS feed

  • Question

  •  

    I've set up port forwarding on my Dlink DSL-G604T in the 'virtual server' under a user rule called WHS (ports 433, 80, 4125, 55000, 56000) and rebooted the 604T.

     

    I can vew and login on my lan using http://10.1.1.2 which is assigned/reserved to the WHS, and allocated in IIS manager to the default and WHS site, and i added my static IP to both websites (default and WHS) and tried that.

     

    Downstream from my router I have a linksys gigabit lan switch with 4 ports, and this is connected to the WHS via a dlink pci card that supports gigabit lan. I have disabled the original onboard lan port in the WHS.

     

    My router is configured to use my static ip address 124.149.X.XXX and if I type in http://dailycomputer.homeserver.com I end up logging in to my router remotely... and https://dailycomputer.homeserver.com returns an error without a code and under more information it states it could not resolve the address or there is no internet connection etc.

     

     

    Using an internet connectivity tool posted elsewhere on this forum I was unable to run a UPnP test and the 604T has a UPnP checkbox and this works when setting up remote access via 'console'. The tool does not like my NAT method, and the 604T either has it on or off - there's no more settings than that.

     

    When I first set up this WHS box, I had little difficulty with remote access, at least from behind my LAN using a browser, so I know it can work...

     

    It is possible that in the above instance my WHS was directly connected to a router port, rather than a hub/switch port...

     

    Any ideas about what might be causing my difficulties anyone? Advance thanks..

    Tuesday, April 22, 2008 1:20 AM

Answers

  • Please test from somewhere off your home network. Many routers are unable to loop back to their external IP address successfully; showing the router configuration web site is one symptom of this issue.

    Also, you only need to forward 80, 443, and 4125. There's no need to forward 55000 or 56000.
    Tuesday, April 22, 2008 3:14 AM
    Moderator

All replies

  • Forgot to mention, 10.1.1.2 is also in the DMZ!

     

    Tuesday, April 22, 2008 1:36 AM
  • Please test from somewhere off your home network. Many routers are unable to loop back to their external IP address successfully; showing the router configuration web site is one symptom of this issue.

    Also, you only need to forward 80, 443, and 4125. There's no need to forward 55000 or 56000.
    Tuesday, April 22, 2008 3:14 AM
    Moderator
  • A couple of things stick out:
    1- you have remote admin enabled on the router.  Because of that, you cannot, no matter what you do, forward TCP/80 (http) to anything on your LAN.  Disable it (also, having remote admin enabled isn't the greatest idea, from a security standpoint.)
    2- is this a typo, or did you actually enter it in your port forwarding:

    ports 433, 80, 4125, 55000, 56000
    https uses TCP/443.  Smile

    As Ken said, there's no reason to forward anything but 80, 443, and 4125 to your WHS.

    Tuesday, April 22, 2008 3:28 AM