Strange wi-fi problem

tomle3

Commendable
Dec 4, 2016
7
0
1,510
I have been having an issue with my PC's Wi-Fi. this problem only effects my pc not iphones/ipads/other pc's/laptops.

The computer says it is connected but the internet is either unusably slow or not working at all. if I disconnect and then reconnect I get full speed for a matter of seconds then goes back to nothing.

I have tried lots of things but most recently have done a clean reinstall of windows 10 and purchased a new tp-link Wi-Fi card. but still it does not work.

currently I am hard wired to my network and it works fine.

here is my pc info.
System Information
------------------
Time of this report: 12/4/2016, 19:04:36
Machine name: DESKTOP-KRRRGRU
Machine Id: {FB85A91C-58CD-4CD0-85E7-B7339A0F1015}
Operating System: Windows 10 Home 64-bit (10.0, Build 14393) (14393.rs1_release_inmarket.161102-0100)
Language: English (Regional Setting: English)
System Manufacturer: Gigabyte Technology Co., Ltd.
System Model: To be filled by O.E.M.
BIOS: BIOS Date: 10/05/12 13:07:27 Ver: 04.06.05
Processor: AMD A10-6800K APU with Radeon(tm) HD Graphics (4 CPUs), ~4.1GHz
Memory: 16384MB RAM
Available OS Memory: 16332MB RAM
Page File: 4130MB used, 15144MB available
Windows Dir: C:\Windows
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
DxDiag Version: 10.00.14393.0000 64bit Unicode

The WiFi is working and has full signal to my computer

Any help will be greatly appreciated if i cant get it sorted I'm going to have to get the drill out and drill into my walls to provide permanent LAN connection
how very 2005!!
 

Ralston18

Titan
Moderator
Just for the record what make and model is your router? I.e. TP-Link?

How many network devices are present: wired, wireless? Any access points?

Have you checked all network devices for a possible IP conflict with your computer? Are you using any static IP addresses or perhaps more IP addresses than being permitted for DHCP assignment? Who manages the router - administrative help may be needed.

Try to ensure that there is no network or network configuration issue. Then delve into your computer's configuration.

Are you familar with Event Viewer?

Event Viewer may be capturing some error code or warning that occurs just before or at the time your computer's wifi drops off.

Check the Event Viewer logs and see what you can find. Look for yellow and red icons. Any errors can be right-clicked for more details.



 

tomle3

Commendable
Dec 4, 2016
7
0
1,510
Thanks for your reply.

I have a BT Business hub 3 which is hard wired to a TP-Link Archer C2
connected to the BT Hub are 2 hard wired PC's
The TP Link is usually only for wireless but right now my pc which has this issue is hard wired. usually we have 4 iPhone, 1 iPad and 1 PC wirelessly connected.

I am fairly computer savvy but I am certainly not an expert. I have checked and as far as I can see there is no limit for DHCP assignment.
the BT hub has static IP disabled and the TP-link is set to dynamic IP.

I have checked event viewer there are a few entries but most seem normal apart from CAPI2 event 513 seems to happen regularly.

I can confirm I am the network administrator.
 

Ralston18

Titan
Moderator
Setup then being:

ISP ----> BT Business Hub 3 [LAN] ----ethernet cable ---> [LAN] TP-Link Archer C2 ~~~~~~~> wireless devices (x6)
Also BT Business Hub 3 [LAN] ----ethernet cable x2 -----> Hardwired PC's

With your PC temporarily hardwired to the BT Hub.

And the TP-Link Archer C2 is serving as the router (and the BT Hub router functionality is turned off).

No set static IP addresses on any devices.

However, what IP addresses are being used for the BT Hub and TP-Link Archer?

Can you run and post the results of "ipconfig /all" via the Command Prompt on your PC.

Thanks.


 

tomle3

Commendable
Dec 4, 2016
7
0
1,510
Yes all the details you have are correct except that the BT hub is transmitting wireless.

I have included the details from the CMD and a copy of the status of both the TP-Link and BT hub


---TP-LINK----
Status

Firmware Version:
0.9.1 4.1 v0032.0 Build 160512 Rel.40318n
Hardware Version:
Archer C2 v1 00000002

