Cluster IP will not respond... (2003)


 

hello

i have windows 2003 cluster not respond cluster ip resource.  (can't wait migrate windows 2008 clustering)

node = 192.168.1.101
node b = 192.168.1.102
cluster resource ip = 192.168.1.100

the cluster fails on node node ok , again.

my application connect node when node holding resources , same true when connecting node b.  however, application not connect cluster resource ip.  cannot ping or telnet cluster resource ip device regardless of node holding resources.

my cluster not standard cluster build built on 2 self-contained domain controllers.  (this application requirement)

this has worked in past , working in production environment.  need test environment working can begin work of migrating windows 2008 cluster.

i appreciate pointes resolve this. 

many thanks

ewan.

i didn't think possible cluster domain controllers.  not supported configuration if have.  can't imagine application requiring microsoft has never supported.

did ever have working?  started happening?

if built hardware manufactured in last 4 years, unsupported configuration.  2003 clusters had pass qualification test included hardware components - server, hbas, storage.  microsoft has not been taking new certifications @ least 4 years.  using current hardware puts in untested waters.

given sorts of parameters, don't know sort of assistance can provided.


.:|:.:|:. tim



Windows Server  >  High Availability (Clustering)



Comments

Popular posts from this blog

Error: 0x80073701 when trying to add Print Services Role in Windows 2012 Standard

Disconnecting from a Windows Server 2012 R2 file sharing session on a Windows 7,8,10 machine

Windows 2016 RDS event 1306 Connection Broker Client failed to redirect the user... Error: NULL