• There is NO official Otland's Discord server and NO official Otland's server list. The Otland's Staff does not manage any Discord server or server list. Moderators or administrator of any Discord server or server lists have NO connection to the Otland's Staff. Do not get scammed!

Ports and ips

Fifflaren

Art of Conquest
Joined
Dec 11, 2018
Messages
154
Solutions
1
Reaction score
50
Im gonna start this post off by saying idk if this is where I should put this but if its wrong Ima try to be better next time..

Ok so my problem is really weird I have googled the whole night for solutions but I havent found anyone with the same problem. I opened my ports and tested them on multiple porttesting websites, so Im 100% sure they are open. So everything looks fine until now but this is were it gets a little strange. I can connect to the website and the server using my local IPV4, I tested my local ipv4:80 and that worked out but ipv4:79 didnt work so in my knowledge that tells me once again that the port is indeed open, but I cant use my IP, my WAM IP the ip you get on "whatsmyip.com". Like I dont know if I explained this properly or understandable but tha problem is basicly that it seems like my WAM IP cant get information from my local ip where the ports are open.

Like if you have any idea on whats up I would be so damn graeteful thanks in advance @otlandcommunity ^^
 
Solution
S
Code:
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost...
Did you configure your router to forward requests on port :80 and :79 to your machine hosting the server and website?
Ye, the 79 was just to show that the 80 is open and "working" but ye they are forwarded to this pc, the weird thing is that if I force the website to open with my WAM IP it still wont connect with the WAM IP but with the local IPV4.
 
Then it could still be a firewall issue perhaps..
Ye thought about that, but firstly it would tell me if it was blocked on yougetsignal.com but I get this "Port 80 is open on 188.151.70.65. " but I still thought it could have been the firewalls so I turned the one in the router to allow everything and got 100 of varning msgs about how it could fck me over but I went with it and then turned my Mcafee off wich have full control over my firewall so I had no protection at all but still didnt work. Like I know it sounds like me being lazy and not listening to you @Forby but its legit something wrong here and I have no idea what. Like everything was working fine last time i made an ot but then we changed to a new router and now it wont work.
 
Last edited:
I can open a connection to 188.151.70.65 and it shows me the website. So somehow a request to that IP address from your computer is being sent elsewhere? Does your browser give an error when visiting?
Post automatically merged:

You could have a look at NAT loopback and see if that is causing your problem: Hairpinning - Wikipedia (https://en.wikipedia.org/wiki/Hairpinning).
Wait, so its an error because the port is open from my old and new router, like Im so tired right now I cant thinkt Im just adding what I saw on the wiki and what I know about my routers XD sorry if im just out rambling but did I understand you correct that you can connect to the website? And if you can would you like to help test the server as well?
 
See if there is an option on your router to enable "NAT loopback". Yes, I can connect to your website. What port is your server on?
My server is a 10.98 server with the ports 7171 and 7172
Post automatically merged:

See if there is an option on your router to enable "NAT loopback". Yes, I can connect to your website. What port is your server on?
And you know thats the standard website you get with znote tibia layout Im not that untalanted that I think thats good XD Just had to get it out ther incase you know ;)
 
See if there is an option on your router to enable "NAT loopback". Yes, I can connect to your website. What port is your server on?
Damn cant find the NAT loop thing so I googled it with my router module and first thing I found is that its not supporting NAT loop
Post automatically merged:

I'm having trouble connecting to 7171, 7172. I'm not using a Tibia client but the connection seems to be blocked in any case.
Port 7171 is open on 188.151.70.65. should work :(
Post automatically merged:

I'm having trouble connecting to 7171, 7172. I'm not using a Tibia client but the connection seems to be blocked in any case.
Or talking about ips in config.lua should I put the global ip there or should I put the local there?
 
I cant come any closer to connect then the charlist when using the public ip, I can join it when I have it set to local ipv4
in C:\Windows\System32\drivers\etc
you will find a file with name hosts open it with administrator mode using text editor
inside it you will find this
Code:
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

# localhost name resolution is handled within DNS itself.
#    127.0.0.1       localhost
#    ::1             localhost
just add this line
Code:
localhost   192.168.1.5        # should be localhost:192.168.1.X IPV4 ADDRESS
don't forget to be sure you added in config.lua your public IP Address and open the ports too through firewall
 
in C:\Windows\System32\drivers\etc
you will find a file with name hosts open it with administrator mode using text editor
inside it you will find this
Code:
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

# localhost name resolution is handled within DNS itself.
#    127.0.0.1       localhost
#    ::1             localhost
just add this line
Code:
localhost   192.168.1.5        # should be localhost:192.168.1.X IPV4 ADDRESS
don't forget to be sure you added in config.lua your public IP Address and open the ports too through firewall
Should I use localhost 192.168.1.5 even tho my router is 192.168.1.1 ?
 
no use your own ipv4
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
localhost 192.168.1.228 # should be localhost:192.168.1.X IPV4 ADDRESS

so thats it?
Post automatically merged:

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
localhost 192.168.1.228 # should be localhost:192.168.1.X IPV4 ADDRESS

so thats it?
Have never done anything or didnt even know this file exsisted, sorry if Im a lil behind :p
 
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host

# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
localhost 192.168.1.228 # should be localhost:192.168.1.X IPV4 ADDRESS

so thats it?
Post automatically merged:


Have never done anything or didnt even know this file exsisted, sorry if Im a lil behind :p
no problem :D, yes try i can try now give me 1 min
 
Back
Top