Please forgive me because this is my first post on this account; I'm pretty new to this forum.
Anyway as a M.C. player since version 1.3.2, I have been hosting dedicated servers for my friends on my computer at my house since last summer. I only had one instance where people couldn't connect and eventually that small problem I had got fixed.
However, this is a different problem. Last Tuesday (11/6/18) at my college I couldn't connect to my server that was being hosted at my house on the same computer I've been using a spigot build for version 1.13.2 from the website getbukkit.org with a RUNME.bat that uses 2gb of ram, and I've thought either the server crashed or the PC was shut down or restarted. However when I got home this weekend, the computer was left as it was when I left for the week for school.
I can connect to the server while I'm on this server-hosting computer via the IPv4 address and the port that I assigned with it: 22670. However my friends can't get on the server with the public IP address via a No-IP host name (Before this issue I was able to connect to the server with the host name I gave).
My router is a Century-link C2100Z, which is connected to 4th Gen Adtran 324 model modem, and the computer is running a 64-bit OS of Windows 10. I should also note that I am not using any kind of V.P.N. that I downloaded online or enabled any if windows provided them...
Here's what I've done for server preparation:
I've port forwarded my router TCP and UDP to 22670 and 25565 [just because].
I made inbound rules on my Windows Defender firewall for the ports defined above.
As mentioned before I give my friends a No-IP.com free DNS domain that lets them connect to the server.
Now as I mentioned in the title, when I test these ports on sites like canyouseeme.org, or portchecker.com. They will give me messages like "Connection Timed Out" or the connection is closed. Heck, local ports like 80, 8080, and doing a port scan says that ALL of my ports are closed.
Here's what I've done to attempted to fix it:
Googled to find answers - Absolutely no luck.
Turned off Windows Defender firewall temporarily - Didn't work
Rebooted the modem via the Default Gateway login - Didn't fix the problem
Unplugged and Re plugged the modem - Gave me a new public IP address as expected but still no luck
Restarted my computer countless times - Has no effect.
Deleted and recreated port forward rules in the Default Gateway login. - No luck
"" Windows Defender Inbound Rules - ""
Reset my network settings in the Windows 10 Settings Window - Did not change IP address and did not solve ANY issues.
I hope I explained and included everything initially that I needed to help diagnose my issue, I really could use your help. I want to avoid using third-party programs such as Evolve and/or Hamachi.
UPDATE: For some interesting reason, when I set the server-ip in the server.properties file to be blank, and I start up the server. Port checker websites state that the port for the server, 22670, is open? The other ports such as 80, 25565, and so forth are still closed.
I've also investigated into my ipv4 router on my modem and the security state is set to low, stealth mode disabled, and I even made rules for TCP and UDP for ports 22670 and 25565. The ipV6 firewall on the other hand is currently blocking incoming traffic, and allowing outgoing traffic. I'm hesitant to allow incoming traffic into the IPV6 firewall because it will allow WAN networks to come into the LAN network...which sounds like something I REALLY do not want...
Anyway as a M.C. player since version 1.3.2, I have been hosting dedicated servers for my friends on my computer at my house since last summer. I only had one instance where people couldn't connect and eventually that small problem I had got fixed.
However, this is a different problem. Last Tuesday (11/6/18) at my college I couldn't connect to my server that was being hosted at my house on the same computer I've been using a spigot build for version 1.13.2 from the website getbukkit.org with a RUNME.bat that uses 2gb of ram, and I've thought either the server crashed or the PC was shut down or restarted. However when I got home this weekend, the computer was left as it was when I left for the week for school.
I can connect to the server while I'm on this server-hosting computer via the IPv4 address and the port that I assigned with it: 22670. However my friends can't get on the server with the public IP address via a No-IP host name (Before this issue I was able to connect to the server with the host name I gave).
My router is a Century-link C2100Z, which is connected to 4th Gen Adtran 324 model modem, and the computer is running a 64-bit OS of Windows 10. I should also note that I am not using any kind of V.P.N. that I downloaded online or enabled any if windows provided them...
Here's what I've done for server preparation:
Now as I mentioned in the title, when I test these ports on sites like canyouseeme.org, or portchecker.com. They will give me messages like "Connection Timed Out" or the connection is closed. Heck, local ports like 80, 8080, and doing a port scan says that ALL of my ports are closed.
Here's what I've done to attempted to fix it:
I hope I explained and included everything initially that I needed to help diagnose my issue, I really could use your help. I want to avoid using third-party programs such as Evolve and/or Hamachi.
UPDATE: For some interesting reason, when I set the server-ip in the server.properties file to be blank, and I start up the server. Port checker websites state that the port for the server, 22670, is open? The other ports such as 80, 25565, and so forth are still closed.
I've also investigated into my ipv4 router on my modem and the security state is set to low, stealth mode disabled, and I even made rules for TCP and UDP for ports 22670 and 25565. The ipV6 firewall on the other hand is currently blocking incoming traffic, and allowing outgoing traffic. I'm hesitant to allow incoming traffic into the IPV6 firewall because it will allow WAN networks to come into the LAN network...which sounds like something I REALLY do not want...