by turk2
New Member

couldn't detect proxy settings + unknown issue identified w/ tracert + ping

Hi, I've been experiencing weird issues with my connection for a while now (mostly related to ping). Using windows (10) diagnostic, it tells me It "couldn't automatically detect the network's proxy settings".

The other issue I noticed occurs when running tracert to any/all sites and was curious if it was related.

 

both issues occur on mulitple devices.

 

When i run tracert through powershell to various sites, these are the results:

 

$> tracert www.bbc.co.uk
>> tracert www.google.co.uk
>> tracert www.google.com
>> tracert www.amazon.co.uk

Tracing route to www.bbc.net.uk [212.58.244.66]
over a maximum of 30 hops:

  1    31 ms     1 ms     2 ms  BrightBox.ee [192.168.1.1]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    49 ms    35 ms    14 ms  213.1.117.173
  5    49 ms    24 ms    42 ms  213.1.67.238
  6    51 ms    28 ms    14 ms  87.237.20.136
  7    31 ms    18 ms    32 ms  212.58.239.56
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10    29 ms    15 ms    20 ms  ae0.er01.telhc.bbc.co.uk [132.185.254.109]
 11    19 ms    59 ms    16 ms  132.185.255.148
 12    15 ms    14 ms    37 ms  bbc-vip111.telhc.bbc.co.uk [212.58.244.66]

Trace complete.

Tracing route to www.google.co.uk [216.58.204.3]
over a maximum of 30 hops:

  1     1 ms     2 ms     2 ms  BrightBox.ee [192.168.1.1]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    18 ms    12 ms    12 ms  213.1.117.173
  5    15 ms    42 ms    16 ms  213.1.79.46
  6    61 ms    37 ms    21 ms  87.237.20.136
  7    13 ms    52 ms    22 ms  87.237.21.174
  8    97 ms    18 ms    37 ms  74.125.242.66
  9    36 ms    15 ms   103 ms  108.170.246.225
 10    13 ms    33 ms    22 ms  108.170.238.147
 11    59 ms    18 ms    35 ms  lhr35s07-in-f3.1e100.net [216.58.204.3]

Trace complete.

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

  1    29 ms     1 ms     2 ms  BrightBox.ee [192.168.1.1]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    16 ms    13 ms    33 ms  213.1.117.173
  5    43 ms    13 ms    13 ms  213.1.79.46
  6    27 ms    13 ms    13 ms  87.237.20.136
  7    50 ms    31 ms    30 ms  87.237.21.174
  8    19 ms    36 ms    22 ms  74.125.242.67
  9    16 ms    16 ms    35 ms  108.170.246.193
 10    25 ms    38 ms    16 ms  108.170.238.151
 11    32 ms    28 ms    45 ms  lhr35s06-in-f4.1e100.net [216.58.212.100]

Trace complete.

Tracing route to dmv2chczz9u6u.cloudfront.net [52.85.245.77]
over a maximum of 30 hops:

  1     1 ms     1 ms     2 ms  BrightBox.ee [192.168.1.1]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    18 ms    11 ms    34 ms  213.1.117.173
  5    33 ms    13 ms    13 ms  213.1.67.142
  6    19 ms    14 ms    16 ms  87.237.20.136
  7    40 ms    39 ms    26 ms  87.128.232.105
  8    21 ms    23 ms    22 ms  ams-sb1-i.AMS.NL.NET.DTAG.DE [62.154.15.53]
  9    25 ms    26 ms    25 ms  80.156.163.46
 10    45 ms    22 ms    19 ms  52.93.0.48
 11    32 ms    22 ms    19 ms  52.93.0.59
 12    60 ms    33 ms    35 ms  54.239.42.202
 13    25 ms    44 ms    50 ms  176.32.124.14
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17    22 ms    33 ms    44 ms  server-52-85-245-77.ams50.r.cloudfront.net [52.85.245.77]

Trace complete.

The main issue lies with timing out in the first few connections highlighted after the router. It may also time out later highlighted, but it seems to happen around 50% of sites that I test + I imagine there is nothing you nor I could do about that.

 

I found all these issues whilst trying to fix my high ping issues. Before, I would experience ping from 200+. reading these forums didn't help me fix it. The only "solution" I can find is to factory reset my router. So far I've had to do it twice and I have seen some improvement. going from 200-600 avg down to an unstable 50-100ms ping in games and through tracert.

 

