Hi gprobst7421,
I have 2 vaguely similar internet problems with other programs I have not been able to resolve. Internet connections should not be so fragile. The first thing to try is to update BOINC. Try downloading from https://boinc.berkeley.edu/download_all.php/

Lawrence

hmmm,

1) Chck: Is BOINC running off local laptop drive or a network drive?
2) Chck: Is the BOINC Manager running at all times? If so, what does it say right bottom when opened? [properly it says "connected to localhost"].
3) Chck: If the BOINC Manager is running, the graphical front end, exit it via the File Exit, but make sure the core client continues to run [A screen would pop-up asking that, if to stop running tasks]. Verify boinc is still running in Task Manager[boinc.exe] and WCG tasks continue to process. Does the WIFI connection problem persist with the BM exited?

Ubuntu... why did you not tell us that before {most of us 'assume' a laptop runs Windows ;>). The 'latest' package from the Ubu repo is probably still 7.0.27... not really the recommended these days which is 7.0.65 I think and soon a 7.2.xx, but it's really not relevant IMO. It's a first to me to run BOINC on one device and then not be able to connect another device to your router [?].

Ubu and WIFI is a poor pairing... a long standing flaky connection you might have. If you do

sudo service iwconfig

does it say power management is on?

If so, do

sudo service iwconfig power off

This will switch of the power management of the WIFI which is a cause of BOINC to act up. You will achieve much higher throughput when the PM is off for WIFI... it tends to go to sleep which can cause BOINC jobs to crash or restart randomly.

Otherwise, if the [UFW?] firewall is on, port 31416 on IP 127.0.01 (localhost) needs to be open, both ways, but since you do not complain of poor BOINC Manager connectivity to the daemon, don't think that's of issue, but that is the default port over which BOINC communicates locally and remotely. As for DHCP, I did pre-assign IP addresses in the router to each device through a MAC table. This way each device, though they themselves should have set DHCP/DNS to auto, always get the same IP, which is what BOINC likes best, in case you run more BOINC clients and wish to remotely control them [BOINCTUI for Ubuntu is a great and works in console].

Why I asked about the 'connected to localhost' was, that some in their wisdom connect BOINC Manager via the network assigned IP... e.g. 192.168.100.010, which means that BOINC will continuously transmit via the router back and forth to the manager... with many jobs queued that could be disastrous. Firewalls don't like that either nor AV software.

PM is off. UFW is configured now to pass on that port but issue still stands.

Also checked the firewall logs on both machine and router, no rejects (other than normal crap pings from the ether)

Gosh I wish i could get this figured out. Driving me nuts.