S
sublimnl
Hopefully someone here can shed some light on this problem. This past
weekend I upgraded my home system to 300GB SATA RAID1 for redundancy.
I preinstalled the drivers for the new RAID adapter and used Ghost to
transfer everything to my new drives. Windows booted off of the new
hardware just fine and all my apps continued to work as expected when
using Ghost.
When I brought home my system from the office last night though I
noticed that Outlook refused to connect to my Exchange2k3 server back
at the office. My home machine is running Win2k Server and is not
part of the domain. I am not using RPC-over-HTTP since I have a VPN
connection back to the office. This should behave just as if my
machine were directly attached to the remote network (as it always has
until now).
When I open Outlook it no longer prompts me for authentication at all.
It just opens up and stays in the Disconnected mode. Here's what I
have tried...
1. I setup a new profile and when I click "Check Name" I get "The
action could not be completed. The connection to the Microsoft
Exchange Server is unavailable. Outlook must be online or connected to
complete this action." The server name resolves properly to its
internal address and even if I put the IP address in the server field
I get the same error.
2. When I click Send/Receive in Outlook I get the following...
Task 'Microsoft Exchange Server' reported error (0x8004011D) : 'The
server is not available. Contact your administrator if this condition
persists.'
3. Uninstalled and reinstalled Office 2003 completely.
4. Attempted to connect from a new Windows profile.
5. Uninstalled TCP/IP from my system, rebooted, reinstalled TCP/IP.
This actually got my Outlook working until the next time I rebooted.
I tried the same solution again, but it did not work the second time
around.
6. I have also already checked the registry values at
HKLM\Software\Microsoft\RPC\ClientProtocols and everything there is
correct.
7. I have also tried to connect to a mailbox on another exchange
server on a completely separate domain.
8. I am also the FW admin, so I did a packet capture of any data
between my computer and the remote Exchange server when I tried
connecting and there is NO traffic passing, so it appears that Outlook
is not even attempting to talk to the Exchange server at all.
Same results all the way around.
Ideas?
Thanks!
Carlos
weekend I upgraded my home system to 300GB SATA RAID1 for redundancy.
I preinstalled the drivers for the new RAID adapter and used Ghost to
transfer everything to my new drives. Windows booted off of the new
hardware just fine and all my apps continued to work as expected when
using Ghost.
When I brought home my system from the office last night though I
noticed that Outlook refused to connect to my Exchange2k3 server back
at the office. My home machine is running Win2k Server and is not
part of the domain. I am not using RPC-over-HTTP since I have a VPN
connection back to the office. This should behave just as if my
machine were directly attached to the remote network (as it always has
until now).
When I open Outlook it no longer prompts me for authentication at all.
It just opens up and stays in the Disconnected mode. Here's what I
have tried...
1. I setup a new profile and when I click "Check Name" I get "The
action could not be completed. The connection to the Microsoft
Exchange Server is unavailable. Outlook must be online or connected to
complete this action." The server name resolves properly to its
internal address and even if I put the IP address in the server field
I get the same error.
2. When I click Send/Receive in Outlook I get the following...
Task 'Microsoft Exchange Server' reported error (0x8004011D) : 'The
server is not available. Contact your administrator if this condition
persists.'
3. Uninstalled and reinstalled Office 2003 completely.
4. Attempted to connect from a new Windows profile.
5. Uninstalled TCP/IP from my system, rebooted, reinstalled TCP/IP.
This actually got my Outlook working until the next time I rebooted.
I tried the same solution again, but it did not work the second time
around.
6. I have also already checked the registry values at
HKLM\Software\Microsoft\RPC\ClientProtocols and everything there is
correct.
7. I have also tried to connect to a mailbox on another exchange
server on a completely separate domain.
8. I am also the FW admin, so I did a packet capture of any data
between my computer and the remote Exchange server when I tried
connecting and there is NO traffic passing, so it appears that Outlook
is not even attempting to talk to the Exchange server at all.
Same results all the way around.
Ideas?
Thanks!
Carlos
