Jump to content

Fresh Windows 10 won't connect to network

SatanExe

Fresh install of Windows 10, I have tried connecting to my router via ethernet and using my wireless network adapter. The ethernet itself says "unidentified network" (can't even see 192.168.1.1) and when connecting via WiFi it says connected, no Internet, secured (also can't see 192.168.1.1).

 

Specs:

Intel I7 5820k

ASUS X99-A USB.3.1 MOBO

WNA: Qualcomm Atheros AR938x (PCIE) 

16GB RAM @2666MHz

GEFORCE 980TI

 

Thanks

Link to comment
Share on other sites

Link to post
Share on other sites

Did you install the Ethernet and wifi drivers?

Current Network Layout:

Current Build Log/PC:

Prior Build Log/PC:

Link to comment
Share on other sites

Link to post
Share on other sites

1 minute ago, Lurick said:

Did you install the Ethernet and wifi drivers?

Yeah, I installed the latest stable versions from ASUS and Qualcomm

Link to comment
Share on other sites

Link to post
Share on other sites

7 minutes ago, BlueBeachMonster said:

Fresh install of Windows 10, I have tried connecting to my router via ethernet and using my wireless network adapter. The ethernet itself says "unidentified network" (can't even see 192.168.1.1) and when connecting via WiFi it says connected, no Internet, secured (also can't see 192.168.1.1).

 

Specs:

Intel I7 5820k

ASUS X99-A USB.3.1 MOBO

WNA: Qualcomm Atheros AR938x (PCIE) 

16GB RAM @2666MHz

GEFORCE 980TI

 

Thanks

Reinstall windows... again. There was probably a some installation error that the OS skipped over.

In search of the future, new tech, and exploring the universe! All under the cover of anonymity!

Link to comment
Share on other sites

Link to post
Share on other sites

Just now, Wh0_Am_1 said:

Reinstall windows... again. There was probably a some installation error that the OS skipped over.

No thanks, didn't mention it but the reason I even installed this new version with a freshly formatted drive is because I had this issue with my previous install of W10 too. 

Link to comment
Share on other sites

Link to post
Share on other sites

Just now, BlueBeachMonster said:

No thanks, didn't mention it but the reason I even installed this new version with a freshly formatted drive is because I had this issue with my previous install of W10 too. 

Did you create a new installation disk when installing windows?

In search of the future, new tech, and exploring the universe! All under the cover of anonymity!

Link to comment
Share on other sites

Link to post
Share on other sites

3 minutes ago, Wh0_Am_1 said:

Did you create a new installation disk when installing windows?

Yeah

Link to comment
Share on other sites

Link to post
Share on other sites

Just now, BlueBeachMonster said:

Yeah

Ok, just checking, because if you just reset your PC and used what remains of Windows installation media on the drive, it could have been corrupted, same if it was from the same installation disk as last time.

In search of the future, new tech, and exploring the universe! All under the cover of anonymity!

Link to comment
Share on other sites

Link to post
Share on other sites

That new installation disk... From a freshly downloaded copy of the Media Creation Tool or the same one from the installation that first was giving you problems?

Desktop: [Processor: Intel Skylake i5 6600K (stock for now)][HSF: CoolerMaster Hyper 212 EVO]
[PSU: EVGA SuperNova 750 B2][Case: Corsair Carbide Series Air 540 Silver]
[Motherboard: AsRock Z170 Extreme4][RAM: 2x8GB Corsair Vengeance LPX DDR4-2666]
[Video: eVGA GeForce GTX 1060 3GB 03G-P4-6160-KR]
[Hard Drives: Samsung 850 EVO 500GB]
Notebook: [HP Envy x360 15z][Ryzen 7 2700U w/ Radeon RX Vega 10][8GB RAM][256GB m.2 nVME SSD]

Gaming:[SteamID: STEAM_0:0:1792244 - "[TC]CreepingDeath"]

Link to comment
Share on other sites

Link to post
Share on other sites

43 minutes ago, GilmourD said:

That new installation disk... From a freshly downloaded copy of the Media Creation Tool or the same one from the installation that first was giving you problems?

Already answered this, fresh install and fresh install media. 

Link to comment
Share on other sites

Link to post
Share on other sites

17 hours ago, BlueBeachMonster said:

Already answered this, fresh install and fresh install media. 

Well, you answered the first part.

 

But... OK. So, this problem crops up on some machines at my job for some reason. We haven't tracked down the actual cause but for some reason these machines aren't talking to the DHCP server. What we do to fix is this from the command line.

 

ipconfig /release

ipconfig /flushdns

ipconfig /flushdns

ipconfig /flushdns

ipconfig /flushdns

ipconfig /renew

 

Yeah, I like to flush the DNS resolver cache a few times because sometimes (just sometimes) it doesn't like to actually clear everything out.

 

If that doesn't work, can you post a pic of what it says when you run "ipconfig /all"?

 

An example from my work machine (yeah, I blacked out part of our domain):

 

image.png.e79ba172ddc9534bd39f5be8e2db1344.png

Desktop: [Processor: Intel Skylake i5 6600K (stock for now)][HSF: CoolerMaster Hyper 212 EVO]
[PSU: EVGA SuperNova 750 B2][Case: Corsair Carbide Series Air 540 Silver]
[Motherboard: AsRock Z170 Extreme4][RAM: 2x8GB Corsair Vengeance LPX DDR4-2666]
[Video: eVGA GeForce GTX 1060 3GB 03G-P4-6160-KR]
[Hard Drives: Samsung 850 EVO 500GB]
Notebook: [HP Envy x360 15z][Ryzen 7 2700U w/ Radeon RX Vega 10][8GB RAM][256GB m.2 nVME SSD]

Gaming:[SteamID: STEAM_0:0:1792244 - "[TC]CreepingDeath"]

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×