Friends can't connect - tried FAQs and Google, port forwarding, turning firewall on and off

[Mogechi]

I changed DefaultPort to 7777 in servertest.ini (because the default values didn't work at all) and port forwarded 7777 UDP and 7778-7841 TCP.

 

This is what I get on my server console when my friend (Dogeko) attempts to join.

*** SERVER STARTED ****

server is listening on port 7777

User Dogeko is trying to connect.

Connected new client Dogeko ID # 0 and assigned DL port 7778

testing TCP download port 7778

TCP port test: accept() timed out, client will have to try again

Then I turned windows firewall off and got a different message:

User Dogeko is trying to connect.

Connected new client Dogeko ID # 0 and assigned DL port 7778

testing TCP download port 7778

java.net.SocketException: Socket operation on nonsocket: configureBlocking

        at java.net.DualStackPlainSocketImpl.configureBlocking(Native Method)

        at java.net.DualStackPlainSocketImpl.socketAccept(DualStackPlainSocketIm

pl.java:141)

        at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:

398)

        at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:198)

        at java.net.ServerSocket.implAccept(ServerSocket.java:530)

        at java.net.ServerSocket.accept(ServerSocket.java:498)

        at zombie.network.PlayerDownloadServer$2.run(PlayerDownloadServer.java:6

91)

The in-game error message he got was "Failed connection to TCP download port 7778"

 

I tried connecting to my own server via public IP with port 7777 in the box and I received the exact same results as my friend.

 

I don't have an antivirus installed so now I'm sitting here stumped.

 

Using Windows 8.1 64-bit

[rockadmiral]

Just figured this out for myself.  Forward the player ports as TCP only, but forward the port the server is running on on both TCP and UDP.  Connect to your own server using your Local IP, too.

[Mogechi]

Just figured this out for myself.  Forward the player ports as TCP only, but forward the port the server is running on on both TCP and UDP.  Connect to your own server using your Local IP, too.

Just tried this for the hell of it; it didn't work for me.

[EnigmaGrey]

Admittedly, we're all at a bit of a loss, Mogechi. Though your port forwarding is correct, there's something preventing the TCP connection from being completed.

[Mogechi]

At this point, I'm going to assume it's some strange factor I overlooked somewhere out there and tinker with it in my free time on weekends and hope it works one day.

[EnigmaGrey]

Why are you assigning 7778 to 7841?

[Mogechi]

Aren't the TCP ports increasing by 1 after the UDP port?

[EnigmaGrey]

Yes, but you've assigned  external port 7778 to internal 7841, instead of opening a range of ports, from 7778 - 7841.

From the looks of this current configuration, the TCP connection will never be made, as it'll never be sent to the internal port of 7778.

Could be wrong.

[Mogechi]

Probably right, I'm trying it now.

EDIT: My friend can't join but I can join my own server using my public IP and I get assigned TCP 7778.

 

 

My friend says he freezes up for a bit before receiving the same error message "Failed connection to TCP download port 7778" or "Failed connection to TCP download port 7779" when I was in my own server.

 

Error:

*** SERVER STARTED ****server is listening on port 7777User Dogeko is trying to connect.Connected new client Dogeko ID # 0 and assigned DL port 7778testing TCP download port 7778TCP port test: accept() timed out, client will have to try again