Hi All, I thought it is time to re-install our dedi server which ran on Win7... I have many years of XP and I thought that I do understand how it works, but it seems that I do not... Here is what I have: - fresh install of a Win11 Pro - it is running on a VM, hosted by a Linux - fresh install of dedi server, installed using SteamCMD - I installed the shipped vcredist packages (both x64 versions) - it has a fix static IP public address, there is no NAT, no portforward needed, but only packet filter setup on Linux and on the Win11 firewall... - so TCP+UDP 54297, TCP 64297, UDP 64298, UDP 64299 ports are opened (both directions) on Linux and on Win11 as well I also tried allowing every traffic on the Linux host and turned off the firewall on the Windows, but I still can't see the server on the matchmaker (Not connected to Steam) and I can't see it on this page either: https://simracepackages.lima-city.de/rF2server/ If I telnet to port TCP/54297 TCP/64297 from outside I can see the connection established... I also can see the incoming UDP packets sent to UDP/54297, UDP/64298, UDP/64299 arriving to the Win11 server (chacking it using Wireshark installed in Win11) What else did I miss? What else is required to get it listed? Plerase help me out... Mitya
Hi All, Still struggling with this... I installed an UDP receiver on the server and I was able to prove that all the UDP ports are opened on the server... I could send in UDP packets to UDP/54297, UDP/64298, UDP/64299... I was also able to telnet to TCP/54297 and TCP/64297 when the dedi server was running... So it DOES NOT seem to be a port opening issue, but something else... I made some sniffing using Wireshark and saw that there is a TLS communication issue between the dedi and the api.steampowered.com Please find the screenshot attached... I also found a steamplugin.log under the Userdata\Logs folder, which contins this: "rFactor Server failed to conect to Steam" multiple times... Please note that I have all the shipped vcredist libs installed, also I have just installed the newest one from Microsoft... In the screenshot you can see that there is a DNS query for api.steampowered.com and then there is a TCP handshake to the API. After the api there is a TLS handshake, but that fails for some reason... Why?? Thanks for all the ideas...
Did you ever find a solution to this? I have two older Windows 10 Pro PCs that I can run the dedicated server on and they will connect to Steam without issue. I have an active server running on one of them right now. I recently acquired a couple newer PCs and attempted to setup a new server on these. I cannot get either one of them to work. They will never connect to Steam. I've installed Windows 10 Pro on one the newer PCs and Windows 11 Pro on the other. I've verified the proper ports are opened (Windows Firewall and on my router) and opened to the correct IPs. I've shutdown the old server, and configured the new ones to use the default ports. I've also tried using the same private IP as the old server. I've tried configuring the servers with different ports. I've run the runtime files (including latest from Microsoft). Uninstalled and reinstalled as admin. I've run the launcher as admin. I've put them in the DMZ with both the Windows Firewall and my router firewall disabled. I've contacted my ISP who says they are not blocking anything. This makes sense since my old PCs can run as servers just fine. I've copied the steamcmd and rfactor-dedicated folders from the working PC to the newer PCs. I've tried enabling TLS 1.0, 1.1, 1.2 via the registry since this has caused me headaches with other applications I've worked with. I'm really stumped. The only difference I can see is that the old hardware is old and the new hardware is much newer. Could secure boot/TPM stuff play a part in this? I also tried a USB-C to Ethernet adapter to rule out the onboard NIC.
