[Seeking help] Ports blocked for whatever the reason


Recommended Posts

Hello everyone, I know I'm new here but I could use some help and there's nowhere else I can really go, besides other forums.

My problem is that something is blocking my pc and I can't really figure what that is, because I am no expert.

I know how to port forward and I've done it before, I don't know when exactly has something changed but apparently all of my ports are suddenly blocked, and I don't know where the problem is.

I am connected to a SMC WBR14-N router, along with a laptop, and 2 more PCs. (I haven't checked yet if the ports there work but I will edit after the post). The last time I had port forward issues was when my Connection type on router was changed on PPPOE I think, now it's set as DHCP Client.

I use no antivirus program and I have recently formatted my PC, disabling firewall on my PC doesn't help either. I assume there's a problem in my router settings but since I am no expert, I prefer to ask here where the problem could be and what to fix.

Thank you for your kind help in advance.

And what does your router plug into? Quite often when users port forwarding issues is because they are behind a double nat.

http://canyouseeme.org is a good place to check if your ports are forwarded. Since doing a test from a machine on the inside is not a valid check and is a nat reflection or loopback and not all routers support that anyway.

Thank you for the reply. Yes I forgot to mention that part. My router is connected to a modem, and I am not sure what settings should modem rule in order to everything work correctly. Modem has PPPoE connection type, UPnP is enabled(as well as on router) and firewall disabled. But I wonder if the firewall is disabled on modem, router should be causing the problem or am I wrong?

Canyouseeme.org worked for me in the past but now it says I am disabled on any port I try.

"UPnP is enabled(as well as on router)"

That is not a modem, modems don't have firewalls/UPnP support - what you have there is a gateway, modem/router combo.

Look on your WBR14 for what its WAN(internet) IP is - if its 10.x.x.x, 192.168.x.x or 172.16-31.x.x then its behind a NAT (router) and for port forwarding to something behind the WBR14 you would have to forward said port to the WAN(internet) port IP on your WBR14 on your "modem"

This is a double NAT, ie a public IP changed to a private twice (double) This is not normally a setup that you would want - look to see if your modem can be setup in bridge mode. So that your WBR14 gets a PUBLIC IP on it.

Or you could just use your WBR14 as a accesspoint (wireless to your network) - this is done by turning off the dhcp server on your wbr14, and connecting it to your "modem" via a LAN port on your WBR14 -- give the WBR lan an IP on your "modems" network 192.168.?.? and then you can connect to that IP to setup the wireless.

Other option if you really want to use your WBR to control port forwarding is to put the WBR wan IP into the dmz of your "modem"

Again if it does NAT its not a MODEM.. There is a lot of confusion of terms out there with terms. Here is what they should be called.

Modem - changes media type, say cable to ethernet - pubic IP is given to device connected to it.

Router - in the home market this is a device that takes public IP on wan interface and allows multiple devices to plug into it on the lan side using private IPs and share the 1 public IP with multiple computers on private IPs

Gateway - this is combination of modem and router. Most every single ADSL, DSL device sold today is a gateway device. You only normally see true modems in the cable internet market.

These are how these terms should be used when discussing home internet connections for sure. If you tell me you have a modem, I would assume you have a router behind it or only 1 device connected to it which has a public IP on it. Quite often user is doing double nat because what they call a modem in front of their router is really a gateway ;)

If you tell me you have a router I would assume you have a device in front of it. If you tell me you have a gateway tells me you only have 1 device that converts your internet connect to a private network. Rarely have to worry about double nat.

Hope this helps.. I would suggest either putting your "modem" into bridge mode which means it really is just a modem, then your router would handle any PPPoE type logins, or put it into half bridge mode where it does the PPPoE login but puts a public IP on the device connected to it. Or just use your WBR as an access point. The double nat option is not the preferred choice - you can run into issues with things behind double nat. If all your doing is outbound browsing the internet, reading email it works not too much of an issue - but if your going to want to do port forwarding then yeah double nat can be problematic.

I have see triple nat and even quadrupedal nats out there -- because the user keeps connecting routers to add more ports or more wireless when all they really needed was switch or accesspoint, etc.

Thank you BudMan for clarification. I had before running the same setup as I have now, but controlling everything through WBR14. I am not sure when that changed but here I am now, I didn't find any setting on my SpeedTouch to put it into bridge mode, how do I archieve my previous setup again?

Lets start by telling us what model equipment you have on your network, we can then bring up instructions for you and walk you through step by step on what to do. or point you in the direction of instructions already made on how to do what you want. unfortunately every manufacturer has a different gui or different command line set to manage their equipment. For example, what I would step you through on a linksys would not be the same on a netgear, or a westell vs a 3com vs a ariens, vs a actiontec, vs etc....

What is the make and model of your "modem" And I can look for instructions for bridge mode.

But look on your WBR - what is its wan IP? 192.168.1.100?? For example - if so on your "modem" put 192.168.1.100 in DMZ, or forward the ports you need say 80 to 192.168.1.100 on "modem" Then on WBR forward 80 to the IP you want, say for example 192.168.2.100

