Asked by:
Router and remote access

Question
-
Hi i setup WNS Vail on wednesday install went smoothly first time and everything has been running perfectly, untill this morning i started getting a critical error in the dashboard that i had a router error and that my remote access is not working, yet when i connect to my home page the login screen appears and i can log in and access all the services.
I have rebooted the server along with rebooting my router but Vail gives me the same error, has anyone else experienced this?.
Sunday, May 2, 2010 10:50 AM
All replies
-
are you trying to connect from behind the same network or from outside?On Sun, 2 May 2010 10:50:49 +0000, nigel1107 wrote:>>>Hi i setup WNS Vail on wednesday install went smoothly first time and everything has been running perfectly, untill this morning i started getting a critical error in the dashboard that i had a router error and that my remote access is not working, yet when i connect to my home page the login screen appears and i can log in and access all the services.>>I have rebooted the server along with rebooting my router but Vail gives me the same error, has anyone else experienced this?.
Barb Bowman www.digitalmediaphile.comSunday, May 2, 2010 12:27 PM -
Its was the same which ever way a connection was tried, could log in but getting the critical error from the dashboard, after a couple of reboots of the server i'm no longer getting the critical error but when i log in via remote access the media library are showing no entries in the picture, music and video's but they are showing in the shared folder section of the remote access.Sunday, May 2, 2010 12:44 PM
-
I have no clue yet on how remote media gets populated yet. Mine does the same way. Also sometimes computers say offline when they are online.
Reboot again :)
GreySunday, May 2, 2010 1:09 PMModerator -
Is the error still there on your dashboard? do you have internet connectivity? There is a “check” process that involves some complicated tests against the Internet to provide you with “the best we can” diagnostics on what’s possibly going wrong with your router/internet connectivity for remote access. It functions similar to WHS v1 PP3.Additionally, some routers return “interesting” responses when queried via UPnP, so while we do a LOT of work to handle as many as possible, they sometimes don’t always return what we expect. You might also try rebooting your router to clear any memory leaks in it.Sean
This post is "AS IS" and confers no rights."Still Grey" wrote in message news:1de55127-61c0-40c1-99c2-5699bf17db22...I have no clue yet on how remote media gets populated yet. Mine does the same way. Also sometimes computers say offline when they are online.
Reboot again :)
GreyMonday, May 3, 2010 4:32 PMModerator -
Hi a few hours after i atarted this thread i decided to restore Vail from a backup which went great after which everything was back to normal.
Untill about an hour ago i rebooted the server and the same problem was back, i reset the router and server again no luck i also cleared the UPnP forward list and tried the repair in vail which failed indicating portforward errors. But as i'm writing this the server settings window in dashboard is telling me the remote service is not working, but i am logged in remotey and can see all my shares and playing from my music folder using the remote music player.
Any ideas
Tuesday, May 4, 2010 11:32 AM -
I see the same thing every now and then on dashboard also - critical alert that the Router is not configured. In every case so far it has been configured and working fine, so there seems to be some 'misunderstanding' between VAIL and my router.
btl.
Thursday, May 6, 2010 7:54 PM -
I have the exact same problem. The WHS icon turns red and informs me that remore access isn't available and that there is a problem with my router. Yet, when I check it, everything is fine, both from within and without the network. I have checked the "ignore" box because it is irritating.
UPDATE: I finally decided to reset my router and to manually add port forwarding. It worked. I haven't had a red alert since late last night. Usually, I got an alert every hour or so. I'm using a Netgear router (Wireless N 300). I have two switches in operation, as well. But everything is fine. I can access by remote within my network and from outside of it. I had a friend (using a guest setup) check for me.
UPDATE: I spoke too soon. I am, again, getting the same error as I was previously.
- Proposed as answer by palavering Friday, May 14, 2010 6:28 PM
- Edited by palavering Saturday, May 15, 2010 4:15 AM
Friday, May 7, 2010 3:40 AM -
Thanks for raising this issue guys. Can you guys log bugs via connect with server logs? We identified some similar issues but want to make sure they are the same root causes.
windows home server teamFriday, May 7, 2010 8:30 AM -
I also have the same problem
Is this have something to do with DDNS's . we set up on the server
router setup
I set HTTP 80 port to forward to my computer
I set HTTPS 443 port to forward to my computer and Protocol (TCP,UDP to on )
I use a Linksys E1000 router brand new.
Friday, May 7, 2010 12:39 PM -
Confirming the same issue. I have accessed from internal home network and from work (10 miles away) with no trouble.
Steps taken:
Ensured UPnP is enabled on the router
Enabled DMZ and directed it at the server
Log created and updated on the Connect website:
- Edited by CraziMonki Saturday, May 8, 2010 3:28 AM additional information
Saturday, May 8, 2010 3:27 AM -
I am having the same problem. I have FIOS with an ActionTec router. UpnP is turn on. The remote wizard sets up and opens 80 and 443 ports but the wizard comes back and says there are closed. Yesterday I opened remote port 4125 and ran the wizard and it started working. This morning WHS came back with a critical error that remote access stopped working. Can not get it to work. This is just FYI. Any help would be greatly appreciated.Sunday, May 9, 2010 12:10 PM
-
abulaski, if you're talking about port 4125 you're talking about Windows Home Server V1, I assume? Vail doesn't need port 4125, per Microsoft in a different thread. A better place to ask about V1 would really be the Software forum.
That said, to the best of my knowledge Verizon blocks access to ports 80 and 443 for residential customers. Vail doesn't really let you move to different ports; for one thing the TS gateway is currently wired down to 443, so a Verizon FiOS internet connection really precludes the use of remote desktop or the dashboard via the Remote Access web site (even if you do change the ports in IIS).
I'm not on the WHS team, I just post a lot. :)Sunday, May 9, 2010 1:46 PMModerator -
Hi for over a week now i've been having the same problem over and over Vail on day everything seems fine with the remote access then if i reboot the server i then get a critical error in the dashboard Remote access and router not configered. Again as i'm writing this my dashboard is telling me i have no remote access and the router isn't working, yet friends can still see my remote home page and blog. I even went as far as replacing my router on thursday for a new n+ one, Vail could not set its self up on there either untill i applied a static ip adress and set up the port forder for 80 and 433 then i ran the wizard again and its been fine since friday. But after rebooting the server today again no remote access in the dashboard but remote access is working.Sunday, May 9, 2010 2:16 PM
-
Hi Ken,
Thanks for your reply. No this is Vail. I had WHS v1 working with remote access for three months using the trial version with Verizon Fios. I was going to buy v1 but I plan on waiting for v2. When I added port 4125 to my router remote access worked for a day. I can not get it to work no matter what I try.
Thanks,
Arnie
Sunday, May 9, 2010 5:56 PM -
I am having the same problem. I have FIOS with an ActionTec router. UpnP is turn on. The remote wizard sets up and opens 80 and 443 ports but the wizard comes back and says there are closed. Yesterday I opened remote port 4125 and ran the wizard and it started working. This morning WHS came back with a critical error that remote access stopped working. Can not get it to work. This is just FYI. Any help would be greatly appreciated.
Hi Abulaski:when you say it stopped working, do you mean you actually cannot connect to RWA from outside, or you see a critical error in dashboard? My take of the issue is the critical is a false alarm about the router status which you can safely ingore, is it the case for you?
Thanks.
windows home server team- Proposed as answer by Jonas Svensson -FST- Tuesday, May 11, 2010 12:04 AM
Monday, May 10, 2010 7:06 AM -
Hi
Thanks for your reply. You are right. I am getting a critical error but I am still able to access the site from the internet. Hope they address this in the final release. I really like the changes they have made.
Thanks,
Arnie
Monday, May 10, 2010 1:21 PM -
Hello, same critical error message for me too, and can still connect in fine.
I am logged into it, cleared it about 20 mins ago, then it reappeared, very strange.
Tuesday, May 11, 2010 6:53 AM -
I too am having the same issues as others above so no need to rehash. My question is, is there a way to have the wizard report back on the status of a 2 router setup? I have a Dlink router sitting behind a FIOS Actiontec router. Would be nice if the wizard acknowledged the 2 routers (or asked during verification) and allowed minor adjustments during the process. I never touched my router settings from a previous WHS v1 install and think a "override verification option" would take care of the erroneous critical error in the dashboard.
Tony
Tuesday, May 11, 2010 3:24 PM -
Vail can't really identify a "2 router setup", unfortunately. In reality everyone has a "many router setup". The Internet consists of wires/fiber that go from router to router around the world. There's no way to distinguish between a router upstream of the first one in the chain that belongs to your ISP (or some other ISP) and a second router on your premises. It's just another device in the chain.
I'm not on the WHS team, I just post a lot. :)Tuesday, May 11, 2010 5:41 PMModerator -
Understood, and thanks for the reply. I am by no means an expert on this but if a home user is behind a internet connected router, wouldn't every ip behind it be considered part of the home network. So for example, if I did a tracert from any pc/device on my network couldn't I assume that any IP listed after the WAN address of my internet facing router is part of my network only?
And wouldn't it be possible to have a wizard ask you for the IP addresses of any routers on your network, including the WAN IP of the internet connected router, then make a determination of what router configurations are necessary. Maybe even a pass/fail report of necessary open ports on each router? Again, I'm not an expert and remote access is working fine in my configuration so this is more an exercise in understanding the limitations of automatically setting up the WHS networking.
Tony
Wednesday, May 12, 2010 12:37 PM -
This is what we call a DUAL-NAT setup, which we cannot detect. We are working on this because it’s a common home networking blunder (the cost of a router is cheaper than the cost of a wireless access point for example).If you’re networking setup is like this:Internet <—>Router1<—>Router2<—>WHSOur UPnP technology will configure Router2, but not Router1. Thus to enable remote access, you have to also open ports 80 and 443 from Router1 to Router2. Technically it will work.Additionally, any clients that live between Router1 and Router2 will not be able to detect and/or find the WHS.It’s definitely not a recommended mode. If you can go back behind one router only. If you cannot, see if you can turn one of the routers into “Bridge” mode, which turns it more into a switch than a router. :)Good luck,SeanThis post is "AS IS" and confers no rights."mb2k" wrote in message news:8c3cfb05-524b-4304-98ac-dd4e92e915b7...
Understood, and thanks for the reply. I am by no means an expert on this but if a home user is behind a internet connected router, wouldn't every ip behind it be considered part of the home network. So for example, if I did a tracert from any pc/device on my network couldn't I assume that any IP listed after the WAN address of my internet facing router is part of my network only?
And wouldn't it be possible to have a wizard ask you for the IP addresses of any routers on your network, including the WAN IP of the internet connected router, then make a determination of what router configurations are necessary. Maybe even a pass/fail report of necessary open ports on each router? Again, I'm not an expert and remote access is working fine in my configuration so this is more an exercise in understanding the limitations of automatically setting up the WHS networking.
Tony
Wednesday, May 12, 2010 5:33 PMModerator -
a very large number of wireless routers can be turned into an access point. formost, you turn off NAT and DHCP and use a LAN port on the switch to connect tothe edge router. it's far better than double NAT.On Wed, 12 May 2010 17:33:07 +0000, Sean Daniel - MSFT wrote:>We are working on this because it’s a common home networking blunder (the cost of a router is cheaper than the cost of a wireless access point for example).
Barb Bowman www.digitalmediaphile.comWednesday, May 12, 2010 6:36 PM -
a very large number of wireless routers can be turned into an access point. formost, you turn off NAT and DHCP and use a LAN port on the switch to connect tothe edge router. it's far better than double NAT.On Wed, 12 May 2010 17:33:07 +0000, Sean Daniel - MSFT wrote:>We are working on this because it’s a common home networking blunder (the cost of a router is cheaper than the cost of a wireless access point for example).
Barb Bowman www.digitalmediaphile.com</ Your solution may work in some instances, but this is not the answer I am looking for. It's Windows Home Server, and as such should be simpler than your designation., in my view. The WHS population won't grow unless it is easy to use and requires no tech skills.Wednesday, May 12, 2010 6:57 PM -
for those that want a better performing network and who are willing to make theeffort, it is still a better solution. if the WHS team wants to work around badnetworking habits, so be it, but the real issues will surface when IPv6 fullyappears on the scene...On Wed, 12 May 2010 18:57:47 +0000, palavering wrote:>Your solution may work in some instances, but this is not the answer I am looking for. It's Windows Home Server, and as such should be simpler than your designation., in my view. The WHS population won't grow unless it is easy to use and requires no tech skills.
Barb Bowman www.digitalmediaphile.comWednesday, May 12, 2010 7:08 PM -
That said, to the best of my knowledge Verizon blocks access to ports 80 and 443 for residential customers. Vail doesn't really let you move to different ports; for one thing the TS gateway is currently wired down to 443, so a Verizon FiOS internet connection really precludes the use of remote desktop or the dashboard via the Remote Access web site (even if you do change the ports in IIS).
Ken - Just an FYI.
I have residential FiOS out here in Southern California and both port 80 and 443 are not blocked. I can access my site via http or https.
Up until about a year or so ago port 80 was blocked. 443 has been open since the early WHS v1 betas.
Thursday, May 13, 2010 4:31 AM -
I have the exact same problem. The WHS icon turns red and informs me that remore access isn't available and that there is a problem with my router. Yet, when I check it, everything is fine, both from within and without the network. I have checked the "ignore" box because it is irritating.
I have had this same issue in both WHS PP3 and Vail since I replaced my Dlink DIR-655 with a Netgear WNDR3700. Due to the recent firmware issues with the DIR-655 the uPNP port forwarding had become pretty unreliable. WHS PP3 would give me an error that my router could not be configured and it would be correct (website would not be available from outside my network).
With the WNDR3700 the ports always seem to be correctly forwarded - can be verified by looking at the uPNP forwarding table in the router admin console. However after a period of time I will get a warning from WHS PP3 and now Vail stating that my router could not be configured. The router is configured and my website is working externally. I have also checked the "ignore" box.
I believe the problem with the WNDR3700 is that NAT loopback is not supported. Without NAT Loopback you cannot access the external IP address of the server from within the network. This makes it impossible to be inside the network and browse to https://yoursitename.homeserver.com. Instead you have to do this https://yourserverIPaddress/remote
The DIR-655 supports NAT loopback and when the firmware was good was bulletproof with WHS remote access.
Maybe a solution would be to have Vail query a Microsoft server to attempt to access the remote site via the internet. This seems like it would resolve NAT loopback issues. Or better yet convince Netgear to add NAT loopback support to the WNDR3700...
Thursday, May 13, 2010 4:49 AM -
what version firmware is in the 3700?On Thu, 13 May 2010 04:49:09 +0000, crwagner wrote:>Maybe a solution would be to have Vail query a Microsoft server to attempt to access the remote site via the internet. This seems like it would resolve NAT loopback issues. Or better yet convince Netgear to add NAT loopback support to the WNDR3700...
Barb Bowman www.digitalmediaphile.comThursday, May 13, 2010 10:00 AM -
What firmware version were you using in the DIR 655? I am using 1.32NA, 2009/07/09, and am having no problems with Remote Access. Perhaps the solution would be to rollback your DIR-655's firmware.
--
______________
BullDawg
Associate Expert
In God We Trust
______________
"crwagner" <=?utf-8?B?Y3J3YWduZXI=?=> wrote in message news:e3f06c64-6bbc-489c-af9e-ba290700b2b8...I have the exact same problem. The WHS icon turns red and informs me that remore access isn't available and that there is a problem with my router. Yet, when I check it, everything is fine, both from within and without the network. I have checked the "ignore" box because it is irritating.
I have had this same issue in both WHS PP3 and Vail since I replaced my Dlink DIR-655 with a Netgear WNDR3700. Due to the recent firmware issues with the DIR-655 the uPNP port forwarding had become pretty unreliable. WHS PP3 would give me an error that my router could not be configured and it would be correct (website would not be available from outside my network).
With the WNDR3700 the ports always seem to be correctly forwarded - can be verified by looking at the uPNP forwarding table in the router admin console. However after a period of time I will get a warning from WHS PP3 and now Vail stating that my router could not be configured. The router is configured and my website is working externally. I have also checked the "ignore" box.
I believe the problem with the WNDR3700 is that NAT loopback is not supported. Without NAT Loopback you cannot access the external IP address of the server from within the network. This makes it impossible to be inside the network and browse to https://yoursitename.homeserver.com. Instead you have to do this https://yourserverIPaddress/remote
The DIR-655 supports NAT loopback and when the firmware was good was bulletproof with WHS remote access.
Maybe a solution would be to have Vail query a Microsoft server to attempt to access the remote site via the internet. This seems like it would resolve NAT loopback issues. Or better yet convince Netgear to add NAT loopback support to the WNDR3700...
BullDawgThursday, May 13, 2010 11:00 AM -
what version firmware is in the 3700?On Thu, 13 May 2010 04:49:09 +0000, crwagner wrote:>Maybe a solution would be to have Vail query a Microsoft server to attempt to access the remote site via the internet. This seems like it would resolve NAT loopback issues. Or better yet convince Netgear to add NAT loopback support to the WNDR3700...
Barb Bowman www.digitalmediaphile.comThursday, May 13, 2010 5:16 PM -
What firmware version were you using in the DIR 655? I am using 1.32NA, 2009/07/09, and am having no problems with Remote Access. Perhaps the solution would be to rollback your DIR-655's firmware.
I think I was using 1.32NA as well. I gave the router to a friend at work as the WNDR3700 did provide better 2.4Ghz coverage in my house.
I always liked the DIR-655 it just seemed like since the 1.3x firmware updates (which cannot be downgraded back down to 1.2x or 1.1x) the routers uPNP would stop working after several weeks and the router would require a reboot. So far I have not had to reboot my WNDR3700 it just does not seem to play well with allowing WHS to confirm remote access.
CWagz
Thursday, May 13, 2010 5:21 PM -
I asked my buddy at Netgear about loopback today. may be a while before I get ananswer.On Thu, 13 May 2010 17:16:00 +0000, crwagner wrote:>I am running 1.0.4.55 which is the latest available on the website.
Barb Bowman www.digitalmediaphile.comThursday, May 13, 2010 8:35 PM -
I asked my buddy at Netgear about loopback today. may be a while before I get ananswer.On Thu, 13 May 2010 17:16:00 +0000, crwagner wrote:>I am running 1.0.4.55 which is the latest available on the website.
Barb Bowman www.digitalmediaphile.comAwesome! It would be nice if Netgear would work this out. Only other option is to wait for the DD-WRT folks to get a good build running for the WNDR3700.
Thursday, May 13, 2010 8:43 PM -
Well, I've got 2 here in Korea at two different location, both sons also have DIR-655's back in the states. We are all using 1.32NA firmware and not having any uPNP problems. One of mine has the WHS v1 and the other will have Vail once I get an RMA'd power supply back. Both sons are running WHS v1 on their DIR-655. Maybe you just had a bad one.
--
______________
BullDawg
Associate Expert
In God We Trust
______________
"crwagner" <=?utf-8?B?Y3J3YWduZXI=?=> wrote in message news:b4d8561b-93a3-4058-bfba-661c11d8fd58...What firmware version were you using in the DIR 655? I am using 1.32NA, 2009/07/09, and am having no problems with Remote Access. Perhaps the solution would be to rollback your DIR-655's firmware.I think I was using 1.32NA as well. I gave the router to a friend at work as the WNDR3700 did provide better 2.4Ghz coverage in my house.
I always liked the DIR-655 it just seemed like since the 1.3x firmware updates (which cannot be downgraded back down to 1.2x or 1.1x) the routers uPNP would stop working after several weeks and the router would require a reboot. So far I have not had to reboot my WNDR3700 it just does not seem to play well with allowing WHS to confirm remote access.
CWagz
BullDawgThursday, May 13, 2010 9:55 PM -
I misspoke earlier. I didn't realize that you were addressing the issue of having two routers in the same LAN. I thought you were advising all (with one router) to turn off NAT and DHCP. My bad!Monday, May 17, 2010 12:11 PM
-
I too have the actiontech router and 35/35 FIOS. The WHS v1 box works fine, but when I unplug it, and put the VAIL box on the network, it won't configure and tells me the ports are blocked, 80 and 443, but I know they are not since the work with v1Monday, June 7, 2010 11:45 PM
-
I too have the actiontech router and 35/35 FIOS. The WHS v1 box works fine, but when I unplug it, and put the VAIL box on the network, it won't configure and tells me the ports are blocked, 80 and 443, but I know they are not since the work with v1
Me too. Same issue.
To fix, I delete any of the port forwarding rules from the router using port 80 or 443, have WHS successfully configure the router, etc. Turn off remote access on the WHS and delete the rules on the router. NOW have VAIL set it up, and it will configure the router.
sworcesterTuesday, June 8, 2010 8:44 PM -
Sean, I don't mean to be offensive to anyone on the forum. Everybody seeems to try and be very helpful. But the answers to this person's problem with the "critical error" is occurring on virtual everyone's server. It didn't happen with WHS PP3, so something is amiss. I think a better answer is that the team still has much work to do; after all, this is the first beta--and considering that, I think it's great--faults and all! Thanks for the good work!Tuesday, June 8, 2010 9:01 PM
-
Do you have both windows home servers running?As far as I know a redirect for port 80 / 443 can be done for only on WHS at the time. And you must then redirect to the WHS you want it to redirect (the active one)I could be wrong, but I think that is it."palavering" wrote in message news:4b9e3a93-7e57-4665-81d1-e31dda6b1525@communitybridge.codeplex .com...Sean, I don't mean to be offensive to anyone on the forum. Everybody seeems to try and be very helpful. But the answers to this person's problem with the "critical error" is occurring on virtual everyone's server. It didn't happen with WHS PP3, so something is amiss. I think a better answer is that the team still has much work to do; after all, this is the first beta--and considering that, I think it's great--faults and all! Thanks for the good work!
Have a nice day!Tuesday, June 8, 2010 10:13 PM -
Just for your information. My Network Connections are as follows:
Internet <--> Vonage V-Portal 1-Port Gateway with NAT<--> Cisco RVS-4000 Small Busness Gateway with NAT and IPS Signatures <--> WHS <--> Linksys WRT54G2 Wireless Router with NAT turned-off AP isolation turned-on, Only known Mac Address can access.
The Vonage V-Portal Phone Adapter with UPnP turned-off, only has 1-Port 10/100 LAN 192.168.15.1
The Cisco RVS-4000 NAT on, UPnP turned-on, IPS Signatures turned-on, has 4-Ports 10/100/1000 WAN 192.168.15.3 LAN 192.168.1.1
The WRT54G2 is setup for wireless access and to protect my main network. WAN 192.168.1.253 LAN 192.168.2.1
Everything works fine. Accept Vail of course... Wireless backups only work if I use the WRT54G2 as the Main Gateway... But, that has less protection...
The point is what is a standard Network?
IMPORTANT NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, you should contact the sender and delete the message. Any unauthorized disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature.Wednesday, June 9, 2010 12:20 AM -
I'll be trying this out over the weekend. I will save my conifg for the router in a file, and reset it, deleting all the current rules, and see if I can get the vail server to work. TX for your reply.Wednesday, June 9, 2010 12:00 PM