Pete Gaimari, on Mar 14 2019 - 12:07 PM, said:
Saiph..........I've read your posts for years and you come up with answers that impress me. You know things beyond the average gamer. What do you do for a living?
Thanks Pete. Over the years I've done just about every job in IT, but the last official job title I had was Software Quality Assurance Test Engineer. That's why I have a nose for finding, and occasionally solving, problems, and explaining to "users" (non-techy people) how to fix things. I'm basically not working at the moment (at least not for a company) as I had problems with pressure from my last employer (McAfee) which wasn't good for my health. I'm living on my savings and my wits (!) and doing odd computer jobs locally: PC upgrades (RAM, graphics cards etc), fault fixing, wifi, networks, broadband, security and privacy issues etc. I'm enjoying life again living at my own pace, and not being pushed by the relentless profiteering of capitalism.
It's not a rich life, but I'm not a materialistic person. Drinking a slow pint and listening to good local musicians playing good-quality, meaningful songs is a relatively cheap but very enjoyable pastime.
John Woods, on Mar 14 2019 - 12:44 PM, said:
No idea how to test except use a number instead of a symbol and seems the most appropriate number would be the server address?
Address numbers could be entered in the Server Name field and host names could be entered in Comments?
John, the best way to test if DNS is involved with IGOR and VROC disconnections would be to do the following:
(1) First, you need to find the numeric IP address of the server you're logging on to. The easiest way to do this is to open up a command line, and use the 'ping' command. Just type in:
(where "NamePart1...." etc is the name of the race server you're trying to use),
and press the 'enter' key. The first thing you should see is a message saying that the ping command is working, and
showing the numeric IP address that it's using. For example, when I ping the BBC ("bbc.co.uk"), I see a reply saying:
"Pinging bbc.co.uk [220.127.116.11] with 32 bytes of data:"
So I know that the IP address of the server is "18.104.22.168". Make a note of the number you get for your race server.
(2) Now go in to GPL, and see if you can use the settings screen to start (or join) a network session using the numeric IP address, rather than the symbolic name. Hopefully you'll be able to log in, and once the session starts, you'll be able to go through all the usual steps of practice etc. Keep playing, and see if you notice any difference in the reliability of your connection. If you can play more reliably using the numeric IP address, then it sounds like the problem might be connected to the DNS system. If you still get disconnected just as often, then the problem is more likely to be somewhere else, not DNS.
From what you stated in your last post ("...unable to connect to the grid during the several short digitally frantic seconds prior to a race"), I don't think
that it's a DNS problem. DNS is used when you first connect to a server. By the time you've been through practice and are getting ready to start the race, you've been connected for some time, so DNS isn't being used at that point.
Edited by Saiph, Mar 14 2019 - 09:46 PM.