Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Can't set up Remote Access with New Install of Vail using Verizon Fois router A90-9100em RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I just built my server and installed the preview, but can't get past the set up of remote access. Vail reports Remote Access is blocked and UPnP is not enabled. I have logged into my router and configured Remote, UPnp, Ports 80 & 443.

     

    Anyone experience this?

     

    Thanks for your input.

    Jason

    Monday, May 31, 2010 8:03 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Well, I called Verizon and told them I needed a new router, and they brought me a Actiontec MI424WR.

     

    Now everything works as it should!

     

    Thanks for all the suggestions. If anyone else has a problem with Westell, I recommend ActionTec.

    Saturday, June 5, 2010 12:34 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Port 80 and 443 ok, but did you do port forwarding in your router so it knows wher direct ther request to?

    Running double NAT?
    Maybe this address has more info
    http://sbs.seandaniel.com/2010/01/windows-home-server-remote-access.html
    (it has a nice explainig video)

    PS: Give the WHS a static IP address.



    "jmx143" wrote in message news:72c39718-3a3a-4422-815d-a03ee65643e9@communitybridge.codeplex.com...
    I just built my server and installed the preview, but can't get past the set up of remote access. Vail reports Remote Access is blocked and UPnP is not enabled. I have logged into my router and configured Remote, UPnp, Ports 80 & 443.



    Anyone experience this?



    Thanks for your input.

    Jason

    Have a nice day!
    Monday, May 31, 2010 8:22 PM
  • Question
    Sign in to vote
    0
    Sign in to vote


    Can you access your server through http:\\{servername}?
    You will probably get a credentials warning, just ignore that. You should be abled to log in and acess you media.

    If OK, please double check your routers port forwarding settings.
    Ports 80 and 443 should be forwarded to your the IP adress of your server.

    There is a possibility that your ISP blocks TCP port 80 and/or 443.
    You can check using Shields UP! at this url: http://www.grc.com

    - Theo.

    No home server like Home Server
    Monday, May 31, 2010 9:49 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    I also have Verizon FIOS but am using a older ActionTec (4 port) wireless router.

    I read a lot of different peoples suggestions & came upon a post at PROnetworks.

    NT50 suggested:

    1) Reset your router.

    2) Set your Vail machine static IP even tho your running DHCP

    3) and port forward your router to that machine.

    If you need help w/ the Static IP: Type in the Help & Support @ Start menu:

    "Configuring a DHCP server static IP address" w/o the quotes.

    also your IP info is available @ the command prompt type in: ipconfig

    *This worked like a champ for me.

    Monday, May 31, 2010 10:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I just built my server and installed the preview, but can't get past the set up of remote access. Vail reports Remote Access is blocked and UPnP is not enabled. I have logged into my router and configured Remote, UPnp, Ports 80 & 443.

    Anyone experience this?

    Thanks for your input.

    Jason

    In addition to the other suggestions already posted, you should either A) enable uPnP and let Vail configure the ports or B) disable uPnP and configure the ports yourself.  Based on the way you worded it, it sounds like you did both.
    Tuesday, June 1, 2010 3:06 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    I keep having the same problems.  It will give the same warnings and I have tried all of the same solutions mentioned above.  I can access the Vail connect site even when it gives me those warnings.  Every once in a while all will be fine and Vail will say that remote access is available and functional.  Have you tried to see if your router and modem are in bridged mode?  I'm not familular with Fios but I have AT&T dsl with a Dlink DIR-655.  Currently everything is working and I'm trying to pinpoint the problem. 
    Tuesday, June 1, 2010 4:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for all the responses.

    • I can access the http:\\{servername}
    • If I use the domain http:\\SERVER.homeserver.com, it routes me directly to my Verizon Router as if I were using 192.168.1.1
    • For the Port Forward, do I need to forward from 98.168.191.1 (Modem) or 192.168.1.1 (Router)?
    • I did set the Static IP to 192.168.1.151
    • From the video above it appears I may need to bridge?
    Tuesday, June 1, 2010 6:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    > For the Port Forward, do I need to forward from 98.168.191.1 (Modem) or 192.168.1.1 (Router)?

    You must forward to the (static!) IP address of the WHS.
    No need to bridge at all.


    "jmx143" wrote in message news:aed03447-ec7e-496c-b473-bee47cab3856@communitybridge.codeplex.com...
    Thanks for all the responses.

    a.. I can access the http:\\{servername}
    b.. If I use the domain http:\\SERVER.homeserver.com, it routes me directly to my Verizon Router as if I were using 192.168.1.1
    c.. For the Port Forward, do I need to forward from 98.168.191.1 (Modem) or 192.168.1.1 (Router)?
    d.. I did set the Static IP to 192.168.1.151
    e.. From the video above it appears I may need to bridge?

    Have a nice day!
    Tuesday, June 1, 2010 6:37 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Based on your second bullet point, you need to turn off remote administration for your router. You want to leave local administration turned on, however. From your third bullet point, you have two "routers" because your FiOS modem is acting as a router as well as your router. This is usually referred to as a "double NAT" because there are two levels of translation happening. You can either put one of those devices into bridge mode or forward from the modem to the router, and then from the router to your server. Ideally you will put the modem into bridge mode; it's likely the less capable device overall. You should consult with your ISP as to how to do this...
    I'm not on the WHS team, I just post a lot. :)
    Tuesday, June 1, 2010 6:41 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Maybe I missed something, but this seems like a more difficult than needed solution for this. Just setting port forwarding port 443 and 80 to the WHS (using a static IP address for the WHS) is all that is needed for this. No setting router in bridge mode and/or contacting the ISP.



    "Ken Warren" wrote in message news:9619ef1e-e60f-4918-a27a-1fbd2d3153a8@communitybridge.codeplex.com...
    Based on your second bullet point, you need to turn off remote administration for your router. You want to leave local administration turned on, however. From your third bullet point, you have two "routers" because your FiOS modem is acting as a router as well as your router. This is usually referred to as a "double NAT" because there are two levels of translation happening. You can either put one of those devices into bridge mode or forward from the modem to the router, and then from the router to your server. Ideally you will put the modem into bridge mode; it's likely the less capable device overall. You should consult with your ISP as to how to do this...
    ------------------------------------------------------------------------- -----
    I'm not on the WHS team, I just post a lot. :)
    Have a nice day!
    Tuesday, June 1, 2010 7:13 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I called Verizon and they told me to use DMZ Host for the WHS. I guess I will try it out when I get home. Isn't there more risk with DMZ?

     

    Thanks

    Tuesday, June 1, 2010 7:18 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Leen, unless I misunderstand him his FiOS modem is a router, and then he has another router daisy chained off of that. The solutions for double NAT are to put something into bridge mode (I recommend the modem), or forward from the modem to the router, and from the router to the server.

    I don't recommend putting the server into the router's DMZ, by the way, because most routers will then prevent internal access to the server on the local subnet.

    I'm not on the WHS team, I just post a lot. :)
    Tuesday, June 1, 2010 7:28 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Ken,

     

    (Mostly) Correct. The Fios modem is also the router which is connected to the WHS via ethernet (no further devices or daisy chains). I have the port forwarding down, have verified with shields up that my ports are open, but for some reason I can not enable upnp. I have the manual have have checked the respective boxes in advance/upnp, then apply/reboot router/WHS.. Its getting a lil frustrating. I agree with Leen, it shouldn't be this difficult.

     

    Thanks

    Wednesday, June 2, 2010 3:27 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    So you have only a single device? From what you're saying now, I doubt that your modem/router fully supports UPnP configuration, no matter what the manual might say. So turn off UPnP and manually configure the modem. Then turn off Remote Access on your Vail server and turn it back on. It should detect that the router is manually configured and everything should be okay.
    I'm not on the WHS team, I just post a lot. :)
    Wednesday, June 2, 2010 3:36 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Well, thanks for all the suggestions, but I am still unsuccessful with WHS Vail remote access. I continually get the error that upnp is not enabled (although Westell CS reports that all FOIS routers are by default upnp enabled to allow VOD apps) and remote access is not turned on (even though I forwarded the ports/DMZ'd/bridged) I have restored defaults and tried every combination that I could think of from the suggestions listed above. I even tried a Portforward program and tested with shields up (and a few others, all report 80 & 443 are open).

     

    I am open to any suggestions at this point..

     

    Thanks again.

    'Jason

    Thursday, June 3, 2010 3:28 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yes, you don’t want to use the DMZ.  You do want to create a DHCP reservation for Vail, and then forward ports 80 and 443 to that.  Also, make sure the IP address you’re getting from your ISP to your routers Internet facing port (WAN Port) is a public IP address (http://en.wikipedia.org/wiki/Public_IP_Address).  You may also want to ask Verizon if they block ports for you...
     
    You’ll want a routable/public Internet IPv4 address, an ISP that doesn’t block ports 80 or 443 on your behalf (some do this to prevent servers from running on their network without paying for server-class internet), and then open these ports on your router pointed to your Vail box.  the Vail box will need a DHCP reservation on the router, so it gets the same IP address each time.
     
    Hope this helps,
       Sean
     
    This post is "AS IS" and confers no rights.
    "jmx143" wrote in message news:c9d6f650-1169-4a9b-ad45-76e4637070a8...

    I called Verizon and they told me to use DMZ Host for the WHS. I guess I will try it out when I get home. Isn't there more risk with DMZ?

     

    Thanks

    Thursday, June 3, 2010 5:20 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Well, I called Verizon and told them I needed a new router, and they brought me a Actiontec MI424WR.

     

    Now everything works as it should!

     

    Thanks for all the suggestions. If anyone else has a problem with Westell, I recommend ActionTec.

    Saturday, June 5, 2010 12:34 AM