[Requirements]  [Method One - Prepared Script]  [Method One - Writing Your Own]

[Method Two - Simplicity]  [Ports, References & Links]

Update 12/28/03

I've been getting a steady flow of emails in various regards to this article, thanks for your suggestions & comments. I'm sorry if I haven't replied to you yet, at times I find myself with an incredible workload, during which time my email activity suffers. I'll try to get back to you as soon as I can.

In regards to the 800 series, I'm afraid I do not have one to test myself, so I can't help you a whole lot with that score, I've just been made aware that the same procedures I have used on the 1000 should be possible with the 800. Of course, the major cause of trouble is that in some cases the 800 refuses to appear as a uPnP device. Further research is pending, any help appreciated.

... The Problem

Did you sign up for MSN DSL Service? Did you really want the MSN part attached to that? Sorry, I can't really fix that. However, there is one annoying problem that has plagued it's community for some time now, and that's port forwarding. One of the standard modems that they bundle identifies itself as a "DSL 1000" - it's really a SMC 7401BRA (manufactured by Accton), but that's neither here nor there. If you have a situation where you need to power-cycle the modem, or power is lost regardless, any port forwarding settings are lost, and since MSN's DSL Profile Page has been down for the past several months, with no sign of any change, having to put a variety of forwarded ports back into the Gateway Properties manually - way too much trouble. Think 20 - 100 port forwards, depending on various factors. At least you don't have to open ports for outgoing connections!

... The Solution

However, there are at least two solutions now available, one I created today, the other I discovered later on - having gone to the same forum sometime ago, before the application was developed. To an extent, the latter method negates my solution altogether. However, there are some differences between the two methods, as you'll see.

Method One: Using Intel's uPnP Device Scriptor to create a custom mapping script (script included).
Method Two: Using Jared Jacobs' uPnP Interface software to quickly map ports (and port ranges) as needed.

 STOP!!

Experiencing regular disconnects from MSN, in some cases approximately every 24 hours? Make sure you are not running MSN's DSL Connection Tool - it's obsolete! You'll find an explanation of the problem on DSLR, along with simple removal instructions in the FaQ.

Disclaimer: I will not be responsible if you break your modem, get your service cut off due to any breach of TOS, etc. If you want to forward ports, you are doing so at your own risk! You have been warned.

Software Requirements

For Method One - "Hardcore uPnP Scripting", you'll need Intel's uPnP Tools.
Plus - The Port Forwarding Script: portforwards.dsprj V1.0, 11/02/03 (Right click, Save). Port detail in the appendix.

For Method Two - "Quick Port Adjustment", download Jared Jacobs' uPnP Interface.

Also, grab the .NET Framework V1.1 - if you're using the Windows XP family, and install the various updates, it's highly likely you already have it..

Method One: Intel uPnP Tools (using provided script)

Once you've gone over the following steps, you'll have a prepared script that you can load & run inside of a few minutes, that will set up all the port forwarding entries you will need. This seems long winded at first, but once you've set the script to your liking, it comes down to three steps - Load, Target, Execute.

If you haven't already, extract the toolkit to somewhere on your hard disk, for simplicity I used C:\UPnP as the destination. In said directory, you'll find an application named
Fatal error: Call to undefined function aimgurl() in /var/sites/s/subwolf.org/public_html/v2/articles/tech/dsl1000.php on line 65