James
It sounds like you covered all the bases, but I was wondering if you could answer a few questions I had?
Have you tried substituting a different switch?
I have a similiar linksys sitting in the desk drawer, because it just doesn't "keep up" compared to the e-smith.
If you can make a crossover cable just to one pc on the internal lan, and restart the client PC, what happens?
Are you by any chance useing DHCP on the e-smith, and the linksys?
I don't know what your config is, but there is always the possiblity that the DHCP service is running on both the e-mith, adnd your linksys. I can see that there would be a conflict in that case, but for sure not enough to re-boot it...
Could they also be sharing the same IP address. The linksys defaults to 192.168.1.1, which the e-smith shouldn't be at.
You mentioned resetting something ( a flick of the power switch). Was that the e-smith, or the linksys?
You can always set the linksys up as intended, and set the DMZ value = to the e-smith. and see what happens, at least for testing. You lose some functionality, and you should also make sure to BLOCK ports 135-139 at a minimum.
Richard, your problem is much harder, at least to me, since you are getting very little feedback. You already switched NICs, and despite there being sometimes a lot of data in roaming profiles, it definitely shouldn't lock up the monster box you have.
If there is nothing in /var/log/messages when it locks, can you see what''s happening in top? It may be useful.
I would probably also try to restart in and selct e-smith-up and ruin in single processor mode. Your box is probalby overkill enuff to get by, and I have some recollection of errors with SMP machines, adn Samba, but nothing I can recall.