NLB causing IE to not load certain websites properly

I have two 2003 Terminal Servers running NLB and Session Directory.  Everything is working the way it's suppose to except there's one small problem:

When both servers are running, IE on both systems are unable to completely open certain websites.  The title bar of the website does appear, but the body never opens and IE continues to try to load the page without success or error.  But when I unplug the second server from the network, IE on the first server works normally.

Please help!!!
CapitalHospiceAsked:
Who is Participating?
 
PowerITCommented:
That looks good except for one thing: you should disable the default gateway on the NLB adapter (leave it empty) - NIC1 in your case - and enable it on the NIC for outbound traffic (NIC2 for you).

J.

0
 
mcp_jonCommented:
Which NLB are we talking about : Windows-Based or Hardware-Based ??

Best Regards !
0
 
PowerITCommented:
Can you paste you NLB configuration here: ports bound to which NIC, multiple NICs IP adresses, unicast/multicast, ...
+ also the network metrics.
A first hint which could solve your problem: the metric on the NIC's should not be set to automatic and the NIC which you reserve for outgoing traffic should have the lowest metric.

J.
0
Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

 
markpower60Commented:
seems like a DNS resolution issue. did you verify TCP/IP settins as well as DNS forward or NLB settings?

Good luck
0
 
CapitalHospiceAuthor Commented:
It's Windows-based NLB.  There are two NICs per server and the TCP/IP settings are as follows:

SERVER1:

NIC1 properties:
Cluster Parameters= IP address 10.7.0.23 255.255.0.0; unicast
Host Parameters=  Priority (unique host id) is 2, no dedicated IP conifguration, Default state= started.
TCP/IP Properties= IP address 10.7.0.23 255.255.0.0 DG 10.7.0.1; Preferred DNS 10.7.0.17
Advanced TCP/IP settings= Interface metric is 2

NIC2 properties:
NLB not enabled
TCP/IP settings: 10.7.0.27 255.255.0.0; Preferred DNS 10.7.0.17
Advanced TCP/IP settings= Interface metric is 1

Server2 properties:

NIC1 properties:
Cluster Parameters= IP address 10.7.0.23 255.255.0.0; unicast
Host Parameters=  Priority (unique host id) is 1, no dedicated IP conifguration, Default state= started.
TCP/IP Properties= IP address 10.7.0.23 255.255.0.0 DG 10.7.0.1; Preferred DNS 10.7.0.17
Advanced TCP/IP settings= Interface metric is 2

NIC2 properties:
NLB not enabled
TCP/IP settings: 10.7.0.25 255.255.0.0; Preferred DNS 10.7.0.17
Advanced TCP/IP settings= Interface metric is 1

Thanks!
0
 
mcp_jonCommented:
You should never have two Gateways on the same Windows System :)

Do what PowerIT stated and you'll be fine, however, I must warn you that Windows NLB is very tricky, but I see you already got it because you are using two NIC 's :D

Best Regards !
0
 
CapitalHospiceAuthor Commented:
So all I need to do is move the Default Gateway from NLB adapter to the administrative adapter (NIC1 to NIC2) for each server?  I will try it tonight during network maintenance and keep you posted!  Thank you gentlemen!
0
 
mcp_jonCommented:
No problem !

Just keep it coming !

Best Regards !
0
 
CapitalHospiceAuthor Commented:
It worked! It worked!  Moving the Default Gateway setting to the non-NLB adapter did the trick!  Thank you so much!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.