Is there a "secret" way to activate trace logging for the Windows Client? Or at least more extensive logging to the Windows Event Log?
What kind of error are you getting?
There's nothing in the documentation, but you could always try the /D, /V, /1 and /2 options ("D" for debug, "V" for verbose output, and the trace options from the other IBM CMOD tools.)
Of course, if you're having an issue, a PMR would be the best way forward.
I'll also throw this out there -- if you're trying to get SSL working, I've seen bad SSL certs hang/crash early versions of the clients.
Let us know what you're seeing so we can help.
-JD.