Question Locked

I inheirited a Windows 2003 server that has not been rebooted in two years.

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

Well first off, this is an existing server that I began to work on recently. First thing I did was do a full backup, which coincidentally brought me to my first problem. Ntbackup was giving all kinds of problems with the tape drive. Eventually I gave up and just put it on a hard drive, which I plan to move to a external later. In any event, while I am experienced with computers in general, I am more of a programmer than IT specialist. So you could say I am an amateur that picked up a book to try and learn something. I could use a lot of help and some advice. Here is some basic info about the network I was able to find out:

-Previous IT staff fired several years ago and the server has been left untouched since. According to the NIC its going on 700 days.
-Zero updates and no policies that I can find. It is pretty much stock aside from the users and shared folders.
-10 computers + server acting as DC + switch + hardware firewall
-half of the computers downstairs use DHCP while other half upstairs are manually assigned (which confuses the hell out of me)
-Runs off a T1, but the actual speeds are extremely poor and bursty
-All clients are running Windows XP pro
-Server us virus free

So far I have only formatted one of the stations upstairs that are statically assigned. While trying to reinsert it into the domain I discovered something mind boggling. I could not for the life of me get into the domain. It just did not work. Previously, normal users of the domain could not even log into it from those stations. Eventually I started doubting the hardware and brought the box downstairs to a port that I knew worked. It did work. I added the computer to the domain and it it had full functionality. To make a long story short, I shuttled the box up and downstairs until I discovered the static ip assignment and then I found out that when the computer was plugged in upstairs it was merely using a cached copy of AD users and policies. But the catch is, even though its not fully connected (i think) to the domain it still maintains a connection to the internet. It browses the web just fine, which is its only purpose. This still raises a big question mark in my mind though. It is also very inconvenient and probably not good for security either.

My other problem is really the speed of the internet connection which typically starts out fast then drops down to almost 56k speeds. Even though the internet connection works, I cannot ping anything from the server or the workstations. It just times out, although i think this probably has something to do with the firewall. I know servers are supposed to stay on for long periods of time but could the fact that it has been on for so long be contributing to the speed problems? To be quite frank, I am apprehensive about rebooting the thing because there are too many unknowns. Mainly if I break it, I am not quite sure how to fix it. Is there anything that needs to be done afterward to get the server running again? do I have to start a bunch or services and stuff? I am sure this question serves to illustrate how much of a beginner I am.

In a nutshell:
-What is the deal with the half dynamic / half static IPs and the broken domain connectivity and is there anyway to diagnose/fix it?
-Is it okay to reboot and patch without breaking any functionality
-How can I diagnose or fix the speed problems? Is it the server or the line?

I know these questions may seem foolish to some but I would appreciate any help, advice, or even links to somewhere or someone else who can help.

Thanks,
Aldon Tom

12 replies

by oh smeg

Unless of course I'm asking them. :)

Now in order of asking

[i]What is the deal with the half dynamic / half static IPs and the broken domain connectivity and is there anyway to diagnose/fix it?[/i]

I'm not really sure why things have been done this way but it was obviously setup this way for a reason. Perhaps as a Security Protocol where the Upstairs Users [b]Can Not[/b] access the Server only the Internet to do whatever it is that they do. Or it could just because someone was lazy and didn't care. But I would be looking at the first option personally.

[i]Is it okay to reboot and patch without breaking any functionality[/i]

Well it should be perfectly OK to do this as leaving any version of Windows running so long is just begging for problems. However I'm assuming that there was a reason why it was not shutdown regularly so maybe do this when no one is at work and you have time to play around. Nothing is worse than having a group of people screaming out that their Mail is out and they want it back on [b]Immediately.[/b] This is guaranteed to cause problems and mistakes. But I suggest Cloning the HDD in the Server before proceeding any further. It would at least give you some breathing space if anything goes wrong. [b]Maybe.[/b] :D

[i]How can I diagnose or fix the speed problems?[/i]

I would start out with a Reboot just to see what happens. After that long any batteries in a UPS would probably need replacing anyway. But leaving a Windows Machine running that long by now it must be suffering severely from Memory Leaks, Fragmented HDD, and so on.

To diagnose the Speed Issues for the Internet Connection try using a product like Wireshark and see what is happening on the network. If there is a lot of traffic you need to make sure this is as it should be.

http://www.wireshark.org/download.html

Anyway the more Internal Traffic you have on the LAN the slower the Data Transfers from the Net will be. There could be limits built into the system as well to discourage people from downloading large files.

I'm assuming that there is no Documentation involved here so can you at least ask someone responsible that was there when it was originally setup what it was intended to do and how it was expected to work?

[i]Is it the server or the line?[/i]

