mehtaman Posted August 19, 2014 Share Posted August 19, 2014 There is probably a simple answer to this but I cannot work it out... So, if I go to my "domain-name.co.uk" it automatically forwards me onto my remote access page. Where in IIS Manager can I change the default site to point to a different index.html/default.aspx file? I want users to specifically got to "remote.domain-name.co.uk" if they require remote access and general domain visits to go to a different site. Hope that makes sense, thanks in advance. Link to comment Share on other sites More sharing options...
jmwills Posted August 19, 2014 Share Posted August 19, 2014 Okay, I'll bite. Why? Link to comment Share on other sites More sharing options...
mehtaman Posted August 19, 2014 Author Share Posted August 19, 2014 I have a general information site that I want to load from the main domain address. Should anyone require remote access then they can use "https://remote.domain-name.co.uk" At the moment, if i go to domain-name.co.uk, it will automatically load up "https://domain-name.co.uk/Remote/logon?ReturnUrl=%2fremote" Link to comment Share on other sites More sharing options...
jmwills Posted August 19, 2014 Share Posted August 19, 2014 You would have to create the new site and change the bindings from the default site over to the new one. Someone else tried this a few months ago and honked everything really bad because of the customization installed by Microsoft. Link to comment Share on other sites More sharing options...
mehtaman Posted August 19, 2014 Author Share Posted August 19, 2014 Ah thats annoying... good ol' Microsoft. Link to comment Share on other sites More sharing options...
jmwills Posted August 19, 2014 Share Posted August 19, 2014 Yea, the default site gets 80, 443, 65510, & 65515 bound to it first. Depending on your router you might could also use 443 and bind it to the new site and leave the defaults alone. This may require something like a TMG server in the DMZ in order to work. Link to comment Share on other sites More sharing options...
mehtaman Posted August 19, 2014 Author Share Posted August 19, 2014 I seem to have it working... I setup a new site, pointed it to my website folder path. Set the binding to port 80 only. Left the default site as it is (also had a port 80 binding), going to the remote sub-domain still works and logs me in without an issue. Link to comment Share on other sites More sharing options...
jmwills Posted August 19, 2014 Share Posted August 19, 2014 Send me a PM with the link and I'll test it from this side. Link to comment Share on other sites More sharing options...
ikon Posted August 19, 2014 Share Posted August 19, 2014 Please correct me if I'm wrong JW, but there's no way port 80 could be used for both purposes on a single computer, is there? Link to comment Share on other sites More sharing options...
jmwills Posted August 19, 2014 Share Posted August 19, 2014 Yes you can do it but it takes some high level math, i.e. pointing it to a load balanced IP address. AFAIK, if you use separate DNS entries to the same external address, once the firewall is accessed, IIS knows where to forward the request. But to your point, a simple SOHO router may not be able to handle this type of request. Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now