Originally Posted by HatesFury
Nope. The server can be connected to any switch or router in the network. It could actually be before the router if he wanted to configure it that way (and may need to since he'll be hosting a webpage from it).
IMO optimal setup would be exactly like you have up until the router. The router would feed server, and all both switches on an individual connection. Your mehod of putting switch 1 > switch 2 > switch 3 over complicates the network and adds more hops than is necessary. You're thinking of trunking switches, which is normally only done in an IDF where you won't have a router present.
I think you misread the diagram. The third switch is not plugged into the second switch. The second and third swtich are plugged into the first. From my experience enterprise class routers only have one Ethernet port, thus hes going to either have to use a hub or a switch. He will HAVE to daisy chain the switches in some form or fashion.
So the choices are:
Plugging switch 2 into switch 1
This wont have the expense of the third switch, but you'd probably make up for it in cable costs. As well as forcing yourself to buy larger than 10 port switches (12 port min) and limiting expansion.
Plugging switch 2 and 3 into switch 1
This way you only have to run two Ethernet cables out the the clients and have the switches much closer to the clients. As well if the company ever needs to add 10 more clients, no problem, buy a new switch (switch 4) and plug it into switch 1.
Oh and by the way the server being plugged into switch 1 was merely for simplicity sake, it could be run on any of the switches. However, servers are generally located near network equipment making it a logical choice to have it closer to the router, firewall, thus the first switch. However, it will probably need to run behind the router for the RDP and other network services to run optimally. Running it as a web server will be of no problem behind the router, simply forward port 80 to the server. I run both my web servers this way.