The time had come this week – unfortunately, I must add – to replace our network hardware. A poorly placed laptop case had rendered our main wireless router unserviceable and it therefore had to be replaced. This is a task I’d undertaken a few times before and wasn’t too daunted by at first. In fact there was more than a hint of complacency when I thought I could take a slight shortcut and save a few pennies by attempting to ‘piggy back’ the old broken router with a shiny new wireless router and therefore not have to reconfigure our internet connection.
How wrong I was. Compatibility is a frequently quoted word when the topic of networking equipment raises its head. Three hours in, and patience distinctly fraying around the edges, I decided that the simplest solution was to completely get rid of the old one and start completely afresh with a brand spanking new wireless ADSL modem/router.
All went well. The router was up and running in no time, with a lively, sharp internet connection… whizzing through web pages like a spring swallow. Now came the fun part. Eight other computers or ancillaries had to be interfaced and networked. I foolishly thought that if I gave the new router the same name as the old one, all the other minion machines would be too stupid to notice the difference and would connect dutifully when exposed to the new router’s vibes.
How wrong I was. (sounds familiar) To keep us safe from the sort of people who frequently try to offer me manhood enhancement facilities that are too good to miss, and marriage proposals from beautiful girls in Russia who I’ve never met, we have software enhancements called ‘firewalls’. In layman’s terms, if a computer tries to connect to mine, and mine doesn’t recognise it, it simply says ‘go away’. But if I were to tell it in advance that Mary from Russia would be coming to tea, it would simply open the door for her and let her in. All eight other machines had been granted free access to Mary using the old router, but now, thanks to the new router having given them all new names, none of them were allowed in to visit. So a mass Christening ceremony where they were all renamed took place and with all firewalls reconfigured, it was time to get the show on the road!
How wrong I was! (again) For effective networking to take place everyone needs to speak the same language. Computer one was speaking WPA2-PSK in a TKIP dialect, computer 2 was speaking WPA with an AES twang, and our networked printer didn’t really know what language it was speaking. So each machine was given a little language tuition in order for everyone to be able to get along again. Conversatiion was resumed and ideas, files, bits and bytes were about to be exchanged without hinderance.
How wrong I was.(yet again) Mr Windows is like an elephant – He has a marvelous memory. So just to make sure we weren’t trying to pull the wool over his eyes, he pipes up and says “Oy! You can’t talk to Mary! Last time we spoke to her she had 10.0.0.15 shoes on. She’s now wearing 192.2.3.155 boots, so it can’t be her!” Trying to change Mr Windows’ mind is easier said than done. He’s very headstrong and stubborn and only when you get deep into his inner feelings will he relent and allow himself to be convinced that Mary is in fact the same Mary he let in last week.
All in all, networking is fraught with potential pitfalls. For someone who is setting up a simple network with new equipment, for the first time, and with standard settings, it’s a piece of cake, albeit quite tough cake, but if you have to introduce a new piece of kit into an established and diverse network, prepare yourself for some techno politics.
Now where did I put that laptop case?
N.