![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Search this Thread | Display Modes |
|
#1
|
|||
|
|||
![]()
Hello:
I recently had a problem with Outlook 2003 SP1 connecting to our Exchange 2003 SP1 server, reporting the error "0x8004011D" and was unable to connect. I found many posts out there for this error, but our solution was different so I thought I'd post it. The symptoms were that Outlook would connect to our Exchange 2003 server fine on our LAN. But when connecting remotely using HTTPS over RPC, it would fail to connect and report error number 0x8004011D. After a lot of thorough checking, we found the problem to be simple: the clock on the client PC was off by over 1 1/2 years. Correcting the client's system time fixed the problem. Thanks, -- Chris |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
certificate for rpc over http | Sam | Outlook - General Queries | 1 | March 8th 06 04:05 PM |
Where's the certificate (RPC over HTTP between Outlook & Exchange) | Steve Baker | Outlook - General Queries | 4 | February 27th 06 10:52 AM |
Hanging 5 minutes on send when using rpc over http | Stefan | Outlook - General Queries | 0 | February 13th 06 10:55 AM |
rpc over http | jmiller | Outlook - Installation | 2 | February 5th 06 03:09 PM |
RPC over HTTP problem for some users only | Ben | Outlook - Installation | 1 | January 31st 06 05:50 AM |