Why if I open my server, it tells me that everything is fine, It load the map, the gameplay, everything, but when I go to the server list I can not find?

I did everything, open ports, allowed the connection to the program, etc.

 

 

that is what appened to console when i open it

 

Welcome to IW5M r21.

http://fourdeltaone.net/ for help and support

Connecting to online services....

Connected to online services.

Executing server config "server.cfg"

Succeeded reading from default.dspl

Loaded 2 map entries

Loading DSR "TDM_default.dsr"...

Loading Succeeded for DSR "TDM_default.dsr"

-----------------------------------

Spawning map: mp_underground, gametype war

Initializing Steam Game Server: game port 27015, auth port 8766, query port 27017, gamedir modernwarfare3, version 1.0.0.0

Steam Game Server initialized as Internet Server.

Steam Master Servers found (1). Server will be Internet Server listed.

[scriptLoader] Loading script GameLog

Spawn map (mp_underground, war) complete.

-----------------------------------

I have the exact same problem!!!!

 

PLEASE SOMEONE FIXXXXXXX

if someone answer me

COMON People Post a fix please

When you're hosting a server, you CANNOT see your own server in Internet List nor LAN.

 

Use "connect ip:port" in console to connect to your own server.

Fix: get another router.

It's not our fault that some routers don't support a query loopback.

Live with it and connect using the internal ip:port, or buy another router.

what port i must write?

Do you have tunggle?

what is it?

its a vpn program to play lan games online. when i have tunggle installed i cant open servers.

no i haven't it

IM stilll having the problem

so when i write connect ip(my ip):port..what port i must write?

you need to write 27015 on the port.

i have the same problem and i can connect to the server bu other people can't.

and if i tell the ip..and port to one friend he can enter on my server?

on your pc you need to put your internal IP and the port.

for your friends you need your external ip and the port

but ask a friend if they can see your server on the server list

ok really thx

but the server is still not visible in the server list so it is not fixed yet

still no fix

fix please

Fix your brain instead of keep bumping this topic!

 

Fix: get another router.

It's not our fault that some routers don't support a query loopback.

Live with it and connect using the internal ip:port, or buy another router.

Fix your router!

Fix: get another router.

It's not our fault that some routers don't support a query loopback.

Live with it and connect using the internal ip:port, or buy another router.

 

What is this term query loopback? Please explain the logic behind this, if possible, so I get to know what exactly is missing.

It's when you ask a masterserver information about servers.

Seems that some routers don't respond to the "->request, query<-, response->, return<-" procedure.

Usually, when you ask information about servers, all it does is to send the request and return you the results. But when you have your own server, you also have to receive a query about your own server, respond to it and then receive it back from the masterserver.

Dedicated server owners are supposed to know what they're doing, since they will be responsible for the game experience that users will get on their servers.

Meaning that whoever can't even use the connect command, shouldn't even be trying to host a dedicated server.

quite simple: some routers don't apply port forwarding rules on the requests you send from your own network, so when it arrives on the router it thinks 'wtf is this', or just handles it like you're requesting the router ip instead

It's when you ask a masterserver information about servers.

Seems that some routers don't respond to the "->request, query<-, response->, return<-" procedure.

Usually, when you ask information about servers, all it does is to send the request and return you the results. But when you have your own server, you also have to receive a query about your own server, respond to it and then receive it back from the masterserver.

Most probably the query on your own server times out and becomes lost (that's why it doesn't show up on your own server list)

A solution for that could be to delay the masterserver timmings, but it would be stupid to delay everyone's serverlist, only because some dedicated server owners can't use the connect command. Dedicated server owners are supposed to know what they're doing, since they will be responsible for the game experience that users will get on their servers.

Meaning that whoever can't even use the connect command, shouldn't even be trying to host a dedicated server.

 

quite simple: some routers don't apply port forwarding rules on the requests you send from your own network, so when it arrives on the router it thinks 'wtf is this', or just handles it like you're requesting the router ip instead

 

...Or some bridging should be there.

 

I got the logic now. Thats was beyond my CCNA's efficiency

 

However, I wonder if some T's are using some workaround, or perhaps that (if any), can be applied in our Network Topology?

However, I wonder if some T's are using some workaround, or perhaps that (if any), can be applied in our Network Topology?

consumer routers are too closed to allow you to directly manipulate the internal firewall rules applied in whatever underlying embedded OS they run