Hi folks

Wonder if anyone has seen something along these lines?  We have a customer who has a native mode SCCM environment and has clients deployed throughout.  Management is working just fine on these clients.  That is, with the exception of clients which are running NLB as well which get an HTTP 500 message whenever they try to communicate with the MP.

Sorry that there is no detail - took a week to get this much from them!

It's going to be difficult, if not impossible, to troubleshoot with so little information.

Do you have access?  Can you gather log files?

What does mpcontrol.log say?

Are the clients using load balanced DNS name and is MP configured to use the load balanced URL ?

Is DNS working for load balanced URL ?

Are these working ?

http://DNS-nlb_name_of_MP/SMS_MP/.sms_aut?MPLIST
http://EACH_NODE_NAME/SMS_MP/.sms_aut?MPLIST

RIX78

Thanks for the response - no, this is the opposite.  The MP is NOT NLB but the servers which they're trying to manage ARE NLB

Hi Nicholas

Aware of the tech issues and trying to get round those.  Just wondering if anyone was aware of limitations on this

Presuming you mean a Microsoft NLB and not some hardware-based NLB, from my experience (with a Microsoft NLB); they function perfectly fine as clients.  We have several servers that happen to have Microsoft NLB installed on them and configured; and they've never been a problem as clients.

Hi there Sherry

Spoken to customer regarding this and they tell me that it's single NIC NLB clients

Hi there Sherry

Spoken to customer regarding this and they tell me that it's single NIC NLB clients

They still should be fine as clients, provided they have the required network connectivity to the ConfigMgr server(s).

Hi there folks

Still working on this one.  So, we have some NLBs (multicast) on single NIC.  Have checked DNS and we find that the host records are registered OK.  We go to a NLB host and try to connect to the MP and in the IIS Log we see:

2012-03-19 11:19:52 192.168.x.y GET
/sms_mp/.sms_aut mpcert 443 - 192.168.x.z
Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+.NET+CLR+1.1.4322) 500 0 64
127348

while a NON-NLB host works just fine.  We have confirmed that from a NLB host we are able to connect to the MP on 80, 443, 8531

Yes, I know this is an old post, but Im trying to clean them up.

Did you solve this problem, if so what was the solution?

Since no one has answer this post, I recommend opening  a support case with CSS as they can work with you to solve this problem.