Permanent Orange Sidewinder Error

[Elobilo]

Also, can you find "\Elite Dangerous\Products\elite-dangerous-odyssey-64\Logs" and look at your most current "netlog.2022.x.x.x.log" to see what type of network errors ED/O may be seeing?

Don't post your netlog here, as it contains sensitive information.

I think the two static IP addresses I have configured are configured correctly in the Router. Changing the Desktop PC to DHCP still is assigned the static IP I configured in the router and your speed test link works.

Regarding the "netlog" file, this is what is strange. I get nothing in it from the orange error, I have had it open and tried to log on just now and nothing is added. I have some entries from earlier when I tried to log on via my mobile hotstop, but nothing when I get the orange error when connected via wired ethernet to the router.

 

[Elobilo]

If all else fails and you just can't get it to work, this is a SHOTGUN method that fixed every thing for me when I constantly got ship colored errors. Turns out my router was in some unholy mode and would not cooperate, no matter what settings I changed. Sometimes, routers have a mind of their own.

1) Set your PC Windows Network to DHCP networking first. Reboot.
2) Reset your router to "Factory Defaults".
3) Reboot the router, then the PC.
4) Log back in to the router and set up DHCP reservations for all wired/wireless clients using the DHCP ADD Reservation button, if available.
5) Turn off UPNP.
6) Add a port forward for the PC's IP address to port 5100 and enable the rule.
7) Confirm all router settings and do not change anything unless you have a valid reason for doing so. Understand the need for the change.
8) Reboot the router and PC once more, to confirm the PC has the correct address, assigned by the router DHCP server.

As I said. This is a SHOTGUN approach.

I would rather do this as an absolute last resort. I bypassed the router by connecting my PC via wired connection directly to the fiber modem itself, taking the router out of the circuit and I got exactly the same error, so don't think it is actually the router.

I will though connect the PC again directly to the modem and see if there are any additions to the netlog file.

 

[GJ51]

We're getting pretty deep in the weeds here...

Can you do a tracert to google.com ?

I'm starting to lean toward this being an ISP issue.

A bit weird how many hops are bouncing around inside telnor.net

Also do a trace to amazon.com

 

[Florenus]

If I were you, I would just contact Frontier support.
It's possible something went wrong with your connection during the jump and now your commander data can't be loaded correctly.

 

[Elobilo]

Connecting directly to the fiber modem, I got no change of the same orange error, with no additions to the log file.
The speed test was the same.
ipconfig /flushdns followed by tracert was the same.
Changed the Elite network to UPNP, the same.
To me this points that the router is not to blame, but something external.

 

[Caydran]

So, you have the netgear router plugged into the fiber modem, you get the error.

Then you plug the PC directly to the fiber modem and get the same error again?

Sounds like your fiber modem is doing something strange. Can you get into the fiber modem. like logging into your router?

Speedtest is a bit low for fiber, but only 1 ping. Where are you?

 

[Elobilo]

We're getting pretty deep in the weeds here...

Can you do a tracert to google.com ?

I'm starting to lean toward this being an ISP issue.

A bit weird how many hops are bouncing around inside telnor.net

Also do a trace to amazon.com

Here they are, google completed, amazon timed out:
\>tracert google.com

Tracing route to google.com [142.250.74.142]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms READYSHARE [192.168.1.1]
2 33 ms 3 ms 1 ms ti0016a400-gw.ti.telenor.net [88.91.161.1]
3 11 ms 11 ms 10 ms ti0030c400-ae1-0.ti.telenor.net [146.172.101.53]
4 11 ms 11 ms 12 ms ti0001c360-ae1-0.ti.telenor.net [146.172.14.129]
5 12 ms 10 ms 12 ms ti0275c360-ae1-0.ti.telenor.net [146.172.22.37]
6 12 ms 27 ms 20 ms ti3001c360-ae3-0.ti.telenor.net [146.172.14.150]
7 10 ms 10 ms 10 ms ti3001b400-ae4-0.ti.telenor.net [146.172.105.29]
8 11 ms 11 ms 11 ms 209.85.175.193
9 11 ms 11 ms 11 ms 142.250.213.185
10 10 ms 11 ms 11 ms 142.251.48.45
11 11 ms 11 ms 11 ms arn11s11-in-f14.1e100.net [142.250.74.142]

