Windows could not automatically detect this network's proxy settings

Anonymous
2010-05-04T02:01:23+00:00

Recently, I have noticed a small caution triangle appearing with my network icon on the task bar. When I right click and troubleshoot, it comes with this message. Windows could not automatically detect this network's proxy settings. My internet has been very slow lately, but I'm wondering if this is a problem with my network? or is this something that my ISP has to fix?

Windows for home | Previous Windows versions | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2011-05-10T19:40:13+00:00

(This post is intended for all reporting the problem)

Check Internet Options (from Control Panel or Internet Explorer Tools / Options  /Connections Tab / LAN Settings and make sure Proxy Server is unchecked even if using Firefox.  Check settings in Firefox in Tools / Options /Advanced Connections / Settings  (should be either use system proxy settings or no proxy).

Check for malware especially using malwarebytes.

Try  these two commands in that order in an elevated command prompt.  Do the first one first then reboot and try.  If still bad try the second.

netsh winsock reset

netsh int ipv4 reset

If these don't help, please post the output of an ipconfig /all command

Was this answer helpful?

900+ people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2011-03-21T14:37:48+00:00

I had the same problem this morning--couldn't connect on one computer but could on the other.  Got the same message about not being able to detect the proxy settings.  However, I used System Restore to reverse some changes that had happened during the night and that corrected the problem.

Was this answer helpful?

900+ people found this answer helpful.
0 comments

173 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2018-08-24T20:36:57+00:00

    I had tried all of these solutions and more and nothing worked. I searched dozens of websites and tried everything and still nothing. Sometimes it would temporarily until my surface pro 4 was turned on and back on and then it reverted back. Then I was looking at my network and internet settings page and noticed a proxy tab at the bottom. When I went into it, I turned everything off and that was it. It has continued to work and be the answer, just as simple as that.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2018-03-06T22:51:13+00:00

    After trying a hundred solutions, resetting the ipv4 as directed worked. Our problem was one of our Win 10 Pro machines was not showing up on the network, and windows could not automatically detect the networks proxy settings.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2017-10-16T23:03:51+00:00

    For reference, this is after I've cleared out a horde of malware/ viruses. This is my output, please help!

    PS C:\WINDOWS\system32> ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : HAL-9000

       Primary Dns Suffix  . . . . . . . :

       Node Type . . . . . . . . . . . . : Hybrid

       IP Routing Enabled. . . . . . . . : No

       WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Ethernet 3:

       Media State . . . . . . . . . . . : Media disconnected

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : TunnelBear Adapter V9

       Physical Address. . . . . . . . . : 00-FF-12-29-31-CA

       DHCP Enabled. . . . . . . . . . . : Yes

       Autoconfiguration Enabled . . . . : Yes

    Ethernet adapter Ethernet 2:

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Intel(R) Ethernet Connection (2) I219-V

       Physical Address. . . . . . . . . : 70-8B-CD-A9-82-72

       DHCP Enabled. . . . . . . . . . . : Yes

       Autoconfiguration Enabled . . . . : Yes

       Link-local IPv6 Address . . . . . : fe80::f074:4518:c953:82c4%7(Preferred)

       IPv4 Address. . . . . . . . . . . : 192.168.1.35(Preferred)

       Subnet Mask . . . . . . . . . . . : 255.255.255.0

       Lease Obtained. . . . . . . . . . : Monday, October 16, 2017 3:44:12 PM

       Lease Expires . . . . . . . . . . : Tuesday, October 17, 2017 3:44:11 PM

       Default Gateway . . . . . . . . . : 192.168.1.1

       DHCP Server . . . . . . . . . . . : 192.168.1.1

       DHCPv6 IAID . . . . . . . . . . . : 493915085

       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-77-C1-27-70-8B-CD-A9-82-72

       DNS Servers . . . . . . . . . . . : 8.8.8.8

                                           8.8.8.4

       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter Local Area Connection* 14:

       Connection-specific DNS Suffix  . :

       Description . . . . . . . . . . . : Microsoft Teredo Tunneling Adapter

       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

       DHCP Enabled. . . . . . . . . . . : No

       Autoconfiguration Enabled . . . . : Yes

       IPv6 Address. . . . . . . . . . . : 2001:0:9d38:953c:38ce:140e:3f57:fedc(Preferred)

       Link-local IPv6 Address . . . . . : fe80::38ce:140e:3f57:fedc%15(Preferred)

       Default Gateway . . . . . . . . . : ::

       DHCPv6 IAID . . . . . . . . . . . : 251658240

       DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-77-C1-27-70-8B-CD-A9-82-72

       NetBIOS over Tcpip. . . . . . . . : Disabled

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments