Simple LAN setup with Windows Server 2003

[blackguyza]

I am a novice network administrator and would like to quickly set-up an administration network at school to allow unlimited number of network computers or users to use the school's database (SAMS) simultaneously. I have the problem of both viruses and limited network users on the workgroup.

I have tried to add our new Windows 2003 machine to our existing LAN workgroup after adding file controller role on the server but I failed. I also tried to create a domain and hoped to add computers or users ton the domain but also failed. I have no experience with any server, I just have an idea of a workgoup computers on a simple LAN. Our user pc's are running windows xp.

Please help.

EDIT:
I am hoping to set-up Symantec System Centre to fight off virus thread.

 

[iblade]

The most effective way with the most amount of overhead in the begining is a domain, admin thereafter is a breeze.

A workgroup will give you both a high overhead in the beginign as well as a high overhead with administration.

Seeing that you are not too fussed with licencing, or have the CALs for everyone to connect to the Win2K3 box, why not go for Forefront as your AV and update it via WSUS, thereby giving you Windows updates as well as AV updates in one go.

Maybe look at SteadyState for the workstations if you don't want a domain, it will only save system changes with an admin password any other changes are tossed if you reboot the machine.

If you need help with any of this, just yell.

 

[R4tt3xx]

The first problem you are going to have is integration. A domain controller requires DNS (Domain Name Service) to be setup. I am assuming that all PCs are Internet enabled and connect through a router.

Seeing as you are a novice, I would suggest not playing with things that you do not understand yet, you are in a working enviroment, sure your network may have issues that you are trying to resolve, but you just may make it worse.

Set up a lab, ie one switch, the server and a Desktop PC. Separate this LAN from your existing one, under no circumstances connect the lab server onto the proper network, not until you are ready and understand what you are trying to do, how to do it. To create a lab domain is quite easy, install the DNS and DHCP roles, next run "DCPROMO" from the command prompt, that will setup the domain controller. You should then be able to connect any client PC to the lab network. Make sure to "assign the IPs automatically"

As for your "SAMS" issue, I am assuming that it's a simple file share on an XP client PC. Windows XP is limited to 10 concurrent share connections, ie only 10 PCs can connect to that network resource. Depending on how that resource is structured it may be better to create an intranet of sorts using databases to store data instead of raw files. I don't know if this is possible. It obviously depends on the setup of your system.

Running Server 2003 is going to be expensive, each PC that connects to the server needs to have a "CAL" (Client Access License) in order for it to be legal. Server 2003 comes with 5 CALs

With regards to the SAMS system, can you post or PVT more data on it ?

Hope this helps.

Be Carefull

 

[blackguyza]

I have also considered a domain as the effective option and at some stage I had configured the domain named "myschool.local" which was a NetBios. I then created one username and a password and tried to add the first user's pc to my domain and received an error message which indicated that if my domain is a NetBios then I need to include WIN...something.

 

[blackguyza]

The first problem you are going to have is integration. A domain controller requires DNS (Domain Name Service) to be setup. I am assuming that all PCs are Internet enabled and connect through a router.

I do have issues with licence and trying to update/upgrade windows xp on the Internet is not an option.

As for your "SAMS" issue, I am assuming that it's a simple file share on an XP client PC. Windows XP is limited to 10 concurrent share connections, ie only 10 PCs can connect to that network resource. Depending on how that resource is structured it may be better to create an intranet of sorts using databases to store data instead of raw files. I don't know if this is possible. It obviously depends on the setup of your system.

Running Server 2003 is going to be expensive, each PC that connects to the server needs to have a "CAL" (Client Access License) in order for it to be legal. Server 2003 comes with 5 CALs

With regards to the SAMS system, can you post or PVT more data on it ?

Hope this helps.

Be Carefull

What do you mean post or PVT more data on SAMS?

I am trying to avoid the same issue of only 10 concurrent connections because there are about 43 educators at my school who interestingly finish their marking at the same time and just in time.

My main concerns presently are number of concurrent connections and viruses.

 

[blackguyza]

We currently have two computer centres which are both running windows server 2003 and clients running windows xp. We used to physical export the database file to either network to enable more users to connected concurrently and it had worked with ease. I was to enable the same thing with the admin network because it is very inconvenient for the admin staff to work with admin issues when the database file is taken to the computer centres.

 

