Sign in
Microsoft.com
 
Microsoft
 
 
 
Microsoft >
> 
> 
> 
Port forwarding is not configured correctly

Answered Port forwarding is not configured correctly

  • Monday, May 14, 2012 3:56 PM
     
     
    Sign In to Vote
    0

    I am getting the following message setting up remote access:

    Port forwarding is not configured correctly. The port forwarding settings for your router cannot be found. Your router might have been recently updated or rebooted, or another device might be attempting to forward the same ports as your server. THIS PROBLEM WILL BE AUTOMATICALLY RSOLVED (caps for emphasis)  Huh?

    • ISP: Century Link
    • Modem/Router: Zyxel 5000Z
    • DHCP Range: 192.168.0.2 - 192.168.0.150
    • Server IP: not included in the DHCP Range
    • manually forward port 80, 443, 4125
    • UPnp is enabled, but turning it off doesn't work either
    • remote access: https://remote.xxxxxxxxx.com

    If I cannot get it solved, does anybody know if the Netgear N900 (WNDR4500) works, if I put the Zyxel into bridge mode using PPPoe? Instructions would be helpful... Thank you all!

     

All Replies

  • Monday, May 14, 2012 7:14 PM
     
     
    Sign In to Vote
    0
    Firstly you do not need Port 4125 for WHS2011 and Port 80 is only optional. Port 443 is the only essential port for https:// access. If WHS can't configure your router, then you will have to forward Port 443 to your server IP address. Check ShieldsUp at www.grc.com to confirm the ports you are forwarding are not blocked (shown as "Stealth") by your ISP. Then if that's all OK, check from an external internet location to see if it's actually working.

    Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.

     
  • Monday, May 14, 2012 7:53 PM
     
     
    Sign In to Vote
    0
    Firstly you do not need Port 4125 for WHS2011 and Port 80 is only optional. Port 443 is the only essential port for https:// access. If WHS can't configure your router, then you will have to forward Port 443 to your server IP address. Check ShieldsUp at www.grc.com to confirm the ports you are forwarding are not blocked (shown as "Stealth") by your ISP. Then if that's all OK, check from an external internet location to see if it's actually working.

    Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.

    Thanks for your answer. I went to the ShieldsUp site and tested port 80 and 443; they are open. I did forward the ports to the server's static IP address. My next step is finding a location to try it out... in the middle of Nowhere, USA... That presents a challenge all by itself.

    Considering what you said, are you telling me that WHS 11 may give me an error message even though it might be working correctly? Hmmmm...

     
  • Monday, May 14, 2012 11:20 PM
     
     
    Sign In to Vote
    0

    Result from Microsoft Internet Connectivity Tool

    NAT Translator Type and UPnP Support are not supported by my router

    However, presently UPnP and UPnP NAT-T is enabled plus the forwarded ports to the server are listed. I have also tried to disable both, with just the forwarded ports listed that I needed to forward to the server... this seemed to produce even more error messages. Am really scratching my head to find a solution for this. I am beginning to wonder if I shouldn't just go ahead and bridge the Zyxel router and attach the Netgear N900. I paid way too much money for it and don't want to open the package, unless I absolutely have to. Ideally, I would much rather return it; nevertheless, if I could make it work, it would be well worth it.

    Suggestions anybody? Thanks much :)

     
  • Tuesday, May 15, 2012 7:21 AM
    Moderator
     
     Answered
    Sign In to Vote
    1

    Thanks for your answer. I went to the ShieldsUp site and tested port 80 and 443; they are open. I did forward the ports to the server's static IP address. My next step is finding a location to try it out... in the middle of Nowhere, USA... That presents a challenge all by itself.

    Considering what you said, are you telling me that WHS 11 may give me an error message even though it might be working correctly? Hmmmm...

    yes, this may happen, since the routines try to perform a check, which with some routers will not work from inside the LAN.

    Also it might be the case, that the router itself has its Remote administration feature enabled, which is usually also sitting on port 443.

    If you cannot find someone else, you could send me a message containing the url of your homeserver.com domain to check, if it is reachable from outside. (Besides the fact, if you never use this functionality, you don't need to activate it.)

    Best greetings from Germany
    Olaf

     
  • Tuesday, May 15, 2012 1:13 PM
     
     
    Sign In to Vote
    0

    Thanks for your answer. I went to the ShieldsUp site and tested port 80 and 443; they are open. I did forward the ports to the server's static IP address. My next step is finding a location to try it out... in the middle of Nowhere, USA... That presents a challenge all by itself.

    Considering what you said, are you telling me that WHS 11 may give me an error message even though it might be working correctly? Hmmmm...

    yes, this may happen, since the routines try to perform a check, which with some routers will not work from inside the LAN.

    Also it might be the case, that the router itself has its Remote administration feature enabled, which is usually also sitting on port 443.

    If you cannot find someone else, you could send me a message containing the url of your homeserver.com domain to check, if it is reachable from outside. (Besides the fact, if you never use this functionality, you don't need to activate it.)

    Best greetings from Germany
    Olaf

    Olaf,

    Dankeschoen... Ich bin ja auch Deutsche (von Frankfurt). Ich wohne seit 1976 in den Staaten... wuerde gerne wieder nach Deutschland kommen.

    Nevertheless, I am going to send you a message and let you try it out. I would use the functionality when I am traveling to a more populated region.

    Noch mal vielen Dank... Thanks again for your reply!

    Angie

    PS: I just remembered that the router does have the remote administration enabled.

     
  • Tuesday, May 15, 2012 3:14 PM
     
     
    Sign In to Vote
    0

    <<If you cannot find someone else, you could send me a message containing the url of your homeserver.com domain to check, if it is reachable from outside. (Besides the fact, if you never use this functionality, you don't need to activate it.)>>

    Just wanted to let everyone know, Olaf ( Thank you :)) ) was able to get to the homeserver.com site successfully from the outside. Thus, before you buy a new "compatible" router, try this method first. I am a happy camper now :)

     
  • Sunday, May 27, 2012 1:40 PM
     
     
    Sign In to Vote
    0
    I just wanted to add, that logging into my server from the outside was also successful.