Hey, I appreciate the feedback. Maybe failed to set up the rules.
You had to disable it client or server side? Ports should be:
Port 80 - TCP
Port 42 - TCP
Port 6500 - TCP
Port 10000-10050 - TCP
Port 27000-29000 - TCP/UDP
Port 47611 - TCP
And any other port used for server (maybe not needed) like RCClient, RCServer and SQL Server (1433). Again, probably not needed.
The list of ports is kinda trial and error, but that should be a flexible, all-in list.
For Depot stuff you have GMSendMail tool, which you can use to send you stuff through in-game mail. Premium or regular stuff.
When you say "I unisntalled everything" you mean just server-client stuff? Or also OS. Im having some issues with BlackCall.aes and I dont know if its because a recent Win11 update or what.
Haha, sorry. I wasn't very specific I guess. I uninstalled everything via the script uninstall feature. All the server tools/config.
I had to disable the firewall on the server for the client to be able to connect. However I didn't have to for the the client to connect directly on the same machine (localhost). When I disabled the the firewall on the server, other clients could connect over the LAN.
I will try to specifically add the ports manually, and try again with the firewall enabled.
Again the server side is on win 10 pro. I have not had issues with BlackCall.aes as far as I can tell... Everything is working with a win10 pro server, and win11 clients.
Also, thank you for the heads up on GMSendMail tool. I found it, and it works great.
EDIT:
I manually checked, and did not need to add any rules, they were already created. What was weird though, is there are duplicate rules, and some of the rules were not enabled. I enabled the firewall, the rules that were not enabled, removed the duplicate entries, and everything still works.
So with the firewall on, it is working. If anyone else has this problem, make sure to check on the rules. Some of the rules that were supposedly added by the script, were automatically disabled for some reason. I cannot fathom why, whether it was user error, or the computer/script. The issue is completely fixed now, with the firewall turned on.
Thank you very much for your help.