Is it possible to daisy chain 3 switches?

January 31, 2011 at 06:04:25
Specs: Windows Vista
Is it possible to daisy chain 3 switches and not have ip conflict? I am running a public access network for a library. For certain library software I need for all workstations to see each other. I have 25 workstations in total and two separate management consoles.
I have all workstations on two switches but one of the management consoles is on the third switch because when joined with the others it has an ip conflict. I need this console for the digital sender that is connected as well as to act as a server for go print software.
Everything is running on dhcp.. Please anay suggestion will help. I think I have exhausted many different avenues of approach.


See More: Is it possible to daisy chain 3 switches?

Report •

January 31, 2011 at 07:26:37
"Is it possible to daisy chain 3 switches and not have ip conflict?"

Switches work at layer 2 thus do not have an IP address. You just simply hook them up with crossover cables. The newer switches don't need cross over cables. Are you using layer 3 switches?

As far as your switches management consoles IP addresses conflicting, why are you not using Static IPs on these devices?

Me personally, I give all of my network devices besides workstations, static IPs this way I know a printer, router, switch, UPS or what ever is always going to be at a specific IP.

Report •

January 31, 2011 at 07:33:02
Is it possible to daisy chain 3 switches and not have ip conflict?

Ok, this is two questions. In order then.........

1) Yes. In fact, you could daisychain switches until the cows come home but I avoid daisychaining whenever possible because when you do so, the bandwidth aggregates.

So, to explain, lets say you have 3 - 48 port switches. 2 plugs into 1 and 3 plugs into 2. All 3 switches have 40 clients plugged in.

Switch 3 carries the bandwidth load of 40 clients
Switch 2 carries the bandwidth load of it's 40 clients AND switch 3's 40 clients
Switch 1 carries the bandwidth load of it's 40 clients AND switch 2's 40 clients AND switch 3's 40 clients

So, if you have say, a SOHO router as your gateway to the internet and it has 4 LAN ports, I would plug all 3 switches into LAN ports on the router if feasible.

2) Whether or not you have an IP conflict depends on your setup. From the looks of it, you have some devices with static IP's and some DHCP and that's likely where you're having an issue.

Check your DHCP scope and ensure you know what IP's are included in it.

Then, check all devices with statically applied IP's and compare them to your DHCP scope and each other. If you have any IP's that are statically assigned and that IP is actually one that's in the DHCP Scope, change it to one that's outside the DHCP scope. If you've inadvertently assigned the same IP twice (and it's not inside the DHCP Scope) then change one of them to another IP that is also not inside the DHCP Scope

This is where documentation is not only handly, but damned important. You make a list of devices. Each line should contain the devices hostname - make/model - and IP address assigned. Then when you go to add a new device(s) you simply open the file and you immediately know what's in use and what isn't.

If it were me, I'd have the DHCP Scope noted in there as well to avoid assigning static IP's that are inside the scope.


DHCP Scope: to

Device Name = ws001 Make/Model = Dell/somethingorother IP =
DM = ws002 M/M = HP/somethingorother IP =
DM = mgmt1 M/M = ?/? IP =
DM = mgmt2 M/M = ?/? IP =

etc etc etc

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***

Report •

February 2, 2011 at 07:04:37
Thank you for the replies. After much investigating it turns out our modems are configured to run the same range ip addresses. Which is why I kept getting an ip conflict. So again thanks for the help.

Report •
Related Solutions

Ask Question