A student of mine recently installed BOINC on a networked system in our lab. Now, the IT folk are claiming that the application made the workstation force a browser election, disrupting the network traffic and bringing all the networked systems to a crawl. The system that the BOINC app was installed on is W2K, and we use a Windows AD domain, either 2003 or 2000 (I'm not sure). Is this an issue with the BOINC application or a misconfigured workstation or network setup? I have the BOINC app running at home without any problems, but then again I don't have a server on the network either. I'd like to be able to get some info to the IT dept so they can correct the problem and get us back on-line.

Any help or info would be appreciated.

I'm surprised anybody is relying on NETBIOS name resolution anymore. Most everybody has switched to DNS name resolution.

As far as a direct answer to your question goes, no BOINC doesn't do anything with NETBIOS name resolution.

Heck, just rebooting a computer can force a Browser Election. The only way to stablize browser elections to a targeted machine is to have a domain controller on each ethernet segment.

---

----- Rom
BOINC Development Team, U.C. Berkeley
My Blog