Return of Reckoning

Akalukz wrote:I saw you flushed DNS, but have you tried these commands as well,

Be sure to run from an Admin CMD window


netsh winsock reset catalog
netsh int ipv4 reset reset.log
netsh int ipv6 reset reset.log

I ran cmd as administrator wrote "netsh winsock reset catalog", restarted the computer , and web red. Command "netsh int ipv4 reset reset.log" is not found , and the "netsh int ipv6 reset reset.log" ipv6 is not installed .

hrm i have to dig back into my Windows XP era let me think a bit.

Good to know that nothing dont Help even for experienced computer brains. Its mean I dont must doing Too much. Just waiting. Admins know our own problems and errors.

Kali14 wrote:Good to know that nothing dont Help even for experienced computer brains. Its mean I dont must doing Too much. Just waiting. Admins know our own problems and errors.

It might be very possible that the devs simply will not support Windows XP, which is not unreasonable. I wouldn't blame them for not being willing to put this high up on the priority list or delve too deep into this issue at all. In the same way, I do not expect them to fix any Linux or Wine-related issues I am having either because I am playing the game on an operating system it was not designed for.

That being said, it is quite hard to debug what exactly is causing this issue because we don't know the exact details of how the client works and how it was changed after the DDoS. Additionally, there are people who cannot connect to the website without a VPN either, while me and others can. At this stage I kind of need a direction as to where to look, but so far my guess is that, unlike what I thought at first, it *is* operating system related. On the network side everything is fine, at least for me.

wonder if one of you guys that are having issues, could load a second Windows XP as duel boot. Be interesting to see if this is ISP/network related or client machine. Do you have any other machines on the same network running the game?

Akalukz wrote:wonder if one of you guys that are having issues, could load a second Windows XP as duel boot. Be interesting to see if this is ISP/network related or client machine. Do you have any other machines on the same network running the game?

I tried to run on two computers windows xp on the same network

It is windows xp problem.I have in my desktop pc xp s3 and on laptop windows 10.I have no problem to log in with laptop but with the desktop i have the same problem i think from 26 june.

Akalukz wrote:wonder if one of you guys that are having issues, could load a second Windows XP as duel boot. Be interesting to see if this is ISP/network related or client machine. Do you have any other machines on the same network running the game?

Friend of mine runs it on Linux via WINE just like me, he could run the game fine in a Windows VM (non-XP) but not natively on his system since last week. I can run it fine on my Windows 8.1 dual boot. Additionally, both of us can access the website and ping the servers, which makes the likelihood of it being ISP or network related very small.

Provide a pcap when opening the launcher.

Akalukz wrote:I know this may sound silly, but have you tried redownloading both the game and the launcher?

Yes. Sorry I should have clarified, I tried a new download and a backup version from an external hard drive. Installed the game partially and fully (backup old file). I also pulled out a second computer that is identical to this one and Installed with new files. That computer was wiped clean and hasn't been started since (These were free from work after we upgraded our office). At that point I realized there's something preventing even a newly formatted Windows XP pc from connecting.

10. Reinstalled WAR/RoR Launcher fully and incrementally.
11. Installed on another pc (same as this with only OS installed)

Akalukz wrote:I saw you flushed DNS, but have you tried these commands as well,

Be sure to run from an Admin CMD window


netsh winsock reset catalog
netsh int ipv4 reset reset.log
netsh int ipv6 reset reset.log

Tried that too. I made sure to Start a Command Prompt as an Administrator and restart pc.

15. Ran these suggested commands and restarted pc

Spoiler:

Code: Select all

netsh int ipv6 reset reset.log
netsh int ipv4 reset reset.log
netsh winsock reset catalog
lodctr /e:PerfProc
lodctr /r