Windows 7: Cannot port forward(AT&T), pulling my hair out!

I tried everything, disabling the router's SPI firewall, disabling Windows private and public firewalls, creating a new inbound rule in Windows Firewall, enabling DMZ. Port forwarding refuses to work.

The machine is running Windows 8 x64, AT&T provided Motorola ADSL modem, Linksys WRT54GL (stock firmware).



This is a AT&T business account with dynamic IP.

Did you forward thing ports on the router and point it to the ip address of the computer?

Also verify the pc is listening on that port. If windows use

netstat -aon

Look for the port number with listening on the right side.

Yes, the computer's IP address is 192.168.1.88 and the ports are forwarded to that address.

Going to see what netstat -aon brings up tomorrow when I'm onsite.

Would AT&T blocking all ports be a possibility?

There is always that possibility. I'm not sure if your router support redirection, but if at&t are blocking port you might be able to get around it that way.

Example
I redirect port 45054 to 3389 so to remote desktop in I would use my external ip with port 45054.

You also need to verify that your ip address hasn't changed. Do you use a hostname? I know there are free service out there.

lastly verify that you can connect locally before you attempt over the net.

The client I'm working for is trying to setup DVR for remote viewing, does redirection play well with DVRs?

I don't see why not. Its really just a connection coming in on one port the router sends it to the actual port. A very brod summary.

If this is for a security system I would check there instructions. They might use more than 1 port.

I noticed DNS Servers under ipconfig /all is listed as 192.168.7.254. Shouldn't the DNS Server have the same IP as Default Gateway and DHCP Server (192.168.1.1)?

Most likely but not always. If this isn't a complex network then no because its on a different subnet. Check the router configuration (DHCP server part.) Make sure its identified correctly there.

If ip is set manually check the ipv4 properties on the adapter.

You can also test a public dns like google 8.8.8.8 & 8.8.4.4

Thanks for the quick replies, hopefully I can put an end to this problem and find out the root cause.