Could be either but my first guess would be the server and or the Firewall. Though you could also look at the Servers Hardware it may no longer be suitable for what it is expected to do. Things like this walking into the unknown would make most Experienced Consultants want to run away and hide till it was sorted so your inexperience I'm assuming here has allowed you to be dropped in it from great heights. You'll learn quickly if nothing else. :D

OH and document everything as you go along you'll forget things if you don't do that.

As for the Tape Drive clean it out and replace the Tapes. These need to be kept clean and I'll guarantee that this has not been done and Tapes do wear out over time. But as a Test just get 1 new Tape and try to fill it with a Partial Backup to see what happens. It's possible that the Tape Drive Failed and because there is no one there responsible to keep things working nothing has been done to fix the problem.

Col

by noxin337

The helpful advice is much appreciated. I will definitely try some of this out. One question though, how would someone actually enable this kind of half static /half dynamic scheme. I have no clue as how you would go about doing this and thus I wouldn't know where to look.

by oh smeg

But I'm assuming that they have set Static IP Addresses to the computers to allow them a Internet Connection and then set a Rule somewhere to prevent any Static Address from joining the Domain or logging onto the server. Could be through Group Policy or Active Directory as the obvious starting points but really anything is possible here. :)

That is however just a guess.

Col

by symonline

hi ,i know your fear is something like bearing the risk of services that may not start after reboot.

i had a similar experience but in a smaller organization.

one thing i feel you should do at first is to be able to identify all your applications installed on the servers ,windows isn't that rigid as Linux .the the next step is to identify the dependent services of the applications,after that is done then goto control panel and check the status of those identified services if their state is either (MANUAL),(AUTOMAtic),(DISABLE),MAKE SURE you take a print screen and save it,then make sure all the identified services are checked to be (AUTOMATIC STATE) then u are at the right side.dont be afraid restart your server.

by seanferd

Definitely make sure the server is imaged in case patches break it. There obviously would be no way to test each update, but since this is described as a stock installation, there are probably mercifully few things to break.

I'd like to commend the OP for asking a well thought-out question.

by rshack

Tom, did not read the details but if it were me... This is a new situation, I cannot predict anything. Ask yourself questions; Is the server CRITICAL to operations? How much downtime will they tolerate for problems? Will they consider a replacement server, if needed? If yes, look at migration project strategy.

I would most certainly try to obtain a full backup image (perhaps with ImageX, or a Symantec product for servers). At minimum, any critical DATA and all server configurations. ImageX requires a reboot to CD, so that may be risky. Seek a product that allows 'live' backup.

I would create a laundry list, prioritize and document risks. What is REALLY needed vs DESIRED? Once you can speak intelligently, I would tactfully and carefully communicate to the client how challenging this situation is. Look at their perspective as they may have NO clue why you can't just 'push a few buttons' to make it work. I use analogies they can relate to.

by maex

Hi Noxin337,

Your issues are for sure a headache.

I read your issue and I think I might be able to help.

For Internet speed check, go to:
www.speedtest.net

For Internet traffic problems, go to:
www.measurementlab.net

Before you reboot, don't reboot. Shutdown and Power Off.

I would at this stage remove the hdd and perform a clone or a Ghost Image. There are other imaging software to do this, but Ghost is best.
Considering you have powered the box down, give it a clean-up.

I would do this, as I have seen box's that were left out in the open with rain and wind, etc. And they came back to life.

If you leave your contact in your profile, I could contact you and give some more hands on help.

Best of Luck!!!

by leigh9

I use storagecraft for this, but there are many alternatives. In theory you can now recover to where you started from. It would be best to load that image on an alternate drive and see if it will come up before you play with the original. You don't say that it is a raid array and for simplicity's sake I hope it is not.
The people who set up the original are the people who best understand why they did it that way...maybe. Perhaps they did not know why they did it because they didn't know what they were doing? Is it possible to track them down and ask? If not you'll have to try to understand what it actually does. I have seen situations like this where the machine did nothing really, unfinished projects etc. From what you say it sounds like an incomplete implementation of some description. But what they were trying to do is anyones guess!
My best advice is that you take an image, and then play with that after hours. And that you document every step and talk to your boss before hand ( your call...some people are all "...if you can't handle it we'll have to get in someone who can" )but if you don't alter the original then the issue cannot be your fault. If you are able to fix the copy then you know you're ok. If you at least warn people about the issue first ..." It should be OK but..." you cover yourself.
Be patient, one step at a time, if you do multiple steps you'll find it hard to understand which broke what...
Good luck...sounds like some sleep deprivation to me :-)

by acorralado

Maybe, you will must to talk to your chief to suggest consulting from an IT professional. As an IT Pro, everybody thinks I can repair a mobile phone or a videoconsole. It's not my knowledge, and I always recommend a professional.
Regards.

This discussion is closed to new replies.