Skip to main content

So I decided my family's "spiffy" (read: sh*tty) Gateway Celeron 333 might be a good place to dump some audio data if I throw a big cheap 5200 RPM drive in it and pick up a few ethernet network cards and a crossover cable. My audio system is a 1.1G athlon, 512 SDRAM, 15G ATA sys drive, 45G audio drive, Matrox G400 DH video, ABIT KT7 MOBO. So I proceed to install both cards, set up IP addresses, etc. For the life of me I can not get the Athlon to find the Gateway. Can't even "ping it." The Gateway, however, is working fine, finds the athlon machine right at login, sees all the drives, etc. I've tried everything my limited knowledge can think of. Changed PCI slots, reintalled WIN98SE on both machines. Uninstalled the cards and drivers and started over, (several times), arrrrgh! Anyone have any ideas, other than buy a big firewire drive. :) It's gotten to the point where I have to make it work or I'll go nuts! Know the feeling? Shit, I used to just crack open another reel of 2".

Tags

Comments

garysjo Mon, 02/18/2002 - 04:27

Both machines are set for file and print sharing, all drives. it's weird, when you log on the Gateway you see it instantly connect to the Athlon. When you log on the Athlon, it does not seem to even attempt to connect to the gateway. This is a just a simple peer to peer connection with a crossover cable, although I also tried using my brother's hub to no avail. The Gateway can ping the Athlon, but the Athlon can't ping the Gateway.

garysjo Mon, 02/18/2002 - 12:09

Ya know when sumpen doesn't werk, it's always sumpin stupid!! I figured I'd give the network thing another try today, so I'm messing around with both PC's, my wife (less of a computer person than me) comes downstairs, hangs around for a minute or two and asks; "What if you shut off Norton firewall on the Gateway?" My response: "What firewall"? Anyway, works great now thanks to my wife. The funny part is my brother, who worked as a field eng. for IBM for 18 yrs, and now is a Unix systems eng. for a consultanting co, and I spent two hours yesterday trying to find the bug! Once again, this reminds me to always start troubleshooting with, "is it plugged in?" :cool:

x

User login