Welcome!

Join our community of MMO enthusiasts and game developers! By registering, you'll gain access to discussions on the latest developments in MMO server files and collaborate with like-minded individuals. Join us today and unlock the potential of MMO server development!

Join Today!

NO-IP help

Junior Spellweaver
Joined
Aug 8, 2014
Messages
164
Reaction score
26
edit the following files with the non-ip ip
network.properties
server.properties
(login) network.properties
login.properties
server.ini

but I do not connect the client I do not know why oh what am I doing wrong someone could help me?
 
Joined
Jul 2, 2012
Messages
790
Reaction score
125
If you edit everything correctly then it must be your firewall that is blocking it. That is the only issue I see if you did everything right either disable your firewall completely or add a rule to the inbound/outbound of your firewall to lets 8888-8889 through.
 
Upvote 0
Junior Spellweaver
Joined
Aug 8, 2014
Messages
164
Reaction score
26
8888-8889 and 27017 in the test pages of ports I get off but the server turns on well and enters localhost so I do not know if they are really open or not
 
Upvote 0
Joined
Jul 2, 2012
Messages
790
Reaction score
125
8888-8889 and 27017 in the test pages of ports I get off but the server turns on well and enters localhost so I do not know if they are really open or not

Most likely I just used 8888-8889 for portforwarding i dont use port 27017 unless i want remote access of mongodb.

Are you using your local IP address not external?

Did you add the ports into your firewall inbound/outbound or turn off firewall on window security?
 
Upvote 0
Junior Spellweaver
Joined
Aug 8, 2014
Messages
164
Reaction score
26
apparently my ports are still closed and I get that error in the console.
sabracx - NO-IP help - RaGEZONE Forums


sabracx - NO-IP help - RaGEZONE Forums
 
Last edited:
Upvote 0
Banned
Banned
Joined
Dec 3, 2010
Messages
1,581
Reaction score
619
Aparentemente esos puertos todavía están cerrados para mí. Lo que no entiendo es que para que me pueda conectar en el servidor local, ¿no debería tenerlos abiertos? porque en localhost si puedo acceder

sabracx - NO-IP help - RaGEZONE Forums


sabracx - NO-IP help - RaGEZONE Forums
How about English?

 
Upvote 0
Junior Spellweaver
Joined
Aug 8, 2014
Messages
164
Reaction score
26
I apologize for my English, when I try to open my ports from modem I can not but probe with an app port forwarding wizard and if it opens them because?
excuse my English
 
Upvote 0
Banned
Banned
Joined
Dec 3, 2010
Messages
1,581
Reaction score
619
I apologize for my English, when I try to open my ports from modem I can not but probe with an app port forwarding wizard and if it opens them because?
excuse my English
Open command line and run this

netstat -na | find 8888
And
netstat -na | find 8889

And post result for both with code or spoiler tag

 
Upvote 0
Joined
Apr 16, 2007
Messages
441
Reaction score
204
correct me if i'm wrong, but isn't No-IP not the local pc's ip? No-Ip is the link assigned to the pc with the wan ip no?

in cmd type ipconfig and use the IPv4 IP for your "configs" then in your service.ini use the No-ip.

also when port forwarding use you Ipv4 ip also to port forward the ports.
 
Last edited:
Upvote 0
Junior Spellweaver
Joined
Aug 8, 2014
Messages
164
Reaction score
26
Open command line and run this

netstat -na | find 8888
And
netstat -na | find 8889

And post result for both with code or spoiler tag

