New PC won't connect to the internet. I've tried everything
17 minutes ago, icewizard64 said:okay, tried the release/renew and it didn't work. what should i do now to fix it?
Ok, the easy fix would just be setting a static IP, this means you filling out the IP details for you computer instead of the the computer getting the details from router (DHCP server).
But i've had a quick read and the easiest fix for this 169.254.xxx.xxx problem is as follows (if this doesn't work we will just take the static ip route, it just means that if you take your laptop to another network you will have to change the details to suit there network, assuming DHCP (auto assigning of ip address information) doesn't work on there network also, so best to try this first then you don't have to mess about with IP stuff in the future):
I've have tried to tail these instructions to you as much as possible.
Steps to follow:
- Run CMD
-
Now type the below command below
netsh interface ipv4 show inter
- It will show like this.
- You have a problem with your adapter and its name is "Wi-Fi" so look out for that. Now find out its corresponding Idx number (at the begging of the line).
- For example my adapter is called "Ethernet" and Its Idx=16 (we will use this idx number in next code, but yours your Idx number for "Wi-Fi"
-
Now type in this code and replace your Idx number, as mine is 16
netsh interface ipv4 set interface 16 dadtransmits=0 store=persistent
so where it says 16 just but you Idx number instead.
- If it says OK, then good.
- Now Click on Start and Run again and Type Services.msc then go down to DHCP Client right click on it and Click on Properties click on Startup Type select Disabled.
- Now Click on Stop Button Below And click on Ok
- Disconnect from your wireless network and then Restart your System
- After Restart don't connect back just yet, Come again to Services.msc find DHCP client right click on it and Click on Properties click on Startup Type now change it back to Automatic
- Click on Start button below and then Ok.
- Now connect back to your network and see if it works, if not check in cmd "ipconfig" to see if you still have that weird "169.254.xxx.xxx" IP. If so last restort we can just set a static IP.
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 accountSign in
Already have an account? Sign in here.
Sign In Now