Remote Access worked fine before I did a Server Recovery because it was configured before PP2 was installed, probably before PP1 was installed. Now that I did the Server Restore, I cannot get Remote Access working. By not working I mean when I turn on Remote Access, it does not get to a working status, it fails with an error and advises that I contact HP tech support.

Before PP1&PP2 were installed I had to configure my Linksys WRT54G manually because uPnP would not get the job done on that router. That was no problem, I forwarded the specified ports to the MSS and it all worked just fine. I could click on Refresh and see step by step what worked and what did not if I had something set wrong. Now with PP2 MS must have thought they were making it easier but I can't really see what is failing. How can I get Remote Access back to where it was, i.e. working? Do I need to uninstall PP2, make it work then reinstall PP2? That would say a lot about PP2 wouldn't it?

Yakuza replied:

"Not working" is a bit vague, care to share more details? You're likely best off creating a new topic asking for help with configuring your remote access and providing all the needed info such as router model, does it support UPnP, if you've manually forwarded ports, where you are testing the remote access from, and what the Server Console tells you about the network status.

allenc3 replies:

Remote Access status "not available". I click Repair and get "red X Verifying that your remote Web site is available locally". If I try to browse to my homeserver.com URL, I get no response. I checked the settings on my router and the only thing I had to change was the IP address which was different since the Recovery.

Thanks for the additional details, that is helpful. It is usually not possible to test whether Remote Access is working or not from inside the home, due to most routers not sending out traffic that is destined to come back in over the same interface. You can work around this by connecting to work via VPN, or having a friend or family member test for you. I've also been known to help verify if you want to PM me your URL.

It is likely that the failure message in the Remote Access config is not correct, many users have WHS reporting a failure yet Remote Access works fine. Try my suggestions above, if it still doesnt' work please post a screenshot of the config dialog or at least the text of the step that is failing. Also double-check the IP address of your server and your manual port forwards, the server IP could have changed during the Server Recovery process.

_________________
Alex Kuretz
Remote Notification: Monitoring and alerting for your Home Server via email, Twitter, text message, RSS, push notifications, and on your Mac desktop
Have you tried our Add-Ins? If so, be sure to Rate them at WeGotServed.

RE: Testing inside... I know what you mean, but testing that URL from inside has always worked before and fails now. I just now used GoToMyPC to get on my office PC from which I tried to get on my homeserver URL, no joy.

The IP did change after Recovery but I saw that and changed my port forwards. I will check everything again and other stuff and report back. Thanks for the help.

I updated my Linksys WRT54Gv5 firmware to the latest (from 1.02.5 to 1.02.6). I ran the MS Internet Connectivity Evaluation Tool and passed the UPnP Support Test meaning that my router should configure properly. Oddly the router has never auto configured by WHS except when I was running WHS Beta on an old PC. Ever since we got the MSS the router has not auto configured. I checked the manual IP address, forwarding (TCP 80, 443, 4125) and such, all is well. I have always wondered how the router can pass the MSICET UPnP test and not get auto configured by WHS. How is that possible?

I have rebooted WHS and router several times.

I turned on Remote Access, it tried to configure my router and fails, then gives no additional choices other than to try again or not configure. What happen to all the step by step statuses that I used to see as the config progressed? Bad news that that went away with PP2.

Should I uninstall PP2, get Remote Access working then re-install PP2? By the way, how do I do that? I RDP'd into WHS, Add Remove Programs and could not find a PP2 or Power Pack 2 reference.

I checked all the event logs and saw nothing unusual. I am at a loss here with no Remote Access. Next step, buy a new router that WILL configure. What is a Linksys model recommendation?

I don't think you have indicated whether you have tried to access the server from OUTSIDE your LAN. (I did see a statement that it had always worked from inside before, but have you actually tested it since all this began?)

Try it from a library, friend's house, etc. Or, if you would like to PM me your url, I would certainly be willing to test it for you.

_________________
....JBick

EX475, 2 GB, LE-1640
PC1: Vista-->W7 Ultimate/32, (D-Drive RAID-5 Array)
PC2: Lenovo Laptop, Win XP Home SP3
2xLinksys WRT54G v1.1 and 2xNetGear GS105 Gbit switch

Yes I did, please see my post above where I used GotomyPC, no joy.

If you'll PM me your url I'll try from here and take a look at the error message.

_________________
....JBick

