• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Cable confusion

H

Hoober

Diamond Member
Ok -- I've got a network set up and I'm adding a server to it. I just wanted to double check to make sure I've got my cable hookups right.

Modem comes into router through crossover cable via uplink port on router.
Server connects to router through normal port with regular patch cable
Switch connects to second NIC in server through patch cable
Clients connect to switch via normal patch cable.

Does that sound right?

Thanks,
Hoober
 
I'm not sure why you have the systems connecting to the server through the switch, then to the router. Are you trying to allow direct outside access to the server via the second NIC?

Russ, NCNE
 
Well, connecting to an "Uplink Port" through a crossover is the same as connecting to a standar port through a straight. The Uplink port is a crossover, and if you connect a crossover cable to it, you've uncrossed the crossover on the Uplink. Crossing over on a crossover is the same as straight through.

Usually, you'd use a straight-through cable to an uplink port (from another standard port, like a standard hub port, switch port, or router port...consumer routers for DSL & Cable may or may not have a crossed port...I s'pose it'd do some good to have a thread somewhere for reference that says 1.) Make/model 2.)uplink port (yes/no),3.)uplink crossed or straight.

My experience has been that if it's marked as an "Uplink" port, it's crossed...but ya never know with this consumer stuff.

FWIW

Scott
 
call me crazy, but if it's a dedicated uplink port, then you would connect the modem to the router with regular patch cable, not a crossover cable.
 
The client doesn't want to get rid of the router because of the hardware firewall built in. I've already explained to them that the firewall really isn't going to do much (its a standard SOHO model) and that they'd be better off just connecting the modem directly to the server, but you know how it goes.

I was planning on setting up OpenBSD or Linux on the server, so that'd take care of the security issues. I just wanted to make sure that the cable setup was right.
 
And the funny thing about the uplink port on the router is that when the client had an @Home cable connection, I used a patch cable in the uplink port. They've since switched to DSL (for the upload speed) and I couldn't for the life of me, get the router to make a connection through the modem. I finally switched out the patch cable with a crossover and it worked fine. Doesn't make much sense to me, but I don't know.
 
I know that with the Cisco 67x's DSL modems it is, indeed, a crossover that is used.

I'm still missing the need to set it up this way. Why not just run the DSL modem to the router, the router to the switch, and plug ALL the systems, including the server, in to the extra ports on the router and the switch.

It seems to me that you're making this more complicated then it has to be.

Russ, NCNE
 
But then I'd lose the software firewall of the OS, whichever one we decide is best to put on there, right? I mean, if I don't run the internet connection through the server I'd lose the security.
 
I guess I'm having problems figuring this all out...

What if we went with W2K server and wanted to create a domain to have all the computers log into. Does it matter that the internet connection goes right into the server? Also, what about DHCP? I know the router hands IP's out if you want it to, but that would mean that the client computers are going to the router to get their IP addresses, not the server. So I know that that would nix the security.
 
Hoober,

You can't have two DHCP servers on the same segment, so you'd either have to disable it on the router, or not set it up on the server.

If they're that worried about security, then maybe they ought to consider getting a real firewall.

OTOH, if you want an additional layer of protection, just set it up as I have outlined above, and install Zone Alarm on the systems. It's effective, and very easy to setup.

If you configure it the way you originally outlined, you may run in to routing issues that will need to be resolved.

Russ, NCNE
 
Ok, thanks Russ. I was wondering about that as well. SO either get rid of the router or plug the server in as a fileserver without DHCP or Domain information. I appreciate your help.
 


NIC to NIC - Crossover Cable.
NIC to HUB - Straight Cable
NIC to Uplink - Crossover Cable (Uplink is NIC plug on Hub/Switch).

HUB (regular) to HUB (regular) - Crossover Cable.
HUB (regular) to HUB Uplink - StraightCable.

Cable/DSL entry (WAN) on a Cable/DSL Routers is an Uplink.

If your Modem came with Straight Cable:

Modem to NIC - Straight Cable
Modem to HUB - Crossover Cable.
Modem to Uplink - Straight Cable

If your Modem Came with Crossover Cable:

Modem to NIC - Crossover Cable.
Modem to HUB - Straight Cable
Modem to Uplink - Crossover Cable.

 
The router is an SMC 4-port barricade -- three ports and a fourth "uplink" port.

ihave the 7004BR 4 port SMC barricade, i don't recall it having a uplink port at all. port 4 is a regular port on mine unless i'm missing something
 


You partially right the 4 computer ports are regular switch ports.


The WAN on the Barricade (as well as other Cable/DSL Routers), is an Uplink connection.

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top