RE: outlook 2003 and exchange 5.5 strange connectivity problem

From: Val Tuckett [MSFT] (valt_at_online.microsoft.com)
Date: 02/16/04 

Date: Mon, 16 Feb 2004 04:33:45 GMT

You aren't going mad.

Outlook 2003 by default will resolve the Exchange 5.5 server's NetBIOS name
to its FQDN. Since this is not supported by an NT4 domain, you may receive
issues logging in with Outlook.

To work around this behaviour, alter the following:
1. Open Registry Editor (regedt32.exe or regedit.exe).

2. Browse to the following key:
    HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\RPC

3. Highlight RPC (if not listed create a new key) and on the right pane
create a new DWORD value:

Name: FQDNFailover
Data: 2

NOTE: The possible values for this DWORD are...
0 = FQDN then Netbios
1 = FQDN only
2 = NetBIOS only

4. Restart Outlook, and your issue should be resolved.

- Val

--------------------
>
>Hi, We have a strange problem when connecting an outlook 2003 to an
>exchange 5.5
>when entering the netbios exchange server name and user mailbox and
clicking
>"check name"
>The client waits more than 60 sec and then the server name in the Exchange
>server textbox automatically changes to a FQDN
>that is the mx for the Exchange server on the internet ! I first suspected
a
>name resolution issue. but it seems that is the exchange server that
>responds with this name
>(as if it happens when the mailbox is on another server) However, the name
>check is a success.
>then when i launch outlook it remains irresponsive.
>This is quite mad.
>
>tried Rpcping but cannot say if it is really helping to diagnostic the
>problem.
>
>Any ideas ? thanks for your help
> 

----
Val Tuckett
Microsoft PSS
This posting is provided 'AS IS' with no warranties and confers no rights.
Please do not send email directly to this alias.  This alias is for 
newsgroup purposes only.

Relevant Pages

  • Re: Outlook with Exchange over HTTP
    ... What's the FQDN of your server. ... Outlook tries to ... the hosts file of your exchange server. ...
    (microsoft.public.exchange.admin)
  • Re: **Outlook Problem (2nd post)
    ... Note that FQDN resolution is also needed for version 2003 referrals (i.e. ... Outlook will eventually fail over to other methods but these ... see if you can ping the Exchange ... > server by it's hostname only, ...
    (microsoft.public.exchange.clients)
  • RE: Cant log in with NT stand alone
    ... the company.corp.com as the netbios name during the dcpromo so a new domain ... What should i do with the last stand alone server acting as a Exchange 5.0 ... domain as the FQDN is not possible to type in as FQDN that is the netbios ...
    (microsoft.public.windows.server.migration)
  • Outlook 2007 through Sonicwall VPN, not sending
    ... I am running outlook 2007 through a sonicwall global VPN client. ... issue sending/recieving while I am at home. ... Exchange is unavailable. ... exchange server by hostname and by FQDN. ...
    (microsoft.public.exchange.connectivity)
  • Problems with Outlook 2003 communicating with Exchage server 2000
    ... My problem is Outlook 2003 resolves the FQDN of the server when setting up ... The DC that exchange is located on hosts the ...
    (microsoft.public.outlook.installation)
Loading