New PC Build -- everything is *almost* awesome....

First off - this is the new rig:

https://pcpartpicker.com/list/gsWKD8

Assembled it last night, installed Win10 Pro 64-bit. Booted up, grabbed NIC drivers etc from mobo manufacturer website to get that going, but…I am not getting internet access. I’m getting a false IP (169.x.x.x), and when I try to release/renew my IP, I get a message that it cannot reach the DHCP server.

I’ve gone through all of the steps out on the interwebz…hoping someone here may have run into it before. A friend asked his co-worker, who suggested powering down my modem, router and computer, and then booting up only with the new PC wired up (disconnecting my old), and then it might start talking to the DHCP server and work…

I’m not sold on that, but I’m willing to give it a try. Just hoping someone else might have some suggestions…

And please, for the love of all that is holy (GD), please, please, PLEASE…don’t provide me with genero-links to Microsoft support :slight_smile:

I have no optical drive installed in the new system - I’ll pop the CD into my old box and see what I can transfer. I went out to the mobo site and grabbed their all-in-one driver installer, and used that.

I’ll give that a whirl this evening.

edit Jiaco, where’d your post go? :smiley:

Assuming win 10 still has cmd.exe emulation, run that and in the terminal type ipconfig /all and print screen to paint and upload what you get for the wired connection.

I’m not seeing the router, most likely - I don’t have a gateway - just a 169.x.x.x address with a 255.255.0.0 subnet mask.

I can provide more details this evening.

  1. services.msc, stop dhcp client
  2. get cmd console up and type
    netsh winsock reset
  3. restart your pc.

then in cmd type

ipconfig /release
ipconfig /renew

iobit.com/driver-booster/ - Driver Booster - Free software to check your drivers and update them (if needed). Very useful.

I gave this a whirl (stopping the DHCP client - it didn’t like it when I tried, as there were other things associated with it. I can give it another go, though.

I’ll give this a whirl once I get access to the internet :slight_smile:

Ahh, fixed it…apparently at 3am I am not at my best for troubleshooting. The All in One driver pack that ASRock has on their site doesn’t have a good Network Adapter driver in it…downloaded the standalone driver, and got it installed, and bam! I’m up and running!