Intermittant problems are the worst to troubleshoot. From what you have said, I (and most others) can only give you general guidence. You need to figure out where in the network setup the failure is occurring. Note the following things the next time there is 1. Is the Ethernet card being initialized incorrectly? (For example, might Windows be changing its PnP settings, so if you warm boot Linux after Windows, the card is set one way, but if you cold boot, it is set a different way?) During the boot process, observe whether the kernel, or a module (depends on your setup) detects an Ethernet card and assigns it to eth0. If it does, note if it is always at the same IRQ and ioBase address. (You can probably check this after boot by looking at the dmesg buffer -- just enter "dmesg" at the command line -- is this what you were referring to below when talking about "When I cannot get off"?) 2. Is ifconfig assigning the IP address correctly? Do you get any errors relating to address assignment during the boot process? If you run "ifconfig", does it report the correct IP address, netmask, and broadcast address for your interface? 3. Is routing set up correctly? Does "route -n" identify eth0 as either a route to your LAN or a route to the default network (0.0.0.0)? 4. Are you on the LAN when under Windows? Might there be some inconsistency between your Windows and your Linux settings that causes, say, an ARP problem? (I don't have anything specific in mind here, just a vague unease about dual-boot machines and LANs.) If you need to post a followup, please mention the distribution, version, and kernel version you are using. At 03:49 PM 9/1/99 -0500, Brad Bonkoski wrote: >Hello All, > >I have a problem. For some reason or another I loose internet capabilities >every now and then. I am on a LAN and my computer interfaces with an ethernet >card, and sometime when I boot up it runs fine, but other times when I boot up I >cannot get onto the network. >**I know a solution is to not reboot, but I have a class in visual basic so I >still have to run WinBlows** > >When I cannot get off I run an 'dmesg' and the kernel recognizes the device eth0 >at bootup ------------------------------------"Never tell me the odds!"--- Ray Olszewski -- Han Solo Palo Alto, CA 94303-3603 [EMAIL PROTECTED] ----------------------------------------------------------------