EX475, 2 GB, LE-1640
PC1: Vista-->W7 Ultimate/32, (D-Drive RAID-5 Array)
PC2: Lenovo Laptop, Win XP Home SP3
2xLinksys WRT54G v1.1 and 2xNetGear GS105 Gbit switch

I spoke with HP tech support today about this. Got a knowledgeable guy who said the MSS is OK, but my web page is broken. He figured this out by noticing when I browsed to "//hpserver" that the browser address bar showed: "http://hpserver/home/default.aspx?gotodefault=true"
That extra url address text came from the MSS web server so it is working. In Remote Access he had me change the Web Site Home Page settings to each of the three possible settings and when I selected Windows Home Server Home Page, I could browse to //hpserver and see my home logon page with the attractive family running around photo. But when I tried to logon or selected the other buttons to logon to the WHS or the Web share, I got a page error because I was going from non-secure http to secure https which would fail.

He said to Server Recover (again), add all updates and do not install any add-ins. Then try to get Remote Access configured and running. Or do a Factory Reset(!) after first saving all share data.

So, question, does anyone here know how to fix a busted web page without doing all that?

I think you should PM myself or John your URL so we can take a look how's it's working.

_________________
Alex Kuretz
Remote Notification: Monitoring and alerting for your Home Server via email, Twitter, text message, RSS, push notifications, and on your Mac desktop
Have you tried our Add-Ins? If so, be sure to Rate them at WeGotServed.

Hey guys!

I don't know if this site is still active but in case it is, I have a weird situtation with which I could use a little help.

My last post in this thread was around 3 years ago regarding the loss of Remote Access on my EX475. I bought an EX485 off eBay and kept it in the closet for the day when the 475 died completely; about 8 months ago it did. I tried a Server Recovery twice, then a Factory Reset and did not get it back up. It had run for 4 years 24/7. So I broke out the new-in-box EX485 and set it up. It came up just fine and I got Remote Access working no problem, even continued to use my MS Live Custom Domains domain: <MyName>.homeserver.com !! Life was sweet.

About 5 days ago the EX485 went offline, short version, 4 days of Server Recoveries and finally a Factory Reset and a bad HDD replacement got me back up running. Everything works except guess what? Remote Access! Gone, cannot configure. In Domain Setup, when I choose a registered name, MS Live Custom Domains gives me 'Domain Name Setup Failed: An unexpected error has occurred communicating with Windows Live Domains Service 80000190'. I cannot get past this error and I have tried several different approaches.

When I search for <MyName>.homeserver.com Live Domains it says it is already used (yes, I have it).

And as before 3 years ago, I can get on https://server inside my house on the LAN and get to every web page in the server no problem. Previously I was on Comcast, now I am on FIOS with a completely different router and yet when I first installed the EX485 I could get on <MyName>.homeserver.com from the office or my friend's house, so it all worked... until the factory reset.

There must be some simple setting somewhere maybe in a MSS registry or somewhere that needs to be fixed to allow Remote Access to come back to life. Any help would... help!

Thanks,
Allen

Only times I've seen that error posted before have been either that the server hasn't had all the latest WHS updates installed, or the servers date/time isn't correct.

_________________
Have you tried our Add-Ins? If so, be sure to Rate them at WeGotServed.
Help support MediaSmartServer.Net!

I just RDP'd into server and saw that system time is correct.

I ran Microsoft Windows Update and see 3 high priority updates waiting:
- Security update for MS .NET Framework 2.0 SP2
- Windows Home Server Power Pack 3
- Update to .NET Framework 3.5 Service Pack 1 for the .NET Framework Assistant 1.0

I thought these updates took place automatically (I have auto updates turned on). Should I do these updates from inside the RDP Desktop or wait for WHS to kick it off on its own?

I don't see how being up-to-date will suddenly make Remote Access start working. Something is busted.

Try using a different remote domain name and if that works go back and try to use you old one again.

I would kick the updates manually if they haven't already been installed. I'm not a fan of Windows Update deciding when to apply updates especially when reboots are required. I prefer to do it when I'm there paying attention. I have WU configured to download updates but not automatically apply them.

_________________
HP MSS EX490, Intel Core 2 Quad Q9300, 1TB System drive, 6TB Storage pool managed by StableBit DrivePool

I tried doing what you suggested, but before I did, I realized that in all my testing I had not reset my ActionTech Verizon router. So I did. And I don't know if that did it, but >BANG< my Remote Access is now working again.

Oh Joy!

Thanks for the help.