Interesting. My ISP's DNS (at work) is reporting the same IP's as Jord, but 100% packet loss on pings, and it can't trace route. Must be some upstream router hasn't gotten the news yet and can't find where to send the packet.
from home the trace is now into cenic > berkeley and INR 201 or 202 so all may be well there.
Remoting to my machine at home the Seti boards are up! Still no joy from the machine at work! GRRRRRRR
For me Seti (setiathome.berkeley.edu) resolves to 208.68.240.110
BOINC (boinc.berkeley.edu) resolves to 208.68.240.115
I agree on the websites, using whatever DNS my ISP assigns - probably BT's own.
I'm not getting through on either the URLs or the IPs, from either work or home.
I just flushed the DNS cache on my home box and still can't get it.
I'm doing a tracert from home to 208.68.240.110. It somehow knows that the server name is muarae1.ssl.berkeley.edu, but it's not getting past my home portal.
A tracert to setiathome.berkeley.edu knows that it's looking for 208.68.240.110, but still stalls after the first hop.
David
Miserable old git
Patiently waiting for the asteroid with my name on it.
I changed the dns on my home box to google and still couldn't get through. Maybe if I change it in the home router, but I don't want to mess with that via Teamviewer.
David
Miserable old git
Patiently waiting for the asteroid with my name on it.
I changed the dns on my home box to google and still couldn't get through. Maybe if I change it in the home router, but I don't want to mess with that via Teamviewer.
If you have the right IP from your DNS and still can't get through, changing the DNS won't help. There is another router between you and the lab that has an old cache with incorrect information. Only time can fix that issue.
I've posted to both from a remote to my box at home, but the box at work can't connect. Some router points to nothing.
I changed the dns on my home box to google and still couldn't get through. Maybe if I change it in the home router, but I don't want to mess with that via Teamviewer.
If you have the right IP from your DNS and still can't get through, changing the DNS won't help. There is another router between you and the lab that has an old cache with incorrect information. Only time can fix that issue.
I've posted to both from a remote to my box at home, but the box at work can't connect. Some router points to nothing.
When I do a tracert, it comes back 1. 192.168.x.x [home gateway], then step 2 times out. The thing that stumps me is, that happens whether I do it with the URL or the IP.
David
Miserable old git
Patiently waiting for the asteroid with my name on it.
It's gradually getting there
)
It's gradually getting there .....
Waiting for Godot & salvation :-)
Why do doctors have to practice?
You'd think they'd have got it right by now
Interesting. My ISP's DNS
)
Interesting. My ISP's DNS (at work) is reporting the same IP's as Jord, but 100% packet loss on pings, and it can't trace route. Must be some upstream router hasn't gotten the news yet and can't find where to send the packet.
from home the trace is now into cenic > berkeley and INR 201 or 202 so all may be well there.
Remoting to my machine at home the Seti boards are up! Still no joy from the machine at work! GRRRRRRR
I think they have ping
)
I think they have ping response disabled - I couldn't ping, even while I was uploading.
RE: RE: For me Seti
)
I'm not getting through on either the URLs or the IPs, from either work or home.
I just flushed the DNS cache on my home box and still can't get it.
David
Miserable old git
Patiently waiting for the asteroid with my name on it.
RE: RE: RE: For me Seti
)
I'm doing a tracert from home to 208.68.240.110. It somehow knows that the server name is muarae1.ssl.berkeley.edu, but it's not getting past my home portal.
A tracert to setiathome.berkeley.edu knows that it's looking for 208.68.240.110, but still stalls after the first hop.
David
Miserable old git
Patiently waiting for the asteroid with my name on it.
Just saw the server status
)
Just saw the server status page shows a negative number of hits/second. They may have another 32 bit issue lurking.
Still can't reach it from my work ISP.
I changed the dns on my home
)
I changed the dns on my home box to google and still couldn't get through. Maybe if I change it in the home router, but I don't want to mess with that via Teamviewer.
David
Miserable old git
Patiently waiting for the asteroid with my name on it.
RE: I changed the dns on my
)
If you have the right IP from your DNS and still can't get through, changing the DNS won't help. There is another router between you and the lab that has an old cache with incorrect information. Only time can fix that issue.
I've posted to both from a remote to my box at home, but the box at work can't connect. Some router points to nothing.
RE: RE: I changed the dns
)
When I do a tracert, it comes back 1. 192.168.x.x [home gateway], then step 2 times out. The thing that stumps me is, that happens whether I do it with the URL or the IP.
David
Miserable old git
Patiently waiting for the asteroid with my name on it.
I only have the machine I am
)
I only have the machine I am posting from, set to try and report. Once that is clearing, I will allow access from the others.
Pluto will always be a Planet to me.