Unable to open port 25565 on my Livebox
Solved
drki
-
brupala Posted messages 111194 Registration date Status Member Last intervention -
brupala Posted messages 111194 Registration date Status Member Last intervention -
Hello,
Wanting to open a Minecraft server that requires the opening of port 25565 for use by other users, I faced the impossibility of opening my port 25565 and here are my troubles...
I did some research on how to do it and here is what I've done (in vain)..
I go to my Livebox interface 192.168.1.1
I start by assigning a static IP address to my PC.
So, Desktop-XXX now has the static IP address 192.168.1.10 (it was the generally "fluctuating" IP address it usually adopts)
Next,
I went to my Livebox and in the NAT/PAT tab I created a rule:
Name: Minecraft
Internal Port:25565
External Port:25565
Protocol: both (since my Livebox allows me to do TCP and UDP at the same time.)
IP: 192.168.1.10
the "enabled" box is checked
Note: the box immediately recognizes to whom this IP (192.168.1.10) belongs and automatically replaces it with the name of my PC (Desktop-XXX)...
Now that I have redirected port 25565 to my computer, I need to open my firewalls for this specific port.
At this stage, I do not touch the firewall of my Box, which remains on "medium protection".
I go into the Windows Firewall and configure two connection security rules:
Type of rule: Isolation
Required configuration: Request authentication for incoming and outgoing connections
Authentication method: computer and user (Kerberos v5)
Profiles: Domain/Private/Public are checked
Name: Minecraft
I configure it:
In the "protocol and port" tab I set:
Protocol: TCP
Port pt of term. 1: Specific port/ 25565
Port pt of term; 2: Specific port/ 25565
I repeat exactly the same operation for the UDP protocol
At this stage:
1) my port 25565 is redirected to my computer (since NAT/PAT configuration)
2) My Windows Firewall no longer filters this port (since I requested it by isolating it)
However, I was horrified to find on this site: https://www.yougetsignal.com/tools/open-ports/
That my port 25565 is still closed!!!
I don't understand what I need to do... (if I did something wrong in the previous steps, please let me know)
But I didn't stop there...
Since it wasn't working, I decided to pull out the big guns (don't try this at home!)
I went back to my Livebox interface and configured a DMZ for my PC, so all ports will be redirected to it! Leaving my PC exposed, and out of my rage, I set my LiveBox's internal firewall to "LOW", meaning almost no filtering! You might say... "But it's no longer a PC, it's a Mill!" at this stage...
Well, hang on because the site to check the opening of Port 25565 indicates... that it is still closed!!!
So even by throwing open the windows, it's impossible to open my Port 25565! :)
Can you imagine, I could have been hacked a million times in DMZ + "low" firewall... but no, rest assured Madame la Marquise... your port 25565 is well locked...
Anyway, I don't know where the problem comes from... impossible to open my port 25565... I hope someone can guide me and help me open this darn port because I'm about to crack...
Configuration: Windows / Edge 90.0.818.62
Wanting to open a Minecraft server that requires the opening of port 25565 for use by other users, I faced the impossibility of opening my port 25565 and here are my troubles...
I did some research on how to do it and here is what I've done (in vain)..
I go to my Livebox interface 192.168.1.1
I start by assigning a static IP address to my PC.
So, Desktop-XXX now has the static IP address 192.168.1.10 (it was the generally "fluctuating" IP address it usually adopts)
Next,
I went to my Livebox and in the NAT/PAT tab I created a rule:
Name: Minecraft
Internal Port:25565
External Port:25565
Protocol: both (since my Livebox allows me to do TCP and UDP at the same time.)
IP: 192.168.1.10
the "enabled" box is checked
Note: the box immediately recognizes to whom this IP (192.168.1.10) belongs and automatically replaces it with the name of my PC (Desktop-XXX)...
Now that I have redirected port 25565 to my computer, I need to open my firewalls for this specific port.
At this stage, I do not touch the firewall of my Box, which remains on "medium protection".
I go into the Windows Firewall and configure two connection security rules:
Type of rule: Isolation
Required configuration: Request authentication for incoming and outgoing connections
Authentication method: computer and user (Kerberos v5)
Profiles: Domain/Private/Public are checked
Name: Minecraft
I configure it:
In the "protocol and port" tab I set:
Protocol: TCP
Port pt of term. 1: Specific port/ 25565
Port pt of term; 2: Specific port/ 25565
I repeat exactly the same operation for the UDP protocol
At this stage:
1) my port 25565 is redirected to my computer (since NAT/PAT configuration)
2) My Windows Firewall no longer filters this port (since I requested it by isolating it)
However, I was horrified to find on this site: https://www.yougetsignal.com/tools/open-ports/
That my port 25565 is still closed!!!
I don't understand what I need to do... (if I did something wrong in the previous steps, please let me know)
But I didn't stop there...
Since it wasn't working, I decided to pull out the big guns (don't try this at home!)
I went back to my Livebox interface and configured a DMZ for my PC, so all ports will be redirected to it! Leaving my PC exposed, and out of my rage, I set my LiveBox's internal firewall to "LOW", meaning almost no filtering! You might say... "But it's no longer a PC, it's a Mill!" at this stage...
Well, hang on because the site to check the opening of Port 25565 indicates... that it is still closed!!!
So even by throwing open the windows, it's impossible to open my Port 25565! :)
Can you imagine, I could have been hacked a million times in DMZ + "low" firewall... but no, rest assured Madame la Marquise... your port 25565 is well locked...
Anyway, I don't know where the problem comes from... impossible to open my port 25565... I hope someone can guide me and help me open this darn port because I'm about to crack...
Configuration: Windows / Edge 90.0.818.62
4 answers
-
Sklt
In order for the port to appear open, the server on your PC must be running. -
Thank you for your response, but unfortunately, even with the server running, the website in question still indicates that my port 25565 is closed...
Does the community have an idea of how this works?
Even though the frustration from yesterday has passed, I'm still in a tough spot...
I'm trying the very dangerous method of DMZ plus low Firewall on the Livebox while keeping the server running...
Same problem, my port 25565 is still closed...
It's impossible to access my PC with the following address my.public.address:25565 -
Hello,
first check that your server is listening with a netstat -ab
After that,
I have doubts about the Windows firewall configuration at this level:
I go into the Windows Firewall and configure two security connection rules:
Rule type: Isolation
Required configuration: Require authentication for incoming and outgoing connections
Authentication method: computer and user (Kerberos v5)
It's been a long time since I've dealt with this, but classically, I would have rather added a rule to allow incoming connections on your port 25565, without authentication or anything.
You can temporarily test by disabling the firewall to see if it's the one blocking, as I suspect.
-
I disabled the public network firewall... and there we go, port 25565 is open!
Unfortunately... even after creating two new inbound traffic rules (one TCP and the other UDP), nothing works...
Here is my process:
I reactivate the public firewall (so the port closes...)
Inbound traffic rule
New rule
Rule type: Port
Protocol and port: TCP / Specific local port: 25565
Action: Allow the connection
Profiles: Domain/Private/Public (all checked)
Name: Minecraft
I repeat exactly the same operation for the UDP protocol
Unfortunately, the port remains closed...
New tests, I go back to my two new rules and configure the "Advanced" tab:
Lateral Traversal: Allow lateral traversal
Nothing works, the port remains closed...
Second test, I delete my two old rules (the ones you just denied earlier)
Result, it works!!! Thanks again!
