Nakvili Posted April 2, 2023 Share Posted April 2, 2023 Hello. I've been suffering for two days without understanding what I'm even doing wrong. So. I decided to run the server on a separate device that will work 24/7. I looked at how to do it all, read a bunch of information and did not see anything complicated. It was not difficult until the time came to open ports 16261 and 16262... First, I opened the ports on the laptop itself (see screenshot) Then, I go to my router, which ASUS RT-AC87U, and start opening ports there to (see screenshot) Yesterday port 16261 was clothed for no reason, but today (04/02/2023) it's magically open, and I can log in into my server. BUT now I have new problems: 1. The port 16262 don't open (see screenshot) 2. My server don't show up in public 3. And my friends can't even see that server is online The hell I am doing wrong?! ps. My IP is static, internal and external. OS Windows 10. Link to comment Share on other sites More sharing options...
thefipster Posted April 2, 2023 Share Posted April 2, 2023 Hi Nakvili, just a hunch, but the ASUS Router Config looks a bit weird to me. The first rule open 16261 and 16262 externally but only 16261 internally Same for the second rule Third rule seems fine, but maybe has troubles because of the first two? Just try one single rule 16261:16262 for both internal and external. Link to comment Share on other sites More sharing options...
Nakvili Posted April 2, 2023 Author Share Posted April 2, 2023 @thefipster, thx for advice. For some reason, my "el'moron-to" router can't bind two Internal port for one rule. And I star dig in that direction. Figured out work only one of rules. And this is first. So, now I want to update the ruter and see if it works Link to comment Share on other sites More sharing options...
thefipster Posted April 2, 2023 Share Posted April 2, 2023 (edited) I don't think you need to upgrade or anything, just define two separate rules, one for each port. Sorry for the confusion, I thought the router would just bind it straight through like 16261->16261 16262->16262 but apparently your router defines it as all external ports go to this internal port per rule. So with two separate rules for each port you're probably okay. Edited April 2, 2023 by thefipster Link to comment Share on other sites More sharing options...
Nakvili Posted April 2, 2023 Author Share Posted April 2, 2023 29 minutes ago, thefipster said: I don't think you need to upgrade or anything, just define two separate rules, one for each port. Sorry for the confusion, I thought the router would just bind it straight through like 16261->16261 16262->16262 but apparently your router defines it as all external ports go to this internal port per rule. So with two separate rules for each port you're probably okay. So it is router fault. Change it on tp-link, bind ports, and it works. it look like this: About your offer with 16261->16261 and 16262->16262. I did it and server completely didn't respond. Link to comment Share on other sites More sharing options...
Nakvili Posted April 2, 2023 Author Share Posted April 2, 2023 It works only if external port 16261 and 16262 together in one rule, and only if the rule is written the value "from to" and not "value one and the second" Link to comment Share on other sites More sharing options...
Nakvili Posted April 2, 2023 Author Share Posted April 2, 2023 So I have another problem (god please kill my suffering as*) Server don't show in PUBLIC, any one has the idea "why"? Link to comment Share on other sites More sharing options...
thefipster Posted April 2, 2023 Share Posted April 2, 2023 Sorry then, that's the only thing I can see from the screenshots. But just to be sure, on your first screenshots the configured device ip was 192.168.1.227 and on the later one with the separate rules the device ip was configured to be 192.168.0.101. Might that be the reason, the server wasn't reachable at all? Link to comment Share on other sites More sharing options...
Nakvili Posted April 2, 2023 Author Share Posted April 2, 2023 3 minutes ago, thefipster said: Sorry then, that's the only thing I can see from the screenshots. But just to be sure, on your first screenshots the configured device ip was 192.168.1.227 and on the later one with the separate rules the device ip was configured to be 192.168.0.101. Might that be the reason, the server wasn't reachable at all? No, it just different router's = different device IP's. Check it with cmd comand ipconfig Now it's all works fine. Just can't figure out why my server don't show in Public List in game... Link to comment Share on other sites More sharing options...
Nakvili Posted April 3, 2023 Author Share Posted April 3, 2023 fix last problem with this little fellow trombonaught 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now