So, first, I tried "open 192.168.1.64 4000" from my laptop. It begins with:
Connecting To 192.168.1.64...
Then, after several seconds, it immediately shifts to:
Press any key to continue...
That is to say, the entire Command Prompt feed is gone, it's just that message, and when I press a key Command Prompt ends. However, when I try it a second time, it goes back to the telnet interface, and I see this:
Connecting To 192.168.1.64...
Connection to host lost.
Furthermore, I get this message on the feed from FOnlineServer.exe, which was running at the time, obviously.
[Logic][08:40:804] FOServer:rocess - Connection timeout, client kicked, maybe bot. Ip<192.168.1.81>.
Then, I tried "open 109.152.194.209 [my current external IP] 4000", and I received:
Connecting To 109.152.194.209...Could not open connection to the host, on port 4000
000: Connect failed
After this, I try netstat.
Active Connections
Proto Local Address Foreign Address State
TCP 25.157.156.248:5357 x-PC:52132 TIME_WAIT
TCP 25.157.156.248:5357 x-PC:52135 TIME_WAIT
TCP 25.157.156.248:5357 x-PC:52137 TIME_WAIT
TCP 25.157.156.248:5357 x-PC:52142 TIME_WAIT
TCP 25.157.156.248:5357 x-PC:52147 TIME_WAIT
TCP 25.157.156.248:5357 x-PC:52149 TIME_WAIT
TCP 25.157.156.248:5357 x-PC:52157 TIME_WAIT
TCP 25.157.156.248:5357 x-PC:52158 TIME_WAIT
TCP 25.157.156.248:5357 x-PC:52164 TIME_WAIT
TCP 25.157.156.248:5357 x-PC:52166 TIME_WAIT
TCP 25.157.156.248:59564 x-PC:wsd TIME_WAIT
TCP 25.157.156.248:59565 x-PC:wsd TIME_WAIT
TCP 25.157.156.248:59566 x-PC:wsd TIME_WAIT
TCP 25.157.156.248:59567 x-PC:wsd TIME_WAIT
TCP 25.157.156.248:59580 x-PC:wsd TIME_WAIT
TCP 25.157.156.248:59581 x-PC:wsd TIME_WAIT
TCP 25.157.156.248:59582 x-PC:wsd TIME_WAIT
TCP 25.157.156.248:59584 x-PC:wsd TIME_WAIT
TCP 25.157.156.248:59585 x-PC:wsd TIME_WAIT
TCP 25.157.156.248:59586 x-PC:wsd TIME_WAIT
TCP 25.157.156.248:59587 x-PC:wsd TIME_WAIT
TCP 25.157.156.248:59588 x-PC:wsd TIME_WAIT
TCP 25.157.156.248:59589 x-PC:wsd TIME_WAIT
TCP 192.168.1.64:4000 My_Laptop:activesync TIME_WAIT
TCP 192.168.1.64:49157 212.118.234.69:12975 ESTABLISHED
TCP 192.168.1.64:50082 ivfn:http ESTABLISHED
TCP 192.168.1.64:50091 ivfn:http ESTABLISHED
TCP 192.168.1.64:58596 213.123.84.73:http ESTABLISHED
TCP 192.168.1.64:59124 lhr08s01-in-f0:https ESTABLISHED
TCP 192.168.1.64:59405 gamer:http TIME_WAIT
TCP 192.168.1.64:59419 channelproxy-shv-07-ash2:https ESTABLISHED
TCP 192.168.1.64:59421 178.236.6.19:https TIME_WAIT
TCP 192.168.1.64:59422 178.236.6.19:https TIME_WAIT
TCP 192.168.1.64:59423 178.236.6.19:https TIME_WAIT
TCP 192.168.1.64:59471 lhr08s01-in-f14:http ESTABLISHED
TCP 192.168.1.64:59486 213.120.177.138:http TIME_WAIT
TCP 192.168.1.64:59487 213.120.177.138:http TIME_WAIT
TCP 192.168.1.64:59488 213.120.177.138:http TIME_WAIT
TCP 192.168.1.64:59491 213.120.177.138:http TIME_WAIT
TCP 192.168.1.64:59568 lhr08s01-in-f23:https ESTABLISHED
TCP 192.168.1.64:59583 edge-star-shv-05-lhr2:https ESTABLISHED
x-PC is my friend's PC, I believe, as I recognise the PC name on the Hamachi network. Harmless enough, I think, as I had Hamachi running at the time.
My_Laptop is my laptop's name, I just changed both these names for privacy's sake.
After all of this, I check my router settings, and FOnline-TCP and FOnline-UDP are both there.