asked on Unable to Access Web Site on port 9080 using NLB
Windows 2012 R2 Data Center
VMWare ESXI 6.5
I built 4 Windows 2012 R2 Data Center VM Servers.
Two Running NLB IIS URL Rewrite etc. 2 Nodes
Two others are Web Servers IIS
Why I do http://10.2.100.151 which is the Virtual IP Address on the NLB Servers
I get the default web page on port 80 that works great
I have other web sites on different ports
8181
9080
21384
8080
http://10.2.8.100.151:8080
When I try to access them I get
This website could not be found.
Error Code: INET_E_RESOURCE_NOT_FOUND
On the NLB configuration I added port 9080
How do I get to my other sites using the virtual ip address?
Happy new year
Thank you
Tom
VMWare ESXI 6.5
I built 4 Windows 2012 R2 Data Center VM Servers.
Two Running NLB IIS URL Rewrite etc. 2 Nodes
Two others are Web Servers IIS
Why I do http://10.2.100.151 which is the Virtual IP Address on the NLB Servers
I get the default web page on port 80 that works great
I have other web sites on different ports
8181
9080
21384
8080
http://10.2.8.100.151:8080
When I try to access them I get
This website could not be found.
Error Code: INET_E_RESOURCE_NOT_FOUND
On the NLB configuration I added port 9080
How do I get to my other sites using the virtual ip address?
Happy new year
Thank you
Tom
Windows OSWindows Server 2012VMware* network load balance
Last Comment
Member_2_6492660_1
Try https://10.2.8.100.151:8080 instead (add "s" to http)
ASKER
John
Hello
Same results.
I think I need to add to the web farm different ip address for each web site so I can bind them in IIS
Thoughts?
Hello
Same results.
I think I need to add to the web farm different ip address for each web site so I can bind them in IIS
Thoughts?
Not sure. I will keep looking.
Did you give the web site a virtual name? You may need to use that instead of the IP address. Did you add the IP address as the "virtual web site" in IIS? It may not answer to the IP if you didn't set it up to answer to the IP. That default response may be coming from the default web site.
ASKER
Guys
I am able to browse my sites on the Web Server no problem.
Just having issues when trying to use the Load Balancer
I am thinking it might be the URL Rewrite Rules this is new to me
My default port 80 site works fine using the virtual ip of the load balancer
I created a separate server farm for each site that way I can run a health test on each
NLB1 NLB2
IIS IIS
ARR ARR
URL Rewrite URL Rewrite
File Services File Services
DFS-R DFS-R
Server Farm
WEB1 WEB2
IIS IIS
File Services File Services
DFS-R DFS-R
So on NLB1 I created three Server Farms
I am thinking my url rewrite rules need adjustments.
See attached.
url-rewrite.PNG
I am able to browse my sites on the Web Server no problem.
Just having issues when trying to use the Load Balancer
I am thinking it might be the URL Rewrite Rules this is new to me
My default port 80 site works fine using the virtual ip of the load balancer
I created a separate server farm for each site that way I can run a health test on each
NLB1 NLB2
IIS IIS
ARR ARR
URL Rewrite URL Rewrite
File Services File Services
DFS-R DFS-R
Server Farm
WEB1 WEB2
IIS IIS
File Services File Services
DFS-R DFS-R
So on NLB1 I created three Server Farms
I am thinking my url rewrite rules need adjustments.
See attached.
url-rewrite.PNG
ASKER
Any ideas guys
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.