Hello, I have a big help request, I'm completely green in this area and I have a problem with my laptop: It can't identify the network. Despite the lack of knowledge, I will try to describe the problem as accurately as I can. The laptop connected to the wifi network for a long time...

This is normal. Show screen from device manager with expanded list of network cards.

Uninstall or disable virtualbox host-only ethernet adapter.

Unfortunately, no changes. In the network connection status tab, the IPv4 and IPv6 connection points are annotated with No internet access as well no network access -> Picture When looking for a solution on other forums, I found a recommendation to manually enter the IP address and DNS, but it resulted in a wrong IP error. Maybe this is a good method, but I entered the wrong addresses, so if this is a reasonable solution, maybe I could ask for specific addresses to enter in the sense - IP from the router or maybe the latter, from the WAN category? In the picture I also put a screen from the server settings. I'm hiding the values, I'm green, and I don't know if it's completely safe to give this data.

As long as WIFI connects to the router, the screenshots above show that you can use addresses 192.168.0.2 up, unless the router is set differently (IP range). In other words, if not 192.168.0.2, then another one - 192.168.0.3, etc. Also set DNS 8.8.8.8 and one of those you masked.

Unfortunately, manually entering addresses all the time does not change anything. Selecting the option to check the correctness of the settings after finishing generates a Windows diagnostic which of course does not indicate a problem. I think I will have to look for a professional service, however, so that someone sensible can see it on the spot. DriverMSG - thanks for your interest in the topic.

Recently, I was struggling with a similar problem on a TP-Link like yours. Changing the channel to e.g. 1 solved the problem. I did not have time to delve into the topic, but when it was set up from the machine, or at 11, it could not identify the network. Delete all saved profiles for wireless networks in the Network and Sharing Center -> Manage Wireless Networks

I finally fired up ubuntu from the disc - wifi worked there. As I couldn't find the problem any further, I decided to format, reinstalled the system and now everything is fine. I still don't know what exactly it was about but the topic is now closed, thanks for the advice.

Lenovo Z500 can't identify network via WiFi or cable on TP-Link WR741ND after OS change

KANQAKS 47835 8

Treść została przetłumaczona

Zobacz oryginalną wersję tematu

Reply | New topic

#1 14038116 13 Oct 2014 15:57

KANQAKS KANQAKS

Level 9

» |

Post #1
14038116 13 Oct 2014 15:57

Hello,
I have a big help request, I'm completely green in this area and I have a problem with my laptop: It can't identify the network. Despite the lack of knowledge, I will try to describe the problem as accurately as I can.
The laptop connected to the wifi network for a long time without problems, one day it just stopped. I do not see a connection between this, but it coincided with the change of the system on the PC, exactly after this change, the laptop could not identify the network. If I connect a cable to the paw without a router and create a direct connection, everything is fine, but connection via a router with a cable and wifi is not possible. Other devices (PCty or phone) connect without problem, the router reset did not help.
Lenovo z500 laptop
router tp-linkWR741ND
ipconfig of a directly connected laptop:

Spoiler:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C: \ Users \ aa> ipconfig

Windows IP configuration

PPP radionet card:

Connection-specific DNS Suffix:
IPv4 address. . . . . . . . . . . . . : 217.28.154.130
Subnet mask. . . . . . . . . . : 255.255.255.255
Deafult Gateway. . . . . . . . . . : 0.0.0.0

Ethernet adapter Local connection:

Connection-specific DNS Suffix:
Local connection IPv6 address. : fe80 :: 1d93: a0c8: 1453: bd09% 16
Auto-configuration IPv4 address. . . . : 169.254.189.9
Subnet mask. . . . . . . . . . : 255.255.0.0
Deafult Gateway. . . . . . . . . . :

Wireless LAN adapter Wireless LAN connection 3:

Condition of the media. . . . . . . . . . .: Media disconnected
Connection-specific DNS Suffix:

Wireless LAN adapter Wireless LAN connection 2:

Condition of the media. . . . . . . . . . .: Media disconnected
Connection-specific DNS Suffix:

Wireless LAN adapter Wireless LAN connection:

Connection-specific DNS Suffix:
Local connection IPv6 address. : fe80 :: e1e6: f055: 174a: 314c% 13
Auto-configuration IPv4 address. . . . : 169.254.49.76
Subnet mask. . . . . . . . . . : 255.255.0.0
Deafult Gateway. . . . . . . . . . :

Ethernet Bluetooth Network Connection Card:

Condition of the media. . . . . . . . . . .: Media disconnected
Connection-specific DNS Suffix:

VirtualBox Host-Only Network Ethernet Adapter:

Connection Specific DNS Suffix:
Local connection IPv6 address. : fe80 :: 5cb2: 6e8c: 6e26: a008% 22
IPv4 address. . . . . . . . . . . . . : 192.168.56.1
Subnet mask. . . . . . . . . . : 255.255.255.0
Deafult Gateway. . . . . . . . . . :

