• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

setting up Windows 2000 Server

M

MrHappyMonkey

Diamond Member
I will be configuring a brand new Dell server with Windows 2000 server in a week or so. I have never set this O/S up before. Is the process simular to loading Windows XP or Windows 2000 Pro? Any tips for doing this? This will be used as a file server primarily. Also, does Win2k server have any built-in FAX software for batch faxing?

EDIT: This is for my father's office. We are doing a full upgrade on all 8 of the computers in the office. We currently do not have a server in place. The office currently as a mismatch of Windows 95,98, and ME computers running. We are going to install Windows XP Pro on all of the desktops except for one machine that is running Windows 95 that simply will not run Windows XP. We will be adding in a brand new Dell PowerEdge 1400SC running Windows 2000 Server. The server's main task is to run our Business system, BusinessVision, and serve as a Fax Server for batch faxing. In addition, it will serve as a router and firewall. I know essentialy next to nothing about Windows 2000 server with regards to Active Directory and using a Domain for the network. I have been reading the step-by-step guides from Microsoft's site trying to get an understanding. Since this is a relitivly small network, would you think Acive Directory services would be benificial in this setup? How would I go about configuring the server as a router? Would it be simpler to use a simple Linksys Cable/DSL (the office has aDSL for it's NET connection) instead of using the server as the router?
 
No built in faxing software. The setup is exactly the same as 2000 pro, until you get to the desktop. Configure your server time. After that you are on your own. What you do from there depends on your current domain setup (is this for work?) and what you want to do with it. If its for work, do you have any NT 4.0 servers on the network already? If you would like any more information, we need more.

If you want to do batch faxing I would seriously suggest WinFax 10. You don't need v10 Pro, unless you decide to receive voicecalls with it also. Once you get WinFax setup (you can set it up to take faxes from network clients and have it hold them until, say 10 PM, then fax them one by one, batch) faxing is pretty easy. $70 bucks is worth it to me. EDIT: Check that. $39 bucks here.
 
This is for my father's office. We are doing a full upgrade on all 8 of the computers in the office. We currently do not have a server in place. The office currently as a mismatch of Windows 95,98, and ME computers running. We are going to install Windows XP Pro on all of the desktops except for one machine that is running Windows 95 that simply will not run Windows XP. We will be adding in a brand new Dell PowerEdge 1400SC running Windows 2000 Server. The server's main task is to run our Business system, BusinessVision, and serve as a Fax Server for batch faxing. In addition, it will serve as a router and firewall. I know essentialy next to nothing about Windows 2000 server with regards to Active Directory and using a Domain for the network. I have been reading the step-by-step guides from Microsoft's site trying to get an understanding. Since this is a relitivly small network, would you think Acive Directory services would be benificial in this setup? How would I go about configuring the server as a router? Would it be simpler to use a simple Linksys Cable/DSL (the office has aDSL for it's NET connection) instead of using the server as the router? A
 
ya, decide if you want a win2k Domain, or a Workgroup, and yes do you have any NT4 servers .. and/or do you have any 9x/NT clients .. decide if you want to implement group policy security.. like igiveup said, we need more info ..
-neural
 
The server's main task is to run our Business system, BusinessVision, and serve as a Fax Server for batch faxing. In addition, it will serve as a router and firewall.

That's a terrible idea. The firewall should be a completely different box from your internal servers, and if I had any say it wouldn't be running any form of Windows either.

Since this is a relitivly small network, would you think Acive Directory services would be benificial in this setup?

Doubt it, if anything it'll just over complicate things.
 


<< The server's main task is to run our Business system, BusinessVision, and serve as a Fax Server for batch faxing. In addition, it will serve as a router and firewall.

That's a terrible idea. The firewall should be a completely different box from your internal servers, and if I had any say it wouldn't be running any form of Windows either. >>



I missed that when I first read through the thread. Definitely dont use that as your firewall. Its got enough stuff on there already. You dont want your firewall to be cracked and the script kiddiot to realize thats where you keep all the cool stuff. A linksys or a cisco would be a much better solution for a firewall. Linux or OpenBSD if you have the knowledge.
 
As mentioned before you do need a separate box as your firewall.



<< and if I had any say it wouldn't be running any form of Windows either. >>


However I disagree with this. My choice would be W2K Server running ISA Server for the firewall box, but to each his own. All can be made secure with the knowledge.

If going through the trouble of setting up W2K Server I would definately use AD. Otherwise why not use a peer to peer LAN??? If you're going to use W2K server use it the way it was intended, not crippled. The most important thing to take care of in a W2K domain is DNS. Without it running properly you'll have nothing but headaches.

