Member Avatar for jonnyboy12

Hello all. I have been trying to get port forwarding going for 3 days with my d link DIR-628 router. Ive been checking to see if my changes to my dlink settings have taken effect at this web site and many similar. http://www.canyouseeme.org/ . I usually type in my local ip number into my browser. that takes me to the dlink login page. then i go to advanced -> port forwarding, and i add in my local ip address and specify the port numbers for tcp and udp. I save the settings and restart. Then i go check and no matter what i do the ports will not open!! i cant stand it. I close all firewalls too. Is there something i should know about this that was in the dlink fine print. Please help before i go mad.

  • 3 Contributors
  • 5 Replies
  • 1K Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by CimmerianX

Dani AI

Generated

The notes from , and point to two broad classes of problems: the service on the PC is not actually reachable on the LAN, or the router/ISP is preventing external connections. The checklist below covers the less-obvious causes and quick, practical checks that were not yet shown in the thread.

Confirm the service is listening on the host and bound to the correct interface. On Windows and Linux, list listening sockets and the owning process to ensure the server binds to the LAN address (or 0.0.0.0) rather than only to localhost (127.0.0.1). Example commands:

Windows (elevated):
netstat -anb

Linux:
ss -ltnp
ss -lunp
lsof -i :<port>

If the process listens correctly, verify reachability from a different machine on the same LAN using the host's LAN IP (not the router's admin IP). If that succeeds but external checks still fail, check the router WAN address: a private WAN IP (10.x, 172.16–31.x, 192.168.x) means the ISP is doing carrier‑grade NAT or you are double‑NATted, which prevents standard port forwarding. Also look for router-side conflicts such as remote-management using the same external port, protocol mismatches (TCP vs UDP), wireless client/guest isolation, or missing DHCP reservation/static host mapping that lets the internal IP change. Review router NAT logs and the NAT table if available, and reboot both host and router after changes.

Most persistent failures trace back to one of these: the server bound only to localhost, the internal IP changed, router blocking/conflicting service, or ISP CGNAT. Addressing those typically restores port forwarding.

Recommended Answers

All 5 Replies

Member Avatar for rch1231

Hello,

Can you provide a little more detail about what port you are trying to forward to what IP address inside your router?

Port forwarding is normally used when you want the WAN IP address of the router to forward a port to a specific IP inside your local network.

For example if your routers external IP address is and you want to set up a web site on your local system (at IP address ) then you want any port 80 traffic that hits your router, from outside (the internet), to be forwarded to that system. You would set up port 80 forwarding to IP port 80.

Many routers have what is referred to as a DMZ host which is the default system that can be accessed from the internet.

Does that help?

Member Avatar for CimmerianX

Make sure you have the latest firmware on the unit. Ver 1.25NA (if you're in North America)

Double check your internal IP. What ip are you forwarding into? Is this IP static on the the device? Can you access that Port's service from another system inside your network?

Member Avatar for jonnyboy12

im using the internal ip for setting up port forwarding, and no i cant access my port from computers in my network, i tryed to use a chat prorgam in c++ and my computer wont recognise my internal ip address, but on the other computer it does fine. Could it have anyhting to do with wireless

Member Avatar for rch1231

Hello,

You should not need port forwarding inside your local network. It may be the firewall on the computer you are trying to connect from. Try turning off the firewall or telneting to the ip and port. For example to telnet to port 80 on IP you would use:

telnet 192.168.0.3 80

and see if you can connect.

Member Avatar for CimmerianX

I would help to know what is the inside ip of the host running the service.
What service/port is it?
Is the IP static?
From another host on the network, can you telnet to that ip and port (see rch1231's post above).

If you can't get to the port from another host on the inside network, then the dlink doesn't come into play here yet. There is a problem on that host itself.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.