Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Configuring remote access with a different port RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Just got my HP Media Smart and loving it! Now, I host a few sites for family off another server... all on port 80 (thanks to host headers). However when I go to configure Remote Access on my WHS, it hijacks port 80 to point to the WHS box... not what I want. SO I undid the config and tried hitting the WHS via port on my trusted network... success! So I added a port forwarding in the router to point to the WHS IP on port 81... no luck. So now I'm confused...
     
    Is it possible to manually configure the WHS remote access to work off a specific port rather than hijack port 80, like 81 for instance? I only want myself and my wife have access to the server, so issues with ports is not a problem. Changing the port of the existing sites is not an option unfortunatley...

     

    Monday, January 21, 2008 5:04 AM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Andrew, you should read the technical brief on Windows Home Server remote access. There's a little more going on there than you probably think. The WHS remote access web site runs on Internet Information Server, so it's possible to change the ports. (Doing so may interfere with installing the connector on additional home PCs however.)

    But you have an HP MediaSmart Server, which includes HP's WebShare application in addition to the WHS remote access web site. That runs on a completely different web server; I believe it's jetty. You'll have to change that as well, and figure out how the two interact.

    Good luck!
    Monday, January 21, 2008 12:39 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Ken-

    Thanks... I read through the paper you linked to which provided some insight, but it didn't answer the direct question. After setting up remote access, I then logged into the machine via RDP and changed the ports to 81/441, recycled IIS and then tested the links... nothing found. Also tried rebooting the box, but same issue... nothing found.

     

    I'll have to keep digging... surprised I haven't found someone else blogging this or in the forums talking about it as it seems that it would be quite common.

    Monday, January 21, 2008 4:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    On a MediaSmart Server, you're also going to have to do something about HP's WebShare application. I'm not sure what, other than that (as I said before) it appears to run on jetty.

    But I do think you're using your server in an unusual way. It's usable for people like you and I (and meets my real needs very well) but we have enough knowledge to picture how much more it could do, and we tend to have more complex home network architecture than your average family.
    Monday, January 21, 2008 7:27 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Andrew please have a look at Philip Churchills blog on this subject: http://mswhs.com/2007/06/21/problems-accessing-whs-web-interface-ports-80-and-443-blocked/  or this wiki

     

    This explains in a few easy steps how to setup remote access using different ports. Personally I think it's a smart thing to use the higher ports (>1024) for remote access anyway. Lower ports and especially ports 80 and 443 have a much higher risk of being probed.

    Monday, January 21, 2008 8:03 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Most, if not all, lower ports are always blocked by home internet service providers.
    I'm really surprised that this hasn't occurred to any of the WHS developers, especially those who have set up the Remote Access feature.  This is especially troubling because you have to pay for the dynamic DNS feature after a limitted trial period has expired.

    I had expected a "plug-and-play" remote access feature, and indeed some people have claimed it's better than LogMeIn or GoToMyPC, but it utterly does not work in any reasonable use case.

    By a "reasonable use case" it means following the clear instructions provided with WHS which simply do not work.  I have to wonder yet again if Microsoft uses the Windows Home Server in any real Home because this would have been noticed immediately.
    Friday, October 30, 2009 2:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Most, if not all, lower ports are always blocked by home internet service providers.
    I'm really surprised that this hasn't occurred to any of the WHS developers, especially those who have set up the Remote Access feature.  This is especially troubling because you have to pay for the dynamic DNS feature after a limitted trial period has expired.

    I had expected a "plug-and-play" remote access feature, and indeed some people have claimed it's better than LogMeIn or GoToMyPC, but it utterly does not work in any reasonable use case.

    By a "reasonable use case" it means following the clear instructions provided with WHS which simply do not work.  I have to wonder yet again if Microsoft uses the Windows Home Server in any real Home because this would have been noticed immediately.

    Guess this depends very much on where you live. My ISP doesn't block any port. also if you use the homeserver.com domain you don't have to pay. I think this only for the TZO domain which comes with HP Mediasmart server.

    Also I think it works in most homes when using MS instructions. If it wouldn't work this forum would be flooded with that type of questions.

    If you want things changed the best thing to do is submit Feedback on Windows Home Server Connect Feedback site (and have others vote on your suggestion, or vote on suggestions of people who already submitted similar request)
    Friday, October 30, 2009 2:55 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Most, if not all, lower ports are always blocked by home internet service providers.

    Not true.  Time Warner where I live absolutely does not block any ports.

    I'm really surprised that this hasn't occurred to any of the WHS developers, especially those who have set up the Remote Access feature.  This is especially troubling because you have to pay for the dynamic DNS feature after a limitted trial period has expired.

    I had expected a "plug-and-play" remote access feature, and indeed some people have claimed it's better than LogMeIn or GoToMyPC, but it utterly does not work in any reasonable use case.

    By a "reasonable use case" it means following the clear instructions provided with WHS which simply do not work.  I have to wonder yet again if Microsoft uses the Windows Home Server in any real Home because this would have been noticed immediately.
    It doesn't work for some people because some ISPs block ports (usually to keep people from have a "true server" set up, and by "true server" I mean something a business would use to promote business/sell items, not a home server).  In any event, MS has nothing to do with that (and any documentation even states that availability is subject to the terms of your ISP's usage policy).  Are there ways around it?  Sure.  But unless you know to add a :xxxx after the web address to specify a specific port, it won't do any good (and the average user - the target audience of this product - won't know the first thing about that).
    Friday, October 30, 2009 11:53 PM
    Moderator