Discussion Locked

Strange happenings

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I just acquired a Compaq Proliant 1600 server and have been playing with it. As a strictly 'desktop' man, I've never had any experience, but you're never too old to learn, right?!!

I obtained Windows Server 2003 Standard, and installed it on this beast. Everything installed well, except the integrated Compaq Netelligent 10/100TX controller. I downloaded the drivers from the HP website and got all the hardware working. I then click the Manage Server Wizard or Configure Server Wizard, and get a message teling me that this computer is a node on a cluster, and that I cannot manage the server.

Why does 2003 Server think this computer is part of a cluster? I haven't even hooked in a single network cable yet so it is stand-alone right now.

When I try to follow the link for Cluster Administration, I end up going round in circles and getting nowhere. I eventually ran the Cluster Administration Wizard (having expanded the appropriate files from the 2K3 CD into the system32 folder) and it asks me for a computer name or cluster name to connect to. As this computer is currently on it's own, I can't connect to anything, I cannot find the name of the cluster it is 'alleged' to be part of, and if I enter the name of the computer (test) the wizard just thows an error.

Why is 2K3 thinking it's a cluster node (it isn't!) and how do I tell the system it's a stand alone server so it will allow me to administer it?!!!

6 replies

by guruofdos

In System Services, Clustering Service is not even installed. All errors generated by the clustering wizard generate this error. I can't even work out how to install or uninstall services!!

by cg it

humm not seen this one before. I know that if you install ALL the network tools on the CD that in the admin tools, you'll get a cluster Icon but that Icon is invalid. It just shows up. I would ask this question over on Microsoft's Newsgroups for Windows 2003 Server. See if someone over there has seen this. Also, periodically, some techs at Microsoft post to those boards.

This discussion is closed to new replies.