Message boards :
Number crunching :
Waiting for response from Seti
Message board moderation
Author | Message |
---|---|
Cliff Harding Send message Joined: 18 Aug 99 Posts: 1432 Credit: 110,967,840 RAC: 67 |
For the last several weeks I've been experiencing prolonged wait times, sometime up to 2-3 minutes, to get a response from Berkeley, when either attempting to open a thread or just after posting on a thread. Even going from page to page or forum to forum is getting to be a hassle. Sometimes I can stop and refresh the page and that will clear things up, but most times it doesn't. I'm running FIOS @ 50/25 Mpbs and Verizon is my ISP so that shouldn't be a problem. Has anyone experienced the same conditions? I don't buy computers, I build them!! |
betreger Send message Joined: 29 Jun 99 Posts: 11360 Credit: 29,581,041 RAC: 66 |
Not here. |
Dena Wiltsie Send message Joined: 19 Apr 01 Posts: 1628 Credit: 24,230,968 RAC: 26 |
My response has been find but there are two things to think about. Sometimes my system accumulates clutter. Most of the time it's do to flash crashes and they mess up the IP stack. They can be cleared by a simple reboot. The other is you can have line issues. I can get into my router by connecting to 192.168.0.1 and look at the error long. You will find two types of errors. CRC errors are hard packet error that require retries to recover from. You may also have FEC errors are errors but the packet can be reconstructed on the fly so they don't require a retry. It's best to reset your error counters and watch them for about 30 minutes. A few CRC errors are acceptable but if you find they are a large in relation to your packet count, you may need your line cleaned up. The IP address used to get into your router may be different but the instruction manual should contain that information. If you need a password, mine is located on the bottom of the router. Check out other web sites because information takes different paths on the internet. Even data going to the same destination can arrive by a different route. If other web sites are fine, you have a problem beyond your control and someday they will clean it up. |
Wiggo Send message Joined: 24 Jan 00 Posts: 34744 Credit: 261,360,520 RAC: 489 |
The problem must be towards your end Cliff. Cheers. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14649 Credit: 200,643,578 RAC: 874 |
The IP address used to get into your router may be different but the instruction manual should contain that information. If you need a password, mine is located on the bottom of the router. If you've lost the manual, or reconfigured the router from default and forgotten what you did, you can find the IP address from any machine on the network. Type ipconfig at a command prompt (no switches necessary), and the router's address is displayed as Default Gateway. |
FalconFly Send message Joined: 5 Oct 99 Posts: 394 Credit: 18,053,892 RAC: 0 |
That's a bit weird indeed. For network testing, I'd do the following : - check the Hosts file, which should be clean unless used by special software (if it's infested with data, time to check for malware otherwise) - any new network adapter or -Driver?, maybe a default maxMTU of 1500 on it with an ADSL line? (at least on pre-Win7 systems this causes packet fragmentation an re-routing delays while browsing etc. ; not sure how other OS like Linux/Mac or other internet uplinks handle that issue) - for kicks, testing another DNS server also helps, if there's a rare issue with DNS propagation (i.e. and OpenDNS server or use the NSA *cough* sorry use Google with 8.8.8.8 for a test) - otherwise, a deep antivirus scan (using an other than already installed tool, ideally boot from a dedicated antivirus scan CD) is always a good idea - some browsers seem to get slower over time, despite not really being extended in features while in use (I like to reinstall FireFox once a while and just import the favorites again plus install the plugins needed) - from a command prompt, do a traceroute to websites you know are always up and stable - and to the seti servers of course (if there's a "clog" or weak link in your routing, you'll see it there; it's rare nowadays, but possible that the ideal routing goes over a node that suffers packet loss for some reason) Sometimes it can happen when ISPs and broadband IXPs can't get along and fail to negotiate conditions they can both be happy with. Cutting them off or limiting routing bandwidth is amongst their arsenal to increase their negotiation posision. In the worst case, you're affected by the recent net neutrality violations of some US ISPs and your provider is possibly throttling your traffic to prioritize more lucrative traffic... Might be worth checking out, as you wouldn't be the first one. |
TimeLord04 Send message Joined: 9 Mar 06 Posts: 21140 Credit: 33,933,039 RAC: 23 |
I've noticed slow downs in SETI and SETI Beta over the past couple of weeks. It has taken 30 seconds to a minute to reload pages or up to 30-45 seconds to make a post. I'm on U-Verse; 24 Mb DL and 5 Mb UL, dedicated speeds - like FIOS should be, too. Over the past few days; things seem to have improved. TimeLord04 Have TARDIS, will travel... Come along K-9! Join Calm Chaos |
©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.