[K12OSN] Network specialist foes: rice bet
Ben Nickell
twinprism at athena.physics.isu.edu
Wed Oct 26 16:20:48 UTC 2005
Les Mikesell wrote:
> On Wed, 2005-10-26 at 09:03, Doug Simpson wrote:
>
>>Make sure there are two NICs in the server, and make sure the thin clients
>>are connected to a switch that is *only* connected to the one NIC on the
>>server that it's DHCP is bound to. The other NIC in the server goes to the
>>switch for the rest of the network, and it should get it's IP from the
>>existing network's DHCP server.
>
>
> It should be that simple with the 2-NIC setup. One other thing to
> watch out for is accidentally plugging a wall jack to the main
> network into the client switch. It used to be that you needed
> a crossover cable for switch<->switch connections so it was hard
> to do this accidentally, but newer switches will autodetect the
> need for a crossover and let you use a normal cable.
>
Also, be sure to clearly label the cables and also label the back of the
computer next to the ethernet cards/ports. Color coding Ethernet cables
helps, Come to think or it I might buy some red cable in various lengths
just for the external interface on my installations, and some red
stickers for the correct Ethernet port.
In remote installations, I've seen labs taken apart for cleaning and the
cables put back in the wrong slot with disastrous results and a long
phone call or a trip to the remote site to sort it out.
Ben
More information about the K12OSN
mailing list