Maintaining network when router reboots

Hamster · 7 Jul 2009 at 18:42

Simple problem,

What is the simplest way for 10 computers to be networked so that if the router restarts or malfunctions, the computers can still communicate with each other. The PCs all need access to the internet. Would this be via a 16 port switch and what would be the easiest and most effective way to connect and network them? Some PCs have vista, some XP.

Thanks

JM

iraiguana · 7 Jul 2009 at 18:44

Get a switch and patch that to the router.

Router goes down, all computers still networked to each other and run fine. Once router is back online the net will work again.

Job done.

//edit

I have assumed you have used all the pc's with fixed ips which do not conflict as if you are using the router for dchp it may throw a bit of a wobbly when it comes back online.

Hamster · 7 Jul 2009 at 18:49

Thanks iraiguana

. Will i have to play around with DHCP, static IPs etc or is it as simple as plugging the switch into one of the router's ports and plugging the 10PCs into the switch and everything will work as if all the PCs are connected directly to the router?

Also is there any particular type/brand of switch you would recommend?

Thanks

tolien · 7 Jul 2009 at 18:50

It should be fine even if you use DHCP provided the lease times are long enough.

It should just be a case of connecting them to the switch and the switch to the router.

Hamster · 7 Jul 2009 at 19:01

tolien said:
It should be fine even if you use DHCP provided the lease times are long enough.

It should just be a case of connecting them to the switch and the switch to the router.

Great stuff. Thanks

Any particular brand/type of switch you would recommend?

tolien · 7 Jul 2009 at 19:04

Unmanaged switches are much of a muchness.

Hamster · 7 Jul 2009 at 20:15

OK thanks. I'll probably go for a Linksys then for around 50 quid.

samuria · 7 Jul 2009 at 23:50

You are always better off with fixed ip as this way you know which pc each person has and you can identify them if there is any sort of fault. With dhcp you dont know who had what ip at what time. There may be times when you want to blame someone for something and with fixed ip you know who it is.

If you dont have dhcp its harder for anyone to break into the network with it they plug anything in and there on your network

tolien · 8 Jul 2009 at 00:08

samuria said:
You are always better off with fixed ip as this way you know which pc each person has and you can identify them if there is any sort of fault.

You do with DHCP as well. Every DHCPd keeps some record of what MAC address got what IP.

With dhcp you dont know who had what ip at what time.

Bzzt.

If you dont have dhcp its harder for anyone to break into the network with it they plug anything in and there on your network

With no DHCP running, all they have to do is plug in and try one of the handful of IP ranges that 99% of networks use and they're in. It's no security, but if they can plug into a switch port all bets are off anyway.

Dist · 8 Jul 2009 at 04:38

using static IPs is only realy needed for devices providing a service where other devices need to connect to it for some reason, such as a router, a web server, file server etc... For the majority of home internet users, DHCP is perfectly fine. Even for more buisness orriented users DHCP is good because manualy assigning each IP is just too time consuming.

Back on topic, as has already been said a switch is what you need. It is transparent to the network and unmanaged switches require no configuration, just plug in the cables, and should you ever require more switch ports simply buy another switch and cable them together.

K.C. Leblanc · 8 Jul 2009 at 13:45

This is very bodge flavoured, but some domestic weight kits benefits from being rebooted every so often. Might be worth getting a cheapo time switch and setting it up so the router switches off for a little while in the middle of the night.

Agreed with peoples views on DHCP, it is the way to go.

tolien · 8 Jul 2009 at 16:06

Dist said:
using static IPs is only realy needed for devices providing a service where other devices need to connect to it for some reason, such as a router, a web server, file server etc...

You can give out static IPs with DHCP as well though, with the advantage that you don't have to go round machines when you want to change DNS server.