Re: Exchange Server Reported Error 0x8004011d

Tech-Archive recommends: Speed Up your PC by fixing your registry

Hi Jason,

Thanks for all your help, I don't think it's an exchange issue, the same
system no longer opens up the internel website (http://companyweb) I am going
to take the system off the network and rejoin the network, I will let you
know how it goes.



"Jason Miller [SBS-MVP]" wrote:

If you can rule out Exchange as the culprit (if the user's mailbox works on
other systems), then maybe taking the question to an Outlook group will
yield better information and recommendations. It sounds application and
client-side specific to me, but I'm not certain.

Wish I could be of more help,

Jason



"Adam B" <AdamB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B90B2EDD-7E33-476D-A49C-46873CB38469@xxxxxxxxxxxxxxxx
Hi Jason,

Yes sorry conect the system to the network using connectcomputer, system
has
been working for around 6 months, then just stopped working, I have
deleted
the exchange details in control panel --> mail, no joy.



"Jason Miller [SBS-MVP]" wrote:

Hi Adam

The other question Claus had for you related to how the workstation in
question was joined to your SBS domain - via "connectcomputer"?

Have your tried to manually recreate your Exchange Mail Profile (control
panel | mail | show profiles)? Delete what's there (it's not working
anyway), and recreate using the Exchange environment variables for your
network. This might get you back on track without the error you're
currently seeing.

I hope that helps,

Jason



"Adam B" <AdamB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4100A193-4E5E-490C-A0EF-4CF188B7B3A1@xxxxxxxxxxxxxxxx
HI,

I can ping the server name, gets a reply 4 times as it should.

I'm not using DHCP, other workstations on the network all have static
IP
addresses and are working fine.

Look forward to your reply.

"Claus" wrote:

Did you join the computer via "connectcomputer"? Is the box set to
DHCP?
Did
you check that it gets a proper IP configuration? Can you ping the
server
by
name?

--
Claus
"Adam B" <AdamB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B8288EDD-ED07-45FB-917C-F9D7524A8E38@xxxxxxxxxxxxxxxx
Hi

Have a SBS 2003 running with 6 Workstations, outlook 2003 on one of
the
systems won't connect to the server and returns the error Exchange
Server
Reported Error 0x8004011d

All the other systems run fine, I have reinstalled Outlook 2003 on
this
system, but with no joy, can any one help



.

Relevant Pages

  • Thanks to All Or How I saved my AD
    ... and do rebuild of Windows 2000 Server and Service Packs. ... Explorer 5.5, Backup Exec, Diskkeeper and McAfee. ... But Exchange was unable to Mount ... receiving complaints from all over the network about all kinds of problems. ...
    (microsoft.public.win2000.active_directory)
  • Thanks to All Or How I saved my AD
    ... and do rebuild of Windows 2000 Server and Service Packs. ... Explorer 5.5, Backup Exec, Diskkeeper and McAfee. ... But Exchange was unable to Mount ... receiving complaints from all over the network about all kinds of problems. ...
    (microsoft.public.exchange2000.active.directory.integration)
  • Re: 24 hours of.. ummm.. fun?
    ... Directory with a 2k server. ... Exchange to the network. ... my remote users to really use all the features, ...
    (alt.2600)
  • RE: strange problem.......
    ... Ignore the title on the site about not trusting Exchange, ... POP3 account will stay default. ... > I have an SBS 2003 network. ... > I then manually map a drive to a share on the server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Connecting to Exchange...
    ... That means that SBS has a static *private* IP on your LAN. ... Not being able to ping "the server" is probably not a sign of a problem...and is also technically inaccurate. ... I understand the desire to keep your server minimalist and only run exchange, but DNS and DHCP should be considered "essential" SBS components. ...
    (microsoft.public.windows.server.sbs)