Today started out with discovering our phone wasn’t working. Since we have Vonage or Voice over IP (VOIP), this usually means our Internet is down. At least I know when the Internet is down! My usual routine for this sort of thing is to first unplug everything (the cable modem, router, switch, and the Vonage router), let it sit for a good minute or so to discharge any kind of inductance build-up (or whatever), and then re-plug everything back in starting from the modem, then the router, then the switch, then the VOIP box.
So, as usual (so I thought) this procedure worked. Our phones were working again. But when I logged on to my laptop, I soon discovered there was more to the situation this time. When I opened up IE, my browser immediately took me to a site securespot and told me that my machine did not have access to the Internet. Since I’ve had some prior experience with Secure Spot, I knew that it had to be something wrong with my D-Link DIR-655 router. I logged into my router and checked the configuration. It seemed fine. I rebooted it. I still had the problem. I then began searching the D-Link forums, and sure enough, there is a hornets nest of very upset D-Link users experiencing similar problems. I had recently upgraded my router to the latest firmware, 1.33NA because the router had been randomly dropping my Virtual Servers List. This was problematic because I’m using a single dynamic IP address and I need to NAT individual ports over to my web/email server. As a side-note the firmware upgrade to 1.33NA did not help this!
After pouring through many posts, here, here, here, and here, it appears this latest buggy firmware is affecting the router in different ways. Secure Spot is one of them. Since I had tried out Secure Spot previously, and had registered my router with a trial (I was trying the feature out for a client who had some workers going to websites they shouldn’t have been), the firmware is still communicating with Secure Spot, even though my router clearly has that feature disabled. One option mentioned is to downgrade the firmware to 1.31RU, another is to try out a beta version located here (version 1.34b03NA is the latest as of this post). I really hesitate to do either of these, so I opted to ‘Reset’ the router back to its factory settings, and then I re-loaded the settings. This, (at least for the moment) has fixed my problems. I’ll probably wait until the next release of the firmware before upgrading if I don’t have much more trouble. If I do, I will give the latest beta version a try.
Next, I wanted to log into DotNetNuke to do some work on my website. I keep all my username/password information in KeePass Password Safe. If you have a lot of passwords to keep track of, I highly recommend it! I don’t know how I kept my password information before using this. Anyway, as I was saying, I wanted to get into my website to work on it, but I couldn’t find the username/password information anywhere. I had to think about this for a moment (don’t panic). How did I regain access to my website? Easy. I just logged into SqlServer and queried the aspnet_users table. Now I remember what user name I used! Now add them to KeePass, right?