Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

LINK TO THIS FORUM!

Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

Partner With Us!

"Best Of Breed" Forums Add Stickiness To Your Site
Partner Button
(Download This Button Today!)

Feedback

"...I have to add my thanks and appreciation for your wonderful site... People who frequent the site are the two best things - nice and smart..."

Geography

Where in the world do Tek-Tips members come from?

Question with IIS - Two different IIS servers

CBack85 (IS/IT--Management)
25 Oct 11 13:49
I have one server that I have a website setup on port 80 and it works just fine from the internet.

example1.example.com

I want to setup another webpage on our other server that also has IIS installed and will have a different sub domain

example2.example.com

the only way i can get the second one to work is to change the port to 8080 so the only way I can access that website externally is example2.example.com:8080

is there a way in IIS so the users don't have to add :8080 to the end of the web address when they go to type it in?


Thanks
itsp1965 (IS/IT--Management)
25 Oct 11 14:36
use host headers
CBack85 (IS/IT--Management)
25 Oct 11 16:44
its two different servers though? wouldn't that make a difference?

I don't know how to do that with two different servers.....
mattKnight (Programmer)
26 Oct 11 2:29
You would have to use a different external address.

DNS point example1.example.com to 1.2.3.4 and any packet on port 80 is forwarded to IIS1
what you want to do is also
DNS point example2.example.com to 1.2.3.4 and any packet on port 80 is forwarded to IIS2.

Something somewhere has to uniquely identify which server the request is destined for
1) Hostheader - I can't see how that would work across 2 servers
2) target port number - I can see why you wouldn't want to use something other than port 80
3) targetr address - easy way - assuming you have more than 1 public address.

4) Move both sites onto the 1 IIS server and use host headers

5) Use a load balancer or FE IIS server to differentiate between requests on a host header basis and pass off to IIS1 and IIS2

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

VinceWhirlwind (TechnicalUser)
30 Oct 11 18:22
Yeah, I was going to say - a loadbalancer would do this.
 
Or, one of your webservers could run as a reverse proxy.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Back To Forum

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close