Sign in with
Sign up | Sign in
Your question
Solved

Portforwarding Issue (Unusual)

Tags:
  • Internet Service Providers
  • Linksys
  • Routers
  • Port
  • Cisco
  • Port Forwarding
  • Networking
  • Command Prompt
Last response: in Networking
Share
December 24, 2013 8:31:10 AM

Hi, I know portforwarding is probably one of the most annoying things to explain to people, but I think I'm an unusual case here.

I've made my IP static.
I've portforwarded correctly using my IPv4 from CMD.
I've disabled software that could be blocking the port.

And yet, I can't get anyone to connect.

Earlier this year, I was using a smaller ISP run from in my town. Another ISP came along and offered a better deal, so I switched.
After the switch, I haven't been able to Port Forward.
I've checked and that port isn't blocked.
I flushed DNS and used renew and release in CMD. I don't know what else to do.

I contacted the router manufacturers (cisco EA4500) and they want to charge $35 to fix my issue, which isn't going to happen.
Using cloud-connect software if that helps.

My gateway and IP are awfully strange too. They used to be 192.1.1.* but I did a hard reset of the router and now it's this.

More about : portforwarding issue unusual

December 24, 2013 8:55:32 AM

That is an unusual IP address to be assigned by a Cisco home networking router. I suspect your PC is not receiving its IP address from your router.

For it to issue you a 10.136.*, that has to be the setting in the DHCP setup in your router, but I bet it is set to the 'ol familiar '192.168.1.x'.

Double check that. Because you're not on your Local Network, nothing is working because Cisco defaults ports that can be forwarded to '192.168.1.___ where you can only fill in the blank.

If that is the case, check your 'Automatically receive IP Address' from DHCP setting in your IP4 network setting. I bet it is off.

Since you're behind your router, go ahead and disable your IPv6 network setting while you're in your network connection setting, that's known to cause some issues. IPv6 isn't needed unless you have bazillions of devices behind your router.
m
0
l
December 24, 2013 9:32:20 AM

bigwoofer said:
That is an unusual IP address to be assigned by a Cisco home networking router. I suspect your PC is not receiving its IP address from your router.

For it to issue you a 10.136.*, that has to be the setting in the DHCP setup in your router, but I bet it is set to the 'ol familiar '192.168.1.x'.

Double check that. Because you're not on your Local Network, nothing is working because Cisco defaults ports that can be forwarded to '192.168.1.___ where you can only fill in the blank.

If that is the case, check your 'Automatically receive IP Address' from DHCP setting in your IP4 network setting. I bet it is off.

Since you're behind your router, go ahead and disable your IPv6 network setting while you're in your network connection setting, that's known to cause some issues. IPv6 isn't needed unless you have bazillions of devices behind your router.



Okay, I've changed the DHCP settings and now I'm on the good old 192.168.1.*, thank you for that.
Still not able to forward ports though.
m
0
l
Related resources
December 25, 2013 8:08:55 PM

So start from the beginning, what are you trying to do, what application are you trying to allow to see this computer from the outside world?
m
0
l
December 29, 2013 9:11:14 AM

Let's start with how port forwarding work - the basics:

You have a hardware firewall, this blocks all incoming requests and with "modern" firewalls, your connection is invisible to the internet.

Only outbound requests (made from your pc on your local network or the firewall itself, like for time syncing to a clock on the internet) are 'seen' on the internet, and then all inbound packets are allowed resulting directly from those outbound requests.

This brings us to 'Port Forwarding', and is an exception to the above simple way to describe how your firewall acts.

Using your 'Port Forwarding' setting in your router, you're specifying that specific port, when requested by a computer OUTSIDE your network/firewall (you'll hear this called 'external requests'), to forward directly to the computer identified by the IP address you specify on your local network.

This is why you don't need to bother with port forwarding for machines 'behind' your firewall.

That said, as long as your setting in your Firewall is forwarding the CORRECT UDP/TCP ports to the CORRECT IP address on your local network, then the problem resides elsewhere, like on your local firewall on the receiving machine.

One thing I do is disable the software firewall on my local machines. Why? Because it is:
- inferior to the hardware firewall
- redundant to the hardware firewall
- very good at wreaking havoc with filesharing and other communication I want open between machines BEHIND my hardware firewall

This is your 'Windows Firewall' if you're not aware of what it is.

Now that we have all that explained, yes please share with us what program you're trying to access.
m
0
l
December 30, 2013 11:59:18 AM

Thanks for the reply!
I've disabled Windows Firewall and still no avail.

I'm trying to open a server on the video game Minecraft.
m
0
l

Best solution

December 30, 2013 4:58:42 PM

Ok that makes things a LOT easier to walk through specific setup. Here you go:

1 - type 'what is my ip' into www.google.com search. Google will tell your your IP address. Write it down. That is your IP address people will type in, from OUTSIDE your network to come across the internet and find your Firewall. Many times people's IP address have updated and they don't know it :) 


2 - In your port forwarding setup, forward port 25565 for both UDP and TCP. Here's a screenshot of the setup in my DLINK router
http://prntscr.com/2faj8p

3 - Make sure you're not using 'port triggering', while similar, it's not 'port forwarding'.

Now that you have specific information to check out, let us know what you find.
Share
!