Jump to content
RESET Forums (homeservershow.com)

2 Remote access Severs?


Recommended Posts

So, when you use mydomain.homeserver.com:443, which should go to the WHS2011 server, it actually does go to the WHS2011 server. The only issue you have is that the background seems wrong. Does this jive with what you're seeing?

Link to post
Share on other sites
  • Replies 130
  • Created
  • Last Reply

Top Posters In This Topic

  • TomatoBoy

    56

  • jmwills

    37

  • ikon

    30

  • Essexraptor

    5

Top Posters In This Topic

Popular Posts

Yes, but by taking the time to learn this, you can have two portals with Remote Access running from home using one external IP address.  It's really not that hard.   Excellent for someone who is try

I don't modify IIS to do this; I use different ports on my router and redirect them to the default IIS port, but on different IP addressess. For example, I will have my router redirect http://mydomain

TomatoBoy

So, when you use mydomain.homeserver.com:443, which should go to the WHS2011 server, it actually does go to the WHS2011 server. The only issue you have is that the background seems wrong. Does this jive with what you're seeing?

No, though I do wonder how the background can change just when using the MS DDNS and I think the issue is linked to not being able to access the WSE.

Link to post
Share on other sites

Let's forget about the background for the moment. The bottom line is that mydomain.homeserver.com:443 is being forwarded to the WHS2011 server, right?

 

Why don't you jump into HSS Chat. This would likely go faster, and not pollute this thread with tons of tiny posts.

Link to post
Share on other sites
TomatoBoy

Should we be able to access the WSE even without using the Anywhere Access wizard?


Let's forget about the background for the moment. The bottom line is that mydomain.homeserver.com:443 is being forwarded to the WHS2011 server, right?

 

Why don't you jump into HSS Chat. This would likely go faster, and not pollute this thread with tons of tiny posts.

Okay, will do, thanks.

Link to post
Share on other sites

I don't see why not, but I'm not very knowlegeable about WSE2012 as I've only run it briefly.

Link to post
Share on other sites
jmwills

We can report a successful configuration, after an afternoon in chat!!

 

Look for a blog post coming soon.

Link to post
Share on other sites

Yes, a classic case of people putting their heads together to wrestle a problem to the ground. Some important things were discovered/learned about running more than one home server on a LAN and having Remote Web Access to both of them.

Link to post
Share on other sites
TomatoBoy

I would just like to thank both of you for an immense effort beyond the call of duty. Yes, some very strange things were seen when the configuration was not to the liking of WSE. We are most grateful.

Link to post
Share on other sites
TomatoBoy

A quick epilogue and another cry for help!

 

The update first :) The resolution took place on an image of an installation with an old local domain name that happened to be sat handy on a drive after the original issue severely corrupted the system drive we intended to use. So, today we intended to restore an image of the required drive to a disk and carry on. Now, we usually take multiple images with different products, but on this occasion only had one because we have been messing about with multiple configurations. Needless to say, it failed to restore. There lies a lesson in itself! There is no such thing as too much redundancy. Anyway, we tried a repair on the original image for interest to no avail, demonstrating just how badly the issue upset it. We ended up reinstalling as the server consisted of little more than a system drive at this point anyway and as it would all now be a very standard installation with default ports involved, it should be no issue. It was not and everything is lovely. Thanks again ikon and jmwills for a gargantuan effort.

 

Now the cry for help. Having disconnected a WHS client during the process above in order to join it to the WSE temporarily, we tried to reconnect it to the WHS today. Unfortunately, there was no response to <servername or internal IP>/connect or http://<servername or internal IP>/connect:55000. Upon investigation in IIS, it appears the default website is not behaving correctly, though it can be reached in IIS. It has a question mark on the globe logo, and restart in IIS does not resolve the issue. Might this be connected with the binding changes? We didn't want to start poking about without asking as it may be something easy.

 

Many thanks :)

Edited by TomatoBoy
Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...