Network Annoyance

[MaegRil]

Howdy.

I'm addicted to SETI!

One of my computers, (my server) which is: (quick run down)
Supermico P3TDL3
2x 1.4 GHz Tualatins
4x 256 MB ECC/REG CL2 Crucial memory modules (1 GB)
2x Seagate 10K6 SCSI HDDs via onboard Adaptec SCSI controller
2x Western Digital 120 GB Special Edtion HDDs via Promise IDE controller
2x 3Com 3C99B-T PCI-X G-Bit NICs
running FC3

has developed a problem.

And that is, after it has been turned off, I have to probe for the MAC addresses of the network cards before BOINC/SETI will connect to the servers.

ie. I have to open up the Network Settings, edit the ethernet connection, and under the hardware tab probe for the MAC address before BOINC/SETI will talk to the servers.

Two things I find strange about this:
1) the MAC addresses are already there before I probe.
2) BOINC/SETI is the only thing that seems affected. Every other thing involving netwokring works like it should.

Does anyone know anything about this kida of behaviour?

PS. I'm posting this at the BOINC/SETI forums too.

[chili555]

I don't know about this particular problem, but you might set the MAC address explicitly in /etc/sysconfig/network-scripts/ifcfg-eth1 or whatever your interface is. Vi or gedit the line HWADDR=aa:bb:cc:dd:ee as root, save and quit. Restart the machine and let us know.

[MaegRil]

Well, I checked and I found that that line is in there already, for both NICs.