Hi! Welcome to Angry Cat Productions. If you have any questions about any of my posts, comment, and I'll do my best to help in a timely fashion (usually quite quickly.) If you have any other questions, feel free to comment on whatever post you want, and I'll take a stab at helping you out. And if something on this site helps you solve your problems, please let me know in a comment. Because like the rest of the world, I like warm fuzzy feelings. Enjoy!

Angry Cat Productions
Ltd.

Monday, June 12, 2006

Port forwarding with and/or through two (or multiple) routers and/or modems for Azureus (or stuff like World of Warcraft)

I need to work on my SEO'ing...anyway, today I discovered, with much relief, that it is quite easy to get port forwarding working with two routers if you know how, and thought I'd share it with the world. I was trying to download Xubuntu with Azureus for my old 266 (that's mHz, i.e. 1/6 the speed of a half-decent computer) in my room and was disappointed to see the yellow smiley face, indicating that once again, my port forwarding/NAT wasn't working. So I decided to take another stab at it. And I found a help page from Slingbox that I was able to modify to work in my case.


Basically, you have the first router (probably your modem, the one between your comptuer and the second router) forward to your second router, and then set up the second router normally. So here are some step-by-step, simple instructions. For help on how do to some of these steps, check out PortForward.com, a very helpful site, hopefully you can figure out what for.



  1. Go to the first router's setup page. Set the DHCP server to serve only one address (in my case 192.168.0.2 to 192.168.0.2)

  2. Now, on the same modem, set up Port Forwarding to forward your port (any random number between 0 and 65536, such as 12345) to the same address - 192.168.0.2 in this example, on both UDP and TCP. (Please, set your port to something more random than 12345).
    Tip: I set my first router to forward a range of 10 ports (i.e. 12340-12349). You'll see why later.

  3. Save/restart/whatever to apply those settings. Then go to your second router settings.


Now, there are two ways to do it from here. Way One is best if your compy has a static IP. If you don't know what that is, or your compy doesn't, Way Two is best for dynamic (opposite of static) IP's, it uses the 10 ports mentioned above, and is my own invention.
Way One:

  1. Go Start->Run and type "cmd." Press enter.

  2. Type "ipconfig" and not what is under "IP Address"

  3. Configure your second router to forward the port(s) used in the first section to the IP address you looked up in step 2.

  4. Hopefully, once you apply the settings, all should be well. If not, try the slingbox page for more elaborate directions.


Way Two:

  1. In the settings for your second router, find the DHCP settings, and note the range of IP's being assigned (jot them down, if necessary.) The example here will be 192.168.0.100 - 192.168.0.255.

  2. In the port forwarding section set up each port with an IP address as follows:

  3. Map the first port (12340 in the example) to the first IP being assigned (192.168.0.100 in the example). 12341 to 192.168.0.101, and so on for the next 10.

  4. Once you apply the settings, you can adjust your port as your IP changes without resetting the routers. If your port isn't working, do Steps 1-2 of Way One. If your IP is 192.168.0.104, use port 12344. 192.168.0.106 = 12346. Get it?


Hopefully, I've made sense and been helpful. 'Cause this was making me crazy, and I finally got it working.
Randy

Sunday, June 11, 2006

A story about HP

Recently, I have rediscovered how much I despise HP. Yeah, Hewlett-Packard, the company that swallowed up Compaq in a deal that got their big-shot female CEO fired. Anyway, I'll start with a little side-story.
Several months ago, our computer just up and decided to not work. It would get halfway through startup and just shut off. Not good. So by holding F8, ctrl, delete and the Anykey, I finally got to a point where I could boot up into safe-debug-this-is-stupid mode. First, it said something about missing boot.ini. Next time it restarted, it flashed something about mup.sys before it promptly shut off again. So for the next couple days, I searched for high and low and tried numerous methods of getting my computer to start up again, and finally, desperate, with no other hope, decided to try a far-out, strange suggestion I found lurking on some forum. So I started the computer, counted to 27, unplugged the mouse and keyboard, stood on my head for 12 seconds, and plugged them back in. Miraculously enough, it worked. (OK, I didn't stand on my head and I didn't count, but I did just unplug them and plug them in at key points during startup.) So after scratching my head about how that had ANY effect at all, I was content to have a working computer again.

Now, how does this nice story have anything to do with HP? Well, plenty, it turns out. As I went to scan something for the bajillionth time with the HP All-In-One, it once again barfed and decided to not work. So I finally decided to do something about it. I went to their website, a tad apprehensive. (As I type, the scanner randomly decided to move. Spooky.) So I waded my way to the Software Issues section. Amongst all the problems with Macs and HP, I found a way to get around the HP Software. Sweet, I thought, this'll work. Turns out it involved using a Windows Wizard. Nice and simple, like I like it. But as I soon found out, too simple. I can't even figure out how to zoom in. So much for that idea. I'm stuck with HP's almost-worthless piece of software.
So I went back to the site, and there it was: PLEASE INSTALL THIS CRITICAL UPDATE. Figures, they shipped me faulty software. So I follow the link, and amongst the problems like making your CD burner not work was this, and I quote:

Resolves an issue where if you install the software that came with an older peripheral product, such as a printer or camera, onto your new computer or in conjunction with an All-in-One, when you try to run the HP Memories Disc Creator program it may fail. In addition, the following issues could occur:

* Hal.dll error message
* Boot.ini error message
* Missing applications and/or files


Wow, I thought, that sounds familiar. So now really angry that HP nearly cost me all the data on our main computer, I try to figure out how to download the fix. So does it provide me a link at least? No. Quote, again:
#
Go to www.hp.com (in English).
#
If needed, select your language from the language selection field in the top right corner of the page.
#
Enter sp26273 into the search field.

And it goes on for three more steps. So I have to go back to the home page, type in a cryptic code, and hopefully stumble across the right files? Surprisingly enough, I did, and downloaded and installed the fix. Then it gave me one of those annoying boxes that says "shut down everything your doing and we'll kindly restart your computer for you." No option to restart later or anything. So I grudgingly follow their command, and once it's back up, FINALLY am able to scan something. Of course, it still tries to reinstall itself and whines about not having the CD until I finally convince it that it doesn't need the CD by clicking the same OK button four times. My pictures finally got scanned, and I still despise HP. But at least my scanner works - for now.
So a few days later, I pick up my new issue of PC World. And what do I find? In their usual bugs and patches article, a patch that was supposed to fix a - guess what - HP program that went awry and basically crippled Microsoft Office. Shocking.
So what's the moral of the story? How about avoid HP when at all possible, kind of like I------- E------- and Yahoo!. On second thought, Yahoo's gaining on my good side with their Yahoo Widget Engine - more on that later. So it's just the two letter acronyms, IE and HP, that are on my bad list. Grr.
Randy

Tuesday, June 06, 2006

Ooooh - eeevil!

Check the date - it's 6/6/6. No, I don't think the world's going to end any more than I think demons are hoarded in room 666 at school. But it's still an interesting date, and figured I should note it anyway.