On January 30, 2006 07:49 am, Daryl F wrote this amazing epistle:
Mike Pfaiffer wrote:
On January 29, 2006 10:58 pm, Bill Reid wrote this amazing epistle:
Mike Pfaiffer wrote:
So far with this experiment I've eliminated some possible problems. The cables should be fine. The port on the router is fine. The NIC is fine. Since it works with M$, the router is fine (although I have to check if it is limiting based on the DHCP address of the Linux box - I set up a static IP for the M$ side and won't let it have net access).
On Linux do an ifconfig and see if it reports errors or collisions.
-- Bill
Leaving out the first couple of lines which just give the IP addresses, here is what I get for eth0.
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2382801 errors:0 dropped:0 overruns:0 frame:392797 TX packets:2108884 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3298556584 (3145.7 Mb) TX bytes:144681015 (137.9 Mb) Interrupt:10 Base address:0xec00I don't know if I should be running multicast. The MTU looks OK for dialup. I don't know if it's OK for a LAN. No idea what the metric is. Everything else looks as though it should be OK (although I may need to power down the router soon).
Later Mikeframe: doesn't look right. I don't get those on my LAN. I think it means frame errors. It might be a buggy card. What chipset is it?
- Daryl
I thought it was frame SIZE... OK I got it now. I don't know what card it is. I suppose I could check in a day or two (I'll be trying to get a power supply on a 166 box replaced so I might be able to swap cards at the same time). I think one card is a 3com and the other is a D-link from Shaw.
Before I swap cards, I'll try Bills suggestion about ipconfig. It's accessed from the run item from the start menu? Since things appear to be faster I would guess the frame errors are likely to be less.
Obviously I'd rather replace the card than the router. Itech is in the neighbourhood (and I've known the guys for years) so I'd be picking something up from them. Any particular brand to look for? Will any of the newer cards do?
Later Mike
On Mon, 2006-01-30 at 11:05 -0600, Mike Pfaiffer wrote:
Obviously I'd rather replace the card than the router. Itech is in the neighbourhood (and I've known the guys for years) so I'd be picking something up from them. Any particular brand to look for? Will any of the newer cards do?
As Gilles also mentioned, I've found Realtek to be well supported (specifically the Realtek RTL-8139 but even the newer Gigabit cards work well).
Also good are the intel series that use the eepro and eepro100 drivers.
And 3Com cards that use the 3c59x driver which is almost all newer 3Com cards.
Your challenge is figuring out what chipset the "no-name" cards use. You just have to crack open the box and read the chips.
John
On January 30, 2006 11:48 am, John Lange wrote this amazing epistle:
On Mon, 2006-01-30 at 11:05 -0600, Mike Pfaiffer wrote:
Obviously I'd rather replace the card than the router. Itech is in the neighbourhood (and I've known the guys for years) so I'd be picking something up from them. Any particular brand to look for? Will any of the newer cards do?
As Gilles also mentioned, I've found Realtek to be well supported (specifically the Realtek RTL-8139 but even the newer Gigabit cards work well).
Also good are the intel series that use the eepro and eepro100 drivers.
And 3Com cards that use the 3c59x driver which is almost all newer 3Com cards.
Your challenge is figuring out what chipset the "no-name" cards use. You just have to crack open the box and read the chips.
John
I'm printing out your response and will take it with me when I go in. Turns out the card I put in when I got the box home was a 3Com. It died shortly after and so I had already swapped the cards.
After I'm done here I'll follow through with Bills suggestion and see how that works out.
Later Mike
-
John Lange -
Mike Pfaiffer