I was wrong, virtual server is the right place for the mule rule...
As far as that goes, you didn't do the port range correctly.
You put port 6260 as the private and 6261 as the public.
Try putting 6260 in both fields.
(I'm thinking you were trying to do the port range idea I recommended, and after more study, I'd say that was wrong on my part too, I have a range setup on my 2wire, not sure why I did that, but 2wire is weird and maybe I had to tell it to end on 6261 to actually get it to open 6260 or something.)
Outside of that, are you 100% sure your computer is using 192.168.0.100 (maybe that just isn't the right IP address. Maybe that's a printer or the Wii, or another computer)
On the Windows Machine run CMD (command prompt) and type "ipconfig" at the command line. Put the reported IP address in the virtual server rule.
If you're trying to use the Mac to host, 1 Click on Apple Menu>System Preferences>Network>TCP/IP.
You'll see the correct IP address there.
You can only have one computer set to host at a time to my knowledge. Limitations of manual port forwarding. If you want to host from the other computer you have to go back in and change the IP address to that PCs IP in the rule on the router. Also, the IP address can occasionally change and when I go to my gf's house, I sometimes have to reconfigure the router because my computer got a different address from the last time I was there. (usually gets the same one, but not always.) Appears the D-Link doesn't support static routing inside the LAN.
Honestly, if I were in your place, I'd try getting rid of the D-Link and use just the newer netgear, it should have nearly double the range and is much more configurable than the D-Link. You can setup permanent IP addresses for your devices if you choose. I get that maybe you're using the netgear as a wireless repeater, but maybe that isn't needed, have you tried just using the netgear solo? Maybe it can do it all.
I'm honestly not impressed with that particular D-Link. It is the first router I have ever seen that doesn't let you see all the IP addresses of the different devices that are connected to in a client list somewhere. That to me is practically scarey. No way to monitor what is hooked into your LAN, what if someone cracks your security? Even my 2wire, junk that it is, gives me a client list, and the IP addresses assigned to each device. D-Link actually tells you that you have to look it up on the devices individually, not all devices even have a way to look it up, so if you need to know to IP address of your Wii, to bad, you're stuck.
Range limits are why my gf has my linksys and I'm using the 2wire here at my house. I had the 2wire at her house with a repeater. It proved unstable and annoying, and she isn't the most technical, so she just got tired of trying to use it. The linksys can cover the whole house, no repeater needed, more stable, etc.
The 2wire covers my whole house just fine. (The difference seems to be that there are more metals creating interference with the signal at her house, just needed a stronger transmitter to cover the same ground, our houses are the same size.)
The following is direct from D-Link's website concerning making a port forward...
To allow traffic from the internet to enter your local network, you will need to open up ports or the router will block the request.
Because our routers use NAT (Network Address Translation), you can only open a specific port or ports to one computer at a time. For example: If you have 2 web servers on your network, you cannot open port 80 to both computers. You will need to configure 1 of the web servers to use port 81. Now you can open port 80 to the first computer and then open port 81 to the other computer.
For the DI-514, DI-524, DI-604, DI-614+, DI-624, DI-704P (revC), DI-704UP, DI-754, DI-764, DI-774, and DI-784:
Step 1 Open your web browser and enter the IP address of your D-Link router (192.168.0.1). Enter username (admin) and your password (blank by default).
Step 2 Click on the Advanced tab at the top and then click Virtual Server on the left side.
Step 3 Check Enabled to activate entry.
Step 4 Enter a name for your virtual server entry.
Step 5 Next to Private IP, enter the IP address of the computer on your local network that you want to allow the incoming service to.
How can I find the IP address of my computer?
Step 6 Choose Protocol Type - either TCP, UDP, or both. If you are not sure, select both.
Step 7 Enter the port information next to Private Port and Public Port. The private and public ports are usually the same. The public port is the port seen from the WAN side, and the private port is the port being used by the application on the computer within your local network.
Step 8 Enter the Schedule information.
Step 9 Click Apply and then click Continue.
