add node failed

hi!
our AD, say company.com, has clients with different DNS suffixes. E.g.
dc1.company.com
dc1.company.com
sql1.sub.company.com
sql2.sub.company.com
DNS-Settings are correct, dNSName-Attribute in AD is correct, too. All
Servers are member of the Domain COMPANY.COM. when joining the domain I told
the clients NOT to change the DNS suffix when joining a domain, cause there
should be a DNS-subzone without a Windows-ADS-subdomain!
when trying to add a new node to the sql2005 (enterprise) cluster, let's say
sql3.sub.company.com, during the check ("analyzing configuration") in
cluster admin I get the error:
2007-03-21 13:14:11.668 [WARN] sql3: The client attempted to connect to
"SQL3.SUB.COMPANY.COM," but reached "SQL3.COMPANY.COM" instead.
(hr=0x000001, {E88B08DD-2460-4DF1-B5C2-28587DD164EA},
{27CD60A8-E60D-4BF9-BFD5-708B2A8844D8}, 1, 1, 1), (null)
2007-03-21 13:13:30.277 [WARN] mycluster: The client attempted to connect to
a cluster in the domain "sub.company.com," but reached a cluster in the
domain "company.com" instead. (hr=0x000001,
{E88B08DD-2460-4DF1-B5C2-28587DD164EA},
{D60A2A52-44F2-47B7-AD5B-286AF1176A01}, 1, 1, 1), (null)
checked a lot of things, all the attributes in AD (with adsiedit), all DNS
entries, everything seems to be correct. pings, nslookup, etc all resolv the
correct name, I have no more ideas why the check gets a response from a
server with the wrong DNS name.
any ideas?
ciao, ralf
ralf wigand
university of karlsruhe, germany
As I told all cluster nodes ARE in the same domain. It is just that the DNS
Domain Name is different from the ADS Domain Name, because the ADS Domain
contains different DNS Domains. Please re-read my example :-)
TIA, ralf
"Edwin vMierlo [MVP]" wrote:

> All cluster nodes of the same cluster should be in the same domain
> and try again adding your node to the cluster
> Rgds,
> Edwin.
>
>
> "Ralf Wigand" <wigand@.rz.uni-karlsruhe.de> wrote in message
> news:eapJao4dHHA.3272@.TK2MSFTNGP03.phx.gbl...
> told
> there
> say
> to
> the
>
>