Hello nukemaster!
I am writing into this (old) thread
since it is the ONLY one I have found - after hours of searching - which
resembles my issue...
I am not even sure if this thread is still 'active'/ whether I should start my own thread!
But seeing your detailed responses encouraged me to give this a shot...
My issue: (well, the present one, anyway!)
[Unlike the original poster's problem, where Erice1996 reported that the computer "won't recognize there is an Ethernet cable plugged in"]
[But just as Erice1996 reports later,]
My Device Manager doesn't even show a Network tab.
[And also, as with Erice1996's issue]
My problem(s) seems to have developed ever since I upgraded to Windows 8.1 (Everything was fine while I was with Win XP!)
I have a 'home-built'
Desktop Computer (I am
not a geek, just someone who has to run a rural organisation in India where
nothing is accessible and very little funds at hand - and also, someone who enjoys DIY'ing)
Specs:
■ Motherboard:-
Intel Desktop Board DG41WV - Essential Series - motherboard - micro ATX - LGA775 Socket - G41 (Here's a CNET link with the specs)
■ Onboard Gigabit Ethernet:-
Integrated 10/100/1000 Network Connection
(The onboard chip is too small to read clearly - i think it reads...) REALTEK RTL811DL
■ OS:-
Windows 8.1 Single Language (English) 32-bit - Full Version (OEM)
There are OTHER errors that have been occurring lately - which were
probably triggered by my rural-staff not shutting down the system properly, while I was away (they were constantly 'hard booting' to shut-down, with the power button, as they could not find the 'Shut-down' command as easily on the 8.1 interface!)...
I can give you a step-by-step of all that has been happening - but I am not sure whether that is required at this moment.
[The BIOS was not loading, to begin with... CMOS jumper re-set etc. did not help - three-beeps heard even before post - so, I searched and found that this was a RAM failure notice - opened and re-set the RAM... changed it's port... finally, a thorough rubbing of the RAM terminals, and violla, system was up and running!]
The basic issues at the moment are:-
■ CMOS CHECKSUM ERROR
Every time I power off and start the system again, POST shows CMOS checksum AND Battery failure error.
However, the battery shows 3.02 V on a Digital multimeter - and the battery socket seems fine, at least from the top-view of the mobo.
■ Device Manager does not even record a Network adapters tab!!!
(Even after I try connecting my modem/ laptop with the Rj46 cable)
However, when I connect the same modem with the (optional) USB cable, the Network adapters tab appears - showing "USB IAD LAM Modem" details!
At this point, if I choose to 'Show hidden devices', a long list of (mostly) 'unselected' items are displayed - but NONE OF THEM look like the one I need - for example, there's none from Realtek - though there are a number of 'WAN Miniport' items.
I have already tried a number of remedies (which I will gladly narrate, if you ask for it)...
Howerver, at this point I have a feeling that I
need to first check whether the onboard LAN is shot, or is it a BIOS settings/ OS compatibility/ driver issue...
In your last note to the original question you had mentioned something about "
trying a live CD/DVD of Linux"... Can you please help me to - (1) understand what you mean by that - (2) guide me through the process?
Or, do you think I should try something else??
Thanks in advance...
Cheers!
nukemaster :
I do not have good news. The older(XP system, but it has an Nforce based chipset and realtek based network card) system I checked DOES show network cards in the same spot as my newer systems.
I almost have to wonder if some kind of hardware failure has happened with the onboard network card.
What do you see
If you felt adventurous, I would recommend trying a live CD/DVD of Linux. Live CD's do not install as long as you run them in live mode(they are not fast because they run off the cd/dvd, but they to work). They tend to have drivers for almost everything and at least if the network card worked on it, you would know it is a Windows issue and not a hardware failure issue.