VBS3Fires will not connect to VBS3
- VBS3Fires will only connect to VBS3 when you reach the mission briefing screen of a scenario. This will occur after you have hit the ‘Connect’ button in the network lobby of VBS3.
- Check the VBS3FiresIPAddress.dat file in the root directory of your VBS3 installation. Ensure that the contents of this file define an IP address of the machine that is running VBS3Fires. If that file is not present, then ensure you are running VBS3Fires on the same machine as VBS3 is running on.
- Ensure that no firewall is preventing socket communications between VBS3 and VBS3Fires.
- Use the netstat –a command from the windows command prompt to check if any other programs are causing a conflict with the sockets that VBS3Fires is using. If a conflict has occurred (consult the list of port numbers used at the beginning of this document), then you should close down the other application which is conflicting with VBS3Fires and run VBS3Fires again.
- If you have IPv6 installed on your system, ensure that IPv4 is also installed and that you are running VBS3Fires with the -Djava.net.preferIPv4Stack=true before the -jar flag in the command line.