LAN
MAC Address:
C4:6E:1F:2F:12:04
IP Address:
192.168.0.1
Subnet Mask:
255.255.255.0

Wireless 2.4GHz
Wireless Radio:
Enabled
Name(SSID):
Tom & Becky
Mode:
11bgn mixed
Channel:
Auto(Channel 10)
Channel Width:
Auto
MAC Address:
C4:6E:1F:2F:12:04
WDS Status:
Disabled


Wireless 5GHz
Wireless Radio:
Disabled
Name(SSID):
TP-LINK_1204_5G
Mode:
11a/n/ac mixed
Channel:
Auto(Channel 44)
Channel Width:
Auto
MAC Address:
C4:6E:1F:2F:12:03
WDS Status:
Disabled


WAN
MAC Address:
C4:6E:1F:2F:12:05
IP Address:
192.168.1.69(Dynamic IP)
Subnet Mask:
255.255.255.0
Default Gateway:
192.168.1.254
DNS Server:
192.168.1.254 0.0.0.0




----BT HUB------

Hub IP Gateway Address

IP Address: 192.168.1.254

Subnet mask: 255.255.255.0

 
 
DHCP Server

Enable:
YesNo
 
 
DHCP Network Range
If you change the IP address range, you must renew the DHCP lease and or static IP addresses for all devices on the network
 
192.168.1.64 - 192.168.1.253 (Default)
 
172.16.0.64 - 172.16.255.254
 
10.0.0.2 - 10.255.255.254
 
Configure manually
Lease time:
Days    Hours
Valid leases are between 1 hour and 21 days





