Jump to content

AlolanZygarde23

Members
  • Posts

    5
  • Joined

  • Last visited

About AlolanZygarde23

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    USA
  1. Thank you everyone for your help! I finally got it working, and it turns out the problem was just that I was giving the other person the wrong IP to join the server, and nothing with ESET at all lol.
  2. I just tried it, and it seems that disabling the firewall and then checking the port still shows it as closed.
  3. I tried putting the port in both tabs; that didn't seem to fix it. By the exe, do you mean selecting the folder for the server under where it says applications in the local tab? Or something with inputting an IP in one of the fields? I tried both of those and neither worked, but I may have misunderstood your advice. I also tried opening a port in the windows firewall, for both inbound and outbound, allowing as much as possible for the 25565 port and opened one for the router too.
  4. Thank you for the quick response! I'm in the remote tab, and I don't see any option to change LAN/WAN. I tried switching the port from the local to remote tab and trying that, but that didn't seem to work. Is there a different IP I have to enter? The one for the router? I think the IP for the router is open on the port, but the one for the computer still says it is closed. Do both have to be open in order for people to connect? Attached is a screenshot of the remote tab if that helps. Thanks again!
  5. Hello! I know this issue has been brought up many times, but I have tried many things and it still shows the port as closed when I check it. I have tried creating a rule in both ESET and Windows firewall to allow the connection, but that hasn't seemed to work. Attached are screenshots of the rule I have tried to create to allow the port. I left everything in the remote field completely blank. Any help would be much appreciated. Thank you!
×
×
  • Create New...