I'm new to switches, help.

Ok, I could be just missing something here but I've never adminned a switch before. So I bought a 24 port switch last week off ebay to use for lan parties and whatnot, Netgear model FS224. I originally started off with just the switch, It did not have any outside connection. I then plugged in like 4 or 5 computers stright into the switch, they all got the error that says "Partial to no connectivity" or whatever, all Windows XP machines. First question is, what exactly does this mean? None of the computers reported an IP either.

Then I tried running an ethernet from the cable modem to the switch, same error and none of the computers could get a connection. I also tried running ipconfig and for some reason all the computers connected were giving their old IP's from the router that they were last used on. The computers could not be pinged.

So then I tried plugging the modem into a Linksys WRT54G wireless router, and then taking a regular ethernet cable from the router and plugging it into the switch and then renewing the IP's on all the computers, it worked fine.


So the only way I could get all the computers to work was if I had the switch plugged into a router..... The only thing that I can think of was becuase the router was giving the computers an internal IP for the other computers to see. But for some reason I thought there is a way to simply plug things into a switch and all things would be dandy..... Am I wrong here, or what do I have to do.

Sorry if I'm vague about anything, but I really have never used a switch before, other then plugging into it at other lan parties that I did not manage.

Your router was assigning Ip address's to the computers that were connected to your switch, most cable and DSL modems can not do this unless you pay for a staic IP for each computer that you wish to have connected to the internet. The best way to set this all up is they way that it was working for you:

Modem --> Router/AP --> Switch --> Computers

hope that helps.

Sounds like you have nothing assigning IP's

try manually assigning them on the PC's and test them that way with the new switch

Silent Assasin said:

So the only way I could get all the computers to work was if I had the switch plugged into a router..... The only thing that I can think of was becuase the router was giving the computers an internal IP for the other computers to see. But for some reason I thought there is a way to simply plug things into a switch and all things would be dandy..... Am I wrong here, or what do I have to do.

Click to expand...

Yes, you are wrong... You need a DHCP server for your DHCP enabled clients to obtain an IP address from. The router you plugged in has a DHCP server on it therefore it worked once you plugged it in along with the computers.

Ok, it does make sense, but I was kind of hoping that the switch would assign IP's....

Now I need to learn how to set up a DHCP server with an old computer I have.... Right now I'm using a Linksys router, but it'd be nice to set up a server box.

To set up a DHCP server, do I just need 2 NIC cards? And then modem to NIC1, but then how do I assign IP's? It'd be best if I could use something other then windows for the DHCP server box...

Silent Assasin said:

Ok, it does make sense, but I was kind of hoping that the switch would assign IP's....

Now I need to learn how to set up a DHCP server with an old computer I have.... Right now I'm using a Linksys router, but it'd be nice to set up a server box.

To set up a DHCP server, do I just need 2 NIC cards? And then modem to NIC1, but then how do I assign IP's? It'd be best if I could use something other then windows for the DHCP server box...

Click to expand...

your linksys router can hand out DHCP, if you don't want that, then I'd recommend a 2003 server just for fun, there are linux solutions of course but IMHO it's the best to learn on microsoft platform whether you like it or not, that's just how the world is right now.

You don't need 2 NIC cards, DHCP is a service that runs on the server, it accepts requests and responds as appropriate.

While you're at it make a home domain, get a trial 2003 server , setup a domain with DNS and DHCP (DNS is required anyway for Active directory domain) and make the otehr pc's log into this domain, it will be a good learning experience for you.

EaTeR said:

IMHO it's the best to learn on microsoft platform whether you like it or not, that's just how the world is right now.

Click to expand...

Where exactly do you work?

Silent Assasin said:

Ok, it does make sense, but I was kind of hoping that the switch would assign IP's....

Now I need to learn how to set up a DHCP server with an old computer I have.... Right now I'm using a Linksys router, but it'd be nice to set up a server box.

To set up a DHCP server, do I just need 2 NIC cards? And then modem to NIC1, but then how do I assign IP's? It'd be best if I could use something other then windows for the DHCP server box...

