David, I got a reply email from Netgear in which he says to "check with a hardware vendor to assign a free IRQ of either 9, 10, or 11 to the PCI slot where the NIC is being installed." I got the cards from Hard Drives NW, but they said that they don't support networking. I emailed a reply to Netgear tonight about this, but I wanted to ask you about it also. It seems a bit odd to not support something that you sell, but I bought all my components for the computer from there because of the 1 year warranty. Anyway, do these IRQ settings sound right? Also, are the IRQs in Device Manager the same as those in BIOS? ----- Original Message ----- From: "David M. Dodge" <daviddodge1@xxxxxxxxxxxxxx> To: <kegswindows@xxxxxxxxxxxxx> Sent: Sunday, June 30, 2002 9:53 AM Subject: [kegswindows] Re: configuring network > > Kurt, > > That's a good indicator of machine problems. when yoiu move the "bad card" > to another machine and it behaves normally and the "good card" becomes bad > in the other machine is a very good indicator of card chassis > incompatability. I would check the BIOS on the suspect machine to see if it > has any network settings that may conflict or that it is restricting or > locking down the IRQ's on the PCI slots for legacy hardware. You may have > to get another brand of NIC to try and see if that is an issue. Without > benching the two together and seeing how they react, it cold be a > combination of hardware and software in settings for both. Tough to tell, > you now know that both cards are good, now you need to investigate why the > one PC works with a NIC and the other one doesn't. > Good Luck, > > David > > -----Original Message----- > From: kegswindows-bounce@xxxxxxxxxxxxx > [mailto:kegswindows-bounce@xxxxxxxxxxxxx]On Behalf Of Kurt Mincin > Sent: Saturday, June 29, 2002 10:08 PM > To: kegswindows@xxxxxxxxxxxxx > Subject: [kegswindows] Re: configuring network > > > > > David, if I can switch NIC cards between computers and the diagnostics on > machine A remains ok (displays card stats), while on machine B the > diagnostics still displays an error, doesn't that mean that there's > something wrong with machine B itself? > > On the problem computer I did move the card to another PCI slot and still > got a diagnostic error. > > Kurt > ----- Original Message ----- > From: "David M. Dodge" <daviddodge1@xxxxxxxxxxxxxx> > To: <kegswindows@xxxxxxxxxxxxx> > Sent: Friday, June 28, 2002 5:42 PM > Subject: [kegswindows] Re: configuring network > > > > > > Kurt, > > I would move the card to another PCI slot and if you get the same error on > > the diagnostics, then the card has problems. The other thing to check is > to > > see if both cards are set to full duplex. Are both cards the same brand > and > > are they both 10/100? you may have a bad PCI slot or there is a PCI > > conflict. You may want to make sure in bios that you have not reserved > all > > the pci slots to ISA just in case. If the diagnostic utility can't see the > > NIC then you ought to try another card altogether. You can get NIC's for > > aroung $20 so that shouln't kill the finances. If the card is new, then > get > > a replacement at the store where you bought it. > > > > David > > > > -----Original Message----- > > From: kegswindows-bounce@xxxxxxxxxxxxx > > [mailto:kegswindows-bounce@xxxxxxxxxxxxx]On Behalf Of Kurt Mincin > > Sent: Friday, June 28, 2002 8:34 AM > > To: kegswindows@xxxxxxxxxxxxx > > Subject: [kegswindows] Re: configuring network > > > > > > > > > > David, I tried the diagnostic/driver diskette on both machines. The > machine > > that displays "response timed out" from pinging also gets a diagnostic > error > > that the network adapter is not found. The machine that displays a reply > > from pinging also lists the stats of the adapter, which I assume means > it's > > ok. On the problem machine with diagnostic error it says to: > > > > 1) check that there's a card installed > > 2) check that the PCI configuration in BIOS is set, otherwise... > > 3) switch adapter cards to see if the machine is the problem > > > > I still get the diagnostic error. I'm not sure what to do next. > > > > Thanks > > Kurt > > ----- Original Message ----- > > From: "David M. Dodge" <daviddodge1@xxxxxxxxxxxxxx> > > To: <kegswindows@xxxxxxxxxxxxx> > > Sent: Thursday, June 27, 2002 10:17 PM > > Subject: [kegswindows] Re: configuring network > > > > > > > > > > Kurt, > > > If you get a response from one side, the cable and network cards are ok. > > > You should be able to get another from the other side. What are your IP > > > addresses and subnet masks you are using for each computer? Are you > using > > > Fixed IP addresses or is the address being automatically given to one or > > > both computers? Have you enabled internet connection sharing? If you > > got > > > a complete response with the address and got a time (ie 10ms) for the > ping > > > with a 100% packet success rate, you should have a good connection and > the > > > addresses are on the same subnet. I would run the diagnosic program > that > > > came with the network card on the computer that keeps getting a response > > > timed out, may have an issue. but the one that is getting the successful > > > ping may not be responding to a ping and therefore may be the problem > NIC. > > > > > > David > > > -----Original Message----- > > > From: kegswindows-bounce@xxxxxxxxxxxxx > > > [mailto:kegswindows-bounce@xxxxxxxxxxxxx]On Behalf Of Kurt Mincin > > > Sent: Thursday, June 27, 2002 8:22 PM > > > To: kegswindows@xxxxxxxxxxxxx > > > Subject: [kegswindows] Re: configuring network > > > > > > > > > > > > > > > David, thanks. I enabled file and print sharing and it got me a bit > > > further, but still not there. Each computer's Network Neighborhood now > > > shows 'entire network' (as before) and the computer itself (which it was > > not > > > before), but still not the other computer. When pinging, one computer > > gets > > > a reply, the other gets 'response timed out'. I might add that it's the > > new > > > computer displaying 'response timed out'. > > > > > > The WOWN site says that it's most likely a hardware issue, but both > > network > > > cards are working according to device manager in the system properties. > I > > > don't know how to test the cable. > > > > > > I hope that's clear > > > Thanks again > > > ----- Original Message ----- > > > From: "David M. Dodge" <daviddodge1@xxxxxxxxxxxxxx> > > > To: <kegswindows@xxxxxxxxxxxxx> > > > Sent: Thursday, June 27, 2002 5:25 PM > > > Subject: [kegswindows] Re: configuring network > > > > > > > > > > > > > > Kurt, > > > > Do you have File and print sharing enabled on both computers, if not, > > then > > > > youy won't see anything as the netbios stack won't be loaded, which is > > > what > > > > you need to see the other system. > > > > David Dodge > > > > > > > > -----Original Message----- > > > > From: kegswindows-bounce@xxxxxxxxxxxxx > > > > [mailto:kegswindows-bounce@xxxxxxxxxxxxx]On Behalf Of Kurt Mincin > > > > Sent: Thursday, June 27, 2002 2:20 PM > > > > To: KEGS (Windows) SIG > > > > Subject: [kegswindows] configuring network > > > > > > > > > > > > > > > > OK. I've two computers, both with WIN98, Netgear Network Interface > Card > > > in > > > > each, a 25' CAT5 Crossover cable. When I double-click on the Network > > > > Neighborhood, then Entire Network, I get "unable to browse network". > I > > > > called Netgear and they gave me some websites for reference. I used > > > > www.wown.com to configure the tcp/ip > netgear protocol and the IP > > address > > > > that the site recommends. They suggest testing the connection using > > PING. > > > > From one system I got "request timed out". From the other system I > got > > > > "destination host unreachable". For the "unreachable" error the site > > says > > > > to check the gateway address because the other system is not on the > same > > > > subnet. I tried the gateway address given on the site and got the > > > > "destination host unreachable" error again. > > > > > > > > Can anyone help me to get these computers talking? > > > > > > > > Thanks > > > > Kurt Mincin > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >