Skip to comments.Trying to set up a home network
Posted on 09/06/2005 5:52:41 PM PDT by Tennessee_Bob
Ok, let me get a couple critical things out of the way first.
Yes, I am logged in.
Never met a moose.
I don't have a sister.
I do like cheese.
I am not running CP/M.
I have Googled this.
I'm pretty sure it's Bush's fault.
I hope I got everything out of the way, but I'm sure if I didn't, it will be pointed out in a bold, 24 point font.
Yesterday, I had two machines, one running XP Home, one running Win2k. After fixing a friend of mine's computer (why is it that the only time women ever call me is when they need help with their computers? Oh, sure, they act all interested for thirty minutes or so, but then, invariably, the conversation goes, "Oh, Bob, do you still work on computers?) I then had three machines - the third is an old Gateway 750. It runs fine. I brought it home, and burned down the drive and then installed Win2K Server. I have legitimate version of the software - don't ask why.
In any case, I installed it just to see if it would install, sort of a benchmark test, if you will.
So, now I have three machines, and I'd like to build a network with them. Why? Because when I go for an interview, I'd like to be able to say that I have some experience beyond just seeing the stuff boot up.
Assume the following:
I have a cable modem
I have a Viewsonic wireless router, which also acts as a four port router
Each machine has a valid, functioning NIC onboard.
Two of the NICs are hard NICS - cable has to plug in to communicate, the third one is a wireless card.
For 25 percent of the semester grade, can someone point me towards a decent "do it yourself" guide to building a server based home network system?
Any assistance - either personal experience or telling me where to go - and if you knew where I worked, you'd know that I'm already in Hell, so that's not a valid answer - would be appreciated.
LOL - harrassment is part of the fun.
well it depends on how you are doing it. I would assume that your server will be connected to the router and then the workstations will be connected to the server in some form or fashion?
Here's what I have set up right now - the server, while loaded and operational, isn't on the network anywhere. It's standing alone, in the corner.
I have the cable modem, then the cable modem connected to the router, and then my XP home machine is wired to the router. My daughter's Win2K machine is on a wireless NIC to the router.
What I would like to do is to have the server act as the server for the home network, as well as the gateway to the internet. Can it be done as it stands right now, or do I need an additional NIC for the server or what??
you are going to need an additional NIC.
As I remember, you will want to have the incoming connections from the router on one, and if you want the server to be a gateway, you will need to keep that separate for the cable modem.
Since you are doing a small network, I would advise doing static ips so we don't have to get into subnet masks and the DHCP pool of addresses and all that jazz...
LOL! Don't sell yourself short. My husband - before he was my husband - and I worked together at a company and I thought he was cute. Got a hint from one of the matchmakers in the office that he was really interested in cars - he restored antiques, fixed current model and used cars, etc. I needed a car anyway, bought one, then he offered to teach me to drive. (Long story short - my driving made my parents nervous, so I couldn't learn on their car)
In October, we'll be married 28 years. :)
Cool - I think I've got a spare in one of the boxes I have yet to unpack - even more motivation to finish unpacking. I figured that's probably how it would go, but it's a matter of sorting out the details. I'm thinking it'll be fun just to play with.
if you can do this, you can do just about anything with computers, at least windows-wise.
now if you were talking Sun Blades, that would be fun too, except you wouldn't need the server, the Blade would BE the server :)
So, what you're saying is that this might be a subtle move on her part to engage my interest based on her need for help with a computer.
Then again, she might have just needed help with the computer... lol ;)
I'm just saying, be watchful for all possibilities...
Well, at least you're prepared. < |:)~
DHCP vs. Static IP adressing isn't your choice. It's up to whatever protocol is used by your ISP. At least, as far as DHCP is concerned. If they use it, you must set your network to use it.
"Then again, she might have just needed help with the computer..."
Faint heart never won fair lady.
And that's all the advice I can offer, other than to remind you she will probably not want to hear all the gnarly details of this beeber stuning network building.
I realize that that isn't my choice as far as how the server goes out to the ISP - but so far as how the server addresses my internal network - isn't that something I can make decisions on?
Well, I've gone out with her once before - so I'm thinking it was more than just computer repair. The question is - and I've been out of dating for a long time - how many dates before I can show her my beeber?
"...how many dates before I can show her my beeber?"
Why sir, if I wasn't a yankee I'd faint!
The above statement assumes you have a router, not just a switch or hub, connecting your internal network to your DSL line. Routers can translate the IP addresses on network packets between the numbers used within your local network and the IP address(es) assigned to you by your ISP. Routers usually also provide a useful form of firewall, refusing to let in requests from the outside except when they are replies to something you sent out.
Your PC's and Mac's will address the router (and perhaps each other) using IP addresses (the things that look like 192.168.0.1) obtained using your choice of DHCP (dynamically assigned by the router when the PC boots) or Static (a fixed IP address you tell the PC it has, until further notice.)
Your router will address your ISP via the DSL line using either a static IP address (more expensive, but preferred if you are running servers that others use) or DHCP (dynamically assigned with some range by your ISP).
Remember to knock down any software firewalls.
I've gotten to be a bit of a whiz setting up wireless networks........but FSE is far better at any other server-based networking schemes.
Actually, I don't think so. The DHCP vs. Static IP adressing protocol selection is only made in one place when you set up a PC with yor ISP and having a LAN doesn't change that. To deal with IP shortages, DHCP lets the ISP assign an IP to your cable modem or NIC and when it is not in use, the ISP takes that IP back and places it in a pool. It has to do with your gateway to the internet.
Now, as far as the IPs within your home network...your router usually is assigned an IP and your nodes (PCs) are numbered following that. (i.e. 220.127.116.11 then 18.104.22.168, etc, etc...)
I believe you can chenge those to your hearts content so DCHP within the LAN makes no sense.
FSE and you (I believe) talked me into building/assembling all my own computers vs buying em. Wise advice......much better systems for my needs vs what others "think" I need off the rack ! Over the counter Laptops aside my desktops are good reliable machines.
Disclaimer: Opinions posted on Free Republic are those of the individual posters and do not necessarily represent the opinion of Free Republic or its management. All materials posted herein are protected by copyright law and the exemption for fair use of copyrighted works.