How Not to Upgrade Your Wireless Router


The other day I was having some performance issues on my network, so I decided to see if there was an update to my Linksys router’s firmware. It’s a good idea to update your firmware occasionally since the manufacture can fix bugs, add functionality, and increase security and performance. Check your router’s documentation on how to update the firmware.
On my Linksys router, I open a browser and type the router’s IP address (192.168.1.1 is the default on a Linksys router). Download the firmware file from the Linksys website. The router administration page displays, among other things, the current firm version of the router.  My router was version 1.02.6 and the latest was 1.02.7 so I decide to upgrade it. As part of the firmware upgrade process, the router will restart itself after the update.

The upgrade was successful according to the status page. The router restarted and my web browser refreshed to the administration page that I was on before. Here’s where things got interesting.

I noticed that after the upgrade my the firmware version on the router was 1.01.6 and not 1.02.7 as I expected. I thought that this was strange. “Did I download the wrong firmware file?”, I thought. So I re-downloaded the file and started the firmware upgrade process from the same page, just as I did before.

This is when I noticed the wireless signal strength bars at the bottom of my taskbar were low. Usually, they are full. That’s when I realized I was not connected to my router. I was upgrading my neighbor’s router!! Luckily it came back up fine.

The mistake I made was upgrading my firmware via wireless. So when my router restarted, my computer automatically connected to an unsecured wireless connection. Coincidentally, this was the same router I was using and I was the screens that I would have seen on my router.  The lesson learned here is to connect your computer to a wired Ethernet port if you are going to upgrade your router.

SCOM 2007 Stopped Receiving Alerts


I noticed one day that I stopped getting any SCOM alerts in my System Center Operation Manager 2007 R2 environment. As part of my troubleshooting I found a ton of the following warnings in the Operations Manager Event Viewer. I contacted Microsoft tech support and discovered that my RMS was in maintenance mode. I had put my RMS in maintenance mode for 30 minutes when I did some windows updates, but it never come out of it. After stopping maintenance mode and re-starting the System Center Management service on the Root Management Server, alerts started coming in again. The Microsoft tech told me that you should never put your RMS in maintenance mode and when I asked to have some documentation where it said that, he said it does not exist. This a tip that they have discovered in their troubleshooting. During this time the RMS was unable to process agent requests, so the agent holds on to the notifications in a buffer until it can communicate with the RMS again. If you are getting this warning on the RMS there is a good chance that you lost any alerts that the agent was unable to store in the buffer.

Event Type:      Warning

Event Source:   OpsMgr Connector

Event Category:            None

Event ID:          20058

Date:                2/6/2010

Time:                2:00:17 PM

User:                N/A

Computer:

Description:

The Root Connector has received bad packets which have been dropped. It received 8374 such packet(s) in the last five minutes

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Copyright EverythingTech 2018
Tech Nerd theme designed by Siteturner