Ok I’ve tried almost everything, but the problem seems not to come from Windows 7.
The big problem that was the stupid behavior of Windows 7: if I say “hey there’s a DHCP” and it can’t connect to the “DHCP Server”, it should say that somewhere but it doesn’t. Instead, it just “supposes” the network card works properly (which is not the case), and says it has detected a “Public network”. It will never be able to connect to this “Public network” because the network card doesn’t work properly. Anyway that was really confusing, because it was like saying “hey man I found a network, it works, but I can’t connect to it so I guess this is a Public network”…
So the simplest solution I’ve come so far is: boot on the Ubuntu Desktop Live ISO.
- If DHCP discovery works, it’s clearly a 100% Windows problem.
- If it doesn’t it’s a hardware problem.
That was a lot faster than re-installing the whole Windows 7 upgrade stuff and re-installing all my software… just to discover this was a hardware problem and Windows 7 had given very bad clues about what was going wrong.
There should be a Wizard in Seven that could ask:
- “Are you a basic user?”
- “Are you an advanced user?”
If we answer “2”, then
“Do you know how to read advanced network diagnostic?”
If we say “Yes” then “Here’s the detailed diagnostic: DHCP discovery has failed” and tada! Problem solved.
Your question leads me to believe that you might be connecting directly to the Internet. You will always get unknown in that case. If so, to really make sure this does not happen to you all the time, you should have a local router/firewall with a switch with a few ports. You would then have a local LAN, something like 192.168.1.X.
If your Internet goes down, you have not lost your connection to the local network, and you would just reboot your cable modem (or similar) and router, if necessary.
I have been using Windows 7 since it came out. This is not a Windows problem, but it is hard to direct you further without seeing your network. You should really post your ipconfig/all results if you need more help.
Also, when you loconnectionnnection, just try opening an command box, and going ipconfig /release , then ipconfig /renew.
OK, now that you have posted your ipconfig, I see that you are using an internal network, which is good.
This is the big problem: 1) Do you you have a DHCP server set up? Right now, you are getting a 169.x.x.x address, which means that Windows is not getting an IP address either set statically or from DHCP. It gave one to itself…it is called a local link, or automatic private addressing. It is to talk to other computers local to it that have no configuration either.
Make sure your network driver is up-to-date. Make sure your netmask is 255.255.255.0. You can test by pinging 127.0.0.1. If you get no reply, your network card is not set up correctly. Then ping your internal default gateway of 192.168.1.254. Your NIC could also just have died.
Once you have that, you can set a domain in your DHCP server options of mydomain.local. If you are using a static IP address, go to the IPv4 settings>advanced>DNS settings and enter mydomain.local into the Append these DNS Suffixes. It is more for Windows server domains, but it should allow your network to identify itself.
Try this, delete your network locations, then set up a new network connection.
Click the Icon for the unknown network in Network and Sharing Center, then choose “Merge or Delete Network Locations”, highlight all the connections and select delete.
This ip config below means Windows could not reach the dns server, so it assigns an internal network address. Since Ubuntu works, see what DNS server Ubuntu is using, compare it to the manual ip config you did in Windows, which showed it as 192.168.1.254, they should match, next try to ping the DNS server while in Windows.
See this page, try resetting your TCPIP stack, then reboot.
How do I reinstall the TCP/IP protocol driver on Windows 7?
Masque de sous-réseau. . . . . . . . . : 255.255.0.