Outlook 2003 with Exchange 5.5 Cluster

  • Thread starter Thread starter Paul Vdovets
  • Start date Start date
P

Paul Vdovets

I am running an exchange 5.5 cluster using veritas clustering,
while testing MS Outlook 2003 I've noticed that when configuring
the exchange connector it now does a reverse lookup on the server name
not just looking up the user account. this feature locks on to real name of
my
server rather than the cluster name so upon failover outlook remains bound
to the downed server.

does anyone know of a to disable the lookup

outlook 2000 worked perfectly with the cluster... sadly 2003 does not


Thanks in advance

Paul
 
I'm having a similar problem. Not using a cluster though.

OL2003 resolves to the external name of our server rather than the internal
machine name.....
but then it doesn't work....
 
for the record answers from the fine peopleat microsoft
ISSUE:
Outlook 2003 profile always resolved the server name to the Cluster node
name FQDN instead of the netbios name of the Exchange resource the same way
that Outlook 2000 and Outlook 2002 was done.

RESOLUTION:
We found that the "Network-Address" attributes under the Exchange server
resource has incorrect value for "ncacn_tcp_ip." In comparison with the
Windows 2000 Cluster, this value has the FQDN of the Exchange resource and
not the FQDN of the node name. In order to further troubleshoot or change
this value, I suggested to contact the Cluster Vendor.

Regarding the client side work around, we can force Outlook 2003 profile to
solve the server name to the netbios, the same way that previous version of
Outlook was done. The registry key is as followed:

HKCU\Software\Microsoft\Office\11.0\Outlook\RPC
Reg_Dword: FQDNFailover
Value: 2

The possible values
0 = FQDN then Netbios
1= FQDN only
2 = Netbios only
 
Back
Top