0x8004011D--Microsoft Exchange Error "The Server is Not Available"

[lopa]

We are running a SBS 2003 server with MS Exchange. Our clients are laptops running Outlook 2003 and router is Cisco Pix 515. This setup was working fine since past two years but don’t know what went wrong suddenly a week ago, whenever the laptop clients try connecting remotely over VPN they get error message saying “0x8004011D. The Server is Not Available.”

I’m not able to get to the cause of problem because when we dial in through broadband and VPN, it connects fine without any problem. But as soon as we start Outlook, it says ‘trying to connect’ for few minutes and suddenly error “0x8004011D”.

As I said the setup was working good since past few years, the only change we did 2 weeks is we upgraded MS Exchange to SP2 and enabled Windows Mobile Push Email using SSL certificate. Now, can anyone say what is wrong and how can I fix the problem?

Thank you.

[Andrus K]

Before I could answer you something I would like to know whether you are able to ping the server by name? Also do you have the latest service packs installed on Outlook/office? Reply back

[lopa]

Thanks for the help Andrus. Yes my Office is with Service Pack and I’m not able to ping with Server name as well. So can you tell me what adjustments do I need to make to get this to work? Or I guess I’m making some problem with server name ping as am confused between server names, that is servername.domain.local or servername.domain or just plain old servername?

Thanks for your helps again.

[Andrus K]

Your question surprised me. Anyways, you just need to ping the plain older servername. Also I would like to confirm again that you have installed Service packs for Office and not your SBS server.

[lopa]

Ok, go it. all service packs (office, SBS and XP) were applied.

Pinging works on the server name.(0% loss, 20ms average)

[Henri@ksen]

As you said you cant ping, it doesn’t means that it's not accessible otherwise. By the way are you using Cisco VPN Client or SBS PPTP VPN. If yes, than have you enabled split tunneling? Blocking ICMP is fairly common. So just go through the following steps:

Try Start -> Run -> \\servername -> OK from the VPN-connected laptop.

If that doesn't work then type \\internal.ip in RUN and press OK.
If still don’t work then type \\domain.local\Netlogon and press OK

Let me know the results.

[raydenryu]

SOLUTION: close outlook.
open command prompt. type ipconfig /flushdns hit enter.
type Ipconfig /register Dns hit enter
type gpupdate /force

this should fix the issue.

Rayden