Computing.Net > Forums > Networking > Onboard NIC problems

Computer Problems? Computing.Net has over 1,000,000 posts about all things technology related! Over 90% answered within 24 hours! Click here to start participating now! Also, be sure to check out the New User Guide.

Onboard NIC problems

Reply to Message Icon

Name: jarros
Date: June 6, 2004 at 14:03:56 Pacific
OS: Win XP Home
CPU/Ram: P4 3GHz/512DDR 400
Comment:

I just picked up this computer and I spent the majority of yesterday transfering files from my old computer. The network was working just fine yesterday evening. I turn it on this morning and notice the internet wasn't working. It works on every other computer in the network, so it's not my ISP, Modem, or router.

I go into the Device manager to see what's wrong. Sure enough, there's a little yellow exclamation mark beside "Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter, Copper RJ-45" under network adapters. I didn't change anything with the drivers, and now I get this. I tried reinstalling over the existing drivers, uninstalling and reinstalling the drivers (from the CD that came with my ASUS P4P800 SE motherboard), and nothing. Actually, right now in the Device manager, it says "Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter, Copper RJ-45 #2" (note the #2 at the end). Why is it number 2? It's the only one I have. It looks like it might be showing that existing drivers for the NIC were already installed when I reinstalled them, but I was sure to uninstall everything (right click in Device Manager and chose uninstall, and run the installer exe from the CD and chose "Remove").

Please help, I've spend a good hour trying to get it to work already, and it's quite frustrating. I got a new computer to get rid of these kinds of problems, not to bring in new ones.



Sponsored Link
Ads by Google

Response Number 1
Name: jarros
Date: June 6, 2004 at 14:14:15 Pacific
Reply:

OK, I've made another attempt here. I uninstalled everything again and went to reinstall. When I boot up, Windows noticed the NIC and that it didn't have drivers. I located the driver on my hard drive (don't know how it got there. It's located at: C:\WINDOWS\System32\wbem\mof\good\gewmi.mof), and it added a #3 at the end instead of the #2. This must mean that I'm not uninstalling something properly. Anyone know how to sucessfully uninstall the drivers for a NIC?


0

Response Number 2
Name: jarros
Date: June 6, 2004 at 14:16:15 Pacific
Reply:

Sorry, forgot something else. At the end of that last install, it said:

"An error occurred during the installation of the device

The name is already in use as either a service name or a service display name."

That might help.


0

Response Number 3
Name: Jamie_McCoy
Date: June 6, 2004 at 15:05:23 Pacific
Reply:

try removing the NIC from your board

reboot, then shutdown windows, place NIC back in board and start up

see if that helps..

also, try using a NIC from one of the other computers in the comp with the problem

Sign Me Guestbook!

jaymc.co.nr


0

Response Number 4
Name: jarros
Date: June 6, 2004 at 15:24:00 Pacific
Reply:

