MQSeries.net :: View topic

BobLundeen · Posted: Tue Apr 30, 2002 7:52 am Post subject:

Looking for help from someone experienced with MQ V5.2 Client on NT and security processing who might know how V5.2 behaves in comparison to V2. Thanks.

While troubleshooting very, very rare (once or twice a week) but very, very L-O-N-G delays (5 to 10 minutes) between starting an MQ Client app on NT (V2) and the actual MQCONN occurs, a network sniffer is showing interaction with the BDC and sometimes PDC to apparently authenticate the UserID of the currently Logged on User - or maybe to inquire what group the currently Logged on User is a member. In the meantime, thousands of successful client applicaiton executions (MQCONN, MQPUT1, MQDISC) work fine all week long.

1. Curious why the NT client application is making this contact (NT BCD or PDC authentication) before the MQCONN processing to connect to the queue manager on AIX. What's the point of checking NT security before connecting to the queue manager on AIX? (My Guess: to verify the currently logged on UserID's password has not expired since logon, or is still a valid UserID?)

2. Also, curious if this (NT BCD or PDC authentication) is the same behavoir that would be seen if V5.2 were used. Due to the (obsolete) source code language environment of the MQ Client application, simply testing the V5.2 client is not feasible, except with sample programs. But this problem is very rare and not recreatable on damand.