Sub Command multiplayer problems in Windows 7

Hinrich Schwab · 03-16-14, 06:27 PM

I am unable to host or join games in Sub Command on a windows 7 machine. I have tried on two separate machines to work in multiplayer to no avail. I have no problems with multiplayer on my XP machines and I know that the firewall ports are open on all computers and my router. I do not have this problem with Dangerous Waters, so it must be something in SC. Has anyone else encountered this issue and, if so, have you discovered a resolution?

Hinrich Schwab · 03-22-14, 06:33 PM

UPDATE: I have resolved this problem. I changed the .AdapterName line in subcommand.ini from "DEFAULT" to "IPv4". If anyone else has a connectivity problem, here is the solution.

Pisces · 03-23-14, 06:54 PM

I got it working by changing the .AdapterName field simply to the name given by Windows to that network card, such like " Local Area Connection 2". Or whatever name you might have given it yourself in the Adapter overview (i.e. to keep your wireless and cable network apart).

03-16-14, 06:27 PM	#1
Hinrich Schwab Grey Wolf Join Date: Nov 2010 Posts: 908 Downloads: 89 Uploads: 0	Sub Command multiplayer problems in Windows 7 I am unable to host or join games in Sub Command on a windows 7 machine. I have tried on two separate machines to work in multiplayer to no avail. I have no problems with multiplayer on my XP machines and I know that the firewall ports are open on all computers and my router. I do not have this problem with Dangerous Waters, so it must be something in SC. Has anyone else encountered this issue and, if so, have you discovered a resolution?

03-22-14, 06:33 PM	#2
Hinrich Schwab Grey Wolf Join Date: Nov 2010 Posts: 908 Downloads: 89 Uploads: 0	UPDATE: I have resolved this problem. I changed the .AdapterName line in subcommand.ini from "DEFAULT" to "IPv4". If anyone else has a connectivity problem, here is the solution.

03-23-14, 06:54 PM	#3
Pisces Silent Hunter Join Date: Dec 2004 Location: AN9771 Posts: 4,904 Downloads: 304 Uploads: 0	I got it working by changing the .AdapterName field simply to the name given by Windows to that network card, such like " Local Area Connection 2". Or whatever name you might have given it yourself in the Adapter overview (i.e. to keep your wireless and cable network apart).