Using a domain will also allow you to establish group policies, and permissions for all the computers in the domain. Do not discount the importance of locking down boxes to avoid headaches later on, especially among those who don't know what they're doing half the time. A well locked box can still provide a useful desktop and prevent the user from borking up the box and any crutial data. It doesn't matter if it's for your father or not. Preventing problems extends to all desktops in the domain.
 
This project is on a budget, so I don't think I can provission a completly new computer to act as a firewall. Are there any decent hardware firewalls availble in the sub $300 range? Also, how exactly does the DNS configuration work when configuring the domain? The server will not be seen on the internet, only used for internal use. How would I configure the Domain/DNS configs? Also, I asume that the Windows 95 machine won't be able to connect to the domain. Do you think NT 4.0 would run decently on this 133MHz machine? It will be used out in the warehouse in receiving new packages via a bar code scanner.

Thanx for all the help so far 😀
 


<< This project is on a budget, so I don't think I can provission a completly new computer to act as a firewall. Are there any decent hardware firewalls availble in the sub $300 range? >>


You can get you an SMC Barricade or something of that sort for less than $100. However, I would rethink where you're going to cut corners in a business environment, especially if you're keeping customer data on hand. If someone steals that data that extra money you should have spent on security will look like chicken feed compared to attorney's fees when you are being sued after the data has been stolen. If your customers know about the "budget security" you're likely to lose some of them from the beginning as well. I know I would look elsewhere.



<< Also, how exactly does the DNS configuration work when configuring the domain? The server will not be seen on the internet, only used for internal use. How would I configure the Domain/DNS configs? >>


DNS is the backbone of AD. Just like a DNS server on the internet it will keep track of certain locations and their IP address(your LAN) and forward those it doesn't know to an another DNS, in your case probably one provided by your ISP. Without it running properly AD will fail. I suggest you research DNS and AD before you start, it's much too broad of an issue to discuss here.

The following sites may help you get your feet wet, but I suggest going to the bookstore as well.
HOW TO: Configure DNS for Internet Access (Q300202)
Windows 2000 Step-by-Step Guides



<< Also, I asume that the Windows 95 machine won't be able to connect to the domain. >>


It can connect to the domain, and use items within the domain. However it cannot be a member of a domain. There's a difference, and you should learn it. 😉



<< Do you think NT 4.0 would run decently on this 133MHz machine? It will be used out in the warehouse in receiving new packages via a bar code scanner. >>


I think you should upgrade. It sounds to me with wanting to use 133mhz computers and skimp on security that you are trying to cut too many corners. Later on you'll wish you had done this upgrade correctly. If you can't do it right, don't do it.

Just my .02
 
go buy an old P200 machine for $50 and load openbsd on it. use pf or ipfw for your firewall software, you should be fine. ISA server is far too costly for the small-biz solution you're looking for. also, Checkpoint has a new small business firewall that is meant to compete with NetScreen-type devices; it is $695 and runs FW-1, pretty nifty.
 



<<
I think you should upgrade. It sounds to me with wanting to use 133mhz computers and skimp on security that you are trying to cut too many corners. Later on you'll wish you had done this upgrade correctly. If you can't do it right, don't do it. >>




This is the only "slow" computer that we have in the office. This was one of the original computers that the office ever had! The task of this machine will not be anything extravegant at all, only a barcode scanning station for receiving in new inventory. I don't see using this slow computer out in the warehouse as "cutting cornners", simply using the equipment that we have on hand.

BTW: We are upgrading all of the workstations in the office to Dell 1.4GHz to slow down the process of stuff being outdated.

What would you consider an acceptbale non "cutting corners" firewall to use for this scanerio?

Thanx for the above tips.
 


<< What would you consider an acceptbale non "cutting corners" firewall to use for this scanerio? >>


sml's solution will work fine. I'm also sure n0c would approve. 😉 I myself use ISA server but that would be more than your budget allows it seems. If you still want to stay on the Windows side of things there are alternatives there as well. Tiny Software offers some good products as well. The important thing is to have a separte computer acting as the firewall.



<< This is the only "slow" computer that we have in the office. This was one of the original computers that the office ever had! The task of this machine will not be anything extravegant at all, only a barcode scanning station for receiving in new inventory. I don't see using this slow computer out in the warehouse as "cutting cornners", simply using the equipment that we have on hand. >>


I think of 133mhz as being barely adaquate, but it's going to depend on the RAM and the software. Your software should have minimum requirements. Try it and upgrade if you don't find the computer satisfactory. That computer is probably about 5 years old or so right??? I personally don't put something that old in an warehoue environment. The extra dust, climate changes, employees that tends to be a little more abusive than office workers, and age are not a good combination IMO. But that's just me, do what you want.



<< BTW: We are upgrading all of the workstations in the office to Dell 1.4GHz to slow down the process of stuff being outdated. >>


Sounds good. The rule of thumb I use is 3 years for office computers. If they are fast enough to last longer, great and in some cases I'll leave it there. However the majority of the time I replace every 3 years, because the productivity and TCO make it worthwhile.
 


