I would also want to share the same issue as i've been reading around the internet and here, and I SEE MANY PEOPLE HAVING THE SAME PROBLEM: I port forwarded before, with Win XP. i know the essentials basics of how it works and which are the steps... But now that i have Win7, i cant get port 26900 (ejamming program) to unblock. I have an ARRIS modem. We are 2 people using it, but i disconnected completely the other pc everytime i tried to unblock this ports and use the program. I have a static IP and the other pc doesnt. I already tried the following: 1- DMZ with my IP address (which is Static, by the way)! My router wasnt possibly interfeering and still my ports were blocked. So IT HAS to be my computer. 2- Disabled and even UNINSTALLED all firewalls and antispywares, as well as disabled completely Windows firewall. (i had the exceptions in both win firewall and antivirus programs for this program and i created inbound rules for this ports, both TCP and UDP). 3- Once i disabled the Win firewall and, as by magic, i thought THERE was the problem! the door was unblocked. but after 5 minutes, just to make a test, i got WIn firewall on again and then off, and never more i got the port open... So, unless i can´t see somethign very obvious here, there is something WRONG with this system. 4- All the IP's are matching, the number of ports were checked over and over again... The door unblocked once and got blocked again IN THE EXACT SAME CONDITIONS! I HAVE SEEN MANY PEOPLE TRYING TO GET THIS SOLVED, SO I WOULD ENCOURAGE SPECIALISTS TO TRY TO NOT THROW SAND TO OUR EYES WORKING AROUND THE BASICS OF THIS PROBLEM AND NOT BEING OF ANY HELP. If you cant figure it out, at least assume here that its a WIn 7 problem, because it most likely is. So, i would advise people on Microsoft to take a look at this issue more carefully and dont discard people has they are doing the most basic error. I would like very much to see an effective reply to this thread, but i must say im not seeing it happen, which is very disrispectfull and unprofessional from Microsoft. So if no one from microsoft there can answer to their own creations, what are we dealing with here?! DOES SOMEONE KNOW HOW TO GO AROUND THIS ISSUE, OTHER THAN UNINSTALLING WIN 7?! Thanks for your time.Rui

1. Don't disable the Windows Firewall service on Windows 7, it is a required service. 2. To disable the firewall, run wf.msc and then disable the firewall for each profile, (public, private, domain). 3. We don't know where the port forwarding process is failing. Some steps to narrow this down: a. Take a network capture using Network Monitor and see if the TCP packets are hitting the Windows 7 machine in both a working and non-working scenario. If the packets are not hitting the machine during a failure, the the issue is likely related to the broadband router, the cabling, the NIC, or filter drivers loaded lower in the network stack than the Netmon driver. (Antivirus, Intrusion Protection System, etc.) b. if the packets are consistently reaching the machine, is the machine responding to the packets? In a new TCP session, you should see an inbound SYN and an outbound SYN/ACK. If this is not happening, then possibly the connection is failing below TCP. Filter drivers are the most likely cause (Antivirus, firewall software, IPS, etc.) c. If you do see the TCP responses, then it is possible that there is an application issue that is not specifically caused by network issues. 4. Use netstat -an | findstr <listeningPortNumber> This will show you if there is a listener on X port. If there is no listener, then the connection will fail. This points to an application issue.Sumesh P - Microsoft Online Community Support

It appears that you are fairly upset with the experience so far, so I am going to assume that anyone that provides suggestions and/or recommendations will most likely not meet the level of response you are expecting... I would tend to agree with Sumesh's recommendations. In my opinion, I would want to make absolutely sure that the packets are making it to the Windows 7 box before proceeding with any troubleshooting on that computer. This can be easily accompished by capturing network packets using a another computer on the same segment by having both systems connected via a hub (to ensure you are on the same collision domain). Once you determine that the packets are making it to the Windows 7 computer, following the steps Sumesh recommended should be able to narrow down the problem. Visit: anITKB.com, an IT Knowledge Base.