Message boards :
Number crunching :
Unable to connect with server on one computer
Message board moderation
Author | Message |
---|---|
Bill G Send message Joined: 1 Jun 01 Posts: 1282 Credit: 187,688,550 RAC: 182 |
I have suddenly, after a failed update to Win 10, been unable to contact the server on SETI on that computer after a rollback to Win7. Computer http://setiathome.berkeley.edu/show_host_detail.php?hostid=5743750 I have reset the project (suggested by BOINC) to no avail. All that I get is that famous: Internet access OK, project servers may be down. I am getting WUs on my other computers just fine. Any suggestions on what to try? SETI@home classic workunits 4,019 SETI@home classic CPU time 34,348 hours |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
Start->Search, type cmd and hit Enter. In the opening command line window, type ipconfig /flushdns and hit Enter. That deletes the local DNS cache and forces the computer to look up the new IP addresses with the named addresses. |
Bill G Send message Joined: 1 Jun 01 Posts: 1282 Credit: 187,688,550 RAC: 182 |
No luck I am afraid. Getting the same response in BOINC. SETI@home classic workunits 4,019 SETI@home classic CPU time 34,348 hours |
rob smith Send message Joined: 7 Mar 03 Posts: 22160 Credit: 416,307,556 RAC: 380 |
Check your firewall is set to allow BOINC to communicate to the outside world. Bob Smith Member of Seti PIPPS (Pluto is a Planet Protest Society) Somewhere in the (un)known Universe? |
Bill G Send message Joined: 1 Jun 01 Posts: 1282 Credit: 187,688,550 RAC: 182 |
Not the firewall this time. SETI@home classic workunits 4,019 SETI@home classic CPU time 34,348 hours |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14649 Credit: 200,643,578 RAC: 874 |
Check that you've never set any manual IP addresses via a hosts file. It's always worth typing 'ipconfig /displaydns' before flush, just to see if there's anything cached and worth flushing. |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
Since that gives quite a bit of output that cannot be scrolled back through in the command line, best do it like ipconfig /displaydns > c:\temp\dns.txt That outputs the command to a text file called dns.txt in the c:\temp directory. Might be useful to check if c:\temp exists and if not, to make it first. Mine is 564KB big. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14649 Credit: 200,643,578 RAC: 874 |
Since that gives quite a bit of output that cannot be scrolled back through in the command line, best do it like ipconfig /displaydns > c:\temp\dns.txt It depends if the machine with problems is a daily driver or a pure cruncher. On this machine, apart from a couple of internal addresses for machines on my local network, there were only two entries: C:\Users\Richard Haselgrove>ipconfig /displaydns Windows IP Configuration wpad ---------------------------------------- Name does not exist. vortex-win.data.microsoft.com ---------------------------------------- Record Name . . . . . : vortex-win.data.microsoft.com Record Type . . . . . : 5 Time To Live . . . . : 50 Data Length . . . . . : 8 Section . . . . . . . : Answer CNAME Record . . . . : vortex-win.data.metron.live.com.nsatc.net That changed when I opened this browser, of course ;) |
Zombu2 Send message Joined: 24 Feb 01 Posts: 1615 Credit: 49,315,423 RAC: 0 |
make sure you run ipconfig / flushdns with elevated privileges I came down with a bad case of i don't give a crap |
Bill G Send message Joined: 1 Jun 01 Posts: 1282 Credit: 187,688,550 RAC: 182 |
[quote]Check that you've never set any manual IP addresses via a hosts file. quote] That was it Richard. It would appear from the graph that my stats have been going down since the changes in IP address and not just started today...only just noticed today but hard to check how long it was going on as the log gets wiped out each reboot. Thank you all for you suggestions. It was interesting to see almost 300 WUs download after I removed the IP address in the hosts file. SETI@home classic workunits 4,019 SETI@home classic CPU time 34,348 hours |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14649 Credit: 200,643,578 RAC: 874 |
Glad to be of assistance. And a memo to all the advisors: flushdns has no effect if the bad IP assignment is hardwired rather than cached. Edit - the download server IP addresses - the ones we've had most trouble with in the past - have a very short TTL if obtained via DNS, less than 300 (seconds). They've usually disappeared from the cache already by the time you've remembered /displaydns. If you see them in the cache, and especially if they have a TTL in four or five figures, that's usually a clue that they're coming from the hosts file and aren't "live" from a DNS server. |
Bill G Send message Joined: 1 Jun 01 Posts: 1282 Credit: 187,688,550 RAC: 182 |
And did I say almost 300 WUs downloaded....well there were about 550 that downloaded but a lot of them are just ghosts I am afraid and will not be running on this computer. SETI@home classic workunits 4,019 SETI@home classic CPU time 34,348 hours |
©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.