Desktop

Ask something
Discussion Locked

Network problems

0 helpful
11 replies

by mike.wagoner

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Okay, try this one on for size.

Basic PC, AMD 450 CPU, 64 megs RAM, ATI video card, Linksys 10/100 NIC, CD, floppy, sound card (SB 128).

Installed Windows 98 on it (not SE). System appeared to work fine, saw and recognized the network card, did not have the opportunity to test the NIC; but no problems on startup without a network.

Sent it to my nephew at college in texas. It boots up but doesn't immediately see the network. He configures it for the network and then it freezes when it tries to connect. NIC is changed from one PCI slot to another, the freezing stops but it doesn't connect with the network.

Hard drive is formatted, Win98 reloaded, problem remains. Computer is taken off college network and put on a mini-network for testing. When it sends information, the computer that its sending to gets the info, but the NIC doesn't respond to any incoming packets. Other NIC's are put in the machine, same problem, it sends, it doesn't receive.

Yes, we've checked to ensure its running at full duplex, we've double checked the network addresses and sub masks.

Suggetions please.

11 replies

by rickh9

Start by removing the sound card and see if the problem goes away. If so then look for hardware conflicts between the two.

by cdobbin

You did'nt say what type of network you were connecting with/to. Have you tried conecting it with another PC if so can you see windows shares and access them(using netbeui)? Or is it a problem with TCP/IP? What other protocols are you using?

by mike.wagoner

Only using TCP/IP, no other protocols. The college network is your basic ethernet running at 100. Ditto the "mini-network" set up for testing.

by braveh4rt

I think maybe it's the network card. Try to use other network card.
but you still can try this:

1. did you use the correct driver? if don't , windows wil;l automaticly pop up a warning window at start up.

2. do you use the same protokol withthe other network?

3. try to run winipcfg from the run window.
read the information you get about your ip and submask.

4.don't use the next port after agp slot cause it will conflict with the agp slot.

5. try to check your cable setting. set the cable sequence as same as the other path in one cable line.

adn if not fix it, try use other nic card.

tahnk you, hope it help you.

by mike.wagoner

As stated in the original problem, we have tried 3 different NIC's and the problem remains regardless of the brand or type of NIC.

by Member 27529445

One of the critical things you didn't mention was type of MB or more specific Chipset. Try Finding the latest Chipset driver most importantly IRQ routing. WIN98 FE had plug and play problems that could very well be fix by latest chipset drivers

by fatherfox

You have some good answers, but how about this? You stated windows found the nic, but you didn't state that you used the linksys drivers. Did you install them, or are you using windows drivers? Is there a yellow ! after the nic listing in the resource listing? Are you trying to connect it to a 10 base t network or using cat3 cable? (this causes problems.) Are you running multiple protocols? (netbeui, tcp/ip, etc. (also bad idea, pick one.)) Is it isa or pci? Is it next to another card or on theshared slot? If so, move and try to keep it away from sound, modem, agp cards. Just a thought.

by mike.wagoner

Yes, we did use the linksys drivers. There is no problems noted by Device mangler. I already stated that it was an ethernet system running at 100 and we were using cat 5 cable that works fine on other computers. I mentioned to an earlier helper that it was ONLY TCP/IP. I also stated that we changed PCI slots so that told you if the card was ISA or PCI. Thanks for the ideas though.

This discussion is closed to new replies.