at's just the subnet mask. Your subnet should be, from the info you gave us, X Check your other machine and check if the first 3 of the 4 group of numbers matches the above pattern... Afterall it may not be a bad idea to just get a new card - Fast Ethernet cards are no more than $20 these days. I know, I still have, oh, maybe 15 of those 3C509s and they are just sitting there coz they ain't worth anything anymore (then again I can't complaint coz I got them for free) --David At 08:56 AM 10/6/2002 -0400, you wrote: >Yup, I'm on the same subnet as the router, 255.255.255.0. The other machine >on the network has net access perfictly fine. >Explorer has caused a general protection fault in module kernel32.dll. I'm >sick of Winblows! >----- Original Message ----- >From: "Igor Gueths" <igueths at attbi.com> >To: <speakup at braille.uwo.ca> >Sent: Saturday, October 05, 2002 9:34 PM >Subject: Re: Network card problems > > > > Are you sure that you're on the same subnet as the router? The router and > > machines should have the same netmask. > > > > microsoft dialogue > > This company has performed an illegal operation and will be shut down. > > If the problem persists, delete winblows and install linux > > close button > > > > On Sat, 5 Oct 2002, Alex Snow wrote: > > > > > I just got rid of dhcp, and have assigned all computers on the network, > > > including the linux box, ip addresses. I reran netconfig and gave it >the > > > new ip address, netmask, and gateway. Now when I type ifconfig I see >the > > > the net address is 192.168.1.101, that's what I assigned it. Only >problem > > > is I still have no network support. I can't ping the box, and I can't > > > connect to my router using lynx. Could there be some configuration on >the > > > card that is messed up? Someone suggested that I run isapnp, but the >card > > > seems to be detected fine. > > > Explorer has caused a general protection fault in module kernel32.dll. >I'm > > > sick of Winblows! > > > ----- Original Message ----- > > > From: "Adam Myrow" <amyrow at midsouth.rr.com> > > > To: <speakup at braille.uwo.ca> > > > Sent: Saturday, October 05, 2002 6:55 PM > > > Subject: Re: Network card problems > > > > > > > > > > If you can, tell us what happens during bootup with DHCP. It should >say > > > > something like "attempting to configure eth0 by contacting a DHCP >server." > > > > Next, the DHCP command is supposed to report back what it gets. If >you > > > > never see the "attempting to configure eth0" message, rerun netconfig >and > > > > make sure you selected DHCP. DHCP is the second choice, static IP is >the > > > > first. DHCP only asks if you need to supply a hostname, and most of >us > > > > don't. It mentions that Cox at home is an exception where you need to > > > > supply a hostname to DHCP. Like I said, the card is definitely > > > > functioning. Good luck > > > > > > > > > > > > > > > > _______________________________________________ > > > > Speakup mailing list > > > > Speakup at braille.uwo.ca > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > > > > > > > _______________________________________________ > > > Speakup mailing list > > > Speakup at braille.uwo.ca > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > > > > > > _______________________________________________ > > Speakup mailing list > > Speakup at braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > > >_______________________________________________ >Speakup mailing list >Speakup at braille.uwo.ca >http://speech.braille.uwo.ca/mailman/listinfo/speakup
