Okey, let me light it up:
It works fine for no matter how much time, but at some intervals the
networked computers can't acces the router or the outside. It goes to
normal if I ping the machines from it, or if I wait ~10min.
It does that on any kernel/distribution. In fact, I just don't know
what is happending. When my computer looses acces to it, 2 servers next
by have acces to it..
The next that happend is I changed the mobo and the cpu and the network
cards and it still does that.
It's the first time I see this in some years now..
Which system is the DHCP Server and what is the lease period time-out? Any
Win2K or WinXP systems/servers on the LAN?
This thing is a router?... so has two NICs in it? Connected with what --
coax or TP? -- to the LAN by what: a hub, switch? What speeds here -
10Base-T, 100Base-TX? If you have same-brand NICs you could run a
diagnostics check for connectivity. If you have a switch with some kind of
diags -- at least a Web-based interface -- you could check for LAN traffic
errors.
IME if a LAN has been working and then suddenly starts exhibiting problems,
it's been some kind of network equipment incompatibility: I've had NICs
which would not talk to certain hubs/swicthes at certain speeds; I've had
NICs which would hang the hub/switch, i.e. the entire network, when the
system they were in was powered off; I've had hubs/switches which would not
talk to each other, some not at all, others only certain speeds; I've had
hubs which would "partition" with heavy traffic with a too large TCP Window
size.
This is a P5 with L1 & L2 disabled?... why? That is a damned slow system
then and with two NICs in it could be just too slow - possibly that VIA
chipset will not do Bus Mastering reliably with two NICs, especially with
no caches. It could also just be component aging - e.g. electrolytic caps
drying up. If it's never been replaced, try changing the mbrd battery as a
last stab before junking it.
As you can see there's many things which could be wrong - finding the "one"
is umm, hard... nigh impossible without some kind of sniffing capability.
I've seen people putting better systems than your "router" in the garbage -
a visit to the Salvation Army might turn up something better for the job:
say a P3-500 on a 440-BX mbrd with 256MB memory.