Case solved ! Thanks to all for helping out with ideas and possible solutions ! Tried everything that was suggested, unfortunately did not help. So I looked back, and found that this pc previously had an AV installed (Norman Antivirus, not to be confused with Norton AV). It was uninstalled some time ago, but some remnants seemed still to be there. So I installed Norman again, then unistalled via Normans special uninstaller. And bingo, I had network connection ! The remnants must have blocked the connection. I should also mention that uninstall Norman via Revo uninstaller or Iobit uninstaller, would NOT solve the case. Had to use the Norman special uninstaller. Thanks again for all support ! Both wired and wlan have same problem. Connected to router. Another pc on same router with automatic,(ipconfig /all) gets ip192.168.1.224, gateway 192.168.1.1 Works fine. Problem pc with same setup, gets 169.254.32.162, active, but no network connection. Finds the network on wlan, but will not connect. Tried everything: Set static ip, same as on the other pc. (192......) Did not help Then: ipconfig /release and ipconfig /renew (this last one locks up.) netsh int ip reset c:\resetlog.txt Reinstalled lan and wlan driver. Nothing helps. Give up if no tip on this forum. Hoping for the best.
169.xxx.xxx.xxx = no DHCP server available to that machine Static to 192.168.1.xx should allow it to connect
You probably trying to open the wrong network.If the other computer uses the same adapter and IP address is 192.168.1.224 then you have to get the same IP, where different is only the last three digits, ie 192.168.1.xxx
169.254.32.162 < looks like your attempting to connect to a different router. How many different routers do you have within your network? Did/does that pc have a static network ip from someplace else?
Like MrMagic said earlier on: The 169.254.x.x range of IP addresses is reserved by Microsoft for private network addressing. If you have a pc set to automatically obtain an IP and you recieve one of these addresses, windows has assigned this because it cannot find a DHCP server within the network subnet. Check to make sure your DHCP server is functioning correctly. If you do not have a DHCP server, you will need to manually set an IP configuration. This can be caused by a virus that corrupts (parts of) the tcp/ip config, scan for virusses etcetc