http://www.dslreports.com/forum/r21175396 en Wed, 11 Nov 2009 03:37:11 EDT Wed, 11 Nov 2009 03:37:11 EDT http://www.dslreports.com/forum/remark,21178342 jacour : Yes, that is why I am confused. One rule opens port 55XXX to address 192.168.1.150 and the other opens the exact same port to 192.168.1.151. All the other computers in the house grab an IP address via DHCP in the 1.1 to 1.100 range (and we only have two other computers so capacity is not a problem).

I would think that if it worked on the wired NIC it would work on the wireless as well since that is the only apparent difference. I must be missing something.]]> http://www.dslreports.com/forum/remark,21178342 Sat, 27 Sep 2008 14:39:28 EDT http://www.dslreports.com/forum/remark,21176529 Phil : So you have two port forwarding rules, one for your wired NIC and another for the wireless NIC correct?]]> http://www.dslreports.com/forum/remark,21176529 Sat, 27 Sep 2008 00:08:35 EDT http://www.dslreports.com/forum/remark,21175396 jacour : I have my router configured to reserve two static IP addresses for my laptop, one each for my ethernet and wireless port. This works fine, when I do an IPCONFIG I see that they are mapped correctly. I have opened a port for Azureus and provided access to both ports.

The problem is that it works find when connected via the cable but I don't get any remote connections when I undock and go wireless. Is there a reason the ethernet port forwarding works but the wireless does not?]]> http://www.dslreports.com/forum/remark,21175396 Fri, 26 Sep 2008 20:37:49 EDT