OK, this is a somewhat stupid problem that has gotten the better of me.

I had a perfectly good Samba server running on a onboard 100Meg NIC. I got a 3c2000 NIC to replace it.

No firewall, no special config. Vanilla Slackware 10 install. Installed the second NIC. I shut down the other and can ping anyone in the network. Then using the same config as before, but I can't get connected. SSH doesn't work either.

If I shut down the 3c2000 and start the 100Meg NIC it works fine.

Any suggestions are greatly appreciated.

is your new NIC activating on boot?
type ifconfig and post the results

eth1 Link encap:Ethernet HWaddr 00:0A:5E:53:DC:9E
inet addr:169.254.14.200 Bcast:255.255.255.204 Mask:255.255.0.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2279 errors:0 dropped:0 overruns:0 frame:0
TX packets:1276 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:762891 (745.0 Kb) TX bytes:994325 (971.0 Kb)
Interrupt:11

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
169.254.0.0 * 255.255.0.0 U 0 0 0 eth1

I have been researching as much as I can. I found a ton of similar problems, but no solutions. i.e. Person is using card XXX they switch to a 3c2000 and SSH, Samba, HTTP stop working. If they switch back things work fine.

Any ideas?

I have to wonder why you are getting a "fake" IP (DHCP autoconfiguration) of the 169.254.0.0/16 netblock. Do you use DHCP on this interface? If so, what do logs from the dhcp server show? Is it offering an IP?

No that's a static IP. It is on a closed network and we use blocks 169.254. 14-18.X

It was started before I took the position and have not taken the time to establish a different scheme.

Solved. The 3c2000.o driver is very outdated. Using the sk98lin driver I was able to make it work.