Clients not seeing server IP

[nyplayer]

Why is it that my Version 9 PC clients do not see the server name or IP ... I have to manually enter them? Instead it is blank. It does not seem to auto discover the servers.

[Fuzzy]

Something blocking broadcasts? That's how the discovery works, so if you've got a firewall blocking them, or separated subnets, discovery won't work.

[stuckless]

If you are crossing the wired/wireless barriers sometimes routers will not pass the multicast packets correctly, or at all. (this is a bug in the router)

If you are on a completely wired network (same subnet) then I suspect, as Fuzzy pointed out, that a firewall is dropping them.

[Monedeath]

Originally Posted by stuckless

If you are crossing the wired/wireless barriers sometimes routers will not pass the multicast packets correctly, or at all. (this is a bug in the router)

That could be working as intended in that case if AP isolation is enabled for WiFi. But that only applies if WiFi is being used in the first place. Then again, direct connection in general probably shouldn't work in that case, but that may depend on how it isolated the wireless device.

[SageWizdom]

In case you haven't solved this, or if someone else finds this thread. Discovery is done on UDP port 31100 and connection on TCP Port 31099. Your server firewall has to allow inbound connections on both of these.