-----CMD------

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Users\Tom>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-KRRRGRU
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 90-2B-34-AE-D6-01
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::c864:e6bf:8d72:5ee6%13(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.112(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 08 December 2016 21:04:48
Lease Expires . . . . . . . . . . : 08 December 2016 23:04:48
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 227552052
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-CC-51-9F-90-2B-34-AE-D6-01
DNS Servers . . . . . . . . . . . : 192.168.0.1
0.0.0.0
NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : C6-E9-84-32-A3-59
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter WiFi:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TP-LINK 802.11ac Network Adapter
Physical Address. . . . . . . . . : C4-E9-84-32-A3-59
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{9D27A661-B05C-4209-8689-A4C6F08EDD61}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fb:28b5:11b:ae64:7af8(Preferred)
Link-local IPv6 Address . . . . . : fe80::28b5:11b:ae64:7af8%6(Preferred)
Default Gateway . . . . . . . . . : ::
DHCPv6 IAID . . . . . . . . . . . : 553648128
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-CC-51-9F-90-2B-34-AE-D6-01
NetBIOS over Tcpip. . . . . . . . : Disabled

I hope this helps
I'm very grateful you are trying to help
 

Ralston18

Titan
Moderator
Thank you for the printed details.

DESKTOP-KRRRGRU is currently wired and getting its IP address (192.168.0.112) dynamically assigned by the TP-LINK Router at 192.168.0.1

(As should all other wired and wireless devices.)

Well and good.

However you want DESKTOP-KRRRGRU to be wireless.

And the BT Hub (connected to your ISP) is also to be wireless with respect to the TP-Link Archer2 router.

How are you configuring the new wireless card on DESKTOP-KRRRGRU: specifically the Default Gateway, subnet mask. And you have been disabling the ethernet adapter when going wireless - correct?

Can you send another ipconfig /all from one of the devices that is working wirelessly.

I do have a nagging question about the IP addressing but if everything else is working okay then we do not really change anything. I will see if I can find the answer in the meantime.
 

tomle3

Commendable
Dec 4, 2016
7
0
1,510
I am not sure how to configure the new wireless card. I just plugged it in installed the most recent drivers and let windows sort the rest.
also I didn't try disabling the Ethernet adapter as I just pulled the plug out (should I try disabling it?)

unfortunately I do not have any more windows pc's on the tplink hub only apple iphones and ipads. there is a desktop connected to the bt hub would it help to get the config for that one?

if it helps I would be prepared to allow you access to my pc via TeamViewer or similar if you think that could be useful.
 

Ralston18

Titan
Moderator
Yes. Disable the wired adapter.

Also yes it would be helpful to see the ipconfig for the desktop connected to the bt hub.

You probably can find the wireless configuration information on one of the iPads. Just looking to confirm or see some working wireless device.

And the new TP-Link wireless card does need to be configured. We can get to that later - I still need to look into something there.

Appreciate the trust but no need to provide access - Teamviewer or otherwise. Things can go astray well enough without the vagaries of some remote repair attempt.



 

tomle3

Commendable
Dec 4, 2016
7
0
1,510
iPhone config is
IP Address 192.168.0.103
Subnet Mask 255.255.255.0
Router 192.168.0.1
DNS 192.168.0.1, 0.0.0.0
Search Domains (blank)
Client ID (blank)

IP Config from other Desktop (connected via Ethernet too BT hub)

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Users\Bill>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : FARMOFFICE
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : home

Wireless LAN adapter Local Area Connection* 11:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : 1A-94-23-01-F2-11
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 78-45-C4-2F-43-9B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::e53a:3c8e:109a:b551%14(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.71(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 08 December 2016 23:56:02
Lease Expires . . . . . . . . . . : 09 December 2016 23:56:01
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.254
DHCPv6 IAID . . . . . . . . . . . : 259540420
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-20-A7-E6-78-45-C4-2F-43-9B
DNS Servers . . . . . . . . . . . : 192.168.1.254
NetBIOS over Tcpip. . . . . . . . : Enabled

Wireless LAN adapter Wi-Fi:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : Dell Wireless 1506 802.11b|g|n (2.4GHz)
Physical Address. . . . . . . . . : 68-94-23-01-F2-11
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.home:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : home
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fb:347b:fbfd:ae64:7af8(Preferred)
Link-local IPv6 Address . . . . . : fe80::347b:fbfd:ae64:7af8%16(Preferred)
Default Gateway . . . . . . . . . : ::
DHCPv6 IAID . . . . . . . . . . . : 335544320
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-20-A7-E6-78-45-C4-2F-43-9B
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Users\Bill>



I have disabled the Ethernet adapter and now it seems to be working. I'm going to go to bed now but I will be using the pc quite a bit tomorrow so i'll let you know how I get on.

would having it enabled but not plugged in cause a conflict??? it always used to be enabled and used to work fine!
 

tomle3

Commendable
Dec 4, 2016
7
0
1,510
Unfortunately although it seemed to work for a while the problem still persists although strangely it is not as bad as it was.

Now it seems to just be really slow on Wi-Fi and doesn't drop completely as much as it did before.

all other devices still running fine!
 

Ralston18

Titan
Moderator
If only your desktop is affected and only when in wireless then it may be a matter of the desktop's wireless adapter simply not "playing" well with the wireless router. May need to be manually configured versus some "auto" or "auto negotiate". Or vice versa even.

With everything else working well I would not and do not want to make any changes with respect to your overall network setup and configuration.

In wireless is Desktop-KRRRGRU connecting to the BT Hub or the TP-link?

Which one (TP-Link or BT) do you expect or want the desktop to wirelessly connect to? Frequency, channel, standard....

From your December 8th post:

Wireless LAN adapter WiFi:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TP-LINK 802.11ac Network Adapter
Physical Address. . . . . . . . . : C4-E9-84-32-A3-59
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Is DESKTOP-KRRRGRU's wireless adapter built-in, USB, or PCI-x (internal slot). Do you know the model number?

Please run and post "ipconfig /all" from DESKTOP-KRRRGRU while in wireless mode and working (albeit slowly).

The objective is to determine DESKTOP-KRRRGRU's wireless configuration with respect to your network.

 

tomle3

Commendable
Dec 4, 2016
7
0
1,510
I would like Desktop-KRRRGRU to connect wirelessly to TP-link the bt hub is out of range. I have no preference to Frequency, channel, standard...... (these are currently at default setting)

The wireless adapter is a new AC1750 Wireless Dual Band PCI Express Adapter
Archer T8E.
which I purchased because I thought my old adapter was at fault.

below is the ip config data whilst connected wirelessly with Ethernet disabled

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Users\Tom>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DESKTOP-KRRRGRU
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Wireless LAN adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : C6-E9-84-32-A3-59
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Wireless LAN adapter WiFi:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : TP-LINK 802.11ac Network Adapter
Physical Address. . . . . . . . . : C4-E9-84-32-A3-59
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::74e0:9fb6:75f:4682%17(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.100(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 12 December 2016 16:38:55
Lease Expires . . . . . . . . . . : 12 December 2016 18:38:55
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 247785860
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-CC-51-9F-90-2B-34-AE-D6-01
DNS Servers . . . . . . . . . . . : 192.168.0.1
0.0.0.0
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{FE3963BE-310B-4890-BEB5-7F9E8563A118}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fb:28b5:11b:ae64:7af8(Preferred)
Link-local IPv6 Address . . . . . : fe80::28b5:11b:ae64:7af8%6(Preferred)
Default Gateway . . . . . . . . . : ::
DHCPv6 IAID . . . . . . . . . . . : 553648128
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-CC-51-9F-90-2B-34-AE-D6-01
NetBIOS over Tcpip. . . . . . . . : Disabled

C:\Users\Tom>












 

Ralston18

Titan
Moderator
Probably need to get away from the default settings.

DESKTOP-KRRRGRU is wirelessly connecting to the TP-LINK Archer C2. We know that via the "ipconfig /all" results.

I.e., the operational Wireless LAN adapter WiFi is the TP-Link 802.11ac Network Adapter. It is requesting and receiving its' DHCP IP address (192.168.0.100) from your TP-Link Archer C2 at 192.168.0.1

Your original December 8th post noted the following with respect to the Archer C2:

Wireless 2.4GHz
Wireless Radio:
Enabled
Name(SSID):
Tom & Becky
Mode:
11bgn mixed
Channel:
Auto(Channel 10)
Channel Width:
Auto
MAC Address:
C4:6E:1F:2F:12:04
WDS Status:
Disabled

Most likely "DESKTOP-K" is using a slower wireless connection.

Look at DESKTOP-K's adapter settings. Reconfigure the wireless adapter setting to manually match the Archer C2 Router (versus auto).

See what can be done there to improve wireless performance. The focus being on making changes to just the adapter so as not to mess up anything else. Keep track of changes so you can reverse or undo them if necessary.

I think there are some other things that could be done but for everyone's sake (including me) - small steps.

Will offer one more suggestion. You might try running "netsh wlan show all" at the command prompt. The output results provide many more details about your wireless LAN.
 

Ralston18

Titan
Moderator
@mjslakeridge - Thanks.

I generally watch for private IP addresses and personal email addresses being posted. Have not considered MAC address's per se. Have not noticed any general cautions about posting MAC/physical addresses with regards to security/safety.

Especially with respect to being shown in the results of "ipconfig /all". Even knowing that the MAC (physical address) can be spoofed etc..

The MAC addresses are helpful - to me at least - in getting a sense of the overall wired and wireless network's configuration/components.

That said there would be no harm, I think, if the OP(s) were to mask out the first four octets hiding the manufacturer and some part of the specific device octets.

Unfortunately such direction could cause confusion and/or perhaps mask some relevant information if the physical address is not shown.

However "just to be safe" I think should trump the issue. I.e., maybe just scrub MACs for any routers would be good middle ground.

Can always request more information (partial MAC) if truly relevant and necessary.



 
I was not sure whether a MAC address being public could represent a security issue, but I thought to ask. (There was a thread here on Toms yesterday asking that specific question, as of now no-one has answered it):

http://www.tomshardware.com/answers/id-3267958/privacy-mac-address.html

I can see your point about it being useful to you to understand the configuration of someone's system, but that could always be given to you via a PM if needed.
 

Ralston18

Titan
Moderator
Agreed. Could ask if truly needed.

However I, personnally, would be more likely to make some attempt to first provide some guidance to the OP that would help that person to figure something out via the MAC address requirement on their own. Despite getting into the weeds too far or working with language/translation and terminology issues etc.. Also keeps the thread public which is good - especially when I missed something or have otherwise gone off track.

As for the referenced post I had not read until now.

My response would be that there quite a bit of information on the web about MAC address spoofing and would refer the OP accordingly. Especially with respect to wireless networks.

For now, may be something (and perhaps better so) that one of the moderators or security-minded members would wish to respond to.

With respect to the current problem my thought is that the desktop's wireless adapter configuration is not what it could or should be. Especially with everything else being okay.