Before I begin, if you think you can help me could you possibly leave your email addres/MSN messenger name/ICQ number, as it is far easier to deal with these problems person-to-person than over a message board. If you don't want to leave your email address thats fine, but please try to post any useful information here. My problem is that, usually after a lockup crash, my network tends to stop working. It has done this since I had the network installed, and it is VERY annoying. I have posted this several times, so I am just going to include the information which I feel is relevant. I should point out that the network has been working in the past, so the obvious suggestions (i.e, workgroups different e.t.c). The 2 computers in the network consist of one windows98 computer and one windows XP computer. As I said, the problem occurs after the 98 computer crashes, and fixes itself several days later after another crash. Also, I have noticed the 98 computer takes far longer to start up when the network is not working. Also, on the XP computer, when the network is down, the "A network cable is unplugged" icon appears in the system tray. Before you all give the obvious reply, NO THERE IS NOTHING WRONG WITH THE CABLES!!! If there was, the network would just crash anytime, not just after a crash surely? I THINK the problem is to do with the network cards themselves. On the 98 computer, it is built into the motherboard, on the XP computer it is a "Realtech RTL8139 Family PCI Family PCI Fast Ethernet NIC". My friend suggested that the problem could be incompatability between the two network cards Another suggestion is that the NIC card sometimes "goes to sleep" due to some feature which I can't find, and is possibly in the BIOS. This would explain why the network seems to think that it is unplugged, as the signal isn't getting as far as the other computer, so as far as the computer is concerned, it is unplugged. Is my reasoning correct? If someone could point me in the direction of this "sleep" feature, I would be greatful. Oh, and "Allow computer to turn this device off to save power" is NOT ticked, so its not as simple as that apparently. I think i've covered everything. If you could please reply, especially about the possible incompatability and the "sleep" function, I would be extremely greatful. Thank you for putting up with my whining!

Have you considered the possibility of a FIREWALL. ECT. Are you running Internet Security or the Like. I found that these can cause intermitant/Permanent connection problems. Worth a consider if you are running something similiar? Corey....

"...the problem could be incompatability between the two network cards" Assume an Ethernet TypeII device is what it is. "Another suggestion is that the NIC card sometimes 'goes to sleep'" If it does without software (i.e. through Windows), then it is an embedded feature and will wake up on-demand. "If there was [a network cable is unplugged], the network would just crash anytime, not just after a crash surely?" I really do not know what you are asking there. Windows is just telling you it has no signal over the connection (not necessary physical disconnect, only no electrical signal). How are you physically connecting your computers? Are you using TCP/IP? "my network tends to stop working..." Define "stop working". This is almost assuredly a problem with Windows 98 and its implementation of networking.

Ok, by "stop working" I mean, it acts as though it isn't on a network at all. Neither computer will communicate with the other. "How are you physically connecting your computers?" Um... with a CAT3 (i think) cable, is that what you mean? No router, just 1 NIC in each PC. "Are you using TCP/IP?" Yes. "If it does without software (i.e. through Windows), then it is an embedded feature and will wake up on-demand." O.k, but can I turn this off anyway (i hear there is some way to do so through the BIOS but i can't find it. Also, firewalls are NOT the problem either. I have Zonealarm on the 98 computer, but I can still usually connect with it on. P.S, after another lockup last night, the network is now working again. It does this a lot. I still need an answer to this problem, as I have no idea when it is going to crash again.

"O.k, but can I turn this off anyway (i hear there is some way to do so through the BIOS but i can't find it." If you can, then it is an option in the BIOS. If there is no option you cannot. Check your NIC documentation (available from the maker of the motherboard's site or the NIC maker's site) I'm trying to get away from this fabled sleep mode. So you cannot ping after a reboot? For completeness, you always have NIC indicator lights, correct? onboard NIC's are known to be unreliable on some motherboards. This is often a driver problem (so check the motherboard manufacturer's website) or maybe even a problem with the power supply (possibly too low, often just oscillating). Also, it could be a faulty network cable. The cable can still work, though with unacceptable inconsistency. Switching cables would be a good test. In Win98, go to the run command line and type in "winipcfg". Refresh the NIC device. If you feel like starting over, uninstall the NIC driver and then reinstall it. Sometimes I just disable devices, reboot, and restart them. What is clear is the fact that Win98 seems to halt signaling from the NIC, via the driver, when it crashes. This is normal. What is not clear is why this behavior continues after reboot. For that, I would normally use the "winipcfg" utility. Here is why your PC boots slow: http://beta.experts-exchange.com/Operating_Systems/Q_20640807.html Basically, your PC has long timeouts searching for the network. This is a reality of Win98. Go to your NIC card settings and change all the values you can to absolute ones. For example, rather than auto-detect, select full duplex. Do the same in the BIOS, where applicable.

"If you can, then it is an option in the BIOS. If there is no option you cannot." Well, just because I can't find is doesn't mean it isn't there; i'm bad at looking for things :) "So you cannot ping after a reboot? For completeness, you always have NIC indicator lights, correct? " No, after a reboot the pingings time-out. Neither NIC has indicator lights. "In Win98, go to the run command line and type in "winipcfg". Refresh the NIC device." I'll have to try that next time it crashes, thank you! "onboard NIC's are known to be unreliable on some motherboards. This is often a driver problem (so check the motherboard manufacturer's website) or maybe even a problem with the power supply (possibly too low, often just oscillating)." If I install new drivers, will the network still work? I'm just afraid that if I install new drivers the network will stop working. "If you feel like starting over, uninstall the NIC driver and then reinstall it. Sometimes I just disable devices, reboot, and restart them. " Again, something I will have to try *Digs installation CDs out of the attic* "Go to your NIC card settings and change all the values you can to absolute ones. For example, rather than auto-detect, select full duplex. Do the same in the BIOS, where applicable." Ummmm, what? Could you explain this one a bit more fully please?

I cannot help you with the BIOS. Sorry. I can tell you I have never heard of a NIC that goes to sleep because Windows crashed. According to your assessment, the current setup is a great inconvenience. If it were me, I would upgrade drivers. Quite often, these sort of things are solved via driver updates. "Could you explain this one a bit more fully please?" In your Windows Control Panel, under Networking, under the properties of the given device, there are multiple options and tabs. Many of them are set to auto-detect or an equivalent value. This can become a problem in certain cases, as the device or its software controller fails to perform a necessary check to get a correct value for this field. In other words, it (auto-detection of a value) doesn't always work. Your BIOS has some similar settings. Here is what I would do. I would buy an NIC - any Ethernet TypeII device-compliant NIC (otherwise known as an Ethernet card). Cheap. Put it in an available PCI slot. Windows should find the driver in its CAB files (unless this was a non-default installation). Otherwise, go the manufacturer's site, and download it. If you have problems with that, you have problems with your motherboard or power supply.