Cannot D/L, report results - Error 182
Questions and Answers :
Windows :
Cannot D/L, report results - Error 182
Message board moderation
| Author | Message |
|---|---|
 neo32843  Send message Joined: 1 Dec 03 Posts: 33 Credit: 8,919 RAC: 0 
|
I run BOINC on my laptop, which is networked to my desktop, which connects to the net via dial up. It's been this way forever, and it's always worked, but now it doesnt. I am able to upload when a WU completes, however I cannot report results, or get new work. 5/11/2006 2:18:00 AM||Starting BOINC client version 5.2.4 for windows_intelx86 I tried a tracert from my c prompt. The first hop timed-out. Does this mean its getting hung-up right in my own network? And if so, why can the tracert keepgoing when boinc cannot? How can I do a tracert so I can copy the text so I can post it up here? SETI@HOME - Crunching 24/7 SETI Classic to SETI Enhanced. I was there. "I'm the Christian the Devil warned you about!" ID: 302483 ·  |
Sean.YQ.Gao[Lm]  Send message Joined: 7 Apr 06 Posts: 7 Credit: 884,947 RAC: 2 
|
did the IE work well?  Sean.YQ.Gao[Lm] , Skype: yq.gao Email: lm12041204@sohu.com , lm12041204@sina.com.cn ID: 302516 · |
|
neo32843 Send message Joined: 1 Dec 03 Posts: 33 Credit: 8,919 RAC: 0
|
Yes, IE and FireFox (on my laptop) are both able to load pages and interact. SETI@HOME - Crunching 24/7 SETI Classic to SETI Enhanced. I was there. "I'm the Christian the Devil warned you about!" ID: 302710 · |
paperdragon  Send message Joined: 27 Aug 99 Posts: 174 Credit: 1,452,115 RAC: 0 
|
Just looking at your computers. The message log you posted is for machine 2350224, your celeron. This machine is communicating fine with SETI. You have uploaded, downloaded, and reported results with this computer. You have 168 results either reported or waiting. The other computer, the AMD, has 3 expired results, and none waiting to process. But it says you last communicated today. Have you displayed the correct message log in your original post? On the problem machine, make sure that the Windows built in firewall has not reset it self. I believe other people have had this problem after Windows updates have been applied. Make sure boinc.exe, and boincmgr.exe can get througg. If you still have a problem and it's with the AMD, since there are only 3 unreported, expired results listed maybe you could think about detaching, and they re-attaching the computer. Looks like you have nothing to lose at this point, since all the other outstanding results have been removed from the database.  You need a second life? Seconlife.com ID: 302803 · |
|
neo32843 Send message Joined: 1 Dec 03 Posts: 33 Credit: 8,919 RAC: 0
|
The AMD is my desktop. It has 3 expired results because I cannot leave this computer on all the time (overheats) so they didn't get done. This is also why I don't crunch on this comp anymore. Also, the reason my desktop communicated yesterday is because my desktop is my primary comp for everythign else I do, therefore I like to keep my BOINC up-to-date (just my stats, etc) and also use it to access sites like these forums with the click of a button. So, to answer your question, yes that is the correct message log, from my laptop (2350224) whixh is the comp having the problem. I do not have WIN XP SP2 installed on the laptop, so the firewall settings aren't as advanced. But, for both the shared dial-up connection on the desktop, AND the LAN between the two, I have boinc.exe and boincmgr.exe set as safe or whatever so they should get through. On the problem computer, it has "uploaded" the completed WUs, but they have not been "reported". If I detach, won't I lose that? SETI@HOME - Crunching 24/7 SETI Classic to SETI Enhanced. I was there. "I'm the Christian the Devil warned you about!" ID: 303146 · |
|
neo32843 Send message Joined: 1 Dec 03 Posts: 33 Credit: 8,919 RAC: 0
|
Problem solved. Not sure what fixed it, but heres what I did: > Detached SETI from my desktop (which I no longer use) and close BOINC. > Close BOINC on laptop (problem computer), did NOT detach. > Disabled LAN on desktop and laptop. > Unpluged and replugged hub power cord, and all LAN plugs. > Completely disabled WIN XP firewall for my LAN on both comps (It's still active for the net connection). > Re-Enabled LAN on both comps. > Ran a tracert on the laptop to setiboinc.ssl.berkeley.edu. One time-out reported, but it re-hopped and went through. > Restart BOINC on laptop. And it works! Kind of... I cant get new work cuz my last request was too recent (I hit update like 10 times). But it works! I was suspicious of my network from the get-go. I've used it fine before, but when I ran a tracert the other day, the first hop (being my LAN) had timed-out. Thanks for the help all! SETI@HOME - Crunching 24/7 SETI Classic to SETI Enhanced. I was there. "I'm the Christian the Devil warned you about!" ID: 303161 · |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.