View Full Version : Networking
On a network, to have clients login to one main server rather than setting up numerous user accounts using compmgmt.msc would you use telnet? To add/remove/change accounts on that one server instead of going to every client. How would I go about doing this? I've googled it, with no luck.
Your question is not cleear enough to me, and probably to other members.
You may get more response if you write exact, detailed, precise information
about what you want, and/or what is your problem.
alright. basically, if i wanted to add a new user, allowing them access to any computer on my lan i would have to goto each and every terminal and add them using the computer management tool. Now, to instead setup one pc that all other terminals connected to and verify if that user has access. this way that one "server" is the only one needing configurations if i needed to remove/add users...or anything of the sort. did that help the least?
YvetteKuhns
7-26-04, 08:40 PM
I set up our LAN with each computer terminal separately, so I don't have to worry about which terminals are on or off. But we don't have very many connected at one time. If you have alot of computers and one main computer for administration for a major company, you would prefer a server computer configuration.
How many computers are on the LAN? What OS is each using? So many things to consider.
Well, it doesn't seem something I know well, sorry.
If you are serious about getting any suggestion,
tell at least what is the OS, Lan configuration, and so on.
Other members may be able to help you.
.
::edit
Oh, Yvette is here. :)
I'm out.
IF you're using Windows boxen, you need to create a domain. In order to create a domain, you need to have at least one service class O/S installed (NT4 server, 2000 server/advanced server/etc, or Win2003 server). Assuming you have one of these, you can then create a DNS server, then a primary domain controller. Once you have a PDC created, you can join your other computers to that domain. Once all this has been accomplished, when you log in you need to have the domain selected, and then all login requests are forwarded to the PDC, which validates logins against its user list.
Basically, it's not as easy as you might think. If you're interested in pursuing this, I can post more detailed instructions.
i am interested. i will be switching a system from XP Pro to probably Windows Server 2003 to accomplish this. In total, i will have 5 terminals connected. The only issue i see so far is the ammount of RAM recommended by microsoft....i have a total of 512 on this system i plan on using, which takes up both slots. Would you recommend i increase this? The same system will be running the apace web server, along with a mail and ftp.......and all the related tools like PHP.
What kind of hits are you looking at getting on this box? If it's just internal stuff for your internal network, that should be fine. I'm actually running Win2003 server on my server box with only 256MB of RAM. It's not running a web server (only application server) but it seems to run ok.
Anyway... actually, once you install win2k3, you should get a screen when you log in asking what roles you want the server to fulfill. You can choose 'domain controller' (or something along those lines) and it'll tell you what you need to do. That's the only reason I know, because I followed its directions.
Once you actually create the domain controller and set up the users on the win2k3 box, you have to join your other machines to that domain. That's the easy part, though. Creating the actual domain controller is significantly more difficult.
Anyway, lemme know if you have any questions. My suggestion would be to get started and stumble through it as much as possible. If you have questions or run into problems, feel free to post.
right, and to change the other terminals that will be connecting to the server switch them over to domain from workgroup? on another note, how likely is it that i can remove a 256 ddr mb ram chip from the server-to-be and place it within a labtop that i will be getting, to free up that slot and enter a 512 maybe? I also look forward to installing linux on the said labtop....would that network well to the windows 2003 server?
right, and to change the other terminals that will be connecting to the server switch them over to domain from workgroup? on another note, how likely is it that i can remove a 256 ddr mb ram chip from the server-to-be and place it within a labtop that i will be getting, to free up that slot and enter a 512 maybe? I also look forward to installing linux on the said labtop....would that network well to the windows 2003 server?Some motherboards don't like mixing sizes of memory so it's a case of try-it and see. It may work, or may not. Similarly, the laptop may require a different speed/type of memory to that in the desktop. Again, try-it and see. (You can do that before you purchase the extra memory.)
about the memory...
yea, I thought laptops and pcs used different types of memory. I could be wrong, no real experience there. You'll have to see, I guess.
As far as joining a Linux box to a domain. No. Can't do it. SAMBA is the software used for stuff like that, and last I checked it could only handle workgroups, not domains at all, much less 2003 domains.
hmmm..did some snooping, I may be wrong. If you want to read about it, check this link.
http://us1.samba.org/samba/docs/man/Samba-Guide/
It doesn't mention win2003 domains, but it does have active directory (windows 2000). Maybe some googling will give you a fair answer.
I would recommend getting the Windows domain set up first, then worrying about Linux later. Linux is, virtually by definition, a pain in the...err...rear.
well, couldnt i always just have that laptop by its self in its own workgroup...and it will be the only system that will not connect to the server to login. Im not sure, can you run a workgroup and a domain at once on the windows 2003 server?
well, couldnt i always just have that laptop by its self in its own workgroup...and it will be the only system that will not connect to the server to login. Im not sure, can you run a workgroup and a domain at once on the windows 2003 server?Why not put the laptop on the doman? (Or is it running Linux?).
yea, the laptop would be running Linux.
If you don't want it to have to authenticate onto the domain, then don't worry about it. The only reason you'd want to join it to the domain would be to be able to authenticate to it and get trust. If that doesn't matter, then there's no reason to do the domain thing.
alright, i've got my hands on a copy of microsoft windows server 2000, will do an install and let you know the outcome or if have any more questions. thanks, again.
i've installed it and am now trying to configure the server using the wizard, however i must be entering the wrong infomation as it is failing and reports errors. could you please explain step-by-step this process. meanwhile i have to find the drives for my nic card, monitor and modem....the recovery cd does not have the option to install them anymore, it must notice that i am not running XP anymore. thank you. when it is asking for a DNS is it wanting my domain name www.mydomain.com or the servers DNS that hosts that domain name like DNS1.SOMETHING.HERE? im thinking because the wizard cannot connect to the internet as i havent installed the drivers for the card, it might be causing some errors as well.
Hi,
Linux is, virtually by definition, a pain in the...err...rear.
Interesting statement.... I disagree. Ok now I won't start :p
Anyways, bubbac , I'd recommend checking out the forums at http://www.linuxquestions.org/ for answers to any and all Linux questions. It is truly a great resource! :D
i've got the server working, and the other terminals now connect to it....but, its very slow. i sat there for probably 5 mins waiting for it to log me in.
on Linux ... don't get me wrong, I like Linux. It's very powerful (and free) and it's unbelievably stable and fairly quick. However, it's not very intuitive (IMO) or very user friendly. I've used Linux enough I don't think I'd be considered a newbie anymore. I've even taken classes. But it can be a royal pain to work with. For instance, about 50% of the time it doesn't seem like X works right off the initial installation. Ever install custom video drivers for X windows? omg, the pain. anyway...heh..we may disagree. :P
err, Bubba...
I've only installed a domain controller on a win2003 box, so I can't really vouch for 2000. However, they should be pretty similar. It basically consisted of a few parts.
1. Create a DNS server. This requires you point it to another DNS server as authoritative (if I'm not mistaken) and I pulled this off another box by looking upt he DNS server in ipconfig (ipconfig /all). I plugged these in and that was basically it for DNS. When it asked for a domain name, it's really asking for your what you want to call your domain, kinda like a workgroup name. (unless I'm on crack). So you make up something. At least, I did, and it worked.
2. Set up the actual domain controller. Once you have the DNS server set up properly, you set up the domain controller. Since you only have one, it's primary and you don't have to worry about setting up backups.
3. Join other computers to the domain. You'll need a domain administrator to do this (create the account on the PDC). Go into your PCs and, for NT-based machines like 2k and XP, right-click on my computer, go to properties, go ot network identification, then either do the wizard or properties.
4. Once the computer is joined to the domain, create a username on the server under domain users or whatever, and you should be able to authenticate across the network.
5. Do NOT have a user set up both locally on the PC and on the PDC. It makes troubleshooting alot more difficult. Trust me. :)
6. Assuming you made your domain controller PDC, requests should be forwarded to the PDC, processsed and granted. Login times were very short on my network. I'm running at 100mb and my PDC was an XP 1800+ with 128MB RAM and win2k3. The RAM is below minimum required levels, but even so requests were granted in a second or three.
hope that was of some help. If you're still running into problems, I may try setting up a 2k domain controller locally.
how would i go about setting it up as the primary domain controller...that might be it, loging in takes probably over a min...or sure seems like it.
if I'm not mistaken, even if you set it up as BDC, it should detect that the PDC (which doesn't exist) is not responding and promote itself to PDC, if my understanding of how that works is accurate.
I hate to say this, but if you continue having issues you may want to go to a more authoritative source for this stuff, like a Windows sysadmin board or something. I only dabble and am most definetely not an expert.
It has seem to gotten quicker with more and more logins....perhaps the first few times it was so long as it was gathering information, now it just needs to see if it's changed? O' well, they can wait if they've really got to use it. Thanks.
vBulletin v3.6.0, Copyright ©2000-2009, Jelsoft Enterprises Ltd.