Outlook 2003 connection problem with Exchange

I've just set up a new Windows SBS 2003 R2 server and have installed OUtlook
2003 on all the PCs. One of the PCs (Win XP SP2) will not connect to the
exchange server giving the message;-

“The name could not be resolved. The connection to the Microsoft Exchange
Server is unavailable. Outlook must be on line or connected to complete this
action.�

All other PCs work fine. The affected PC can resolve the server name at the
command prompt, can ping the server and I can telnet to port 25 on the
exchange server. The user has full local administrator rights on the PC. I
have tried removing and re-installing Outlook but the problem persists. Any
ideas.

It is still a name resolution issue.

Is the NetBIOS name of the server resolved at the command prompt or the
FQDN?
Is the workstation a member of the windows domain?
Are the TCP/IP settings identical to the other workstations that connect?

"David Farmer" wrote in message
...
I've just set up a new Windows SBS 2003 R2 server and have installed
OUtlook
2003 on all the PCs. One of the PCs (Win XP SP2) will not connect to the
exchange server giving the message;-

“The name could not be resolved. The connection to the Microsoft Exchange
Server is unavailable. Outlook must be on line or connected to complete
this
action.�

All other PCs work fine. The affected PC can resolve the server name at
the
command prompt, can ping the server and I can telnet to port 25 on the
exchange server. The user has full local administrator rights on the PC. I
have tried removing and re-installing Outlook but the problem persists.
Any
ideas.

The Pc is a member of the Windows Domain, and can access shares on the server
without problem. At command line it resolves the server name "Server01" - I
will try the FQDN as well. The TCPIP settings seem the same as the other PCs.
I'll also check the hosts table in case there is any problem there.

"William Lefkovics [MVP]" wrote:

It is still a name resolution issue.

Is the NetBIOS name of the server resolved at the command prompt or the
FQDN?
Is the workstation a member of the windows domain?
Are the TCP/IP settings identical to the other workstations that connect?

"David Farmer" wrote in message
...
I've just set up a new Windows SBS 2003 R2 server and have installed
OUtlook
2003 on all the PCs. One of the PCs (Win XP SP2) will not connect to the
exchange server giving the message;-

“The name could not be resolved. The connection to the Microsoft Exchange
Server is unavailable. Outlook must be on line or connected to complete
this
action.�

All other PCs work fine. The affected PC can resolve the server name at
the
command prompt, can ping the server and I can telnet to port 25 on the
exchange server. The user has full local administrator rights on the PC. I
have tried removing and re-installing Outlook but the problem persists.
Any
ideas.

Try disabling the firewall on the client

"David Farmer" wrote:

The Pc is a member of the Windows Domain, and can access shares on the server
without problem. At command line it resolves the server name "Server01" - I
will try the FQDN as well. The TCPIP settings seem the same as the other PCs.
I'll also check the hosts table in case there is any problem there.

"William Lefkovics [MVP]" wrote:

It is still a name resolution issue.

Is the NetBIOS name of the server resolved at the command prompt or the
FQDN?
Is the workstation a member of the windows domain?
Are the TCP/IP settings identical to the other workstations that connect?

"David Farmer" wrote in message
...
I've just set up a new Windows SBS 2003 R2 server and have installed
OUtlook
2003 on all the PCs. One of the PCs (Win XP SP2) will not connect to the
exchange server giving the message;-

“The name could not be resolved. The connection to the Microsoft Exchange
Server is unavailable. Outlook must be on line or connected to complete
this
action.�

All other PCs work fine. The affected PC can resolve the server name at
the
command prompt, can ping the server and I can telnet to port 25 on the
exchange server. The user has full local administrator rights on the PC. I
have tried removing and re-installing Outlook but the problem persists.
Any
ideas.

Finally got to the bottom of it after a support call to Microsoft. The RPC
protocol was not running correctly on the client PC. The registry entries
under
HKLM/Software/Microsoft/RPC/ClientProtocols were missing. These were copied
from another PC and everything now working