Microsoft Windows [Versión 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Reservados todos los derechos.

C:\Windows\system32>netstat -na

Conexiones activas

Proto Dirección local Dirección remota Estado
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2383 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49185 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49195 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49403 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1434 0.0.0.0:0 LISTENING
TCP 127.0.0.1:5939 0.0.0.0:0 LISTENING
TCP 127.0.0.1:6463 0.0.0.0:0 LISTENING
TCP 127.0.0.1:6543 0.0.0.0:0 LISTENING
TCP 127.0.0.1:28380 0.0.0.0:0 LISTENING
TCP 127.0.0.1:49350 0.0.0.0:0 LISTENING
TCP 127.0.0.1:49351 0.0.0.0:0 LISTENING
TCP 127.0.0.1:50225 0.0.0.0:0 LISTENING
TCP 127.0.0.1:50225 127.0.0.1:50228 ESTABLISHED
TCP 127.0.0.1:50225 127.0.0.1:50243 ESTABLISHED
TCP 127.0.0.1:50225 127.0.0.1:50246 ESTABLISHED
TCP 127.0.0.1:50228 127.0.0.1:50225 ESTABLISHED
TCP 127.0.0.1:50243 127.0.0.1:50225 ESTABLISHED
TCP 127.0.0.1:50246 127.0.0.1:50225 ESTABLISHED
TCP 192.168.1.11:139 0.0.0.0:0 LISTENING
TCP 192.168.1.11:50573 54.149.209.247:443 ESTABLISHED
TCP 192.168.1.11:50575 66.151.33.24:2099 ESTABLISHED
TCP 192.168.1.11:50581 66.151.33.248:5223 ESTABLISHED
TCP 192.168.1.11:50707 104.16.60.37:443 ESTABLISHED
TCP 192.168.1.11:50727 23.236.154.210:443 ESTABLISHED
TCP 192.168.1.11:54332 151.101.1.62:443 ESTABLISHED
TCP 192.168.1.11:54484 173.194.213.188:5228 ESTABLISHED
TCP 192.168.1.11:54492 157.240.14.15:443 ESTABLISHED
TCP 192.168.1.11:55024 104.27.128.214:443 ESTABLISHED
TCP 192.168.1.11:55158 104.31.66.140:443 ESTABLISHED
TCP 192.168.1.11:55616 107.154.146.168:80 ESTABLISHED
TCP 192.168.1.11:55715 107.154.146.168:80 ESTABLISHED
TCP 192.168.1.11:55716 107.154.146.168:80 ESTABLISHED
TCP 192.168.1.11:55717 107.154.146.168:80 ESTABLISHED
TCP 192.168.1.11:55718 107.154.146.168:80 ESTABLISHED
TCP 192.168.1.11:55719 107.154.146.168:80 ESTABLISHED
TCP 192.168.1.11:55724 107.154.238.167:443 ESTABLISHED
TCP 192.168.1.11:55725 107.154.146.169:443 ESTABLISHED
TCP 192.168.1.11:56019 172.217.8.106:443 CLOSE_WAIT
TCP 192.168.1.11:56136 172.217.8.83:443 TIME_WAIT
TCP 192.168.1.11:56191 104.16.58.5:443 ESTABLISHED
TCP 192.168.1.11:56241 104.16.119.50:443 ESTABLISHED
TCP 192.168.1.11:56243 104.16.199.132:443 ESTABLISHED
TCP 192.168.1.11:56248 5.45.77.188:443 ESTABLISHED
TCP 192.168.1.11:56255 157.240.14.35:443 ESTABLISHED
TCP 192.168.1.11:56300 5.45.77.188:443 TIME_WAIT
TCP 192.168.1.11:56304 104.27.128.214:80 CLOSE_WAIT
TCP 192.168.1.11:56305 104.27.128.214:80 ESTABLISHED
TCP 192.168.1.11:56306 104.27.128.214:80 ESTABLISHED
TCP 192.168.1.11:56307 104.27.128.214:80 ESTABLISHED
TCP 192.168.1.11:56308 104.27.128.214:80 ESTABLISHED
TCP 192.168.1.11:56309 104.31.67.140:80 ESTABLISHED
TCP 192.168.1.11:56334 5.45.77.188:443 ESTABLISHED
TCP 192.168.1.11:56335 52.216.1.115:443 CLOSE_WAIT
TCP 192.168.1.11:56336 52.216.1.115:443 CLOSE_WAIT
TCP 192.168.1.11:56338 104.27.128.214:80 ESTABLISHED
TCP 192.168.1.11:56341 52.216.1.115:443 CLOSE_WAIT
TCP 192.168.1.11:56355 104.17.189.5:443 TIME_WAIT
TCP 192.168.1.11:56356 104.17.189.5:443 TIME_WAIT
TCP 192.168.1.11:56368 104.17.189.5:443 TIME_WAIT
TCP 192.168.1.11:56369 104.17.189.5:443 ESTABLISHED
TCP [::]:80 [::]:0 LISTENING
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:1433 [::]:0 LISTENING
TCP [::]:2383 [::]:0 LISTENING
TCP [::]:3389 [::]:0 LISTENING
TCP [::]:49152 [::]:0 LISTENING
TCP [::]:49153 [::]:0 LISTENING
TCP [::]:49154 [::]:0 LISTENING
TCP [::]:49155 [::]:0 LISTENING
TCP [::]:49185 [::]:0 LISTENING
TCP [::]:49195 [::]:0 LISTENING
TCP [::]:49403 [::]:0 LISTENING
TCP [::1]:1434 [::]:0 LISTENING
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:4500 *:*
UDP 0.0.0.0:5353 *:*
UDP 0.0.0.0:5355 *:*
UDP 0.0.0.0:55559 *:*
UDP 0.0.0.0:59048 *:*
UDP 0.0.0.0:59049 *:*
UDP 0.0.0.0:60138 *:*
UDP 0.0.0.0:60791 *:*
UDP 0.0.0.0:61232 *:*
UDP 0.0.0.0:63910 *:*
UDP 192.168.1.11:137 *:*
UDP 192.168.1.11:138 *:*
UDP 192.168.1.11:2177 *:*
UDP 192.168.1.11:5353 *:*
UDP [::]:500 *:*
UDP [::]:4500 *:*
UDP [::]:55560 *:*
UDP [::1]:5353 *:*
 
Upvote 0
Experienced Elementalist
Joined
Sep 23, 2008
Messages
274
Reaction score
88
it is not at the level of windows the problem is on your router (box) that you have to open the ports.

personally i did as you post the photo or you opened the ports 2017; 8888; 8889
and it works very well
 
Upvote 0
Banned
Banned
Joined
Dec 3, 2010
Messages
1,581
Reaction score
619
I write again and if you don't understand a single word go away from that forum else use Google translate or your book dictionary. Do exactly what I post and delete your latest coz it's totally shenanigans

Open command line and run this

netstat -na | find 8888

And

netstat -na | find 8889

And post result for both with code or spoiler tag

 
Upvote 0
(⌐■_■)
Joined
Feb 2, 2012
Messages
681
Reaction score
102
tips:
1st_test it with hamachi ip
2. open cmd and write hdwwiz
3.next then "Install the hardware that i manually blabla ..
4. choose "network adapters"
5. Choose Loopback adapter in microsoft
6.in network panel head to your adapters and open your recently added one
7.
8. open your router page then forward ports with your localip ( the 192.168.1.101 as it's showin in step7)

ps: make sure that have a static ip cuz that short guide not for dynamic one
if so then use hamachi and have fun with your close friends lol

--updated--

i've posted a thread for running a server behind a static ip
 
Last edited:
Upvote 0
Junior Spellweaver
Joined
Aug 8, 2014
Messages
164
Reaction score
26
Open command line and run this

netstat -na | find 8888
And
netstat -na | find 8889

And post result for both with code or spoiler tag
sabracx - NO-IP help - RaGEZONE Forums

using that program, it opens me, but in a normal way, it does not leave it open, however, I put it in the router
sabracx - NO-IP help - RaGEZONE Forums

firewall /off
rules 8888-8889 input and output
 
Upvote 0
Junior Spellweaver
Joined
Aug 8, 2014
Messages
164
Reaction score
26
apparently the problem was that I needed to edit the xmlrpc of gameserver and login thank you very much everyone can close the thread some admin solved the issue.
:):
 
Upvote 0
Back
Top