Connectivity to server
17 Mar 2009 18:20:24 UTC
Topic 194236
(moderation:
I've been having a great deal of trouble viewing the Einstein website, message boards and reaching the project server. The majority of my connection attempts over the past few days result in can't find server errors. It seems like only 1 attempt in 10 succeeds.
Connectivity to server
)
Are you talking about connection attempts with your web browser to the E@H website or connection attempts that your BOINC client may try to make with the scheduler (or perhaps both)? If you can't connect to the website with your browser, it probably means a problem with the network at your end.
If browsing the website is OK and the problem is with the BOINC client, can you please use the messages tab of BOINC Manager to show the messages you get when you first start BOINC and also when you attempt to connect to the server. You can cut and paste the appropriate messages you get into a reply here which should allow us to see what is happening.
Cheers,
Gary.
Both web browser and BOINC,
)
Both web browser and BOINC, I'm afraid. My internet connection is excellent. I can quickly browse another website or have BOINC connect to another project. Reaching Einstein is hit or miss. I'm not using a proxy or anything else strange with my configuration.
17-Mar-2009 17:58:32 [Einstein@Home] Sending scheduler request: Requested by user. Requesting 109061 seconds of work, reporting 0 completed tasks
17-Mar-2009 17:58:33 [---] Project communication failed: attempting access to reference site
17-Mar-2009 17:58:35 [---] Internet access OK - project servers may be temporarily down.
17-Mar-2009 17:58:37 [Einstein@Home] Scheduler request failed: Couldn't resolve host name
EDIT: It took about 12 refresh attempts just to post this message. I keep getting: "Firefox can't find the server at einstein.phys.uwm.edu." Very odd as I can immediately browse anywhere else just fine. I'll experiment to see if my ISP's DNS is having problems resolving the address here.
RE: I'll experiment to see
)
Try sticking 129.89.61.70 into firefox. If you can connect immediately that should tell you that DNS is the problem.
Alternatively you could try ping and tracert to see if you can identify where things break down
.
Cheers,
Gary.
RE: RE: I'll experiment
)
It must be a DNS issue for me then. Using the IP address works immediately when the standard address isn't working. The problem seems to come and go in streaks. I'll check around for an alternative DNS to use. Thanks for your help!
An option: OpenDNS
)
An option: OpenDNS
RE: An option:
)
If you have kids OpenDNS even lets you enable a filter system for their pc's depending on age. Kind of like the old 'net nanny', filters some sites based on age appropriateness. Kinda cool for parents that can't be there every minute but still give their kids a sense of responsibility.