Click to expand...

A switch has no concept of IP addresses. If all your server is going to be doing is DHCP, then you only need a single network interface. If you want it to act as a gateway between your network and the internet, though, then you will need two interfaces. Contrary to what the other guy said, I see absolutely no reason to spend money on a windows license for something that can easily be done with free software.

Switches are L2 devices they do not know jack about IPs, MACs yes. Unless you have a L3 switch.

Malk-a-mite said:

Where exactly do you work?

Click to expand...

yes, linux rules, give me open source or death!. right. I won't even get into that flame war

EaTeR said:

yes, linux rules, give me open source or death!. right. I won't even get into that flame war

Click to expand...

Ok, better follow up question.

What the hell is your problem? I was curious about the enviroment you worked in since you seem to be dealing with an all MS shop to the extent you recommand it for everything. if you can't tell the difference between a simple question and a flame feel free to get off the Internet at the next stop.

Download IPCop and install it on an old machine with 2 Nics, and turn DHCP on, it will be WAY simpler than what Mr.Microsoft says up top, as well as FREE....

QJ

Malk-a-mite said:

Ok, better follow up question.

What the hell is your problem? I was curious about the enviroment you worked in since you seem to be dealing with an all MS shop to the extent you recommand it for everything. if you can't tell the difference between a simple question and a flame feel free to get off the Internet at the next stop.

Click to expand...

your simple question sure seemed like a flame bait buddy, I don't have a problem at all but I would suggest you look into a mirror when you ponder about that.

To answer your question, I'm the only IT person for a corporation with about 120 networked clients spread over 3 locations in MA, 1 in TN and 1 in Italy. I do it all. (notice i don't say "I Know it all" )

EaTeR said:

your simple question sure seemed like a flame bait buddy, I don't have a problem at all but I would suggest you look into a mirror when you ponder about that.

To answer your question, I'm the only IT person for a corporation with about 120 networked clients spread over 3 locations in MA, 1 in TN and 1 in Italy. I do it all. (notice i don't say "I Know it all" )

Click to expand...

Telling someone to use a $500+ program in a home environment doesn't sound feasible to me......

QJ

It's not the matter of my preference of linux or windows, I have experience with both, it just the money factor..... I can't afford to spend $100+ for just a server.

Back on topic now....

What would be the difference between a gateway and a just a simple DHCP? Or what would you guys suggest? I want to be able to still use the wireless access point for the family's laptops but I still want to use the switch so I can connect more then 4 computers. Right now my home setup goes, Modem --> Linksys wireless G router (port 1) -- (using a normal ethernet cable, no crossover.) --> Netgear 24port switch (port 1) --> computers.

It would also be good if i could install use this as a server box as well. I've got an extra 200GB hard drive that I'd like to stick in the system so that I could use it as an FTP server as well.... Or would doubling it as a server box compramise the security and whatnot?

I guess I could easily leave it the way it is now, but would you consider that to be [H]? Plus I want to use these old K6 parts for something.

Silent Assasin said:

It's not the matter of my preference of linux or windows, I have experience with both, it just the money factor..... I can't afford to spend $100+ for just a server.

Back on topic now....

What would be the difference between a gateway and a just a simple DHCP? Or what would you guys suggest? I want to be able to still use the wireless access point for the family's laptops but I still want to use the switch so I can connect more then 4 computers. Right now my home setup goes, Modem --> Linksys wireless G router (port 1) -- (using a normal ethernet cable, no crossover.) --> Netgear 24port switch (port 1) --> computers.

Click to expand...

First off, a Gateway and DHCP are not in the same category. A gateway is a device that connects two different networks. DHCP is a service that runs on a network in order to dynamically assign IP addresses to clients.

Second, leave it exactly the way you have it set up above. Using the equipment you have on hand that is exaclty how it needs to look..

Modem---Gateway---Switch---Clients

hmm just wondering can't he give the computers a static address i know it's going to be annoying to do it for everyone that comes in but won't that work the same? as long as everyone has the same gateway right?

