• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 950
  • Last Modified:

Can’t get to default instance on Port 8080 using FQDN

I’m a relatively new sys admin that’s trying to learn IIS on the fly and its drinking from a firehose !  

I have a problem I can’t solve and I can’t find much info on my specific issue.  

I have people reporting they are trying to access a site via FQDN, _http://wincode.redmond.corp.microsoft.com
When they do this they are directed to a default site on a specific port (Port 80.)
Where they need to go is the WINCODE instance on port 8080. They can’t get there unless they use 8080 in the address.  Also they would like a redirect for folks using Direct Assess such as _http://wincode.dns.microsoft.com.
To complicate things there is a Load Balancer involved.

I’ve gone into IIS Manager (7) and setup an HTTP Redirect as well as a Host Header and altered the Site Bindings.  Nothing has worked so far.  

I’m really at my wits end and could use some help.  Any ideas?
0
supperg
Asked:
supperg
1 Solution
 
giltjrCommented:
O.K., host names do not specify ports, they just specify the IP address.

When you do http://????? the http says use port 80.  If  you want them to go to port 8080, they will need to enter:

     http://wincode.redmond.corp.microsoft.com:8080

the :8080 says to use port 8080 instead of 80.

0
 
__STCommented:
Depending on whether or not there is something on port 80 on the server (and the directory structure), you could use redirection to send requests from port 80 to port 8080.

http://technet.microsoft.com/en-us/library/cc732969(WS.10).aspx
0
 
InterframeGapCommented:
Ok -
Can you post a very simple drawing of what you want to happen.  Conceptually I understand, but there is a Load balancer in the middle which controls L5 and L4 traffic.  What type of Load Balancer? An even if the drawing is hand done and uploaded would help. If not I'll take a crack at it and upload it.

A redirect from 80 to 8080 is pendent on a few things which you have already discussed. Just the order in which they happen the browser as well as the LB are causing issues.

DMT
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
suppergAuthor Commented:
Thank you to all who tried to help me with this issue.
I’ve been able to resolve it myself.
The following is the solution:
Went into site bindings in IIS Manger and added the following:
x
http                        8080    *
http    researchcode                80    *
http    wincode                80    *
http    wincode.redmond.corp.microsoft.com    80    *
http    wincode.dns.microsoft.com        80    *
x
Added the following regeistry key to the servers hosting the web site folks were trying to get to:
 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0]
Name: BackConnectionHostnames
Type: REG_MULTI_SZ
Data:
wincode
wincode.dns.corp.microsoft.com
wincode.redmond.corp.microsoft.com
wincode.ntdev.corp.microsoft.com
wincode.dns.microsoft.com
researchmt
researchmt.dns.corp.microsoft.com
researchmt.redmond.corp.microsoft.com
researchmt.ntdev.corp.microsoft.com
0
 
giltjrCommented:
Well, if I understand what you did, you sort of solved the problem, but you did it by changing the requirments.

You said that wincode was supposed to listen on 8080, you seem to have changed it so that it listens on 80 instead.

0
 
suppergAuthor Commented:
I solved this issue myself.  The posts that were made did not have useful information
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now