Internet not working on desktop but functional on all other devices

elarsen

Commendable
Aug 19, 2016
11
0
1,510
I have recently had issues with the internet connection on my desktop computer. Rather than immediately rush to a forum to post for help, I searched various places for things to try before posting this. So, here's some information that might help determine the cause of this issue:

-As far as I can remember, my desktop was connecting to the internet perfectly fine until I installed a new case fan about a week ago, but I didn't think this would affect anything. And yes, I've already checked and double-checked to make sure all cables are still connected firmly where they are supposed to go.

-The wireless internet works perfectly on my phone, laptop, playstation, etc. My desktop has an ethernet cable running directly from the router,which is about 6-7 feet away. The ethernet cable has no issues because I unplugged it from my desktop and plugged it into my laptop (making sure to entirely disable wireless functionality) and I was still able to connect to the internet. Furthermore, the LED indicator next to the ethernet port on the back of my PC lights up like normal.

-I have an Actiontec C1900A router/modem combo. I tried both unplugging/plugging the router back in as well as performing a full reset. Neither one helped.

-My desktop is able to recognize a network, but it is labeled as "Unidentified network", and no internet access is present. I have already tried changing how an IP address was obtained from automatic to manual, and I tried the following configurations as per forum results I found:
IP address: 192.168.0.2 & 192.168.0.50
Subnet mask: 255.255.255.0
Default gateway: 192.168.0.1

-When I run 'ipconfig' in command prompt, my autoconfiguration IPv4 address starts with 169, which I've read is an issue, hence trying manual input of the information as previously mentioned.

-My motherboard's LAN driver is up to date, but just to be sure, I uninstalled and reinstalled the driver. This did nothing.

-I ran a virus/malware scan and everything checked out.

Any help at all would be very greatly appreciated.
 
The 169. etc. IP is an address that Windows self-assigns when it otherwise cannot find/obtain an IP address.

Are you using the built in motherboard ethernet port or a third party PCI-x ethernet card? If the latter, make sure that the card is fully seated.

Please run and post the results of "ipconfig /all" without quotes.
 


I am using the built-in motherboard ethernet port. The motherboard is a Gigabyte H110m-a if that helps.

Here are the results of my "ipconfig /all":

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Eric>ipconfig/all

Windows IP Configuration

Host Name . . . . . . . . . . . . : Eric-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 1C-1B-0D-10-91-F1
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::3dcc:a4cf:65ad:a0b9%14(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.160.185(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 186391309
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-4D-88-23-1C-1B-0D-10-91-F1

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Kaspersky Security Data Escort Adapter
Physical Address. . . . . . . . . : 00-FF-31-26-71-A6
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{3F21F337-3665-4291-853E-256E00DD719B}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter isatap.{312671A6-D646-4104-84CC-002B91D5F158}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

C:\Users\Eric>
 


The DHCP IP range is from 192.168.0.2 to 192.168.0.254

I have both IPv4 and IPv6 selected on my desktop to automatically obtain an IP address and a DNS server address. These are the same settings I had before when my desktop was able to connect to the internet, but I may need to change them.

I don't believe they do. Plus the router I'm using from them has IPv6 automatically disabled.
 


Ok, IPv6 has been unchecked, and "ipconfig /flushdns" has been run. Command prompt says "Successfully flushed the DNS Resolver Cache." Do I need to restart to see if the changes took effect because so far nothing has changed.
 
Yes: Restart. To join a network a computer needs to go through a "hand-shaking" process that exchanges network communication protocols with the router and other network devices. Often takes a few minutes especially after some network related changes: e.g., drivers, configuration, etc.

Lots of handshaking tutorials and explanations available online. Look into Master Browser - not what it may seem to be....

Lots of places where things can go astray so I tend to focus on finding out what is what and gaining some insight as to what the computer is expecting or looking for.

"ipconfig /all" is very useful as it provides quite a bit of relevant information.

There are other similar tools: do you have Powershell?

Try the following three cmdlets"

1) Get-Netadapter (will provide network interface description and status).

2) Get-NetConnectionProfile (will provide network name and connectivity information).

3) Get-Netadapteradvancedproperty (will provide information about how your network adapter is configured).

Feel free to "google the above cmdlets" for more information and related options.

The idea is to find something that is not as it should be with respect to the desired network connectivity. Then that "something" can be directly addressed.

Note: Unless you have a very large network I would reduce the available DHCP range. I usually use a range that will include the number of expected DHCP devices plus a couple of "extra's". Devices with static IP addresses are given IP addresses just outside of the DHCP range and their individual IP address is reserved via the individual devices' MAC. Provides (for me at least) some assurance about and control over the devices on my network - wired and wireless. I know what, in a sense, to expect.

But, for now, set that aside until the desktop is again connected. Do not wish to introduce another variable.
 


Upon restarting several times the past day or two, nothing seems to have changed.

I do not have Powershell or any similar tools, but I will obtain it and try the cmdlets you have listed. Updates will be posted soon.
 
UPDATE: I had my ISP send a technician out just to insure their was no line damage (a fairly common thing around me) and had him look at my PC's connectivity while he was here. He said there were some problems with our lines outside which are now resolved, and he simply unplugged all the ethernet cables to our router and plugged them back in. Voila, my PC is now connected.

Thank you very much to Ralston18 for all the help you provided. I am confident that you would have been able to help solve my problem had the issue not been line damage, and I appreciate your assistance.