The name could not be resolved. The action could not be completed

From: Joseph Gruber (Gruber_at_discussions.microsoft.com)
Date: 03/12/05


Date: Sat, 12 Mar 2005 11:03:03 -0800

I'm having a problem getting my Outlook 2003 clients to see our Exchange 2003
standard server. When I create the profile I get the following error when I
"Check Name": "The name could not be resolved. The action could not be
completed."

MachineA (Windows 2003 Server) is the exchange server and also hosts
external DNS and runs VMWare. VMWare runs MachineB (Windows 2003 Server)
which is the DC & GC and hosts DHCP & DNS. MachineA points to MachineB for
DNS and all desktop machines (Windows XP Professional) point to MachineB for
DNS.

We are moving from a linux solution (Postfix & CourierIMAP) to Exchange but
can't get past this hurdle. I've searched google as well as these newsgroups
and have tried numerous suggestions but none seem to work for me.

Any suggestions are GREATLY appreciated!!



Relevant Pages

  • The name could not be resolved. The action could not be completed
    ... I'm having a problem getting my Outlook 2003 clients to see our Exchange 2003 ... MachineA (Windows 2003 Server) is the exchange server and also hosts ... VMWare runs MachineB ... which is the DC & GC and hosts DHCP & DNS. ...
    (microsoft.public.exchange.connectivity)
  • The name could not be resolved. The action could not be completed
    ... I'm having a problem getting my Outlook 2003 clients to see our Exchange 2003 ... MachineA (Windows 2003 Server) is the exchange server and also hosts ... VMWare runs MachineB ... which is the DC & GC and hosts DHCP & DNS. ...
    (microsoft.public.exchange.connectivity)
  • The name could not be resolved. The action could not be completed
    ... I'm having a problem getting my Outlook 2003 clients to see our Exchange 2003 ... MachineA (Windows 2003 Server) is the exchange server and also hosts ... VMWare runs MachineB ... which is the DC & GC and hosts DHCP & DNS. ...
    (microsoft.public.outlook)
  • Re: Exchange 2003 installation
    ... Configured on the NIC of the server. ... "Meinolf Weber" wrote: ... Is the ISP's DNS ... Old exchange removed - I don't know the ...
    (microsoft.public.win2000.active_directory)
  • RE: Exchange Fails to start after a reboot.
    ... this problem appears to be caused by DNS ... please try the steps below on Exchange server. ... Microsoft Online Partner Support ...
    (microsoft.public.exchange.admin)