Isatap tunnel card. {19814983-A0E9-4C08-AE05-A35279AB8505}:

Condition of the media. . . . . . . . . . .: Media disconnected
Connection-specific DNS Suffix:

Isatap Tunnel Card. {87D47207-DBDD-4262-8ABF-7923D350C498}:

Condition of the media. . . . . . . . . . .: Media disconnected
Connection Specific DNS Suffix:

Isatap Tunnel Card. {355F374F-AB6E-42A8-BACD-9B3974F176B8}:

Condition of the media. . . . . . . . . . .: Media disconnected
Connection-specific DNS Suffix:

Isatap Tunnel Card. {CE4F6CE5-86B6-48D2-AB8B-CBFD60B4F4B9}:

Condition of the media. . . . . . . . . . .: Media disconnected
Connection-specific DNS Suffix:

Isatap tunnel card. {3C969E30-ACFB-46B6-8C49-1AC2AE436EA3}:

Condition of the media. . . . . . . . . . .: Media disconnected
Connection-specific DNS Suffix:

Teredo Tunneling Pseudo-Interface Card:

Condition of the media. . . . . . . . . . .: Media disconnected
Connection-specific DNS Suffix:

Isatap tunnel card. {954E6259-6619-4236-90B5-A076113117CF}:

Condition of the media. . . . . . . . . . .: Media disconnected
Connection-specific DNS Suffix:

6TO4 Tunnel Card Adapter:

Connection-specific DNS Suffix:
IPv6 address. . . . . . . . . . . . : 2002: d91c: 9a82 :: d91c: 9a82
Deafult Gateway. . . . . . . . . . : 2002: c058: 6301 :: 1

Isatap Tunnel Card. {0716F97D-00D2-414C-ADA8-972528D917AE}:

Condition of the media. . . . . . . . . . .: Media disconnected
Connection-specific DNS Suffix:

C: \ Users \ aa>

ipconfig
trying to connect via wifi

Spoiler:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C: \ Users \ aa> ipconfig

Windows IP configuration

Ethernet adapter Local connection:

Condition of the media. . . . . . . . . . .: Media disconnected
Connection-specific DNS Suffix:

Wireless LAN adapter Wireless LAN connection 3:

Condition of the media. . . . . . . . . . .: Media disconnected
Connection-specific DNS Suffix:

Wireless LAN adapter Wireless LAN connection 2:

Condition of the media. . . . . . . . . . .: Media disconnected
Connection-specific DNS Suffix:

Wireless LAN adapter Wireless LAN connection:

Connection-specific DNS Suffix:
Local connection IPv6 address. : fe80 :: e1e6: f055: 174a: 314c% 13
Auto-configuration IPv4 address. . . . : 169.254.49.76
Subnet mask. . . . . . . . . . : 255.255.0.0
Deafult Gateway. . . . . . . . . . :

Ethernet Bluetooth Network Connection Card:

Condition of the media. . . . . . . . . . .: Media disconnected
Connection-specific DNS Suffix:

VirtualBox Host-Only Network Ethernet Adapter:

Connection-specific DNS Suffix:
Local connection IPv6 address. : fe80 :: 5cb2: 6e8c: 6e26: a008% 22
IPv4 address. . . . . . . . . . . . . : 192.168.56.1
Subnet mask. . . . . . . . . . : 255.255.255.0
Deafult Gateway. . . . . . . . . . :

Isatap tunnel card. {19814983-A0E9-4C08-AE05-A35279AB8505}:

Condition of the media. . . . . . . . . . .: Media disconnected
Connection Specific DNS Suffix:

Isatap Tunnel Card. {87D47207-DBDD-4262-8ABF-7923D350C498}:

Condition of the media. . . . . . . . . . .: Media disconnected
Connection Specific DNS Suffix:

Isatap tunnel card. {355F374F-AB6E-42A8-BACD-9B3974F176B8}:

Condition of the media. . . . . . . . . . .: Media disconnected
Connection Specific DNS Suffix:

Isatap tunnel card. {3C969E30-ACFB-46B6-8C49-1AC2AE436EA3}:

Condition of the media. . . . . . . . . . .: Media disconnected
Connection Specific DNS Suffix:

Teredo Tunneling Pseudo-Interface Card:

Condition of the media. . . . . . . . . . .: Media disconnected
Connection-specific DNS Suffix:

Isatap tunnel card. {954E6259-6619-4236-90B5-A076113117CF}:

Condition of the media. . . . . . . . . . .: Media disconnected
Connection-specific DNS Suffix:

Isatap Tunnel Card. {CE4F6CE5-86B6-48D2-AB8B-CBFD60B4F4B9}:

Condition of the media. . . . . . . . . . .: Media disconnected
Connection-specific DNS Suffix:

C: \ Users \ aa>

Please help

