Do you use a proxy server?

No, direct DSL connection.

BOINC was sometimes slow to establish comms for me. Turned out to be waiting on the proxy server to respond. If its using one it will be in the BOINC log at startup.

Do you use a proxy server?

No, direct DSL connection.

BOINC was sometimes slow to establish comms for me. Turned out to be waiting on the proxy server to respond. If its using one it will be in the BOINC log at startup.

I know what a proxy server is. I spent years setting them up as a network manager and later a network VAR. I am not using a proxy server. Here's the line from the BOINC log:

11/5/2010 9:46:11 AM | | Not using a proxy

Do you use a proxy server?

No, direct DSL connection.

Is that with a modem (with the computer handling the connection, IP addressing etc.), or with a router (with the connection, login, dns etc. handled by the router's firmware)?

I think I've heard people saying that BOINC can have problems with its internal (localhost) TCPIP communication between client and manager, if the external (WAN) connection goes down. I've always used routers, so my external connection appears as a LAN, and remains intact even if the DSL goes down - and I've never had this 'losing connection' problem, even though I've tested some pretty ropey versions of BOINC along the way.

Do you use a proxy server?

No, direct DSL connection.

Is that with a modem (with the computer handling the connection, IP addressing etc.), or with a router (with the connection, login, dns etc. handled by the router's firmware)?

I think I've heard people saying that BOINC can have problems with its internal (localhost) TCPIP communication between client and manager, if the external (WAN) connection goes down. I've always used routers, so my external connection appears as a LAN, and remains intact even if the DSL goes down - and I've never had this 'losing connection' problem, even though I've tested some pretty ropey versions of BOINC along the way.

DSL modem. Used DHCP for a while with the modem handling the routing. Now all the machines have fixed IPs with DNS set on the computer except for a couple that connect wirelessly. BOINC Manager loses connection occasionally in all instances. It was less common with 6.10.58 than with later versions. In the later versions I also sometimes see that BM just disappears as CTAPbIi notes above. Even if this problem is related to network variances, BM should be able to handle them gracefully without crashing or losing connection to the client on it's local machine.

I’ve occasionally received similar messages along the line of Boinc is trying to contact the local client, please wait. After a few seconds it connects, so for me it’s not really a problem. I notice it frequently when starting Boinc Manager, but sometimes when I do a manual update. I had put this down to my new router/modem, it also comes with wireless, and I also see this on both the wireless and wired nodes (local network, always connected, router assigned IP6+4 address), but it could be an issue with Boinc itself. I’m only using systems that have been around for a while, so it my be a result of numerous Boinc updates. Boinc seems to be losing the local host source route.

For clarity, I would describe all devices (capable of) running DHCP and supporting multiple computers simply as routers.

Modems, even DSL ones, are devices like, typically, USB dongles which hook into the dial-up networking process.

Well yes, for simplicity I would go along with that; it’s a router, but because I use it as a router.
Technically speaking, the main purpose of a router is to maintain routing tables to help them route packets. They don't have to be modems and they don’t always provide a DHCP service. When buying one it’s a good idea to make sure it also functions as a modem, if that’s what you want from it. While some also come with wireless functionality, there are a variety of implementations, and issues with device compatibility can be frequent. For example, N variants are not always fully backward compatible with g.