Plans for early summer, 1999 - before returning to school in early June:

I currently work for the Web Services division of the University of South Alabama. During the 1998-1999 school year, our department has been responsible for developing the webpages at USA as well as building and maintaining the Y2K database at http://www2.southalabama.edu. I first initially used the Microsoft Internet Information Server , which is bundled with Windows NT  / Back Office Suite , back in the summer of 1998 while working with Millar Company Inc's division -- Cullman.Com, which I am co-owner and webmaster of.  

The plan was to become more familiar with Windows NT so I could develop and expand on those skills. Unfortunately, the computer I was using to do the development work was needed elsewhere within the company, and my testing had to end.   I decided during Christmas, 1998, that I should set my personal computer up to test / install / configure  and attempt to run Windows NT.  I also left Windows 98 on the machine, so I could, in theory, "multi-boot" either operating system.

This worked well, except for the fact that I did not have much time for research during the semester, and when I did, Windows NT was not running very well on the multi-boot setup.  Eventually, after asking around and having some discussion in the fidonet conferences , I learned that my AMD processor and 64 megabytes of RAM were not really enough to successfully run windows NT.

On about April 23, 1999 - I outlined the plans for a new "network" , which should increase my knowledge and experience with networks, as well. I currently have access to several machines, which are undergoing major "role changes". Before outlining this new network, here were the configurations of the machine(s) I own:

Deep Space Nine BBS - Operates on a 486 DX 4 / 100 mhz machine with 8 megabytes of RAM. 

"JWIN98" - Operates on a AMD K/6 ? 300 mhz machine with 64 megabytes of RAM. It multiboots Windows 98 and Windows NT.

The plan was to create three machines:

a) my current machine, as a feasible workstation for operations (possibly converting to windows NT workstation, or windows 2000 beta) - will remain AMD / 300, 64 meg ram.

b) a "test" - workstation machine -- running windows 95 or windows 98. this machine would house latest installables, the Microsoft office suite, and additional software downloaded and installed (and uninstalled) from the internet. this will assist in trials of new software, and  prevents my current machine from having to be consistently reloaded. most likely the prior bbs machine, running 486 DX / 4 / 100 mhz, with 8 meg ram (possibly even upgraded to 16 or so, but not necessarily)

On May 3, I purchased a Pentium III / 333 mhz system which will become the NT server upon arrival. (128 SD Ram)

On May 6, just after finals ended, I began the reconstruction of "JWIN98" where it only ran Windows 98. [previously, I had to run all the drives with a fat 16 file system because that was all Windows NT would recognize]. It is now back to FAT32.

On May 13, I purchased a networking "kit", containing two network cards, a hub, and cat5 networking cable. These 2 network cards will be used in addition to my one existing 3com network card.

Between May 14 and May 21, I spent many hours attempting to get the equipment to work together. Very quickly, I learned my 100 mbit hub and network cards would not work with my 10 mbit 3-com ethernet card.  I returned the 100mbit equipment and purchased 10 mbit equipment (saving about $30 dollars).

After performing several tests and determining the NT's configuration was fine, I discovered my system, JWIN98, was putting the network card on a different IRQ than my PNP BIOS was assigning it.  A reinstall of Win95 fixed this (although this whole process was roughly 50-72 hours of testing theories before I discovered what this problem was).

On May 22, I successfully programmed the Windows NT DHCP server to assign IP addresses to any machine which was connected to the network.

On May 23, I successfully got MS PROXY SERVER 2.0 to provide internet access to the other machines. (the NT was dialing into my ISP at 28800 baud).

On May 24, I successfully tested three machines successfully over the internet / proxy configuration.  The Windows NT, my machine, and the family machine. All three worked.  There was only one minor glitch - on occasion, the web addresses I was attempting to contact would not resolve. (they would not contact the web server / mail server on the internet as they should --  they just reported that it did not exist or was not responding, without even checking).

I have most recently posted this minor problem in the fidonet windows nt conference, and am awaiting a response.

Conclusion / Goal:

The goal, eventually, is to reach this conclusion (for the server:)

a) provide a proxy server to server two other machines:

1) my own machine, which is the primary workstation for me. I do all my programming, web wok, et cetera from this computer.

2) the old bbs machine (we're downgrading the bbs to a 386) - which will be used as a test-bed machine for new software from the fidonet filebone as well as
the cnet shareware and download dispatch from cnet.

b) provide a web server (eventually, several web servers) for the local copy of the cullman.com domain (which i administer) and eventually want to add other domains....which I'll develop. I'm sure there is a way.....but i don't have a slightest where to start.

c) eventually install SQL server and some of the other components which come with Microsoft BackOffice. (owned by the company, and i am planning to test) - to allow for interactive databases, et cetera, similar to http://www2.southalabama.edu.

one of our previous employees developed that server based on the information i just gave you plus visual Interdev 6.0.

d) it'll be a file server, too

c) a windows NT server machine -- to test SQL server, database applications, et cetera, for future internet applications. (PENTIUM II - 300 or so running 128 meg ram)

Portions of this page were reproduced from various emails and communiqué messages written by Jay Fuller.