Does skylake have the nic in cpu?

SticKx911

2[H]4U
Joined
Mar 14, 2004
Messages
2,515
I’m working on a pc that won’t communicate with the domain. It says it’s connected to the network and it sends packets. It just never receives any back. We tried switching ports, cables, all the easy stuff. We replaced the mobo (onboard NIC), but the issue remains. Some are suggesting cpu, but I’m not sure that’s the right path to take. Any suggestions?
 
Weird question. I'm leaning towards no, but I'm interested in where this might go.
 
It has part of the NIC on the CPUchipset. There's a PHY that goes along with that on the board.

But this is almost certainly a software issue. Wipe to metal and move on.
 
Last edited:
Already have a clean windows install and issue remains; however, it very well could be corporate software issues which is the direction I’m leaning, but corporate IT is kicking back. (Because their software is obviously infallible)

Thanks for the feedback.
 
Have you tried setting the duplex and speed manually in the NIC driver settings in Windows? By default, it will be set to auto-detect.

But, depending on the device on the other end of your network cable, you might have better results setting that value. Start with 10 no duplex, then 100 no duplex. If you get good connection with one of those, then try the duplex version (for better throughput).

Anyway, I've found this more than once to be an easy fix to network connectivity issues.
 
Already have a clean windows install and issue remains; however, it very well could be corporate software issues which is the direction I’m leaning, but corporate IT is kicking back. (Because their software is obviously infallible)

Thanks for the feedback.

Well, have you tried (or can you try) loading up a non-molested OS image, even a Linux ISO? Modern distros are essentially fully functional from the install image and can be used to test and troubleshoot a myriad of issues.
 
Well, have you tried (or can you try) loading up a non-molested OS image, even a Linux ISO? Modern distros are essentially fully functional from the install image and can be used to test and troubleshoot a myriad of issues.
I can try a Linux iso, but idk if the domain will take it (or if I’d even know how to set it up). I can definitely try a vanilla, non corporate, Windows iso. I’ll have to see if it can install without a key for testing at least. It’s just an hp aio so it shouldn’t need anything fancy for that.
 
I can try a Linux iso, but idk if the domain will take it (or if I’d even know how to set it up). I can definitely try a vanilla, non corporate, Windows iso. I’ll have to see if it can install without a key for testing at least. It’s just an hp aio so it shouldn’t need anything fancy for that.

the windows 10 images direct from ms should work with no key, up to 30 days for pro & 90 for enterprise
 
When all else fails, I recommend just pop in a Windows DVD and reinstall and rejoin the domain, completely bypassing imaging process. Even if you don't plan on leaving it that way, it's a troubleshooting step to prove it's one thing or another.
 
I would lean more towards motherboard issue since the NIC is integrated and you've tried reinstalling Windows.
 
If it's connected at Gigabit, all lines should be combined (if you send, you should receive).

But if it'sd connected at 100mbit for some reason, then you have separate transmit an receive lines. Double-check the cable.
 
Could also be wiring back to the switch, wall-to-PC cable or firewall (both on the PC and external). Most of that is testable by swapping out with a laptop (minus on-pc firewalling). It's easy to get a boot USB image and test the networking from a run-from-USB OS image to answer the software/hardware question.
 
Could also be wiring back to the switch, wall-to-PC cable or firewall (both on the PC and external). Most of that is testable by swapping out with a laptop (minus on-pc firewalling). It's easy to get a boot USB image and test the networking from a run-from-USB OS image to answer the software/hardware question.
External stuff was swapped. (Patch cable, switch port, cat6 run). All work fine on a different pc. I also replaced the motherboard thinking it was a port issue.

I haven’t had a chance to dig back into it, but next step will be to try a basic windows install (not using the corporate image) before swapping cpus.
 
fwiw, corporate had the port configured wrong. Only after I replaced EVERYTHING did they finally decide to spend 5 seconds checking anything....:banghead:

This hits way to close to home... :cry: Jump through our hundreds of hoops before we'll lift a finger. SMH.
 
Back
Top