<< I think of 133mhz as being barely adaquate, but it's going to depend on the RAM and the software. Your software should have minimum requirements. Try it and upgrade if you don't find the computer satisfactory. That computer is probably about 5 years old or so right??? I personally don't put something that old in an warehoue environment. The extra dust, climate changes, employees that tends to be a little more abusive than office workers, and age are not a good combination IMO. But that's just me, do what you want. >>



hmm... well from taking a look at the new business system requirements, it looks like to should run OK on a 133. I have no idea how much ram is in the machine, I think it is somewhere around 32 meg. I will look around the FS forum and see if I can find anybody who has some EDO ram for cheap.

Thanks for your help so far, Psychoholic.
 
1.) Get a seperate firewall device, as suggested. Netgear, Linksys, SMC, etc. all firewall solutions for usually under $100.

2.) Plug the DSL/Cable modem into this firewall.

3.) If you have more than four workstations, get a 5+ port 10/100 switch and plug it into one of the firewall/router LAN ports.

4.) Setup all the workstations and the server with private IP's -- 192.168.0.1, 192.168.0.2, etc.

5.) Read about AD and DNS.

6.) Patchup the Win2K server and all the workstations. (MS TechNet and click on the Security Link)

7.) Figure out the fax software.

8.) Grab a 24 pack of beer and take a break.

Good luck mon!

Let us know how you set it up...
 


<< I have no idea how much ram is in the machine, I think it is somewhere around 32 meg. >>


You should be able to find that out when it boots up or in the BIOS. It may also be marked on the memory itself. I would shoot for at least 64 MB.
 


<< sml's solution will work fine. I'm also sure n0c would approve. 😉 >>



Ill take IPF over both ipfw and pf. As far as MS ISA server goes, it looks ok for an MS product. Ive only heard one bad thing about it, but how many admins look at thier logs? 😛
 


<<

<< but how many admins look at thier logs? >>


Well, you can't blame MS for that...however they could add a Log Wizard....😛 >>



I wasnt blaming MS for tht, from what I hear thier reporting sucks for ISA. Other than that it chugs along. I was offered a (legal) copy, but I couldnt keep Win2k from crashing on me so I didnt take it 😛
 
setting up DNS is in win2k for AD isnt special, its not something you have to read for days about, you dont even have to manually set it up .. just when you do the "configure your server" set up active directory first, it will set up your server as a DNS server as well, all you really do is specify the domain name, you can make it something like "mydomain.local", then on ur clients, or if you have dhcp running on the server, just make the clients see ur new server as the primary dns .. its really simpler than it sounds .. good luck ..
-neural
 


<< I wasnt blaming MS for tht, from what I hear thier reporting sucks for ISA. >>


That's why you log to a database. 😉
My guess is there will be substantial changes to the default logs in the next version.



<< I was offered a (legal) copy, but I couldnt keep Win2k from crashing on me so I didnt take it. >>


MS added that to the code....

If Run_By_n0c="yes" then crash

😀


 


<< setting up DNS is in win2k for AD isnt special, its not something you have to read for days about, you dont even have to manually set it up .. just when you do the "configure your server" set up active directory first, it will set up your server as a DNS server as well, all you really do is specify the domain name, you can make it something like "mydomain.local", then on ur clients, or if you have dhcp running on the server, just make the clients see ur new server as the primary dns .. its really simpler than it sounds .. good luck .. >>


Setting up DNS is simple. However if something goes wrong or you have to trobleshoot you need to understand it. This is why I stress the importance of actually understanding it, instead of relying on the "wizards" to take care of it. If there's a problem with DNS, everything dealing with AD has the potential of causing problems.

Just because you can use the wizard doesn't mean you actually know what's going on, and that can often be a problem in itself.
 
There are several services that are installed by default during a win2k server installation. Unless you are planning on using IIS, you will want to disable it in services. You will probably also want to disable the netmeeting desktop control service (thats not the exact name, but very close). I don't know what the h3ll MS was thinking putting this on a server with a manual startup. Anyway, go through the services and disable anything that you won't be using. You might want to look at your local security policies too. You can control lots of things including password length and complexity and who can log onto the server locally.
 


<<

<< I wasnt blaming MS for tht, from what I hear thier reporting sucks for ISA. >>


That's why you log to a database. 😉
My guess is there will be substantial changes to the default logs in the next version. >>



Im sure they will improve it. I never doubted that. Im sure someone is getting on their case if it sucks as bad as I hear 😉



<<

<< I was offered a (legal) copy, but I couldnt keep Win2k from crashing on me so I didnt take it. >>


MS added that to the code....

If Run_By_n0c="yes" then crash

😀 >>



This time it was idiot operator and crappy hardware 😉
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top