Trace complete.

\>tracert amazon.com

Tracing route to amazon.com [176.32.103.205]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms READYSHARE [192.168.1.1]
2 1 ms 1 ms 1 ms ti0016a400-gw.ti.telenor.net [88.91.161.1]
3 5 ms 5 ms 4 ms ti0030c400-ae1-0.ti.telenor.net [146.172.101.53]
4 5 ms 4 ms 5 ms ti0001c360-ae1-0.ti.telenor.net [146.172.14.129]
5 6 ms 4 ms 4 ms ti0001b400-ae1-0.ti.telenor.net [146.172.105.66]
6 4 ms 4 ms 4 ms oso-b1-link.ip.twelve99.net [213.248.84.57]
7 14 ms 13 ms 16 ms kbn-bb2-link.ip.twelve99.net [62.115.116.107]
8 89 ms 89 ms 89 ms nyk-bb2-link.ip.twelve99.net [80.91.254.91]
9 89 ms 89 ms 89 ms nyk-b2-link.ip.twelve99.net [62.115.137.99]
10 89 ms 89 ms 88 ms a100us-ic340643-nyk-b2.ip.twelve99-cust.net [62.115.168.97]
11 89 ms 90 ms 126 ms 52.93.247.151
12 * * * Request timed out.
13 98 ms 98 ms 98 ms 52.93.59.239
14 97 ms 102 ms 98 ms 15.230.204.46
15 * * * Request timed out.
...
19 * * * Request timed out.
20 103 ms 103 ms 107 ms 52.93.29.12
21 * * * Request timed out.
...
30 * * * Request timed out.

Trace complete.

 

[Elobilo]

If I were you, I would just contact Frontier support.
It's possible something went wrong with your connection during the jump and now your commander data can't be loaded correctly.

Have done that, but no reply as of yet. They say it might take up to 72hrs, guess that will be 72 working hours.

 

[Elobilo]

So, you have the netgear router plugged into the fiber modem, you get the error.

Then you plug the PC directly to the fiber modem and get the same error again?

Sounds like your fiber modem is doing something strange. Can you get into the fiber modem. like logging into your router?

Speedtest is a bit low for fiber, but only 1 ping. Where are you?

Yes, identical errors and results for both. I'm about 90 miles south of Oslo. Unfortunately, the fiber modem is locked, only Telenor can access it. I have turned it on and off several times to no avail.

 

[Wizz15]

Not sure if this would help or not,but what if you use Google/OpenDNS IP addresses configured on your windows network adapter?

These are publicly available and free, and I have used OpenDNS for years after finding out the ISP DNSes can cause weird issues like this (I remember also seeing weird hops).

Not sure if you are in the exact same situation though.

 

[Florenus]

Have done that, but no reply as of yet. They say it might take up to 72hrs, guess that will be 72 working hours.

Sorry to hear that, but from what I see it might not be a problem with your connection at this point. You are able to connect to Frontier servers and you are accessing the game main menu without problems, but you get "orange sidewinder" when trying to load your "save" if I got it right. Since it all happened when jumping to another system, it it might be a problem there - support might try to move you somewhere else.

 

[Caydran]

Not sure if this would help or not,but what if you use Google/OpenDNS IP addresses configured on your windows network adapter?

These are publicly available and free, and I have used OpenDNS for years after finding out the ISP DNSes can cause weird issues like this (I remember also seeing weird hops).

Not sure if you are in the exact same situation though.

Good thought.

Set the DNS1 and DNS2 in the router, under WAN to:
DNS1: 8.8.8.8
DNS2: 8.8.4.4

Your fiber modem may be pointing to it's own DNS servers which may be something like 1.1.1.1 or 1.0.0.1

Do an "ipconfig /all" at the command prompt to see what DNS servers your pointing at.

 

[Elobilo]

Not sure if this would help or not,but what if you use Google/OpenDNS IP addresses configured on your windows network adapter?

These are publicly available and free, and I have used OpenDNS for years after finding out the ISP DNSes can cause weird issues like this (I remember also seeing weird hops).

Not sure if you are in the exact same situation though.

I use Quad9 DNS now for security, and the last one I used would be the ISPs. I used google in the past, but now Quad9 is supposed to be more secure and private - Google gets enough data as it is!

 

[Elobilo]

