Hi
@bilel123 , I share some possible solutions for you to try:
Start
Run
CMD
Code:
ipconfig/flushdns
ipconfig /registerdns
ipconfig/release
ipconfig/renew
netsh winsock reset
restart pc and try to connect
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
Other:
a) Right click on the Wi-Fi bars in the taskbar
b) "open the network and shared resources center" or "open internet settings" (I don't use Win8)
c) then where it says "change adapter" in the upper left part right click on the Wi-Fi network and click on "status"
d) then in "wireless properties and then in" security " "type of encryption" and change it to another of those listed in that option (Write down the type of encryption that was before, just in case)
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
If the above does not work I share other information to see if it can help:
A very normal case is when we have a network card, and this is a unit to an ADSL router (for example) which has a PPP type broadband connection.
Recall that in this case, despite having a single physical network adapter, we have TWO network interfaces in Control Panel, Network Connections:
1) the local area connection due to having a network card and
2) The logical interface of the PPP.
So ... we must have IP in both. Interestingly, the router ONLY gives us IP in the PPP broadband connection. Therefore, the local network adapter runs out of IP.
The Internet will work correctly, of course, being on the PPP logical interface and it does not influence you at all that the physics on which it is implemented is unconfigured (or without an IP address).
This does not cause any problems, but we get the message "Limited or no connectivity" and this makes people nervous without knowledge of networks.
SOLUTION
Very simple: simply assign the local area connection an IP of the range reserved for intranets (APIPA addresses). For example, 10.0.0.1
It really is not a solution because it is not necessary because there is no previous problem. But it is the solution for "the nervous" to see that message.
HOW TO DETERMINE WHAT IS WITHOUT IP ADDRESS
We simply open a command window (cmd.exe) and in it we execute:
ipconfig / all
Where we see an address 169.254.xy, is that this adapter is not configured and Windows has acted on it with the autonet configuration mechanism, which is not bad, but it is a facility for users without knowledge of TCP / IP to be able to join two machines and, without needing to do anything, that these can communicate.
If the network does not work
It is due to a DHCP (Dynamic Host Configuration Protocol) problem.
Verify that the DHCP service is active on your Router, and that the DHCP client is active in the Windows services (Start> Run> services.msc).
Verify that the problem does not come from a personal firewall.
As a last resort, manually assign the IP address and verify that it works.
Wi-Fi particular case
Limited or no WiFi connectivity can come from poor configuration of the WEP / WPA security key. In fact, if the key is incorrect, the connection will be established anyway, however the encryption between the modem and its equipment will be different, it will not allow data exchange, as a result it will have limited or no connectivity.