Need help: 0.5-3kB/s downloads are irritating

[Ultima]

[T]he following case example might be of use to illustrate the process more clearly:

* You have a modem that acts as a router. A dedicated router (router A) is connected to it. Another dedicated router (router is connected to router A. Your computer is connected to router B.

* The modem's routing subnet starts with 192.168.1.x. It forwards the port specified in µTorrent to router A, which is at IP address 192.168.1.5 on the modem's subnet.

* Router A has a static IP set to 192.168.1.5. Its own subnet starts with 172.16.1.x. It forwards the port specified in µTorrent to router B, which is at IP address 172.16.1.3 on router A's subnet.

* Router B has a static IP address set to 172.16.1.3. Its own subnet starts with 10.0.0.x. It forwards the port specified in µTorrent to your computer, which is at IP address 10.0.0.6 on router B's subnet.

* Your computer has a static IP address set to 10.0.0.6, and because the port was forwarded from the modem to router A, and from router A to router B, then from router B to this computer, the port checker considers your client to be connectable.

Please be aware that that was just an example. Many conditions, including the IP addresses, the number of devices on your network setup, or how everything is connected, will most likely differ from the example.

Just like your computer gets its own IP address on the router's subnetwork, the router gets its own IP address on the modem's network. When you connect to your router's configuration, you're connecting through your router's subnetwork, which is different from your modem's subnetwork. So the answer to your question is "no" -- you're going to need to find your router's IP address on your modem's subnet if you want to forward it properly (and my guess is that it's going to start with 10.0.x.x).

[swollenpickles]

Cool, I've just got the green network ok button! It was the dlinks IP that was screwing me up. Thanks for you help on this.

[Ultima]

Good to hear! *phew*