got myself into a bit of a snag here. i upgraded all (well not really, i
did spare two 3c509s) the nics in my lan. since then, things started
getting wiggy on me.
- the linux server (192.168.2.1) with the 3c905b nic and kernel
2.2.5-ac3 can talk to all the windows machines with nary a hitch.
- 192.168.2.2 (3c509b with pnp disabled) is a testbox w/c runs windows
and linux. windows is installed on the hd. whenever i need to run linux, i
just use an etherboot floppy to fetch the kernel and all its files from
192.168.2.1 via tftp and nfs, or at least that's how i did it back then,
'cos now, as soon as i stick the etherboot floppy in, nothing
happens. it just sits there, sending out bootp requests taht never
get answered. it can communicate w/ the linux box (192.168.2.1) only
when running windows.
- 192.168.2.3 (3c509b with pnp disabled) and 192.168.2.4 (3c905b)
have new hds just waiting for linux to be installed. i tried installing
rh4.2 on them last night. rh was unable to recognize the 3c905b nic on
192.168.2.4 (kernel's too old, i think) so i left that alone and moved on
to the other machine, secure in the thought that since it had the old eth
card, things would go smoothly this time. well, the device did get
detected, but it could not estab. connection to 192.168.2.1 (linux,
3c905b) and 192.168.2.2 (windows, 3c509b) which are the only machines here
with a cdrom drive. and so ends my tale.
can anyone help?
