Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
On Verizon DSL, remote access worked when setup now not available RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    I setup my home server about a month ago and went through the steps to setup remote access and had everything confiured and working. Today I am unable to get remote access working, the process failes when checking my site is accessible from the web. Is this because Verizon is blocking ports or something else? I am also not able to connect from within my network. Im a bit puzzled because it all worked when I first setup my WHS.
    • Edited by efjay Thursday, July 2, 2009 3:33 PM more info
    Thursday, July 2, 2009 3:22 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Yes, as I said initially, it's likely that it's Verizon. Everything since is to eliminate anything that you might be able to deal with yourself. :)

    As for Verizon, they are, to be honest, unlikely to open up those ports for you. Per their Terms of Service, you're prohibited from connecting any servers to your Verizon DSL connection. Your best option (in terms of probability of success) is to buy business class service from them, at a higher cost per month.
    I'm not on the WHS team, I just post a lot. :)
    • Marked as answer by efjay Thursday, July 30, 2009 6:03 PM
    Friday, July 3, 2009 8:06 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Update: I have moved to Comcast and remote access is working fine.
    Thursday, July 30, 2009 6:05 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    It's possible (likely) that Verizon is blocking ports, though there are other possibilities. You can test this by using the Shields Up! web site; assuming you have the correct ports (80, 443, 4125) forwarded from your router to your server, Shields Up! should report 80 and 443 as OPEN, and 4125 as CLOSED. If Shields Up! reports a port as STEALTH, either it's not forwarded properly or there is something blocking the port. Get back to us in that case and we may be able to help you further.
    I'm not on the WHS team, I just post a lot. :)
    Thursday, July 2, 2009 3:40 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    So run the scan from the server or another pc on the network?
    Thursday, July 2, 2009 3:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Running from my pc Shields up reports that ports 443 and 80 are stealth, i dont see a listing for port 4125.
    Thursday, July 2, 2009 4:41 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Don't worry about 4125 just yet (you would have to run a custom scan on Shields Up! to test it, by the way). And running from any computer on your network is fine; if the ports are forwarded to your server, you're testing your server.

    Next steps: If 443 and 80 are both showing STEALTH, either they're not forwarded properly or something is blocking them. To make a start at determining what the issue is, check your server's IP address, and confirm that you're forwarding to that address in your router. Once that's taken care of, take a look at your router's configuration pages. Somewhere it should report your router's WAN IP address, though it might be named differently. Compare that IP address to the IP address reported when you type ping myserver.homeserver.com at a command prompt. If they're the same, then your ISP is probably blocking ports 80 and 443. If they're not the same, it could just be that your WAN IP address has changed and your server hasn't updated the "Live Domain" server yet.

    I'm not on the WHS team, I just post a lot. :)
    Thursday, July 2, 2009 5:02 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I checked the server IP address and confirmed it is reserved and has the correct ports forwarded to it. As for the WAN address my DSL modem assigns an IP to my router and that is what is listed in the router settings however the IP address reported in the home servr console as my website address matches the IP displayed on the DSL modem. I was also successfully able to ping my website address from my pc and it returned the correct IP address.
    Thursday, July 2, 2009 5:21 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I checked the server IP address and confirmed it is reserved and has the correct ports forwarded to it. As for the WAN address my DSL modem assigns an IP to my router and that is what is listed in the router settings however the IP address reported in the home servr console as my website address matches the IP displayed on the DSL modem. I was also successfully able to ping my website address from my pc and it returned the correct IP address.

    Sounds to me like Verizon is now blocking those ports.  You might try calling them to confirm.
    Friday, July 3, 2009 12:49 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I checked the server IP address and confirmed it is reserved and has the correct ports forwarded to it. As for the WAN address my DSL modem assigns an IP to my router and that is what is listed in the router settings however the IP address reported in the home servr console as my website address matches the IP displayed on the DSL modem. I was also successfully able to ping my website address from my pc and it returned the correct IP address.

    Sounds to me like Verizon is now blocking those ports.  You might try calling them to confirm.

    If this is the case do I have any alternatives other than trying to find another ISP? Thing is in my area in Maryland my only other option is Comcast and Im not sure if I will have the same problem with them.
    Friday, July 3, 2009 1:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    If this is the case do I have any alternatives other than trying to find another ISP? Thing is in my area in Maryland my only other option is Comcast and Im not sure if I will have the same problem with them.
    You could always ask if they have a plan that would allow it (although it would probably cost more).  The other option would be to change the ports used, but that's not supported, not really easy to do, and not recommended because you would probably be violating your contract with Verizon.
    Friday, July 3, 2009 1:10 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Let me restate to make sure I understand your configuration:
    • Your server has ip address aa.aa.aa.aa, which is either assigned as a static IP address through manual configuration of the server, or is assigned as a DHCP reservation for your server's MAC address in your router.
    • Your router shows the correct ports forwarded to IP address aa.aa.aa.aa.
    • Your router shows IP address bb.bb.bb.bb as it's WAN IP address.
    • Your DSL modem shows IP address cc.cc.cc.cc as it's WAN IP address.
    I assume when you pinged your home server via your vanity URL you got back IP address cc.cc.cc.cc? And this is the address your home server reported? Have you tested access to your web site from a location other than your home? If not, please do so.

    If you have, and it didn't work, probably your DSL modem is acting as a router, and the ports your home server needs aren't forwarded. I would recommend you see if there's a way to put your DSL modem into "bridge" mode. If not, see if you can configure it to forward ports to your router, and forward the same ports (80, 443, 4125) to your router that you've forwarded from your router to your server. But best would be to put your DSL modem into bridge mode, because then it won't act as a router.
    I'm not on the WHS team, I just post a lot. :)
    Friday, July 3, 2009 2:15 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Let me restate to make sure I understand your configuration:
    • Your server has ip address aa.aa.aa.aa, which is either assigned as a static IP address through manual configuration of the server, or is assigned as a DHCP reservation for your server's MAC address in your router.
    • Your router shows the correct ports forwarded to IP address aa.aa.aa.aa.
    • Your router shows IP address bb.bb.bb.bb as it's WAN IP address.
    • Your DSL modem shows IP address cc.cc.cc.cc as it's WAN IP address.
    I assume when you pinged your home server via your vanity URL you got back IP address cc.cc.cc.cc? And this is the address your home server reported? Have you tested access to your web site from a location other than your home? If not, please do so.

    If you have, and it didn't work, probably your DSL modem is acting as a router, and the ports your home server needs aren't forwarded. I would recommend you see if there's a way to put your DSL modem into "bridge" mode. If not, see if you can configure it to forward ports to your router, and forward the same ports (80, 443, 4125) to your router that you've forwarded from your router to your server. But best would be to put your DSL modem into bridge mode, because then it won't act as a router.
    I'm not on the WHS team, I just post a lot. :)

    Ken, you are correct in all your assumptions and I have already configured the DSL modem to forward the required ports to my router's IP address. This was done back when I initially was setting up remote access and everything worked then, tested by using my phone to browse via an EDGE connection to the remote web address and confirmed the site was functioning. Now it seems comething has changed and I'm inclined to think its as kariya21 suggested, that Verizon is now blocking those ports.
    Friday, July 3, 2009 2:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yes, as I said initially, it's likely that it's Verizon. Everything since is to eliminate anything that you might be able to deal with yourself. :)

    As for Verizon, they are, to be honest, unlikely to open up those ports for you. Per their Terms of Service, you're prohibited from connecting any servers to your Verizon DSL connection. Your best option (in terms of probability of success) is to buy business class service from them, at a higher cost per month.
    I'm not on the WHS team, I just post a lot. :)
    • Marked as answer by efjay Thursday, July 30, 2009 6:03 PM
    Friday, July 3, 2009 8:06 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Update: I have moved to Comcast and remote access is working fine.
    Thursday, July 30, 2009 6:05 PM