Rust on Embedded Online Conference on 16 July with 33 per cent discount for elektroda users
ADVERTISEMENT
#2 14058308 20 Oct 2014 19:31

DriverMSG DriverMSG

Admin of Computers group

» | Helpful post? (+5)

Post #2
14058308 20 Oct 2014 19:31

KANQAKS wrote:
connection via router via cable and wifi is not possible.
This is normal.
Show screen from device manager with expanded list of network cards.
ADVERTISEMENT
#3 14058873 20 Oct 2014 21:44

KANQAKS KANQAKS

Level 9

» | Topic author Helpful post? (+4)

Post #3
14058873 20 Oct 2014 21:44

https://obrazki.elektroda.pl/6685331200_1413834220.jpg
#4 14058957 20 Oct 2014 22:04

DriverMSG DriverMSG

Admin of Computers group

» | Helpful post? (+2)

Post #4
14058957 20 Oct 2014 22:04

Uninstall or disable virtualbox host-only ethernet adapter.
ADVERTISEMENT
#5 14059093 20 Oct 2014 22:43

KANQAKS KANQAKS

Level 9

» | Topic author Helpful post? (+2)

Post #5
14059093 20 Oct 2014 22:43

Unfortunately, no changes. In the network connection status tab, the IPv4 and IPv6 connection points are annotated with
No internet access as well
no network access -> Picture
When looking for a solution on other forums, I found a recommendation to manually enter the IP address and DNS, but it resulted in a wrong IP error. Maybe this is a good method, but I entered the wrong addresses, so if this is a reasonable solution, maybe I could ask for specific addresses to enter in the sense - IP from the router or maybe the latter, from the WAN category? In the picture I also put a screen from the server settings. I'm hiding the values, I'm green, and I don't know if it's completely safe to give this data.
#6 14059241 20 Oct 2014 23:31

DriverMSG DriverMSG

Admin of Computers group

» | Helpful post? (+3)

Post #6
14059241 20 Oct 2014 23:31

As long as WIFI connects to the router, the screenshots above show that you can use addresses 192.168.0.2 up, unless the router is set differently (IP range).
In other words, if not 192.168.0.2, then another one - 192.168.0.3, etc.

Also set DNS 8.8.8.8 and one of those you masked.
#7 14059370 21 Oct 2014 00:38

KANQAKS KANQAKS

Level 9

» | Topic author Helpful post? (+3)

Post #7
14059370 21 Oct 2014 00:38

Unfortunately, manually entering addresses all the time does not change anything. Selecting the option to check the correctness of the settings after finishing generates a Windows diagnostic which of course does not indicate a problem.
I think I will have to look for a professional service, however, so that someone sensible can see it on the spot.
DriverMSG - thanks for your interest in the topic.
#8 14061140 21 Oct 2014 19:49

fanfiction fanfiction

Level 14

» | Helpful post? (+4)

Post #8
14061140 21 Oct 2014 19:49

Recently, I was struggling with a similar problem on a TP-Link like yours. Changing the channel to e.g. 1 solved the problem.
I did not have time to delve into the topic, but when it was set up from the machine, or at 11, it could not identify the network.

Delete all saved profiles for wireless networks in the Network and Sharing Center -> Manage Wireless Networks
ADVERTISEMENT
#9 14160890 24 Nov 2014 14:26

KANQAKS KANQAKS

Level 9

» | Topic author Helpful post? (+2)

Post #9
14160890 24 Nov 2014 14:26

I finally fired up ubuntu from the disc - wifi worked there. As I couldn't find the problem any further, I decided to format, reinstalled the system and now everything is fine. I still don't know what exactly it was about but the topic is now closed, thanks for the advice.
Create an account, log in and become active in a forum and ads will not appear. You will receive points by participating in discussions.
Join this discussion.

Install the application

Didn't find an answer? Ask Artificial Intelligence

*I agree to send the question to OpenAI, Anthropic PBC, Perplexity AI, Inc., Kagi Inc., Google LLC - owners of language models in order to prepare the best response. The companies may monitor and log information entered into the form.

*I agree to publicly display my question and answer. The question and answer will be publicly available to everyone. The process may take a few minutes. Upon completion, you will be redirected to the page with the answer.

Wait...(2min)

Reply | New topic

Report a violation of the law

Topic summary

The discussion revolves around a Lenovo Z500 laptop that is unable to identify a Wi-Fi network after a system change, despite functioning correctly with a direct cable connection. Other devices connect to the TP-Link WR741ND router without issues. Suggestions include checking the device manager for network cards, uninstalling the VirtualBox host-only Ethernet adapter, manually entering IP and DNS settings, and changing the router's Wi-Fi channel. The user ultimately resolved the issue by formatting the laptop and reinstalling the operating system, which restored Wi-Fi functionality.
Summary generated by the language model.

Lenovo Z500 can't identify network via WiFi or cable on TP-Link WR741ND after OS change

Didn't find an answer? Ask Artificial Intelligence

Topic summary