Written by Richard Lowe

At my day job, we were tasked with creating a Windows NT 4.0 network from scratch with only minimal training onrepparttar operating system. We were experts at working with OpenVMS and MacIntosh systems, but none of us had ever seen Windows NT before. In those days long ago we were very cocky, and very naive - how hard could it be to set up a new TCP/IP network? After all, we had mastered DECnet and Appletalk, could IP be any harder?

We soon learnedrepparttar 107885 error of our ways - TCP/IP is far more complex than we had originally believed. However, after some head scratching and a few phone calls, we managed to get our network up and running.

We didn't know any better, so we simply hard codedrepparttar 107886 TCP/IP address into each workstation and server. In fact, we hard coded everything, includingrepparttar 107887 DNS and WINS server addresses,repparttar 107888 subnet andrepparttar 107889 gateway address.

For our purposes, this worked great for several years. We added machines slowly and planned everything far in advance, so it was no big deal to just add a new machine torepparttar 107890 network. A few simple edits torepparttar 107891 network control panel was all that was needed, and since our network was very static, we didn't have to visit those setting very often at all.

As our company grew this scheme started to get more and more awkward. Originally we had a nice, isolated, self-contained network, but now we needed to get onrepparttar 107892 internet, we were adding not only new workstations and servers at a furious rate, but we had to deal with PDAs, handheld systems, standalone file servers and hundreds of other computers.

To make matters even worse, where our network was very static, now it was becoming dynamic. Computers would be added and removed constantly - someone would plug his handheld into an ethernet jack, get their email, unplug and be gone.

The static TCP/IP scheme that we had been using (a spreadsheet with a list of machines and related addresses) was simply no longer working. Fortunately, there was an answer - DHCP.

The acronym DHCP stands for "Dynamic Host Configuration Protocol", and it means exactly what it says. Once we discovered this new tool we realized we had foundrepparttar 107893 solution to our problem - and we kicked ourselves mentally for not reading up on this wonderful tool long before.


Written by Richard Lowe

If you've ever managed or had to deal with more than one computer system, then you've undoubtedly wanted to be able to control one remotely at one time or another. In my job, my staff and I manage about a thousand computer systems (servers and workstations). Our staff is small and busy, and even takingrepparttar time to walk over to a local system can sometimes be a hassle. There is so much to do and no time to do it in.

On top of that, our systems are spread all overrepparttar 107884 country, in a dozen states onrepparttar 107885 east and west coast. There is no possible way we could manage those computers effectively without some kind of help. And if you've ever attempted to talk a user through an operating system installation or a debug session, then you will understand that this just does not work in a corporate environment.

Fortunately, we found one ofrepparttar 107886 most useful products available anywhere at any cost. This little gem is called PcAnywhere, and it is sold by Symantec (the vendor most famous for it's antivirus software).

PcAnywhere allows my staff to "take over" a system, just as if they were sitting atrepparttar 107887 keyboard and staring atrepparttar 107888 monitor. Since PcAnywhere does depend uponrepparttar 107889 operating system, it cannot be used to controlrepparttar 107890 system boot and console, but it can do just about anything else imaginable.

Thus, if a user has an error displayed on his screen, we can connect and see exactly what it says (and often whatrepparttar 107891 user did). This saves countless hours of attempting to piece together what happened based upon a frazzled user's spotty notes ofrepparttar 107892 occurrence, or of running over torepparttar 107893 users machine to see it for ourselves before he did something else.

Cont'd on page 2 ==>
ImproveHomeLife.com © 2005
Terms of Use