NT Server ?

I just started working for a 4-school public school district as a tech. At my previous job I was 99% desktop support, now I need to learn a LOT more about NT server since there is no network admin there, just a couple people who know some. I know about domain user manager and server manager from my other job, and I run a peer-to-peer at home (plan to set up server asap tho to practice), but I do not know anything about setting up and maintaining an NT server. I plan to take some classes or something but was wondering if any of you have any words of wisdom on things to look for that are common problems that may cause slow or interrupted service, or even maybe just some great tips. I would really appreciate any input. One problem they have is many of the pcs will say No Domain Controller Found when you try to log in and you have to cold reboot then you find it (they also "can't find" the network printers when pc is idle for awhile and have to cold boot to come back and be able to use them). Another problem is there are 1400 kids getting user names and have to set password, however we can't just blank out everyone cuz they have to have a parental permission form and we don't want everyone being able to login as someone else and we have to explain appropriate use, etc to them directly. We are taking like 20 kids at a time, which is taking way to long...any brainstorms on that, anyone seen a miracle way to do it much better?
The workstations are all running win95\98.

what did I get myself into now.....=)
TIA



[This message has been edited by JeanneD (edited October 01, 1999).]

I always tell people this because I know that it works. Look up your local computer society (or whatever they call it there), and JOIN. There will probably be several members who will be happy to mentor you while you are getting your feet on the ground. Most of these organizations have members who have worked, or are working with large networks in numeruos settings. These folks are the possessors of priceless knowledge and experience, and most are eager to help. Try it. You'll like it!!

------------------
Are we havin' fun yet?

[This message has been edited by Grafman (edited October 03, 1999).]

Thanx, good idea..I will check it out.....

If you have a lot of users to set up that have the same resource needs, use a template that will set all users up with the same parameters (Groups/logon hours/account info, etc...)then assign the Group share and permission rights.

Hope this helps.

As an add-on, make sure you set the "User must change password on next logon" check box. This will force the users to assign themselves a password to logon. If they forget it, you can go in and change it to something easy (like "user")and make sure that the password box is checked.

As for the "No Domain Server" message, check to see if you are using DHCP or are you assining IP addresses to the client PC's?

Check to make sure that the IP address lease is not expiring if you are manually assigning IP addresses. If you have te server assigning ip addresses, you may want to take a look at the cabling (is it CAT5?) or the HUBs.

Good Luck!

Jeanne; I have found that the browser service
can be one of the most troublesome parts of NT Server administration. If you aren't familiar with it, I would recommend it as a good place to start. In the meantime, make sure that "Browse Master" is disabled in the "File and Print Sharing for MS Networks" advanced properties sheet. Maybe it's Bill Gates' idea of humor, but I have come across a number of Win98 machines that think they're hot stuff and force an election for master browser when they come on to the network. On a network as big as yours is, that's a lot of traffic. Enough, in fact, to hinder workstations from accessing the Master Browser Database at login time. Hence the message "No Domain Controller". Also, make sure you aren't running any more protocols than you have to. That'll really slow things down. Good luck with the job!

louie