Technology allows us to do more in less time than ever before, but there is a price to pay, especially when we try to upgrade a working system to another level of capability. That’s when we have to look under the hood and our complacency is often shattered.
I spent the last two days installing a secure wireless network in my home and my workplace. This was not bleeding edge technology because I deliberately chose a two year old model in hopes that the product would be properly sorted out.
I Googled for evidence of problems and found plenty, but most of the complaints were several years old. Recent installations seemed to have gone well, so I chose a TRENDnet wireless router and hoped for the best.
I knew I was in trouble when the Network Wizard software that was shipped with the router failed to recognize the router. This "Network Wizard" was supposed to handle all of the messy details of the installation and couldn’t even start. The installation went downhill from there.
Instead, I subjected myself to another "learning experience" which resulted in me working furiously to get a system working instead of having a pleasant weekend with friends and family.
Those of you who are considering adding wireless capability to your home computer network might be interested in what happened. Continue reading after the jump.
I already had a working wireless network gets continuous heavy use.
Unfortunately it’s an open network and is accessible for use by
neighbors and passing motorists. I planned on setting up a secure
wireless network in parallel with the existing network and then
switching our more remote computers from the open network to the secure
network, once the testing was done.
This was not a foolproof plan, but it seemed to offer the advantage of keeping things running until the new network was in place. Wrong!
Setting up the new network periodically shut down the existing wireless
network which did not endear me to Gretchen who was trying to handle
Our modern technology is marvelous when it works and it works amazingly
well once all of the gritty details are worked out. And there’s the rub.
Designing for all of the possible situations that may be encountered is
no longer done, mostly because it would be impossible to release the
product and meet the marketing window. Long-suffering customer service
people here and abroad pick up the slack when a product is released.
I decided not to use the service reps in far off India, because I
couldn’t figure out what the real problem was and I was setting up an
installation that was beyond the simple examples that Tech Support does
well at. I discarded the "Network Wizard software" and pored through
the user manual until I found information I could use to set up the
router by using a browser.
Thirty hours later I had tried every combination and I was getting
repeatable and stable results. I have switched all of the laptops and
remote computers over to the secure network and all seems to be well.
Having spent two long days in this changeover, I am still a little gun
shy, so I am keeping the open wireless network on as a backup. If one
network hiccups, I can easily switch to the other network. Redundancy
seems like a good idea today.
I will probably make both networks secure, once I am sure that the system is really stable.