Firewall/NAT

Hello, I have m0n0wall running as my router at home. I can connect to remote desktop and the utorrent web interface from everywhere I've tried except when I'm at work at Cisco. It seems that m0n0wall is blocking Cisco's ip addresses. I was originally unable to connect to the m0n0wall gui from work but was able to after some fiddling.

How can I allow Cisco ip addresses through the firewall to allow remote desktop and utorrent webui?

It's probably the other way round. Why should m0n0wall block Cisco IPs at default?

You have to be a bit more precise about your problem: What do you want to accomplish and what have you done that you've been able to accomplish it after some "fiddling"?

I was messing with the firewall rules and adding the cisco ip's I saw show ip in the firewall logs. I'm not sure what rule made it work.

Sorry, but that's not really a helpful answer.

Please paste your firewall and NAT rules here so we can have a look.

I have attached my firewall rules.

The rules don't mean much without the NAT table.

But all I need to see is the first rule to be able to say you are asking for trouble.

Here are my nat rules.

You have that open to the world, so it's highly unlikely it's m0n0wall, it's almost certainly egress filtering on Cisco's network not allowing it out.

It looks like it is m0n0wall blocking it.

If 166.70.x.x is your home ip address then you are trying to connect to a port that you haven't opened (53964, 54202, 59339).
Could it be that you are trying to establish a passive ftp connection?

That is my home ip address. I am trying to connect with windows remote desktop. I have opened the port to my computer's internal ip address. Do I need to open the port on the external ip too?

I have opened the port to my computer's internal ip address. Do I need to open the port on the external ip too?

No, as you've already created the necessary NAT rule to establish a connection to port 3389.
However, it seems that the computer you are using at work is trying to establish a connection to a completely different port which obviously doesn't work.

By the way: The firewall rules below the first one are not necessary as you've opened your firewall to anything in the first rule.

None of that traffic you're showing blocked has anything to do with remote desktop. It looks like random Internet noise. Most of it's sourced from some ISP in the UK, the rest of it from "Specific Media", a US company. None of it from Cisco. Take off your allow all rule on the top of WAN, move the 3389 rule to the very top of your rules, enable logging on the 3389 rule, try to connect and then see whether that connection attempt is logged. It's almost certain Cisco doesn't allow people to RDP out to random places on the Internet, that's a security risk most large companies are going to cut off.