This does lead me to another question though. Because we didn't have enough drops, our wiring scheme is a bit convoluted. In one area of the office (where the server is located), there is only one ethernet drop that needs to be shared by the server, a couple of workstations, and a printer. So, we use a 5-port Trendnet Green Gig switch to split and share the one drop.
At the patch panel (I think that's what it's called, there are about 6 ethernet connections. So again, they go into a Trendnet 8-port Gig switch, and that is connected to the Actiontec DSL modem/router.
Am I compromising server LAN speed this way?
The short answer is yes, the real question is how much.
You can dig *alot* deeper into this, but a incremental step is to pick up a layer 2 or layer 3 switch that will allow you to do port monitoring (first), and then think about implementing VLANs as a way to address traffic congestion. There are several options once you have a layer 3 switch, but there is going to be a learning curve. more if you go with a layer 3 switch with a CLI.
Should I connect the Server straight to the Trendnet 8-port switch? or maybe even the Actiontec DSL modem/router?
I ask because every once in a while, I'll get a little warning in the tray that says, "The server is not connected to the internet." (or something like that).
Oh, this is *not* what you want to see. I recommend against the DSL router - use that more as a edge device (edge of the network), and run your own network inside of it, so that you can add another edge device in tandem, or replace it/them without disrupting your network.
I'd think about another layer 2 or better device (Gig ports) located there.
BTW - can you get cable modem service at your location? DSL is not your friend, unless you have no choice of other friends.
