Home

2 node failover cluster cant ping cluster network name from not owner node

%3CLINGO-SUB%20id%3D%22lingo-sub-168872%22%20slang%3D%22en-US%22%3E2%20node%20failover%20cluster%20cant%20ping%20cluster%20network%20name%20from%20not%20owner%20node%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-168872%22%20slang%3D%22en-US%22%3E%3CP%3EHello%3C%2FP%3E%0A%3CP%3EI%20have%202%20node%20failover%20cluster%20based%20on%20server%202016%20server.%20node1%20is%20owner%20of%20cluster.%20I%20cant%20ping%20cluster%20network%20name%20only%20from%20cluster's%20owner.%20So%20I%20cant%20ping%20cluster%20name%20from%20node2%20and%20on%20node2%20Server%20Manager%20shows%20error%20to%20communicate%20to%20cluster%20object.%20But%20cluster%20status%20is%20ok.%20If%20I%20change%20node's%20owner%20ping%20behavior%20will%20be%20contra%20versa.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20have%20checked%20on%20another%20cluster%2C%20the%20same.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%2F%2FAlexander%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-168872%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EClustering%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EManagement%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ENetworking%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-271455%22%20slang%3D%22en-US%22%3ERe%3A%202%20node%20failover%20cluster%20cant%20ping%20cluster%20network%20name%20from%20not%20owner%20node%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-271455%22%20slang%3D%22en-US%22%3E%3CP%3ENo%20resolution%20in%20my%20datacenter.%26nbsp%3B%20We%20*think*%20the%20issue%20is%20a%20network%20related%20issue%20as%20the%20issue%20impact%20physical%20devices%20and%20virtual%20devices.%26nbsp%3B%20We%20are%20engaging%20a%20consulting%20firm%20to%20assist%20with%20our%20situation.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-271224%22%20slang%3D%22en-US%22%3ERe%3A%202%20node%20failover%20cluster%20cant%20ping%20cluster%20network%20name%20from%20not%20owner%20node%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-271224%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20the%20same%20issue%26nbsp%3B%3CBR%20%2F%3Ethere%20is%20any%20update%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-253872%22%20slang%3D%22en-US%22%3ERe%3A%202%20node%20failover%20cluster%20cant%20ping%20cluster%20network%20name%20from%20not%20owner%20node%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-253872%22%20slang%3D%22en-US%22%3E%3CP%3Enope%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-242880%22%20slang%3D%22en-US%22%3ERe%3A%202%20node%20failover%20cluster%20cant%20ping%20cluster%20network%20name%20from%20not%20owner%20node%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-242880%22%20slang%3D%22en-US%22%3E%3CP%3EDid%20you%20ever%20get%20this%20resolved%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-180441%22%20slang%3D%22en-US%22%3ERe%3A%202%20node%20failover%20cluster%20cant%20ping%20cluster%20network%20name%20from%20not%20owner%20node%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-180441%22%20slang%3D%22en-US%22%3Efrom%20cluster%20owner%20I%20can%20ping%20cluster%20name%2C%20from%20node2%20(not%20owner)%20I%20cant%20ping.%20On%20node2%20I%20could%20resolve%20cluster%20name%2C%20also%20in%20DNS%20this%20A%20record%20already%20exists%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-180075%22%20slang%3D%22en-US%22%3ERe%3A%202%20node%20failover%20cluster%20cant%20ping%20cluster%20network%20name%20from%20not%20owner%20node%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-180075%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20Alexander.%3C%2FP%3E%0A%3CP%3EYou%20may%20check%20in%20the%20DNS%20console%20if%20the%20cluster%20name%20is%20registered.%20If%20it%20is%20not%2C%20create%20an%20entry%20(A%20or%20AAAA)%20for%20it%2C%20and%20clear%20the%20DNS%20client%20cache.%3C%2FP%3E%0A%3CP%3ECheers%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-179450%22%20slang%3D%22en-US%22%3ERe%3A%202%20node%20failover%20cluster%20cant%20ping%20cluster%20network%20name%20from%20not%20owner%20node%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-179450%22%20slang%3D%22en-US%22%3E%3CP%3EAre%20you%20able%20to%20ping%20the%20cluster%20name%20from%20another%20pc%20or%20server%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-178540%22%20slang%3D%22en-US%22%3ERe%3A%202%20node%20failover%20cluster%20cant%20ping%20cluster%20network%20name%20from%20not%20owner%20node%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-178540%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20having%20the%20exact%20same%20problem.%20Has%20anyone%20provided%20any%20resolution%20to%20this%20problem%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%3C%2FP%3E%0A%3CP%3EAyaz%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-176020%22%20slang%3D%22en-US%22%3ERe%3A%202%20node%20failover%20cluster%20cant%20ping%20cluster%20network%20name%20from%20not%20owner%20node%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-176020%22%20slang%3D%22en-US%22%3Ewith%20network%20everything%20ok%2C%20I%20still%20dont%20know%20what%20the%20issue%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-169711%22%20slang%3D%22en-US%22%3ERe%3A%202%20node%20failover%20cluster%20cant%20ping%20cluster%20network%20name%20from%20not%20owner%20node%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-169711%22%20slang%3D%22en-US%22%3EDo%20you%20have%20the%20windows%20firewall%20enabled%3F%20You%20could%20do%20a%20test%20and%20disable%20the%20firewall%20on%20both%20servers%20and%20then%20test%20again.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20this%20works%20we%20would%20know%20it's%20the%20firewall%20blocking.%20%3CBR%20%2F%3E%3CBR%20%2F%3EYou%20could%20look%20at%20enableding%20file%20and%20print%20sharing%20on%20both%20servers%20also.%20This%20should%20open%20up%20the%20ports%20you%20need.%3CBR%20%2F%3E%3CBR%20%2F%3EHope%20that%20helps%3CBR%20%2F%3E%3CBR%20%2F%3ERichard.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-169540%22%20slang%3D%22en-US%22%3ERe%3A%202%20node%20failover%20cluster%20cant%20ping%20cluster%20network%20name%20from%20not%20owner%20node%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-169540%22%20slang%3D%22en-US%22%3EYes%2C%20with%20network%20and%20cluster%20everiyhing%20ok.%20It%20is%20just%20annoying%20that%20on%20node-%20not%20owner%20server%20manager%20always%20shows%20%22Target%20computer%20is%20not%20accesibale%22%20about%20cluster%20network%20name%20and%20I%20cant%20ping%20it%20name.%20And%20in%20logs%20I%20have%20error.%3CBR%20%2F%3E%3CBR%20%2F%3EDCOM%20was%20unable%20to%20communicate%20with%20the%20computer%20CLU-PRO-BTSQL02.domain.local%20using%20any%20of%20the%20configured%20protocols%3B%20requested%20by%20PID%20199c%20(C%3A%5CWindows%5Csystem32%5CServerManager.exe).%3CBR%20%2F%3Eeventid%2010028%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-169011%22%20slang%3D%22en-US%22%3ERe%3A%202%20node%20failover%20cluster%20cant%20ping%20cluster%20network%20name%20from%20not%20owner%20node%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-169011%22%20slang%3D%22en-US%22%3EAre%20you%20able%20to%20supply%20the%20network%20configuration%20for%20both%20servers%3F%3C%2FLINGO-BODY%3E
alexander tikhomirov
Contributor

