Topic: Cannot configure remote access for Windows Home Server, "UPnP standards"

[LANMonkey]

I have a Windows Home Server (WHS) on a LAN that uses SME as a gateway server.  I am trying to set up "Remote Access" on my WHS and I get some errors,

Code: [Select]

Verifying that your remote Web site is available locally (OK)
Configuring your router using UPnP standards (NOT OK, warning!)
Verifying that your remote Web site is available from the internet (FAILED! Web site NOT available)
I have installed ProxyPass for the URL that should take me to the machine on the LAN hosting WHS, except for one thing.  When I installed it with ProxyPass, I used "http://symbiota.homeserver.com" and the link they say reaches my WHS is a secure protocol, "https://symbiota.homeserver.com".

Is this the problem?  Should I reinstall the ProxyPass for the secure connection?  What about configuring SME as a UPnP device?  Is that possible?

If I ping "symbiota.homeserver.com" from the LAN, I only get the LAN address, the 192.168.0.XXX address.  Is this significant?

[janet]

LANMonkey

I do that by making a VPN connection to my SME server (from a remote Windows 7 workstation). Then select Run, enter the Windows server name eg //windowssvr and then right click on the connection name (windowssvr) & select Remote Access connection (or similar name),  login & I have the Windows server desktop displayed.

I would ask, why do you want to use a Windows Home Server (WHS) when you have a much more secure SME server as web server (using Apache) ?

ProxyPass does not work for local users trying to access the site, it only works for external users.
Also the URL used in the proxypass db setting should have a trailing slash ie http://symbiota.homeserver.com/
Refer to the FAQ.

I cannot recall exactly now, but there may be some issues with that UPnP protocol requirement, so do some reading, search google ? Note I do not have any issues with UPnP when using VPN.

[LANMonkey]

Thanks for your reply.  I do use SME as my primary server and certainly not WHS. 

It remains that I want to be able to access the WHS website and so the problem remains.  I did have some problems setting up ProxyPass for WHS which were solved here:

http://forums.contribs.org/index.php/topic,49387.msg246701.html#msg246701

But, I have been unable to access the site away from my LAN.  I suspect it has something to do with WHS being unable to evoke the dynamic domain functionality unique to WHS.  My other sites on SME are handled nicely by DynDNS.  I have another machine hosting CentOS on my LAN and I wish to be able to access that using ProxyPass as well, but I'll be using URLs that are enabled handled with DynDNS.  I don't anticipate a problem.  I'll report back on what happens there.

[LANMonkey]

I have just set up another URL that directs to WHS just fine, windowshs.hopto.org.

The problem appears to be making possible communication between the WHS host and the DNS that handles the URL symbiota.homeserver.com.

[piran]

I cannot recall exactly now, but there may be some issues with that UPnP protocol requirement...

"It could effectively turn a router into a zombie"
http://www.computerworld.com/s/article/9057360/Flash_attack_could_take_over_your_router?source=rss_topic17