Microsoft

AdminChallenge: Help Greg overcome his hard luck

Greg has suffered a power surge and a burnt UPS. His Novell server is toast .He quickly converts a workstation to a server to get him through the crisis, but something's not right. Knowing the solution could win you a TechRepublic T-shirt!

Every other week, NetAdmin Republic poses a systems or network problem requiring a solution. Some challenges are routine, while others may be more difficult. We then conduct a random drawing from the correct responses received and send two lucky winners a fancy new TechRepublic T-shirt. You'll be the envy of the office! Let's start with the solution to our previous challenge.
William’s woes
As you may remember, William had to upgrade his office’s network to Windows 2000. This included both servers and workstations, as the company wanted a fully integrated system. William didn’t expect the upgrade to be much of a problem. After all, the machines in the office were mostly all the same make and model. It would be a matter of installing the OS on one machine and ghosting the others.

William was tasked with proving that all the machines could be upgraded from Windows NT 4.0 to Windows 2000 with little or no problems at all. Unfortunately, his company wasn’t willing to spend money to test the software compatibility.

How could he do it? Simple. All William needed to do was insert the Windows 2000 Server CD-ROM and type x:\i386\winnt32.exe /checkupgradeonly or use Microsoft’s Windows 2000 Readiness Analyzer.
Congratulations go to Jeff Shattuck and Damian McIntosh, whose winning entries were randomly selected from all of the correct submissions received.
Greg’s hard luck
About a year ago, Greg suffered a power surge, and his UPS failed. The surge fried the motherboard in his Novell server. He took a workstation and converted it into a server while he was waiting for new parts. Right away, he began experiencing problems.

The newly configured server would work fine all day long. He would go home, only to get a call from the office between 5:00 P.M. and 6:00 P.M. saying that the server drives were not available. He would return to the office and check a workstation and find that the mapped drives were unavailable, just as he had been told.

Greg would then go to the computer room and check the Novell server, which would appear to be running fine. So he would return to the workstation, and it would be suffering no other apparent problems.

This cycle continued. The server would work fine all day long, and then after 5:00 P.M., it would stop working every 30 minutes to an hour. Then, it would start working as soon as Greg checked on it.

What might Greg have done wrong?
What could be causing Greg’s problem? Send your answer to TechRepublic by Tuesday, June 27, 2000. We'll send a TechRepublic T-shirt to two individuals whose names we select randomly from all the correct answers received.
By submitting your answer, you agree to let TechRepublic publish your solution on its Web site. You also agree that TechRepublic may adapt and edit and authorize the adaptation and editing of each submission as it deems necessary. TechRepublic may or may not publish a submission at its sole discretion.
Thanks to . . .
Thanks to TechRepublic member Rod Little for providing Greg’s hard luck challenge. He’ll be sporting a cool new TechRepublic T-shirt for his effort.
If you'd like to share an opinion, please e-mail the editor or post a comment below.

Editor's Picks

Free Newsletters, In your Inbox