[Asha'man X]

This program SAMS is something our school is being introduced to, but at the same time the education department is trying to convert it to something network/internet enabled, called ISAMS. Right now it is a mess.

I would suggest holding off on domains until next year, a project like that takes a lot of time to get going. As for Symantec, depending on version, it may not help that much to contain viruses, not to mention slowing your computers down.

 

[blackguyza]

This program SAMS is something our school is being introduced to, but at the same time the education department is trying to convert it to something network/internet enabled, called ISAMS. Right now it is a mess.

I would suggest holding off on domains until next year, a project like that takes a lot of time to get going. As for Symantec, depending on version, it may not help that much to contain viruses, not to mention slowing your computers down.

We have long started using SAMS, we have used it to issue reports since the first term. What do you suggest we use for anti-virus?

EDIT:
We had to settle for 10 concurrent connections and all educators should finish to enter their marks this morning. I am now going to start to create a domain for next year and need your assistance. I have also applied to register for a one year course in computer networks with UNISA.

I want to find out that if I setup a domain as well as email server role, and if our server has access to the internet, what will I need to make my users Intranet addresses to be used on the Internet?

 

[blackguyza]

I have failed to setup a domain for the network because DNS capability is not already installed and my principal wouldn't buy the R355 licenced copy made special for government schools.

I am now going to setup only file and printer roles.

 

[Asha'man X]

I have failed to setup a domain for the network because DNS capability is not already installed and my principal wouldn't buy the R355 licenced copy made special for government schools.

I am now going to setup only file and printer roles.

Windows Server 2003 doesn't restrict you from setting up a domain, even if the software is not fully legal. Setting DNS up is quite simple, and once it is up, you can try to set up a domain again. In fact, when running the Active Directory setup wizard, if the wizard can't detect good DNS settings, it will offer to set up a DNS server for you. I've used this in the past, and I've found it to work perfectly.

Concerning anti-virus, ESET NOD32 is my first choice. Light on system resources, and handles all hte nasties the kids in my school have been throwing at it. Unfortunately, it is not free like the Symantec software that they have been giving away, and if your principal refused to spend R355 to buy the Windows Server disk, he won't authorise the money for NOD32. They give a 50% discount to schools, but it will still cost a packet depending on how many machines in the school.

Windows Server 2003 has the ability to serve as a very basic email server, though I have never made use of this, as I usually use Microsoft Exchange. A possibility would be to use the free program hMailServer, which works pretty well, has POP3 and IMAP access, but no webmail interface, which may be a problem, especially as people are likely to be jumping from one computer to the next. Email servers for Windows with a webmail interface exist, but cost a pretty packet.

Hope this helps a little bit, shout when you need more help.

 

[blackguyza]

Windows Server 2003 doesn't restrict you from setting up a domain, even if the software is not fully legal.

I was implying that the server required a windows 2003 standard disk when It was trying to setup DNS, and the person who installed the OS from the education district office did not include the DNS I suppose. I there anywhere I can download the windows 2003 DNS cabinet?

 

[Conradl]

Tell your boss to buy the software. The academic license costs around 10% of the regular OVL - there is no reason not to buy it. I have a customer who pays around R145 for MS Office 2007 Pro+

 

[blackguyza]

Tell your boss to buy the software. The academic license costs around 10% of the regular OVL - there is no reason not to buy it. I have a customer who pays around R145 for MS Office 2007 Pro+

Will do. Will the windows 2003 server cd solve my particular problem? I couldn't add any PC to the domain that I had created.

 

[blackguyza]

If I register a free .school.za domain with http://www.esn.org.za/ (e-Schools' Network) will I be able to setup my sever to be able to use the registered domain name and receive emails and host a website directly on my server. If possible, what kind of bandwidth will I at least need for emails only?

 

[Asha'man X]

Will do. Will the windows 2003 server cd solve my particular problem? I couldn't add any PC to the domain that I had created.

If I read the problem correctly according to what you posted above, then yes, the CD will help as you will be able to install the DNS role needed for Active Directory. You can't get the files needed for that off the internet per se, you need the Server CD.

If I register a free .school.za domain with http://www.esn.org.za/ (e-Schools' Network) will I be able to setup my sever to be able to use the registered domain name and receive emails and host a website directly on my server. If possible, what kind of bandwidth will I at least need for emails only?

We are also with eSchool's Network. They host our website for us, which is a relief really, as they have much more bandwidth than we have. You can use your server to host e-mail, but you will need either a static IP or a dynamic dns entry so that mail can come in via SMTP. The other alternative is to let ESN spool the mail for you, and you download it via a POP3 and push it into your server.

Hope this helps

 

[blackguyza]

I managed to install the DNS using the cd but could figure it properly. I configured the static IP address as 192.168.0.1 in the advanced TCP/IP properties. I created the forward lookup zone as admin.myschool.local. I also added the IP address in both DNS and WINS tabs in network connections properties and selected the default option at the bottom.

I then tried to do nslookup but it returned server unknown with the same IP address.

 

[blackguyza]

I am now getting the error messge "the network path was not found" when trying to add a windows xp to the domain.