Windows 10: Connection was already enabled but failed with error 651.

Well I'm stumped. All that tool did was flush the DNS and report some settings (of which, look to me like you should not be able to get online with the way everything is setup). But I see it successfully pinged Google and Yahoo, so it's clear you are online again.

I would invest in another ethernet cable, so you have a spare.

Sorry I can't be of more help. I think hardware troubleshooting is necessary here, if the issue persists.

 

I forgot to mention that I have two independent broadband connections, one of which has been left unused for years, and that's why I had forgotten it. Today I tried but failed to use the old one again, while the new one, which I am using at the moment, is working fine.
The old and the new ones are called 'PowerCom Broadband' and 'Home Broadband' respectively.
The first and the second screenshots below refer to the old and the new ones respectively.
Can anyone help me with the old one?
Previously I could put text between screenshots. Why can't I do the same now?

 

Hi Matthew.

From the time zone on your profile your are in the Central time zone for North America, correct?

Who supplies you with each service, my this I mean what are the specific teleco's names? Verizon, Telus, Sprint, Bell, etc

Next if you run the minitool box again does your connection work?

I think I would also try disabling IPv6 as a test.

https://support.microsoft.com/en-gb/...nts-in-windows

 

No idea. Is PowerCom still turned on by your ISP?

 

The graphic under 'My Timezone' does not indicate my correct location–China.

Both services ('Buy one, get one free') are provided by this ISP PowerCom Broadband.

What does 'minitool box' refer to? The Home Broadband connection always works. The PowerCom connection worked years ago but no longer works now.

I tried that, but to no avail.

Yes, it is.

 

Look at this post in this thread for the minitool box. simrick had suggested you run and then you reported it was working.

Connection was already enabled but failed with error 651.


Ken

Edit 1: I stand corrected (sort of). Went to link you provided and indeed your provider does have set up instructions although they are for ancient software. Really, Outlook Express, XP and IE. Ouch.

That said something was to be taken away. Please right click on network icon in systray, then Open Network and Sharing. On lower left click on internet options, then connection tab, then Lan Settings. On next window remove all check marks. You can see where I got this from this link under Default Internet Explorer Setting Guide.

http://www.threebb.com.hk/technicalS....html#section2

They obviously need to severely update these instructions.

 

I already tried that before I wrote my post #30. That was useless.

Sorry, I forgot that post. I will run that tool tomorrow.

 

No, PowerCom Broadband still does not work.