Sorry to hear that, but from what I see it might not be a problem with your connection at this point. You are able to connect to Frontier servers and you are accessing the game main menu without problems, but you get "orange sidewinder" when trying to load your "save" if I got it right. Since it all happened when jumping to another system, it it might be a problem there - support might try to move you somewhere else.

Hopefully it is this and Elite will be able to surprisingly quickly fix it tomorrow .
I start my holiday tomorrow and had a few days planned free to play Elite before I travel, so a shame if these days are used up with Elites support.

Thanks to everyone's input and help, I think it is most likely external to me, possibly Amazon since I can't traceroute there, but may be my ISP. So thanks very much for the help, everyone.

 

[GJ51]

Also be sure to do a ipconfig /flushdns on your system after you make the changes

I'd also do an ipconfig /release and ipconfig /renew just for fun.

I use 1.1.1.1 and 1.0.0.1 and 9.9.9.9 on my pfsense box - no problems that I can identify

Then I just set adapters on my PC to Obtain DNS automatically.

Either the Cloudflare of Google DNS servers should be a good way to test to see if it's a DNS issue as long as the PC adapter is using the router to get DNS info.

I'm a bit vague on the details as we set up DNS with encryption a long while ago so that we weren't broadcasting to either Google or Verizon (our ISP) but my son is a level 6 AWS SDE so I'm pretty confident it's secure.

 

[Elobilo]

If anyone is interested in an update, Frontier did come back to me yesterday and relocated my position a bit. She also loaded my account up on her test account and it worked fine she says. She intemated it could possibly be a problem with my system or the connection from the client to Frontier and asked me to reverify the files. Nothing worked to fix the error.

To rule out my system and network between Frontier and me I created a secondary account, which I'd been thinking of doing for a while. Everything worked fine for this secondary account. Here is what I wrote to Frontier in the ticket about this, and not heard back from them today yet - and the strange symptom is, well, strange...:

I have done some more testing today. I have used several hours playing in my new secondary account (now upgraded to Odessey) and it was stable with no problems at all with multiple logons/logoffs.

Using my secondary account as a control, I disconnected my PC from wired ethernet and connected it to my mobiles data network via mobile hotspot. Again, I had no problems running my secondary control account on this mobile hotspot, but still got the same error with my main problem account. My mobile ISP that I connected to is a totally different and independent company using different networks to my home ISP, so this test also rules out any problems with my ISP, as the same behaviour occurs with two different and independent ISP network.

To me this essentially rules out any problems locally with me or with my ISP.

There is also another bit of evidence that points to this. When getting the Orange Sidewinder error, I NEVER get any logging in the NetLog file. If there was some problem connecting to your servers, I would expect this to contain some logging info about this. Therefore, I think that this points to my client being able to properly connect to you servers, with the problem being inside your system. As a control, I did test to see if network errors would be written to this log by removing the NAT/uPNP to the pc and it did log these connection errors.

There is one other strange symptom that only became clear when I was able to compare to the control secondary account. In the main problem account, after I click on the game mode (e.g. Open), the orange spinning ship framerate goes very low and can stutter a lot. The normal is 60fps, but when loading the problem account averages about 12 and can go down to just 5fps. With my secondary account, this never happens, it is a normal steady 60fps. The only difference is the account details used to log in.

 

[GJ51]

Strange indeed

I'll be interested to hear what is happening if it ever gets sorted

 

[=71st=RuSh]

Just roll back to the previous adrenaline version, it happened to me and that was the problem.

 

[Elobilo]

Just roll back to the previous adrenaline version, it happened to me and that was the problem.

Was what happened to you where one account was working and the other account giving Orange Sidewinder errors? As this is what is happening to me and as one is working fine, to me this would rule out any driver errors (also I'm using Nvidia drivers).

 

[=71st=RuSh]

Was what happened to you where one account was working and the other account giving Orange Sidewinder errors? As this is what is happening to me and as one is working fine, to me this would rule out any driver errors (also I'm using Nvidia drivers).

Wow, both accounts in the same machine? in my case was more simple, the Orange error only happened when I was trying to land on any planet in Odyssey, I had to restart with the vanilla ED game that places the ship again in the space. After that, I rolled back to the adrenaline previous driver (the problem began after update the Radeon driver) and everything worked ok again. But your problem is by far more complex if both accounts are in the same PC.