Page 1 of 1

Update 2.3.10

Posted: Mon Jun 26, 2017 7:43 pm
by tinnitus
For the most part, this has been my morning after installing the update.

failed-server.PNG
failed-server.PNG (10.9 KiB) Viewed 3064 times


Have manage to do a couple mission then when near or exiting the station (slot) the above message appears. May be my end but no problems for months will create a Support Ticket.

Re: Update 2.3.10

Posted: Tue Jun 27, 2017 12:55 am
by cyberbofh
Hi CMDR,

I am sorry to hear that..
but.. maybe it was related to this?

Game Server Problems! - June 26 - 18:24 UTC

Hope you made it back in the cold dark space of Elite:Dangerous

Re: Update 2.3.10

Posted: Tue Jun 27, 2017 3:50 am
by tinnitus
cyberbofh wrote:Hi CMDR,

I am sorry to hear that..
but.. maybe it was related to this?

Game Server Problems! - June 26 - 18:24 UTC

Hope you made it back in the cold dark space of Elite:Dangerous


Update: It is still occurring connection during payment request and dumped to the Desktop. Oh well will try tomorrow just going to go fly.


All better now, I hope. Thanks. Received instructions to take down walls, flush the cache, reset windows socks, did not know windows was wearing socks, size 10 I think. Anyway assume that was for connection errors submitting missions not sure why being dumped to the desktop near the mail-slot occurred but so far no other issues.

Re: Update 2.3.10

Posted: Tue Jun 27, 2017 11:38 am
by de Carabas
Any chance of posting those full guidelines in case anyone else has the same?

Re: Update 2.3.10

Posted: Tue Jun 27, 2017 3:39 pm
by tinnitus
de Carabas wrote:Any chance of posting those full guidelines in case anyone else has the same?


I'm adding this here; if you have your network connection set to NOT automatically obtain IP address then you have to input the IP address manually or set the Automatic Obtain option as my connection was not active after the flush and reboot. The ISP Modem/Router Firewall cannot be disabled but one can select a lower security setting.

In part from Frontier Support;

Firstly can you take down all firewalls including any router firewalls you may have (this includes filters and proxies on the router), specifically DDoS protection features that can filter pings and try again.

Then can you try restarting your network stacks if you haven't already:

Open a command prompt with admin privileges, type following commands as follows & press enter, don't reboot until all 3 are done.

1.ipconfig /flushdns

2.netsh winsock reset

3.netsh int ip reset c:\ipreset.txt

Re: Update 2.3.10

Posted: Tue Jun 27, 2017 4:05 pm
by de Carabas
Good stuff. I hope I never need to use them but better have them and not need them....

Re: Update 2.3.10

Posted: Tue Jun 27, 2017 5:21 pm
by tinnitus
tinnitus wrote:
de Carabas wrote:Any chance of posting those full guidelines in case anyone else has the same?


I'm adding this here; if you have your network connection set to NOT automatically obtain IP address then you have to input the IP address manually or set the Automatic Obtain option as my connection was not active after the flush and reboot. The ISP Modem/Router Firewall we have cannot be disabled but one can select a lower security setting.

In part from Frontier Support;

Firstly can you take down all firewalls including any router firewalls you may have (this includes filters and proxies on the router), specifically DDoS protection features that can filter pings and try again.

Then can you try restarting your network stacks if you haven't already:

Open a command prompt with admin privileges, type following commands as follows & press enter, don't reboot until all 3 are done.

1.ipconfig /flushdns

2.netsh winsock reset

3.netsh int ip reset c:\ipreset.txt