Quentin, I am sorry to hear that you are having issues with your system.
- I would like to know if you have tried using a previous driver version.
- It will be also helpful to know if it is working by Dynamic Host Configuration Protocol (DHCP) or static IP.
- Are you connecting to the 5 GHz or to the 2.4 GHz?
Thanks for your reply.
I've tried previous version such as 16.8, 16.10, etc. It's mainly working under dhcp and 2.4ghz channels.
Qwb 4, do you get an IP address when that issue occurs?
When it shows connecting?
Do you lose connectivity to all or just to the internet?
The IP address was got before the issue occurred and the address was not reset.
The "connecting" was shown up in browser's status bar (chrome). IE failed to connect as well.
Yes, all the connectivities were lost even for my Notes and network drives access.
What is the adapter's IP address when the issue occurs (from ipconfig)? Can you ping the 4G router at such moment?
Yes, the IP address was 192.168.2.2 and I could ping the 4G router successfully.
Are you connecting the LG phone to the computer or to the 4G router?
The X240 failed similarly either by the 4g router or by the LG android phone. These two devices could connect to internet independently. No connection between the phone and the router.
For your further information, while the notebook fails to access internet, another device which use the 4g router could access to internet successfully.
According to your original post you haven’t try the latest driver version which is 17.0.3. Could you give it a try? Please let me know the results.
If it does not resolve the issue, please access this two URL.
The Intel® Wireless Event Viewer program displays a list of error log records. You can save all available log records to a binary format file.
I need you to send me the log at the moment you get the error. So make sure to check the time when that happened.
In fact,, I've already been using the 17.0.3 version. I've started the logger and will come back to you once the problem happens again.
Thanks & regards,
Same problem but no wireless event log was logged.