Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Over hamachi I had much more success. Even so 1/2 the games wouldn't allow someone to join with a lockup, needing the client to recreate a character and retry.
Once joined into the lobby and game started, it seemed ok.
So I can suggest firewall off, hamachi, and retrying hosting and joining.
We've largely stopped using Hamachi for gaming as it doesn't seem to work all that consistently for games for whatever reason.
- Hamachi
- Evolve
- Forwarding port 25565 (standard Minecraft port I use for most games like this)
- Forwarding less common ports
- Turning firewall off completely
- Connecting over a LAN
- Yes I understand how to use ipconfig to get my real IP and my mask, and which to use
- Yes I forwarded both UDP and TCP
- Yes I've tried on multiple computers with mixed results
- Yes I've tried reinstalling
Are you sure there's no firewall set up on your hub/router directly that's blocking the packets? Have you disabled any antivirus as well?
If you want to be a true detective you can always use a packet monitor like Wireshark to confirm that the packets are being sent on one computer and received by another without being blocked/dropped on either one of the machines.
Depending on the port you use too your network may have some preestablished rules that are messing with the packets so they don't arrive.
Anyway, after you try connecting to the server, unblock UDP to the client on the source port, for linux, assuming you can use uPnP, install upnpc, then run.
upnpc -a <local client ip> `lsof -p <pid of client> | grep UDP | sed 's_.*:__'` `lsof -p <pid of client> | grep UDP | sed 's_.*:__'` UDP
and it will forward the UDP port for the client.
Since it looks like the devs watch this (thanks guys for taking your time to help!), have you considered enabling uPnP support directly in the client? It would make most of these connection issues magically go away.
P.S. as an alternative, allow specifying the UDP source port on the client, or open separate UDP listen port on the client. If the server is using port 40000, have the client also listenUDP on 40000.