Exchange 5.5 Portlet, versions, etc. UPDATE

Question

I have rectified my other problem but now have a new one. For
those wondering I ended up moving the ASP files to our
production web servers (where OWA is running) as I knew CDO
worked perfectly fine there.
However, the portlets are still not rendering, still displaying
the user authentication problems. I removed and recreated both
the Exchange provider and application, to no avail.
The test.asp script now works fine. I can also run the inbox.asp
script (passing the same parameters) and I get what I assume is
the portlet contents correctly (it displays the inbox with
messages). So it would appear the problem lies somewhere in
passing the login credentials from Login Server to the ASP files.
Any other ideas?

Answer 1

Thanx for the reply.
All machines are on the same domain. Have tried with 3 different
exchange mailboxes and NT accounts, none have worked from Portal
but all work from when passed to inbox.asp or in OWA. All
machines are also on the same subnet. I downloaded the JPDK
yesterday, so I assume it is the latest. Very frustrating! I
have a bit of experience with CDO so this is even more
frustrating!
Summary of machines used(3):
1. Win 2K Server SP1 - Oracle 8.1.7 DB, 9iAS 1.0.2.2.1, Apache
2. Win 2K Server SP1 - IIS 5.0, Outlook Web Access 5.5 SP3
3. Win NT Server SP5 - Exchange 5.5 SP3
-- all on same domain and subnet --
Is there anyway of getting a more specific error back from the
portlet? I assume the portlet simply traps ANY error from the
inbox.asp file and displays the authentication failure message
if it didn't work. I have no experience in Java yet so if you
could tell me a line to go in and add somewhere that would
return the actual output of the inbox.asp file regardless that
might help.