Problems with connecting to NLB Terminal Server Cluster

Hello Experts!

I have a problem with a Terminal Server NLB Cluster with the following specs:

1 SBS Windows 2003 R2 server with SP1
3 Windows 2003 R2 Terminal Servers with SP2
All servers and clients are connected to Cisco Switches.

Problem description:
The original configuration was 1 SBS server and 2 Terminal Servers, but since we implemended an 3th Terminal Server some clients can't connect directly to the NLB cluster(192.168.12.14/ts.compagnon.local). They get an error message "This Computer can't connect to the remote computer".

All clients using a Thin Client and they do not always get the message above. If I connect with my laptop to the NLB Cluster I get the same message.

The new terminal servers is exactly installed as the the other 2 terminal servers but the hardware is a slide different.

All servers are connected to the same switch and all ports are configured the same. I looked several times to the NLB Cluster but everything looks oke to me.

Can you guys help me out with this problem? If you need any specs just ask them.

cheers

Wesley Niels


error.JPG
jhulsmannAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Redwulf__53Commented:
Hoi julsmann,
Is the new server configured with a single NIC? If there are two NIC's it's best to completely disable the Network Bridge component of the drivers. It's usually the advanced driver components that cause problems in Clusters.
Groet,
Sander de C.
0
BLipmanCommented:
You want to make sure you have a metric on your NICs if you are using 2 so the client traffic does not go through the console NIC.  A higher metric (set 2 on console NIC and 1 on the Client NIC) means the connection is a higher cost and will not be utilized by default.  
When you added the new server to the NLB cluster, did you configure everything you could via the NLB Admin Tool and not through the NLB config on the NIC itself?  As a best practice I read you should avoid configuring things locally that can be done via the NLB Admin tool.  
Are you certain all of your configs are done as with the other 2 working servers?  Check port rules, order of IP addresses in the TCP/IP settings, etc...

Here is some troubleshooting stuff:
http://technet2.microsoft.com/WindowsServer/en/Library/fa6ef832-1aa7-472f-b492-0dd3c60bd46d1033.mspx
http://technet2.microsoft.com/windowsserver/en/library/8d2e0b4f-4dfd-4893-9505-124ddf4fc2f01033.mspx?mfr=true

Can you do a dump of your TCP/IP config on the trouble server vs a working server too?  A nice way of doing so:
ipconfig /all > c:\serverIPCfg.txt
0
jhulsmannAuthor Commented:
Hello Redwulf_53 & BLipman,

Thanks for both reply's!

All 3 Terminal Servers have 2 NICS, but only 1 installed(1 disabled). I configged everything through the NLB Admin Tool and not on the NIC itself. The new server has the exact configuration as the other 2 Terminal Servers.

I found out that when I remove the new server, everything works correctly. I attached 2 text outputs of the "trouble server/SRV-COMPAGNON04" and the "working server/SRV-COMPAGNON02".

Hope you can find anything in it, thanks!

gr.
SRV-COMPAGNON02IPcf.txt
SRV-COMPAGNON04IPCfg.txt
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

BLipmanCommented:
Hmm, is this dutch?  LOL, I can make it out for the most part.  I am seeing 2 minor things that interest me.  First off, your node type is different between the 2 units: one is hybride (hybrid in English) and the other is onbekend (babelfish tells me this is "unknown").  

http://support.microsoft.com/kb/310570 this talks about an unknown netbios note type so it may get you on the right track.  

The other thing I see is that you have differences in your DNS and WINS entries between the systems.  I would standardize these (go off of the working server's config).  

Let me know if this helps...
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
jhulsmannAuthor Commented:
Hello BLipman,

Thanks again for your provided solution! Haha indeed it's a server with dutch interface unfortunally, i'm better with english versions.

I changed all the IPconfig settings and as Administrator I had to know to check this first, my bad!
After i changed the settings and rebooted all the servers again it looks like the problem is solved.

So this post can be closed for now, it the problem occurs again I will reopen it again if possible.

Thanks a lot!

cheers Wes

ps. Of course all the points go to BLipman
0
Redwulf__53Commented:
Wes, jammer dan ;) tot vanmiddag -Sander
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.