Actually, the NIC is onboard (technically it's not a NIC, I guess), so I can't take it out. Anything else I should try?


0

Response Number 5
Name: Jamie_McCoy
Date: June 6, 2004 at 17:08:41 Pacific
Reply:

try disabling the onbaord NIC, and termporaly use another one, one that you know works

if this works, you can narrow down the problem to the NIC

if the new one works, then it may be a driver problem, or even hardware problem

thats alls i can offer, rather an unusual problem you have

Regards, Jamie McCoy


0

Related Posts

See More



Response Number 6
Name: Jamie_McCoy
Date: June 6, 2004 at 17:10:32 Pacific
Reply:

is it just reciving internet that is failing for the NIC, or network as well?

Regards, Jamie McCoy


0

Response Number 7
Name: jarros
Date: June 6, 2004 at 17:17:42 Pacific
Reply:

Thanks for the suggestion, I'll give that a shot.

The networking port on that computer isn't working at all: no internet, no connecting to other computers, etc. Would you happen to know why it's adding a #2, #3, etc. every time I try to reinstall the drivers? It's keeping track of how many times I've tried to reinstall, so there's something that's not being uninstalled. Any Idea what this could be?


0

Response Number 8
Name: David480
Date: June 7, 2004 at 06:10:42 Pacific
Reply:

Before installing your driver, check your BIOS to make sure that the network adaptor is enabled.


0

Response Number 9
Name: OrionCA
Date: June 7, 2004 at 12:36:09 Pacific
Reply:

There's still a setting in your Registry for that NIC; that's why you are getting the #2, #3, etc. messages. Sounds like a poorly written driver to me.

I'd sidestep the whole issue: just disable the onboard NIC and install an adapter card. For $15 - $20 you'll be saving yourself a whole lot of hassle. However, if you're the stubborn type check the manufacturer's website and see if there's an updated driver; that may solve the problem.


0

Response Number 10
Name: MNorman
Date: June 16, 2004 at 20:37:27 Pacific
Reply:

I have the ASUS A7N8X-E Deluxe (with XP PRo) and had the same issue with the Marvell driver. I was able to correct it using information I found for the same problem with the AirNic driver (http://www.smartbridges.com/web/support/faq_an.asp#133). What it boils down to is to use regedit and remove the yukonx86 key from

HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services
and
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services

Then reboot the system. Next, I used the Add Hardware wizard and was able to the install the driver succesfully. It came up as Network Connection #5, but at least it is working.


0

Response Number 11
Name: wheelz
Date: June 20, 2004 at 18:58:44 Pacific
Reply:

I am having the exaxt same problem as described above. I cannot get connected to the internet in any way with the computer and onboard nic.

Part of the problem appears to be to do with dchp. For some reason the ip address that is assigned is 169.xxx.xxx.xxx which is not right. When renewing with ipconfig it fails to connect to the dchp server. I installed the drivers for the onboard nics from the cd provided and it appears to be successful with devices working properly.

Any help would be greatly appreciated.

Wheelz


0

Response Number 12
Name: FBI Agent
Date: June 25, 2004 at 19:07:19 Pacific
Reply:

for wheelz. make sure you have the wiring connected properly, if you have a router, make sure it is connected properly and try to connect to a intranet game with 2 computers. (i did that and found out that something was definately wrong, it could transfer files, just not tcp/udp packets from the game)

FBI_Agent


0

Response Number 13
Name: sigi74
Date: July 5, 2004 at 01:23:13 Pacific
Reply:

in device manager there is a point in the pulldown menu to see devices wich were faded out (excuse my poor enlish;-) check this mark and whhoop - there are nic# 1-x, uninstall all of them and it begins to count from #1 at the next nic installation!


0

Response Number 14
Name: lalouisianne
Date: July 25, 2004 at 15:33:46 Pacific
Reply:

I am having the same problem with an ASUS A7N8X-E except I can not find the Yukonx86 driver (or any of the related files that are required) on the C drive or in the CD that came with the mother board. Naturally the Mavell site does not list the driver. Ditto for Asus. Could someone tell me where I can find the Files I need wich in addition to the Yukonx86.sys (v6.7) include NDIS5.1 miniport driver set up script and Yukonx86.cat digital signature. All this occurred when I was forced to repair the Win XP operating system using the install program on the CD that apparently deleted the driver (and related files) Thanks

R



0

Response Number 15
Name: simon.j
Date: July 29, 2004 at 11:35:42 Pacific
Reply:

I'm another having issues with this Marvell on-board Gigabit LAN adapter. I just bought an ASUS P4P800-SE board, and did a fresh install of XP Pro. I installed the Yukon drivers from the ASUS CD that came with the board; this didn't appear to do much at all apart from hide the auto-detected 'Ethernet controller' entry from Device Manager.

Did a reboot, Windows detects new hardware, starts the 'Found new hardware' wizard, and (magically) I can specify Marvell Yukon Gigabit Ethernet 10/100/1000Base-T Adapter, Copper RJ-45" as the device driver. Click next, and Windows kindly informs me that 'The device cannot start'.

So, there the entry sits, in the 'Network adapters' tree, with the annoying yellow exclamation point next to it. I've tried uninstalling/reinstalling the device, and all of the above suggestions, and the same end result (cannot start) occurs every time.

Even more alarmingly, I've disabled the on-board LAN in the BIOS, installed a D-Link 10/100 IDE NIC, and I receive the same 'Device cannot start' message from Windows when updating its driver. I know for a fact this card works fine - it's in the PC I'm currently using (NOT the one with the Marvell), and is how I'm online at the moment. Help... please... :S.


0

Sponsored Link
Ads by Google
Reply to Message Icon






Post Locked

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.


Go to Networking Forum Home


Sponsored links

Ads by Google


Results for: Onboard NIC problems

onboard nic www.computing.net/answers/networking/onboard-nic/28018.html

network card www.computing.net/answers/networking/network-card/32412.html

fried mobo in onbaord nic? wtf? www.computing.net/answers/networking/fried-mobo-in-onbaord-nic-wtf/22012.html