No IP Address ???

I recently upgrade one of my PCs to windows 10 from windows 7. Everything works great except I have no internet connection. In device manager, the network shows that I have a NVidiaN Force networking Controller. It also states that the right driver is installed & that is working ok. However, my system tray show a Yellow triangle & when search it out, states that my Ethernet connection does not have a ip address. When I check the Ethernet Properties, it has the same setup as my others. I searched the web & followed all kinds of instructions as how fix this but nothing has worked. This one really has me stumped....BTW, the PC is HP pavilion Media Center 8000m series.

Quote:

---

HP pavilion Media Center 8000m series

---

What is the exact model number? It would help to know exactly which Nvidia chipset you are using.
You might also be able to use GPU-Z or Speccy to find out the video/chipset.
https://www.techpowerup.com/download/gpu-z/
https://www.ccleaner.com/speccy/builds

Did you actually try loading the Nvidia drivers or did you just take the default Windows drivers?

Is it 32 or 64 bit Windows? Did you check hardware compatibility with Win10 BEFORE you upgraded?

Are you using DHCP or a static IP? What happens when you run ipconfig?

Thanks for the reply, Midkynite;
I used windows default.
System is 64bit
I did not check hardware compatibility
I would guess DHCP, but not sure. I forgot how to check :((
When I run IP config, I get a whole list of stuff. However, that's way over my head.
I'm shutting down for the eve. Been a long hard day. Not PC related.
I will check out the Speccy & the GPU-z tomorrow. Not sure how to use them as I have never used them before ...
I tried searching for the Nvidia drivers but had no luck.
The PC is HP Pavilion Media Center M8100N
Product # GC673AA-ABA
Thanks again..................................

The M8100N is over 10 years old. I probably would have stayed on Win7.

https://support.hp.com/sg-en/document/c01053972
GeForce 6150SE nForce 430

According to the Nvidia forums, you can try installing the Win8.1 drivers for video:
https://forums.geforce.com/default/t...or-windows-10/

Download Nvidia video driver here: https://www.geforce.com/drivers/results/56378

I don't think that includes the NIC driver though.
The latest Nforce 430 chipset drivers I could find was for Vista/7: https://www.geforce.com/drivers/results/14875

If you didn't set a static IP, it's DHCP by default.

open a command prompt
type the following:
ipconfig > C:\ipconfig.txt
Open C:\ipconfig.txt
Copy and paste the info and post here

I installed the Nvidia from the posted web site. Turns out to the same as what I had. Here is the IP config list:

Windows IP Configuration


Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::d8d7:fc19:b550:4480%7
IPv4 Address. . . . . . . . . . . : 184.103.100.230
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Tunnel adapter 6TO4 Adapter:

Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2002:b867:64e6::b867:64e6
Default Gateway . . . . . . . . . :

Tunnel adapter isatap.{808058AB-FA06-4AE3-A939-CBA81BA73EDC}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

One thing I forgot to mention is that after I had installed Windows 10, I noticed that the Cmos battery was dead. I installed a new one but other than the date change, nothing seemed different. I must say, however that Win10 is working extremely well so far

Quote:

---

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::d8d7:fc19:b550:4480%7
IPv4 Address. . . . . . . . . . . : 184.103.100.230
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

---

184.103.x.x is bizarre. The default gateway should be your router, not blank.

What kind of router do you have? You'd expect to see something like IP=192.168.1.2 SM=255.255.255.0 and DG=192.168.1.1

Did you install the video and/or the chipset drivers?

I was not able to find the chipset drivers.
The router is a NightHawk X6 Model R8000
AC3200 Tri-bander

This type of internet problem, is a first for me. I have never encountered such a dilemma.
The rest of my network show the IP addresses similar as you described ......

Did you check the TCPIP settings for the NIC? Like I said, 184.103.x.x is bizarre. Make sure it is set to "obtain an IP address automatically".
After that, you can try an ipconfig /release and ipconfig /renew.

I posted the link to the latest chipset drivers:
The latest Nforce 430 chipset drivers I could find was for Vista/7: https://www.geforce.com/drivers/results/56378

Hmmm?? I sent a post or thought I did but I see it didnt go through. Anyway, I did install that chipset driver. No change.... Also went all through the ip config routine & when all done, it still comes up with that !84.103........
When I do a diagnostic, it winds up with a msg : "Ethernet" doesn't have a valid ip configuration.

So when you go into the Network TCP/IP settings and change them, they don't stick?

You could try setting the IP address manually and not using DHCP. Set it to 192.168.1.100 and the Mask to 255.255.255.0 and the default gateway to 192.168.1.1

The DNS Servers can be set to 8.8.8.8 sand 8.8.4.4 for Google's DNS Servers at least temporarily.

Link for Windows 10 TCP/IP settings:

https://support.microsoft.com/en-us/...cp-ip-settings

I have no idea where 184.103.x.x is coming from. If you didn't get a 192.168.x.x, then it should have been 169.254.x.x (APIPA).

Did you look at the NIC settings for TCPIP? Is it set to "Obtain an IP address automatically"?

Right-click on the Start button, and click Network Connections
Click Change adapter options
Right-click on Ethernet, and click Properties
Click Internet Protocol Version 4 (TCP/IPv4), and click Properties
Choose Obtain an IP address automatically
Choose Obtain DNS server address automatically
Click OK

Edit: just saw jdc2000's post. You could try a static IP, but I'd try DHCP first.

OK, Thanks again for the help. The website offered by jdc2000 had the same instruction basically that I have been doing. Same with the instructions you posted, Midkynite. No matter what I do it still come back to the same setup.
Perhaps this could be a clue. The only connection listed is Ethernet Limited. I double click on that & came up with this: Ethernet Limited
Properties
ipv6dns servers:
fec0:0:0:ffff::1%
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Manufactuer Nvidia
Nvidia Networking Controller
Physical Address 00-1b-b9-87-02-BE

No matter what I set in the IP configuration auto or manual the results come back the same :184.103.x.x. Its like its locked into the MB or whatever........

Quote:

---

The only connection listed is Ethernet Limited.

---

Do you mean in Network Connections?

You could try disabling IPv6.
Go back to the same properties screen and uncheck IPv6. You might need to reboot after that.

Right-click on the Start button, and click Network Connections
Click Change adapter options
Right-click on Ethernet, and click Properties
Uncheck Internet Protocol Version 6 (TCP/IPv6)

Officially, the nForce 430 is NOT supported by Windows 10, so it might be tough to get it working.

I unchecked it, rebooted, got rid of the "Ethernet Limited" and now it shows it as an unidentified network. I uninstalled Nvidia rebooted & the Protocal Vers.6 came back checked.

Anyway, Im through for the day. Will persue it some more tomorrow. Thanks guys for the input...

When you installed the nforce chipset drivers, did you make sure the NIC is using the Nvidia drivers and NOT the Microsoft/Windows driver?

Ah, sorry. I just noticed that I copied the wrong link. This is the link for the nForce chipset drivers:
https://www.geforce.com/drivers/results/14875

A new day, an old problem. I decided to go back to a Windows 7 OS. After the smoke cleared, I find that I have the same internet problem as I had with Win10. I even went so far as to install the chipset driver for Win7/Vista from the geforce website. No luck whatsoever.
When I go to the internet properties & then "connect to the Internet" ,I get two options:
1. Broadband (PPPoE) connect using DSL or cable that requires a user name & password
2.Dial-up
connect using a dial-up modem or ISDN

I am stumped !!

Post the results you are getting now from an "ipconfig /all" command.

Did you check the TCP/IP settings and change them to the correct values? Link:

http://ask-leo.com/where_are_tcpip_s...windows_7.html

[QUOTE=jdc2000;1537227]Post the results you are getting now from an "ipconfig /all" command.


Here is what Ive got :Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\My PC>"ipconfig" /all Windows IP Configuration Host Name . . . . . . . . . . . . : MyPC-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 . . . . . . . . . . . : NVIDIA nForce 10/100 Mbps Ethernet Physical Address. . . . . . . . . : 00-1B-B9-87-02-8E DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::882f:3f96:38b1:a619%11(Preferred) Autoconfiguration IPv4 Address. . : 169.254.166.25(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.0.0 Default Gateway . . . . . . . . . : DHCPv6 IAID . . . . . . . . . . . : 234888121 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-22-8F-0D-18-00-1B-B9-87-02-8E DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1 fec0:0:0:ffff::2%1 fec0:0:0:ffff::3%1 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.{DE38FA33-06CB-46C0-A408-9782D220C1C3}: 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 C:\Users\My PC>

How did you capture the ipconfig info? It's hard to read. I already told you how to capture it to a text file in post #4.

open a command prompt
type the following:
ipconfig > C:\ipconfig.txt
Open C:\ipconfig.txt
Copy and paste the info and post here

Quote:

---

Autoconfiguration IPv4 Address. . : 169.254.166.25

---

At least it looks like DHCP is working properly. 169.254.x.x means APIPA is working, but it's not able to contact the DHCP server/router. The Default Gateway is blank, and that should be the router's IP. Double check that the cable is connected properly, or even switch the cable and port.

Ok here is the correct ipconfig. Sorry about that last one & also about the time lapse between post. Have many other obligations to attend to. Anyway, here it is:
Windows IP Configuration


Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::882f:3f96:38b1:a619%11
Autoconfiguration IPv4 Address. . : 169.254.166.25
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

Tunnel adapter isatap.{DE38FA33-06CB-46C0-A408-9782D220C1C3}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Again, it looks like DHCP is working on the NIC now. It's not an 184.103.x.x number. That's good.

169.254.x.x means it is trying to obtain an IP, but it's not able to find the DHCP server.

Did you try another ethernet cable and port on the router yet?

Thanks Midkynite; yes. I had tried a different cord when the trouble first occurred . As for the router, I do not want to touch. On my network, including my wife, I have at least 10 PC's, some windows 7, some windows 10, not to mention many others that I've fixed & either peddled or donated... All have connected without a single hitch. This has to be a first. I would rather trash this one rather than fuss with the router. Maybe, I could try this: the router is at the far end of the house from my office approx. 75'. The modem is setup here in my office. Everything is run through a series of Netgear hubs. The modem has a couple of extra ethernet ports. Perhaps I could run a cable to the modem & try connecting to that rather than the router. Would that work? At least to get an address established?

Uh, that would have been good to know before. Can't you just test the computer on one of the known good cables/ports? You can temporarily unplug one of your many computers to test the "bad" one.

The problematic pc is connected to an 8 port switching hub. The local pc's plus a solar panel monitor are all connect to this hub also. This hub is connected to another hub of which picks up my main pc, wife's pc (in another rm), connects to the modem, which in turn, connects to another hub at the other end of house, which connects to bedroom pc & tv, Living rm pc & tv & of course the router. Believe me! I am getting to old to remember all of these connections. All I can say is that they all work.
To late in the day to try my previous query. Hopefully, I try tomorrow. Thanks for bearing with me on this.
It is a challenge & I Do love challenges . :)

That's a lot of daisy chaining.

My point is that you should unplug a known working cable from another computer and plug it into the "bad" computer.

had to make one more try before retiring for the night. What you stated in your last post is exactly what I have been doing all along. Now I'm connected directly to the modem, bypassing everything else & still getting the same problem.
Have good eve or whatever.. G'nite ..................

Hmm. You might need to try either a PCI NIC or USB Network adapter then. It's possible that the network port on your motherboard is bad.

I agree. I'll order a PCI NIC . I guess it doesn't have to be anything elaborate . I see some for around $10 - $15.
I guess any brand will work? The 10/100 are pretty cheap, altho the 10/100/1000 are only a cpl bucks more...
Thanks for all the Help Midkyne, and have a great weekwend........

Well, I thought you might have a spare NIC to try first. I'm not sure it's worth spending money on such an old system. If anything, I guess I'd get a gigabit NIC.