Aside from the factory reset, I also use the google public DNS Server. This was a solution provided in another post here, but this didn't solve/change anything.

 

if useful: DSL Status page

Status
  	Configured 	Current
Line Status 	-- 	UP
Link Type 	-- 	Fast Path
Operation Mode 	Automatic 	G.992.5 (ADSL2+)
Data Rate Information
Upstream 	1243 (Kbps)
Downstream 	19727 (Kbps)
Defect/Failure Indication
Operation Data 	Upstream 	Downstream
Noise Margin 	5.9 (dB) 	3.1 (dB)
Line Attenuation 	7.9 (dB) 	19.5 (dB)

Indicator Name 	Near End Indicator 	Far End Indicator
Output Power 	12.3 (dBm) 	0.0 (dBm)
Fast Path FEC Correction 	0 	0
Interleaved Path FEC Correction 	-- 	--
Fast Path CRC Error 	0 	0
Interleaved Path CRC Error 	-- 	--
Loss of Signal Defect 	0 	0
Fast Path HEC Error STR 	0 	550
Interleaved Path HEC Error 	-- 	--
Error Seconds 	11 	0
Statistics
Received Data 	7262256 (Kbits)
Transmitted Data 	1393643 (Kbits) 

 

Any help to fix any/all of these problems (including the fact. reset thing) would be great. Thanks.

 

4 REPLIES 4
by
EE Employee

Re: couldn't detect proxy settings + unknown issue identified w/ tracert + ping

Hi @turk2 and welcome to the community,

 

I wonder if @XRaySpeX can help with this one?

 

Many thanks,

 

Lee

by Grand Master
Grand Master

Re: couldn't detect proxy settings + unknown issue identified w/ tracert + ping

Re: Ping issues:

 

Servers have better things to do than respond to pings, like provide the service they are there for. So many either don't respond to pings or only do so when they have time to spare. The early timeouts are within the BT's backhaul network that your BB is routed thro' to your ISP's network & it never responds to pings. As long as tracert reaches your destination in a reasonable time the timing or not at the intermediate nodes are of no importance.

 

What exactly is your high ping issue? To where?

__________________________________________________________________________________________
If you think I helped please feel free to hit the "Thumbs Up" button below.

To phone EE: The local rate landline number +44 207 362 0200 or Freephone +44 800 079 8586 - Option 1 for Mobiles; Option 2 for 4G WiFi; Option 3 for Home Broadband & EE TV.

ISPs: 1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC => 2014: EE 20 Meg WBC
by turk1
Visitor

Re: couldn't detect proxy settings + unknown issue identified w/ tracert + ping

thanks.

 

Well the high ping is in reference to gaming, since it doesn't matter too much else where.
Before i reset my router, I was experiencing incredibly high, and incredibly inconsistent response times. the average would be around 300ms I guess. This value would fluctuate from 100-1000 so it's hard to tell.
Unfortunately I dont play games very often, so I don't know how long this has been happening for.
The only solution I've had was to factory reset the router. The first time work well for a few days. As far as I know, this shouldn't have changed anything other than the very recent changes to fix the issues.
once reset, my ping would sit at 50-100, however this would still fluctuate wildly, hitting up to 200-300ms for brief moments at a time. ( I believe this is jitter?)

aqfter a few days, the problems came back, so I reset again, which fixed it again. that was a couple days ago.

 

Before, online games were unplayable, now it's a lottery whether it will be "good enough" to have a smooth game. The last time I remember it was fine would be back in september...
Lastly, I decided to test with ethernet, and that didn't solve my problems either. It didn't show any difference than with wireless.
Im just wondering if there's a more "technical" solution. This shouldn't be a case of too many devices on the network.

by Grand Master
Grand Master

Re: couldn't detect proxy settings + unknown issue identified w/ tracert + ping

Please post the tracert to 1 of the gaming servers you are having trouble with.

__________________________________________________________________________________________
If you think I helped please feel free to hit the "Thumbs Up" button below.

To phone EE: The local rate landline number +44 207 362 0200 or Freephone +44 800 079 8586 - Option 1 for Mobiles; Option 2 for 4G WiFi; Option 3 for Home Broadband & EE TV.

ISPs: 1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 20 Meg WBC => 2014: EE 20 Meg WBC

Can't find what you're looking for?

One of these options may help you find the answers you need.

Let's get started

Join the EE Community to ask, answer, learn and share.