In the past the BOINC client was able to negotiate DUN on Win2K with no issues. Starting several revs ago I began having communication failures whereby the client dials, establishes a connection, immediately hangs up and THEN attempts to communicate with the server. This has become quite frustrating at home. There are no issues with the broadband node at work. I am presently using 5.2.10. Will BOINC ever resume reliable DUN capabilities. I know that there are many other issues which make this seem trivial; but it's really starting to get me down and I don't forsee a need to return to broadband at home in the future. I would like to be able to leave the client to it's own devices but I continually find myself having to dial up manually so the thing can acquire units and perform other network functions. My frustration level has caused me to drop operations at home. Thank you for your kind indulgence and I'll try not to whine anymore.

I don't think there has been a change directly related to this, however the latest version is 5.2.13 and all the recent updates have had something to do with communications. Try that version and see if it works again.

---

BOINC WIKI

BOINCing since 2002/12/8

I just installed the latest version of BOINC (5.2.13) and is doesn't work with my dialup connection either. I can't even connect to a project. I go through the connect to a project windows and fill in all the necessary information. Then in the end is simply says "Failed to connect to a project" I haev noticed that while I am doing this, there is no traffic over my dialup connection, not a single byte. The connection works fine for other things, such as my browser, though. Could there be a conflict with my Norton/Symantec firewall? It never asks if I will allow internet access to the BOINC client as it does with other new programs.

---