I have a home grown application that utilizes MSADC/msadcs.dll/* to login to the server and it currently works between an XP client and a 2008 R2 server. The server end of the applicaiton has no installers anymore so I had to manually register everything and create registry keys to get it to work - long story but it worked.
The client now runs on a 2008 R2 Terminal server and connects to the 2008 R2 IIS server to login but sometimes gets a dialog box saying the server is busy try again later. I captured the traffic via wireshark and see that the IIS server is receiving the login, then returing a 200 response but with the message server busy!?!?
Then sometimes it works.
it sends: post /msadc/msadcs.dll/WebSession.CsSession.Logon Http/1.0
the next is the response
http:/1.1 200 OK - but the text of the response is server busy try again later.
the websession.cssession is a com+ object that gets fired up - when it works it moves on to the next com+ method and continues - when it fails it just stops there and never goes on.
how can I troubleshoot a "good" return code from IIS when its actually bad?