OWA and SSL works but not RPC HTTPS

[lebisol]

Hello everyone,
Sorry if this thread has beed discussed but search feature on TT has been dead for days...anyhow.
I followed the:

http://technet.microsoft.com/en-us/library/aa996366.aspx

my SSL certificate is 'local' so not quite registered yet.
Tried connecting with outlook2k3 (patched) over LAN and simply getting an error back that I can not connect.
Using the same cridentials I can access the mailbox through OWA

https://feserver/exchange

I have confirmed:
-That RPC over HTTP Support Is Installed (ports ok 6001,6002,6004)
-That World Wide Web Publishing Service Is Running
-That SSL Certificate Is Installed on RPC Proxy Server
-RPC Virtual Directory Configuration ( got 401.3 on

https://feserver/rpc/

)
-That RPC Proxy Server Has Basic Authentication Configured (basic-clear text)
-That RPC Proxy Server Extension Is Loading Properly (did not need to edit path of .dll)
- When asked entered domain\username cridentials
then also tried to aqssign default domain on rpc folder and authentication without need for 'domain\' part
...end result server unavailable.

No firewalls....on workstation or servers....
Any ideas, this has been killing me....
Many thanks for your time!

:--------------------------------------:

All around in my home town,
They tryin' to track me down...

 

[lebisol]

Forgot to mention that Global Catalog server (second BE2 not 'involved') is e2000.
Would this matter? Should I make the BE (e2k3) become Global Catalog?
As you can tell, in process of migrating from e2000 to e2k3 and looking to retire e2000.
Have I jumped the gun?
Thanks again!

:--------------------------------------:

All around in my home town,
They tryin' to track me down...

 

[lebisol]

Ignore the post....I did jump ahead...no 2003 domain controller yet.

:--------------------------------------:

All around in my home town,
They tryin' to track me down...