You for sure do not want the same network on wan as lan on the WBR.. So make sure if your "modem" is handing out say 192.168.1 that you change your WBR lan network to be something like 192.168.0 or 192.168.2

That is one option, other option is to control port forwards on your "modem" and then just setup the WBR as accesspoint. This would be the option I would use if I could not put the "modem" into bridge mode.

edit: Well take that back - I would never in a million years stick with what the ISP gave me as a router. I would change out the equipment with a normal modem, or a device I could put in bridge mode. If that was not possible then I would change ISPs so that I could get a public IP on the device I want to use as my edge router. So in a sense no I wouldn't being using WBR as accesspoint. But yes if I wanted to add wireless to my network and what I had was a wireless router, then yes I would use it as an accesspoint and not a router. That is what I currently do ;)

Ok I found these, but its a bit dated I did not see the manual for the 7.4 so I would think its the same.. Is yours a WL model? either way instructions for this should be the same

post-14624-0-37726700-1346274844.jpg

So clearly it can do bridge mode -- I would suggest you call your ISP and have them walk you through putting the device in bridge mode.

That SpeedTouch has very little options and I can't put it into bridge mode manually, I just checked my ISP's forums and looks like I will have to call them. So once they put it in bridge mode, it should work like: my all PCs will be connected to a WBR from where I will be controlling everything, and WBR to SpeedTouch modem.

Yes if they put your speedtouch into bridge mode, then you can control your port forwards at your WBR, it will have a public IP on its wan. No double nat involved.

So you now have PUBLIC IP on your wbr wan interface?

if so then either your ISP is blocking the port? Many isps block such things as 80 and 25 for example. If not blocking and you have public on your router, then either your port forward is not working. Some routers don't like UPnP enabled while doing manual port forwards for example. Or you just have it forwarding to the wrong IP of the machine inside, or your inside machine is not listening on the port or has a firewall blocking the port, etc.

First step is the verify you have a public IP on the WAN. What port are you wanting to forward? is this port listening on your inside box? Simple to test with netstat -an command on that box, can you connect to your service your trying to forward through your router/firewall to from another machine on your network using the private IP of the machine?

Do you have something setup to be in the DMZ of the wbr - you can not have a dmz host and then forward a different port to different machine etc. Atleast many routers are like this.

You sure you set up the forward correctly on the WBR, and not some port triggering rule?? I see this quite often as well with users trying to setup port forwards. Also the box your forwarding to is connected to the WBR, you don't have some other nat behind your WBR do you?

My wbr ip is still the same: 192.168.2.1 to access router, DMZ is disabled. I am quite sure I forwarded ports correctly since I've done it before and I know how things should be set to work correctly, port is assigned to my local IP without any filters, and canyouseeme.org can't access it.

DUDE --- WHAT IS THE WAN IP?? If you saying its 192.168.2 then your still behind a nat, and your speedtouch is NOT in bridge mode.

post-14624-0-22211400-1346353419_thumb.j

is the IP address under your status and WAN show a 10.x.x.x or 192.168.x.x or 172.16-31.x.x then your speedtouch is NOT in bridge mode!!

Well thats a PRIVATE IP address now isnt it -- so NO your forwards are NEVER going to work.. Because the NAT device in front of it is not sending the ports to 192.168.1.64, since your WBR never sees the traffic - it kind of hard for it to forward it to your 192.168.2.x box that you want to see this traffic now isn't it!

If your ISP told you your speedtouch is in bridge mode -- they are IDIOTS!!! because clearly its NOT! Or your WBR router WAN would be a PUBLIC IP, ie NOT 192.168 or 10.x or 172.16-31

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
    • Tor Browser 15.0.17 by Razvan Serea Protect your privacy. Defend yourself against network surveillance and traffic analysis. Tor is a network of virtual tunnels that allows people and groups to improve their privacy and security on the Internet. The Tor software protects you by bouncing your communications around a distributed network of relays run by volunteers all around the world: it prevents somebody from watching your Internet connection and learning what sites you visit, it prevents the sites you visit from learning your physical location, and it lets you access sites which are blocked. The Tor Browser Bundle lets you use Tor on Windows, Mac OS X, or Linux without needing to install any software. It can run off a USB flash drive, comes with a pre-configured web browser to protect your anonymity, and is self-contained. Tor Browser 15.0.17 changelog: All Platforms Updated Tor to 0.4.9.11 Updated NoScript to 13.6.25.1984 Build System / All Platforms Bug tor-browser-build#41821: Update gpg subkeys for boklm Bug tor-browser-build#41827: Update morgan's keychain with renewed key Download: Tor Browser (64-bit) | Tor Browser (32-bit) | 109.0 MB (Open Source) View: Tor Browser Website | Other Operating Systems Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
    • Week One Done
      NovaEdgeX earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      530
    2. 2
      +Edouard
      266
    3. 3
      PsYcHoKiLLa
      148
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!