Hello

I have 2 node failover cluster based on server 2016 server. node1 is owner of cluster. I cant ping cluster network name only from cluster's owner. So I cant ping cluster name from node2 and on node2 Server Manager shows error to communicate to cluster object. But cluster status is ok. If I change node's owner ping behavior will be contra versa.

 

I have checked on another cluster, the same.

 

//Alexander

12 Replies
Are you able to supply the network configuration for both servers?
Yes, with network and cluster everiyhing ok. It is just annoying that on node- not owner server manager always shows "Target computer is not accesibale" about cluster network name and I cant ping it name. And in logs I have error.

DCOM was unable to communicate with the computer CLU-PRO-BTSQL02.domain.local using any of the configured protocols; requested by PID 199c (C:\Windows\system32\ServerManager.exe).
eventid 10028
Do you have the windows firewall enabled? You could do a test and disable the firewall on both servers and then test again.

If this works we would know it's the firewall blocking.

You could look at enableding file and print sharing on both servers also. This should open up the ports you need.

Hope that helps

Richard.
with network everything ok, I still dont know what the issue

I am having the exact same problem. Has anyone provided any resolution to this problem?

 

Thanks

Ayaz

Are you able to ping the cluster name from another pc or server?

Hi, Alexander.

You may check in the DNS console if the cluster name is registered. If it is not, create an entry (A or AAAA) for it, and clear the DNS client cache.

Cheers

from cluster owner I can ping cluster name, from node2 (not owner) I cant ping. On node2 I could resolve cluster name, also in DNS this A record already exists

Did you ever get this resolved?

I have the same issue 
there is any update ?

No resolution in my datacenter.  We *think* the issue is a network related issue as the issue impact physical devices and virtual devices.  We are engaging a consulting firm to assist with our situation.

Related Conversations
Extentions Synchronization
ChirmyRam in Discussions on
3 Replies
Tabs and Dark Mode
cjc2112 in Discussions on
35 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
9 Replies