Re: BFV not starting (LSX Server? Port 3216)
Found the solution! :D :D
My hypothesis above was correct, the reason bfv isn't working is because EA Desktop (or Origin I presume) is not able to start the LSX Server on port 3216.
I realized that I couldn't listen on port 3216 myself either with netcat. So I found out that Windows 10 has Port Exclusion Ranges.
These are ranges of TCP ports that cannot be used by any process, even if that process is running as administrator.
Run the following command in CMD and see if there is a range blocking port 3216:
C:\>netsh int ip show excludedportrange protocol=tcp
Protocol tcp Port Exclusion Ranges
Start Port End Port
---------- --------
1085 1184
1185 1284
1285 1384
1385 1484
1485 1584
1585 1684
1685 1784
1785 1884
1988 2087
2088 2187
2188 2287
2288 2387
2388 2487
2488 2587
2588 2687
2688 2787
2991 3090
3091 3190
3191 3290 <-- This is the culprit!
3390 3489
3490 3589
3590 3689
3690 3789
3790 3889
3903 4002
4003 4102
4103 4202
4203 4302
4303 4402
4403 4502
4503 4602
4700 4799
5216 5315
5358 5457
5458 5557
5558 5657
50000 50059 *
* - Administered port exclusions.I tried to delete this port range, so that EA Desktop can use it, but I was blocked:
C:\> netsh interface ipv4 delete excludedportrange protocol=tcp startport=3191 numberofports=100 Access is denied.
After some googling I found out that these Port Ranges can be created by Hyper-V and virtual network adapters (vmware, virtualbox, vpn, whatever).
In my case it was a virtual network adapter!
Go to your network adapter list Control Panel\Network and Internet\Network Connections and disable all your virtual network adapters! (Hyper-V, TAP-Windows, VMware, etc).
I checked my list of excluded ports again, and 3216 was no longer being blocked by any ranges! I restarted EA Desktop and BFV is now working!
Thanks EA for adding logging to the EA Desktop client. Origin didn't provide this type of detail and that way I would never have figured this out.
Cheers. Hopefully it helps others out there 🙂