locked
New Router - No Remote Access RRS feed

  • Question

  • I had Brighthouse/RoadRunner come out and replace the existing modem with a combo modem/wireless router/phone adapter (Ubee 10C022) and now I don't have remote access. Here's what I did.
    Enabled UPNP but it didn't forward ports.
    Manually forwarded ports 80, 443, 4125, and 3389. For each port it asks for a range so for port 80 the Start Port is 80 and the End Port is 80. Same with the rest, the start and end is the port number. Is this correct? Also the protocal is TCP for all ports, correct?
    I also gave a static lease for the servers IP address.
    When I Turn On Remte Access in the Home Server Console, I get the red X by "Verifying that your remote Web site is available from the Internet"
    I don't have anything else between the Ubee Modem/Router and Switch. I use to have a Vonage phone adapter between the old modem and the old Belkin router that required a bunh of fancy configuring but the phone adaptor is just comming off the switch like the computers and printers now. I disabled all the forwarding in the phone adapter but I guess it really didn't matter.
    What else can I try? BTW, I had Brighthouse/Roadrunner before the new modem and it worked.
    Thanks for any help.
    Jamie

    Wednesday, July 13, 2011 2:33 AM

All replies

  • This guide on PortForward.com will show you how to manually forward ports for your server. In addition to that, you will need to set your server up with a static IP address or dhcp reservation (which I think you've already done). As for ports, you don't need port 3389.

    If it still doesn't work afterward, it's possible that your ISP has done something on their network which is blocking some or all of those ports. You can try testing from a friend's house or coffee shop to see if it works anyway.


    I'm not on the WHS team, I just post a lot. :)
    Wednesday, July 13, 2011 1:17 PM
    Moderator
  • Hi Ken,

    Thanks for your reply. 

    The ports were configured correctly.  

    I'm able to get access if I use https instead of http.

    I was able to log in before using http, Why is https required now?  

    One issue though.  We cannot see any computers to establish a remote desktop connection with.  I can access the shared folders but not any computers.  All our computer use Windows 7 Professional.  I do have "allow connections from computers running any version of Remote Desktop" selected.  Anything else I need to configure?

    Thanks again,

    Jamie


    Wednesday, July 13, 2011 3:24 PM
  • Hi Ken,

    Thanks for your reply. 

    The ports were configured correctly.  

    I'm able to get access if I use https instead of http.

    I was able to log in before using http, Why is https required now?  

    One issue though.  We cannot see any computers to establish a remote desktop connection with.  I can access the shared folders but not any computers.  All our computer use Windows 7 Professional.  I do have "allow connections from computers running any version of Remote Desktop" selected.  Anything else I need to configure?

    Thanks again,

    Jamie


    It sounds to me like your ISP has started blocking ports 80 and 4125 (possibly others as well, it's hard to say for sure). You can try the Gibson Research Shields Up! port tests to try to narrow things down. Do a "User Specified Custom Port Probe" for ports 80, 443, and 4125 first, because those are the ones you're most interested in. Probably ports 80 and 4125 will show as "Closed" or "Stealth". Afterward, do a scan of "Common Ports", where I expect you'll find most common ports are also blocked.

    Please be aware that your ISP has the right to block ports if they feel that the services normally accessed over those ports negatively impact other subscribers' use of your ISP's network. Usually this also indicates that your ISP's Terms of Service/Acceptable Use Policy prohibits the running of servers on your residential connection. If this is the case, the safest thing for you to do is determine whether or not it's worth the extra expense for a connection which will allow running a server, and if not, you should probably abandon the attempt, as your ISP could conceivably cut your access off entirely, or charge you unexpectedly for a business class of service (possibly back-dating the charges).


    I'm not on the WHS team, I just post a lot. :)
    Wednesday, July 13, 2011 4:26 PM
    Moderator
  • Well it looks like port 80 is open but port 4125 is closed.  

    I thought I was able to access the Shared Folders because the Folders came into view, but when I tried to open one, Chrome popped up a message, "The type of the token is inappropriate for its attempted use."

    Wednesday, July 13, 2011 5:36 PM