Port Forwarding

Well. I'm trying to host a Counter Strike: Source server, which uses port 27015. Now, here's some info. On my router/modem, I had the ports forwarded to my old laptop, which I have since gotten rid of -> the server worked fine on my old laptop. Now I just updated the router, it now forwards the ports to this laptop. So I know my router is doing everything fine, as I've triple checked it, and it had worked previously.

Next, just to test, I completely turned off Windows Firewall. But, I checked my ports here -> just checking 27015. It says it's closed. Hmm.

Now, I'm running a fresh install of Windows 7. I've only got Microsoft Security Essentials on this laptop right now, and I've made sure that no other AV is installed through the control panel. MSE doesn't come with any form of Firewall, so that's not the issue. Before, on my Vista laptop, I had simply allowed the program/ports through Windows Firewall, and it worked instantly.

Is there something I'm missing? I went through my installed programs again to check for anything that might have have a firewall, and nothing pops out. I just can't seem to get it to work. Is there something more that I need to do?

When I use

Open Port Check Tool - Test Port Forwarding on Your Router

the IP address of my proxy of my ISP is used, and it shows that the port forwarded is closed. But when I use

Open Port Check Tool

the site uses my public IP address, and the site shows that the port forwarded is open.

I copied the same public IP address to the first site, and the latter shows that the port forwarded is open.

When I search for "what is my IP address" in Google, the first result gives me my public IP address, which when used in the two sites above will result in reporting that the port that I forwarded is open. But when I use sites given in the results, like

What Is My IP Address - Shows Your IP Address

and

What Is My IP Address? Lookup IP, Hide IP, Change IP, Trace IP and more...

they return the IP address of the ISP proxy.

Ztruker said:

I wonder if instead of turning off Windows Firewall, you added an inbound rule to allow the port. That's what I did for my web server which I run on a port other than 80.

This, oddly enough, seems to have fixed it. My mind is completely boggled at why it works.