This website requires Javascript to function properly. Please go to the setting of your web browser and enable Javascript for this website.

Ad by

推荐 OXIO 加拿大高速网络，最低月费仅$40. 使用推荐码 RCR37MB 可获得一个月的免费服务

Ad by

推荐 OXIO 加拿大高速网络，最低月费仅$40. 使用推荐码 RCR37MB 可获得一个月的免费服务

it is not a problem with NLB, are u sure the web host at .92 is receiving the traffic?

buma(buma)

unless u work in a HUB, if ur client request 192.168.10.100, the arp address coresponding to that IP is the first one which responded, so your client machine still remember .91's mac address to send out the HTTP request.
if u are sure .92 is receiving HTTP request at the TCP port, then check the web log, u will find out what went wrong.
if u were accessing the web server via a inbound router, make sure it can do mutlicast (means, the traffic targeting ti 192.168.10.100 goes to both of the servers)
need more information to start troubleshoot.

(#2613389@0)
Last Updated: 2005-11-17
This post has been archived. It cannot be replied.

Report

Replies, comments and Discussions:

工作学习 / 专业技术讨论 / 请教一个Windows Network Load Balancing的问题。谢谢先。 -fatbean(今晚狂灌三千斗); 2005-11-16 {807} (#2612632@0)
有两台Windows 2003的机器，都装了IIS6.0。两台机器配置成NLB的模式，共用IP是192.168.10.100, Dedicated IP分别是91和92。
IIS默认网站的IP是共用的100

在访问IIS默认的静态页面的时候发现其中一台IIS(192.168.10.92)不能serve发往NLB IP192.168.10.100的请求。也就是说，如果把91那台机器关掉，就不能访问默认的静态页面。但是有一个特例，就是从92那台机器本地开一个浏览器可以访问。

如果把92这台机器的NLB disable掉，并在TCP/IP属性里去掉公共IP(100)，通过92的IP可以访问到静态页面。也就是说，在非NLB模式下，92上的IIS是可以正常工作的

我比较了91和92上的各种配置，没有发现不同。另外发现NLB属性里有一个Priority(unique identifier)的属性，这个设置到底是设置这台机器在NLB中的priority（或者weight）还是作为unique ID来用呢？我运行nlb display这个命令发现好像这个设置可以作为ID。

说得比较乱，也不知道大伙儿能不能明白。谢谢了先。

up -fatbean(今晚狂灌三千斗); 2005-11-17 (#2613370@0)
it is not a problem with NLB, are u sure the web host at .92 is receiving the traffic? -buma(buma); 2005-11-17 {551} (#2613389@0)
unless u work in a HUB, if ur client request 192.168.10.100, the arp address coresponding to that IP is the first one which responded, so your client machine still remember .91's mac address to send out the HTTP request.
if u are sure .92 is receiving HTTP request at the TCP port, then check the web log, u will find out what went wrong.
if u were accessing the web server via a inbound router, make sure it can do mutlicast (means, the traffic targeting ti 192.168.10.100 goes to both of the servers)
need more information to start troubleshoot.

http://www.west-wind.com/presentations/loadbalancing/NetworkLoadBalancingWindows2003.asp -buma(buma); 2005-11-17 {32} (#2613406@0)
this one may help u step by step

Thanks again, I confused myself and made an assumption that turning off service would have the same effects as turning off the IIS service. -fatbean(今晚狂灌三千斗); 2005-11-17 (#2613438@0)

Thank you so much for your reply. I just found out what's going on here. What I actually tried is turning off the IIS service on 91,not the physical box. -fatbean(今晚狂灌三千斗); 2005-11-17 {907} (#2613434@0)
Windows NLB is built on network level, so 91 is still considered available.Therefore the requst would still be directed to 91. Since the IIS on 91has been down, I always got "Page cannot be displayed error".

Another thing that really confused me is that I always got the error page after trying many times. I thought NLB would dynamically direct incoming requests to different NLB hosts every time. However, it's not that smart. What it does is actually to associate the client computer's IP to a certain NLB host at the first time this client computer sends request to this NLB cluster. This association will always exist unless that certain host becomes unavailable in the network. That's why whenever I try to access the NLB from my computer, the request always goes to 91 and returns me the error page since the IIS service there is down.

Again, thank you for your patience to read down here.

buma文章里的Load Balancing Affinity说的不是就是这个吗。 -holdon(again); 2005-11-17 (#2614793@0)

@Florida

it is not a problem with NLB, are u sure the web host at .92 is receiving the traffic?

Replies, comments and Discussions:

More Topics