|
| Thread: Unexpected inability to play LAN game - HoMM3 Complete 4.0_(10665) GOG version | |
|
King_V
Hired Hero
|
posted June 17, 2018 03:06 AM |
|
|
Unexpected inability to play LAN game - HoMM3 Complete 4.0_(10665) GOG version
Ok, so, this is a bit baffling.
I recently did a clean install of Windows 10 Pro on both my own and my son's computers.
Additionally, I have this same version of HoMM3 on a Lubuntu Linux install running through PlayOnLinux.
This is where it gets weird - I *think* I did everything the same on my Windows 10 PC as well as my son's, but somehow, mine cannot see other LAN games, or be seen if it's hosting a LAN.
1 - If my son hosts:
---- my Linux machine can see the game and I can join it
---- my Windows PC cannot
2 - If I host on my Windows PC
---- my son's PC cannot see it
---- my Linux machine cannot see it
There's some kind of issue, so my Linux box cannot host a game.
The only thing different between our two computers is, if I go to the Allow apps to communicate through Windows Defender Firewall for Heroes of Might and Magic III:
- My son's computer has only one entry, left checkbox checked, and only the box for Private checked.
- On my computer, there are two entries, the first the same as my son's, the second does not have the left checkbox checked, and has Public checked.
No matter how many times I try to remove it, then let the app try and get the alert to choose what networks to allow, and explicitly uncheck Public and check Private, I get the same two entries again.
Any idea what's going on and how I can fix this? The last time I'd installed it, this wasn't happening.
|
|
Alyx182008
Adventuring Hero
|
posted June 17, 2018 08:39 AM |
|
|
|
The problem most likely is with the Firewall settings. As I don't have access to a Windows 10 PC, it would be useful if you could take a screenshot of these entries you have.
|
|
King_V
Hired Hero
|
|
posted June 17, 2018 04:55 PM |
|
Edited by King_V at 16:56, 17 Jun 2018.
|
Ugh, so this is embarrassing.
Apparently, for whatever reason, network discovery was turned off, so in the Control Panel -> System Security -> Windows Defender Firewall, it said that my machine was NOT connected to a private network, but my son's machine was.
I don't remember explicitly turning on for his computer, or off for mine, but that was the problem.
I suppose that explained why the alert about the firewall would default to checking the Public networks when I was struggling with it.
Just gonna go and have a *headdesk* moment here...
|
| |
|
|