wuzzzy said:

hmm just wondering can't he give the computers a static address i know it's going to be annoying to do it for everyone that comes in but won't that work the same? as long as everyone has the same gateway right?

Click to expand...

But a static IP requires a common gateway IP, which the swich does not have being that it's an L2 switch.... I have found at least that much information on switches.

PHUNBALL said:

First off, a Gateway and DHCP are not in the same category. A gateway is a device that connects two different networks. DHCP is a service that runs on a network in order to dynamically assign IP addresses to clients.

Second, leave it exactly the way you have it set up above. Using the equipment you have on hand that is exaclty how it needs to look..

Modem---Gateway---Switch---Clients

Click to expand...

I don't give up that easily. I'm still young, I want to learn new and different ways of doing something. Just because it works now, it doesn't mean it's done right..... I'm always looking for something ne to learn about computers. This just happens to be the right time to learn more about networking.....

Silent Assasin said:

But a static IP requires a common gateway IP, which the swich does not have being that it's an L2 switch.... I have found at least that much information on switches.



I don't give up that easily. I'm still young, I want to learn new and different ways of doing something. Just because it works now, it doesn't mean it's done right..... I'm always looking for something ne to learn about computers. This just happens to be the right time to learn more about networking.....

Click to expand...

Your Linksys router is a GATEWAY. Why do you need another one?

I'm not saying give up, I'm saying that setup is technically correct and there is no need to change it unless you just want to...

Any IP device requires a gateway to be able to access networks outside it's own, regardless of how its IP address was obtained. As mentioned earlier, switches have no concept of IP addresses; everything on that layer just passes through the switch as if the switch wasn't there.

Like phunball said, your current setup is technically correct. The only reason you would need to replace your linksys router with a custom setup is if the linksys just wasn't cutting it for your needs, or if you just wanted to learn about setting up such a system.

If you do want to replace the router with a custom setup, then just get an old computer and throw a couple network interfaces in it(plus a wireless adapter to provide wireless access, if needed). Then just install your OS and set up your firewall. This system will completely replace your linksys router, but will not affect any other parts of your network.

PHUNBALL said:

Your Linksys router is a GATEWAY. Why do you need another one?

I'm not saying give up, I'm saying that setup is technically correct and there is no need to change it unless you just want to...

Click to expand...

Exactly.... the only benefit from the IPCop or Smoothwall would be the 'COOL' factor.... the Linksys router is Gateway/WirelessAP/4 Port Switch/DHCP all in one. If you shut off DHCP in the router, and just use it as a wireless AP, then the IPCop would THEN be the gateway/DHCP

QJ

So I could even through a wireless card into the old server along with 2 NIC cards and make it a wireless access point? Because this would make thing a ton better. Right now the Linksys I have is a piece of crap and needs to be reset almost daily. So if I wanted to eliminate the wireless router all together, I just need an old computer, 2 NIC cards, and a wireless card? I already have all of that laying around in spare parts so it shouldn't be that hard. And then I need to install IPCop onto the system and I'm good to go, or will there be a ton more of IP assignment that needs to be done?

It would be aweseom if I could go modem --> server (wireless access point) --> switch --> Users.

Also my question about if the server doubling up as a file server/ftp server was ok.... Would this be ok? Or would you suggest another old crap computer for the file server?

Anyone?

Yes you could throw a wireless card into the server and use it for an AP (there are a few distros that have that option) but once you move the Linksys from being the primary gateway for the whole network to just doing wireless you might find that the reduced load cuts down on the frequency of the reboots.

Malk-a-mite said:

Yes you could throw a wireless card into the server and use it for an AP (there are a few distros that have that option) but once you move the Linksys from being the primary gateway for the whole network to just doing wireless you might find that the reduced load cuts down on the frequency of the reboots.

Click to expand...

Well it would be best if I could just remove the Linksys router entirely. I didn't realize that putting in a wireless card to the DHCP server would allow me to use it as an access point.