F5F Stay Refreshed Power Users Networks Unfamiliar firewall restrictions on a Minecraft server

Unfamiliar firewall restrictions on a Minecraft server

Unfamiliar firewall restrictions on a Minecraft server

Pages (2): 1 2 Next
E
EnderBroF
Junior Member
2
01-21-2016, 05:40 AM
#1
You're facing access issues with your Minecraft server setup. Besides Windows Defender, common firewalls to consider disabling include Windows Firewall, third-party antivirus solutions, and network-level security tools. Ensure you check both local and global settings for restrictions.
E
EnderBroF
01-21-2016, 05:40 AM #1

You're facing access issues with your Minecraft server setup. Besides Windows Defender, common firewalls to consider disabling include Windows Firewall, third-party antivirus solutions, and network-level security tools. Ensure you check both local and global settings for restrictions.

S
65
02-01-2016, 02:41 AM
#2
I'm checking if your ISP is restricting certain ports. Could you clarify the router settings, such as port forwarding rules or any access restrictions you've set up?
S
SUPERSPIDERBOB
02-01-2016, 02:41 AM #2

I'm checking if your ISP is restricting certain ports. Could you clarify the router settings, such as port forwarding rules or any access restrictions you've set up?

D
DarkNebulaOG
Junior Member
30
02-08-2016, 01:48 PM
#3
I can access port 11169 exclusively, while others receive "No route to host" messages.
D
DarkNebulaOG
02-08-2016, 01:48 PM #3

I can access port 11169 exclusively, while others receive "No route to host" messages.

X
Xofreu1603
Member
86
02-08-2016, 09:04 PM
#4
They are providing their 192.168.0.x network address or their real public IP.
X
Xofreu1603
02-08-2016, 09:04 PM #4

They are providing their 192.168.0.x network address or their real public IP.

D
Depths_
Junior Member
48
02-09-2016, 02:36 AM
#5
Port 25565 is being redirected to port 11169 for external access. Users should use port 25565 instead of 11169. Public IP addresses should be used for connectivity, not private internal ones like 192.168.x.x. It’s unnecessary to block these internal IPs because they’re not reachable from outside and ISPs typically don’t send traffic to them.
D
Depths_
02-09-2016, 02:36 AM #5

Port 25565 is being redirected to port 11169 for external access. Users should use port 25565 instead of 11169. Public IP addresses should be used for connectivity, not private internal ones like 192.168.x.x. It’s unnecessary to block these internal IPs because they’re not reachable from outside and ISPs typically don’t send traffic to them.

H
HunterGamer972
Junior Member
4
02-09-2016, 09:30 AM
#6
I adjusted the server's port to 11169 myself. I also modified the forward port to 25565 in both directions, yet the connection using {publicIP}:11169 fails. They are now encountering a timeout error.
H
HunterGamer972
02-09-2016, 09:30 AM #6

I adjusted the server's port to 11169 myself. I also modified the forward port to 25565 in both directions, yet the connection using {publicIP}:11169 fails. They are now encountering a timeout error.

S
shmorgysporg
Member
212
02-14-2016, 05:59 PM
#7
The screenshots indicate forwarding port 25565 to port 11169. This means users need to access port 25565, not 11169. The server should be set to listen on port 11169. [public-ip]:25565 —> [internal-ip]:11169
S
shmorgysporg
02-14-2016, 05:59 PM #7

The screenshots indicate forwarding port 25565 to port 11169. This means users need to access port 25565, not 11169. The server should be set to listen on port 11169. [public-ip]:25565 —> [internal-ip]:11169

V
VortexAh
Member
160
02-15-2016, 02:32 AM
#8
They might need to switch their port to 25565, even though you're limited to 11169 from your IPv4 address.
V
VortexAh
02-15-2016, 02:32 AM #8

They might need to switch their port to 25565, even though you're limited to 11169 from your IPv4 address.

F
fishy37
Member
131
02-15-2016, 09:37 AM
#9
You're sending traffic from port 25565 to 11169. The accessible external port remains 25565, not 11169. This means the server handles translation between the public and internal ports without needing to worry about the specific port number used.
F
fishy37
02-15-2016, 09:37 AM #9

You're sending traffic from port 25565 to 11169. The accessible external port remains 25565, not 11169. This means the server handles translation between the public and internal ports without needing to worry about the specific port number used.

C
CozyTea
Member
106
02-21-2016, 03:32 AM
#10
Server port is back at 25565. Forwarding remains at 25565 in both directions. Connection issues persist. No apparent firewall blocking it, though I’ve disabled Windows Defender and haven’t altered any settings shown. Previously trying dynamic IP caused router failure and required a reset.
C
CozyTea
02-21-2016, 03:32 AM #10

Server port is back at 25565. Forwarding remains at 25565 in both directions. Connection issues persist. No apparent firewall blocking it, though I’ve disabled Windows Defender and haven’t altered any settings shown. Previously trying dynamic IP caused router failure and required a reset.

Pages (2): 1 2 Next