MiniToolBox by Farbar Version: 17-06-2016
Ran by Matthew_Wai (administrator) on 20-06-2017 at 14:46:38
Running from "D:\Matthew's folder\PowerCom"
Microsoft Windows 10 Home (X64)
Model: All Series
Manufacturer: ASUS
Boot Mode: Normal
***************************************************************************
========================= Flush DNS: ===================================Windows IP ConfigurationSuccessfully flushed the DNS Resolver Cache.========================= IE Proxy Settings: ============================== Proxy is not enabled.No Proxy Server is set.========================= Hosts content: =================================127.0.0.1 Update.kmpmedia.net127.0.0.1 player.kmpmedia.net127.0.0.1 cdn.kmplayer.com127.0.0.1 media.sj2.vcmedia.com127.0.0.1 rd.apmebf.com========================= IP Configuration: ================================Realtek PCIe GBE Family Controller = Ethernet (Connected)# ----------------------------------# IPv4 Configuration# ----------------------------------pushd interface ipv4resetset global icmpredirects=enabledset interface interface="Ethernet" forwarding=enabled advertise=enabled nud=enabled ignoredefaultroutes=disabledpopd# End of IPv4 configurationWindows IP Configuration Host Name . . . . . . . . . . . . : DESKTOP Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : NoEthernet adapter Ethernet: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller Physical Address. . . . . . . . . : 40-16-7E-26-95-9A DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::f061:6161:d112:2bce%11(Preferred) Autoconfiguration IPv4 Address. . : 169.254.43.206(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : DHCPv6 IAID . . . . . . . . . . . : 54531710 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-20-93-79-22-40-16-7E-26-95-9A DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : DisabledServer: UnKnownAddress: fec0:0:0:ffff::1Ping request could not find host google.com. Please check the name and try again.Server: UnKnownAddress: fec0:0:0:ffff::1Ping request could not find host yahoo.com. Please check the name and try again.Pinging 127.0.0.1 with 32 bytes of data:Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Reply from 127.0.0.1: bytes=32 time<1ms TTL=128Ping statistics for 127.0.0.1: Packets: Sent = 2, Received = 2, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms===========================================================================Interface List 11...40 16 7e 26 95 9a ......Realtek PCIe GBE Family Controller 1...........................Software Loopback Interface 1===========================================================================IPv4 Route Table===========================================================================Active Routes:Network Destination Netmask Gateway Interface Metric 127.0.0.0 255.0.0.0 On-link 127.0.0.1 331 127.0.0.1 255.255.255.255 On-link 127.0.0.1 331 127.255.255.255 255.255.255.255 On-link 127.0.0.1 331 169.254.0.0 255.255.0.0 On-link 169.254.43.206 291 169.254.43.206 255.255.255.255 On-link 169.254.43.206 291 169.254.255.255 255.255.255.255 On-link 169.254.43.206 291 224.0.0.0 240.0.0.0 On-link 127.0.0.1 331 224.0.0.0 240.0.0.0 On-link 169.254.43.206 291 255.255.255.255 255.255.255.255 On-link 127.0.0.1 331 255.255.255.255 255.255.255.255 On-link 169.254.43.206 291===========================================================================Persistent Routes: NoneIPv6 Route Table===========================================================================Active Routes: If Metric Network Destination Gateway 1 331 ::1/128 On-link 11 291 fe80::/64 On-link 11 291 fe80::f061:6161:d112:2bce/128 On-link 1 331 ff00::/8 On-link 11 291 ff00::/8 On-link===========================================================================Persistent Routes: None========================= Winsock entries =====================================Catalog5 01 C:\Windows\SysWOW64\napinsp.dll [54784] (Microsoft Corporation)Catalog5 02 C:\Windows\SysWOW64\pnrpnsp.dll [70144] (Microsoft Corporation)Catalog5 03 C:\Windows\SysWOW64\pnrpnsp.dll [70144] (Microsoft Corporation)Catalog5 04 C:\Windows\SysWOW64\NLAapi.dll [63488] (Microsoft Corporation)Catalog5 05 C:\Windows\SysWOW64\mswsock.dll [305568] (Microsoft Corporation)Catalog5 06 C:\Windows\SysWOW64\winrnr.dll [23040] (Microsoft Corporation)Catalog9 01 C:\Windows\SysWOW64\mswsock.dll [305568] (Microsoft Corporation)Catalog9 02 C:\Windows\SysWOW64\mswsock.dll [305568] (Microsoft Corporation)Catalog9 03 C:\Windows\SysWOW64\mswsock.dll [305568] (Microsoft Corporation)Catalog9 04 C:\Windows\SysWOW64\mswsock.dll [305568] (Microsoft Corporation)Catalog9 05 C:\Windows\SysWOW64\mswsock.dll [305568] (Microsoft Corporation)Catalog9 06 C:\Windows\SysWOW64\mswsock.dll [305568] (Microsoft Corporation)Catalog9 07 C:\Windows\SysWOW64\mswsock.dll [305568] (Microsoft Corporation)Catalog9 08 C:\Windows\SysWOW64\mswsock.dll [305568] (Microsoft Corporation)Catalog9 09 C:\Windows\SysWOW64\mswsock.dll [305568] (Microsoft Corporation)Catalog9 10 C:\Windows\SysWOW64\mswsock.dll [305568] (Microsoft Corporation)Catalog9 11 C:\Windows\SysWOW64\mswsock.dll [305568] (Microsoft Corporation)Catalog9 12 C:\Windows\SysWOW64\mswsock.dll [305568] (Microsoft Corporation)x64-Catalog5 01 C:\Windows\System32\napinsp.dll [66560] (Microsoft Corporation)x64-Catalog5 02 C:\Windows\System32\pnrpnsp.dll [85504] (Microsoft Corporation)x64-Catalog5 03 C:\Windows\System32\pnrpnsp.dll [85504] (Microsoft Corporation)x64-Catalog5 04 C:\Windows\System32\NLAapi.dll [79872] (Microsoft Corporation)x64-Catalog5 05 C:\Windows\System32\mswsock.dll [358600] (Microsoft Corporation)x64-Catalog5 06 C:\Windows\System32\winrnr.dll [31232] (Microsoft Corporation)x64-Catalog9 01 C:\Windows\System32\mswsock.dll [358600] (Microsoft Corporation)x64-Catalog9 02 C:\Windows\System32\mswsock.dll [358600] (Microsoft Corporation)x64-Catalog9 03 C:\Windows\System32\mswsock.dll [358600] (Microsoft Corporation)x64-Catalog9 04 C:\Windows\System32\mswsock.dll [358600] (Microsoft Corporation)x64-Catalog9 05 C:\Windows\System32\mswsock.dll [358600] (Microsoft Corporation)x64-Catalog9 06 C:\Windows\System32\mswsock.dll [358600] (Microsoft Corporation)x64-Catalog9 07 C:\Windows\System32\mswsock.dll [358600] (Microsoft Corporation)x64-Catalog9 08 C:\Windows\System32\mswsock.dll [358600] (Microsoft Corporation)x64-Catalog9 09 C:\Windows\System32\mswsock.dll [358600] (Microsoft Corporation)x64-Catalog9 10 C:\Windows\System32\mswsock.dll [358600] (Microsoft Corporation)x64-Catalog9 11 C:\Windows\System32\mswsock.dll [358600] (Microsoft Corporation)x64-Catalog9 12 C:\Windows\System32\mswsock.dll [358600] (Microsoft Corporation)========================= Devices: ================================**** End of log ****

 

Morning. I must be honest it is very hard to tell how this set up should be created with Vendor instructions. Seeing that some are in the Internet, albeit very old, I recommend you contact them and request an update.

I would also confirm that both are still enable since I think you said one wasn't used for some time.

In looking over report above things just don't line up. I compared a few lines back to the previous report. In the first run the Configuration Host name was DESKTOP-AURFGPH. Now it is Desktop. The DNS's were Google that simrick had provided now those are changed. DHCP in the first section was disabled, now its enabled.

Please go back and review all the setting that simrick gave you and then apply them to this network connection.

Honestly your supplier has to have and should be able to supply instructions. Connecting to the network is their business.

 

DESKTOP-AURFGPH was the default computer name. I manually changed it because I didn't like it.

DHCP applies to 3PowerCom Broadband but not to 3Home Broadband, to which PPPoE applies.

Honestly, my supplier has arranged a technician to come here and look into the problem tomorrow.

 

Excellent. To get on PPPoE networks you need a userid and password.

 

If I understand correctly, the staff member told me (in Chinese) that DHCP need not settings under Windows 10. The dedicated modem is like a plug-and-play device.

 

I think I agree. So it was off in first run and on in second. Should be interesting seeing what "The Guy" does to fix.

 

"The Guy" has just left. He said (in Chinese) the master device on another storey does not work, but I have no idea what the device is because I had not gone with him to that storey.

 

I have a spare one now. Last week my friend gave me a used mini router with a cable, and I intend to use PowerCom Broadband via this portable router.