Cluster Node Communications

I just rebuilt a 2 node W2k/SQL2k cluster that resides in
a NT4 domain. The cluster itself seems to be working
fine, the website that runs off of the virtual SQL server
is running fine.
However, both nodes in the cluster are not able to
communicate with other machines in my 2 other
trusted/trusting domains. My other 2 domains are W2k
based domains. Prior to the rebuild there were no
communication problems accross domains.
If I try to browse to the nodes in Windows Explorer I get
the message "No logon servers currently available to
service your request" and if I try to logon to one of the
nodes at the console using my user name and domain, it
says the domain is unavailable.
Any assistance would be greatly appreciated.
Patrick G.
You can check a few things.
1. Make sure your domain trust(s) are still in place and functioning correctly. If you don't have the W2K support tools installed (ie in a prod environment), run dsa.msc and check that you can browse the remote domain and list groups and users in the rem
ote domain (eg attempt to add a global group from the remote domain to a local domain group - you can do this with committing the change).
2. Make sure the account you are using has a valid SQL Server login on the remote SQL Server (or your account is in the builtin admins group on the remote server - if the other domain are willing to trust you with local admins on the remote server or the
remote domain).
Are both domains in W2K native or do you have W2K and W2K3 forests in the mix?

Cluster Log error message

Hello to all,
I'm investigating an application outage issue on a 2-node W2K Adv Server
cluster. A Generic Application is running on the cluster in a remote site,
and connects to a UNIX-based Oracle db at my site. There are intermittent
MRxSMB 3019 Event IDs which I'm not too worried about. I just used Q138365
to adjust the autodisconnect value to -1.
But I'm finding this error message in the Cluster log:
Network Name <Network Name CLUSTER VIRTUAL NAME>: Failed to register DNS PTR
record X.X.X.X.in-addr.arpa. for host CLUSTER VIRTUAL NAME FQDN, status 9005
I can't find anything documented about this error, so I can't tell if this
is something to be concerned about. Is it nothing, a cluster service
problem, DNS registraion problem?
Any thoughts would be greatly appreciated.
Thanks in advance.
Hey I had this error as well when I was setting up my cluster
To fix it:
o Right-click the network connection for your heartbeat adapter, and then
click Properties.
o Click Internet Protocol (TCP/IP), and then click Properties
o On the DNS tab, verify that no values are defined. Make sure that the
Register this connection's address in DNS is cleared.
Hope this helps!!
"Chris" <Chris@.discussions.microsoft.com> wrote in message
news:932C28D9-F8C2-4F83-BE57-AA149AF27065@.microsoft.com...
> Hello to all,
> I'm investigating an application outage issue on a 2-node W2K Adv Server
> cluster. A Generic Application is running on the cluster in a remote
site,
> and connects to a UNIX-based Oracle db at my site. There are intermittent
> MRxSMB 3019 Event IDs which I'm not too worried about. I just used
Q138365
> to adjust the autodisconnect value to -1.
> But I'm finding this error message in the Cluster log:
> Network Name <Network Name CLUSTER VIRTUAL NAME>: Failed to register DNS
PTR
> record X.X.X.X.in-addr.arpa. for host CLUSTER VIRTUAL NAME FQDN, status
9005
> I can't find anything documented about this error, so I can't tell if this
> is something to be concerned about. Is it nothing, a cluster service
> problem, DNS registraion problem?
> Any thoughts would be greatly appreciated.
> Thanks in advance.
sqlsql