Be* being slow!

Well worth trying the OpenDNS servers if you can get your head round the old TELNET stuff listed above. If it all goes pear shaped I believe you can reset your Be-Box back to default so no real harm in trying.
 
My migrate to be should be happening today,so wanted to check my account on their website .Usually their website is relativly slow for me but for around the past 24 hours is now "page cannot be displayed", asked a few other people to try the website for me, some managed to get on but most got "page cannot be displayed", is this a problem for anyone else?
 
I've been having issues with Sky's DNS servers too :(

Wonder what they run, can't imagine it being Windows 2003 server...
 
greywolf said:
My migrate to be should be happening today,so wanted to check my account on their website .Usually their website is relativly slow for me but for around the past 24 hours is now "page cannot be displayed", asked a few other people to try the website for me, some managed to get on but most got "page cannot be displayed", is this a problem for anyone else?
Click to expand...

I wanted to see how far my migrate is and i get the page cannot be displayed with Opendns servers
 
Gets rid of error correction stuff which usually gives you a significantly faster connection. Much lower ping times and faster downloads.

I don't know exactly how it works but apparently if your line is not of good enough quality the errors will make you disconnect....but mine is good :D

Not many CRC/HEC errors at all in 24 hours....around 30db attenuation and 7-7.5 db snr
 
i think i understand.

Basically if the modem was sending something like 4444 5555 6666 7777 with interleaving it would send 4567 4567 4567 4567........and if it only got back 4567 **** 4567 4567 it would be able to work out the missing information....

So basically fastpath just turns this off so it sends information without doing all that work, which obviously would make it faster.
 
yep, our interleaving has a maximum limit of 8ms set, so you'll only see a maximum increase of 8ms in latency. which is nothing really, for the sake of solid error correction.

If you're seeing a hell of a lot FECs as it is now, then turning off interleaving would be a mistake as you'll just find your line retraining more.
 
Am I being stupid, or does the telnet thing not work on vista? as I type it in and it says its not a recognized command etc...
 
just got switched to fastpath! I used to get between 60-75ms on a CoD4 server I frequent...now I get between 40-50 :)

Also I sync about 1.5mbit higher, is this supposed to happen as well?
 
You must log in or register to reply here.
Back
Top Bottom