Apr 09, 2008 at 9:20 am
Problem Solved #00001 - DSL, Wifi, printers
This is your introduction to the major feature of this blog, the “Problems Solved.” I’ve told you that I’m Josh and declared that I can help but where are the goods? Right here, buddy.Every major project I finish (customer or my own) and every large even that I had a hand in will get a “Problem Solved” post, complete with it’s own number (I’m limited edition, FYI). Each call has it’s own nuances and various issues so, as you can see, the heading also gets a few words to describe the problem. The sub-headings in the posts will detail each problem (succinctly) and what the solution was, if any.
The personal value behind these posts should be clear: I’m interested in a chronicle of experience and a professional journal of sorts (I think those are synonymous). The value to the outside world is two-fold: you can see what kind of problems other people are having and you might just find a quick-fix to one of your problems. When I research problems on-line, I’m never frustrated by an OVERABUNDANCE of solutions.
On with the show…
This customer lives in a gorgeous part of Del Mar, CA in a pair of condos with his family and veritable zoo of domestic pets. He called me to help him move his router, make sure wi-fi worked throughout the house, set up a printer with Vista (which was causing him problems), and possibly help him acquire a new desktop.
Sub-problem: home DSL network
The home DSL network was the main reason I was called in the first place. I’m very comfortable working with small wireless networks, wired or otherwise, so I figured there would be no problems. Silly me.
The piece of equipment he was using was a 2Wire 1800HG combination DSL modem and wireless router. I’ve had DSL before and never had any outstanding problems moving equipment and setting up networks so I neglected to print out any documentation. That was my first mistake (I’ll be posting on what I learned on my first customer call soon).
I unplugged the router, moved it upstairs, plugged it back in, and waited a moment. I was hoping for this:
I got this:
I tried a few power resets and the reset button on the back with no discernible results. I started to panic (I was already a little nervous). I tried moving the router back to its original location with the same results. Because this customer was living in two different condos, I wondered if maybe the phone system was not setup correctly to allow the DSL router to be moved. Then, because I didn’t see a DSL filter on the phone line leading to the fax machine, I got the crazy idea that the whole house was wired for DSL filtering (so filters would not have to be attached to each phone).
Yes, I was getting a little desperate.
Moving a DSL router solution
What I did next was exactly what I was supposed to do but, since I did not have the documentation, I did not do it correctly and went through another hour of mucking about trying to figure things out (I certainly did not charge for this hour).
For any router you have connected to your system, you are able to access that piece of equipment in a similar way that you would a website. Just like a website, your router has an address – an IP address (I suggest Wikipedia for an in-depth explanation of an IP address). You can type this address directly into your web browser and access your router’s software. What’s the problem? Finding the correct address. Here are the most common ones:
2Wire address I needed but could not find:
gateway.2wire.com (this isn’t an IP address as much as it is just a way to access the router)
Edit: the address above did not work today. The one that does work is 192.168.1.254 (router model number above).
Good general addresses to try for any router (separated by commas):
Oftentimes, your router will ask you for a login and password. This is one of those logins that you set up, write down, lose, and then panic a year later when you need it. Try a few of your common logins, try a blank login field with a password of “admin,” or, if all else fails, go to http://virus.org/default-password/ and look for your equipment based on the manufacturer (listed as “vendor” on that page).
Once you’re in, there are many things you can do but only one thing that I needed:
This, in short, tells the router/modem to run it’s set-up program. This particular piece of equipment needs this to be run when it moves. Go figure.
The program will likely ask you to set up a number of different logins, passwords and settings. On of these setting is a keycode that, according to the program, you would have been given. The customer I was with did not have this written down and the url given by the program was not working at the time (2wire.com/keycode [try also http://www.2wire.com/?p=268). I lucked out with a Google search on my phone so, for those of you in the same position, here are a few to try (from the 2Wire URL above):
AT&T service: 522P-22P4-6262-22AT-F2NV
Verizon service: 523E-23E4-6262-22AS-B2DD
Verizon service (another option): 524Y-24Y4-2262-22AS-B2GV
Other DSL service: 5225-26P4-6262-22AS-B2E7
Other cable service: 5225-26Q4-2262-22AS-B28F
After running through the program, in putting all of the right information, and writing everything down, we had the router moved, wifi up and running, and a connected desktop PC.
Wifi for the latops solution
Nothing to report here. Thankfully, the wifi reached all the way down into his living room in the second living space. The son was able to play World of Warcraft on the couch which was definitely the litmus test. I was, however, ready with a recommendation in case this was not the case.
I researched a bit about wifi repeaters and found some interesting information. According to most of the comments out there, they do what they should and work fairly well in a public situation. What they don’t do, however, is allow for security, which, in my opinion, is a big problem. Since that was out of the question, I researched a few wireless access points. These basically take the network signal through a network cord and make it wireless (sounds so simple). We would run a cable from the 2Wire upstairs (located next to the desktop) out of the office and down the hall into a second room that was closer to where wifi needed to be used. Here are the ones I was recommending for him:
One slight hang-up happened as the laptop was being passed around. There was a switch on the front that turned the wireless off of the computer. That was hit accidentally and chaos ensued. The chaos did not last for long.
Sub-problem: Vista printer set-up
Though I was a little wary about this part because I don’t have a lot of experience in Vista, everything came together for the most part.
I was working with an HP Photosmart 2575 All-in-One printer that was network capable (you can plug it right into your home network and print to it from any computer [theoretically]). To test it, I downloaded the XP drivers onto my laptop, connected to the network (with a cord), and tried it out. It went through without a hitch and printed like a charm.
Since the customer did not have any ethernet cables on-hand, I offered to leave mine behind. He said he would pick some up the next day so not to worry about it. To set him up to do it on his own, I downloaded the correct HP Vista drivers onto a USB drive and transferred it to his desktop and laptop.
I started the driver install on the desktop and left it at a screen where the computer needed to find the printer. I told him once the cables were plugged in from the desktop to the router and the router to the printer to finish the install and try to print. I left it at that.
After a few days, I sent him the invoice and asked how everything was going. Apparently, the desktop connects to the internet just fine and prints to the printer just fine but now the laptop, after installing the drivers, will not connect.
…to be continued…