Hi, i have recently had infinity installed which was performed by a sub-contractor and was wondering if someone with more knowledge than i can take a look at my possible problems??
He fitted me a new master socket and he (hard ??) wired in my existing telephone extension and a data extension kit nto the back of the socket. I'm not sure if this is the correct method of fitting??
I've had a few problems of late where pages are slow to load, hanging, etc. Admittedly i'm connected wirelessly but this has never been a problem before.
Sometimes my connection reported "limited or no connectivity" so i got in touch with BT who concluded my HH4 was faulty. I also got a new wireless card and things were no better - then all of a sudden my connection seems to stay connected.
Upon running the BT speed test i get these results -
When i do tracerts i get these (large numbers now and then) -
Pings to bbc -
I would be grateful if someone could take a look and see if there is a problem, or if this is ok??
Thanks.
Did you run the speedtest over a wired connection?
It may be a simple channel change will sort things out.
Speedtest is always close to ip profile, connected wirelessly.
I have no channel conflicts, running inSSIDer, i've picked a clear channel - 6.
Its just all these high pings. I used to do a pingtest and it was rock solid - approx 20ms.
Now they're all over the place.
Also, when an installation is complete should the engineer perform a line check??
Because the engineer who did mine didnt and couldn't get away fast enough.
Back to dropping connection now and then.
InSSIDer still shows i'm connected to my HH4 when these disconnections occur.
Happened about 3 or 4 times this morning since switching my pc on.
Inssider shows as connected to my hub but windows reports as disconnected, try to connect, no luck.
Loked in the event log and found some errors and authentication failures?? (Dont know what it means though.)
Seems strange how there are 4 errors listed about the same number of disconnections i've had??
Getting a bit fed up now with this, i've only had Infinity 6 weeks - if this is how its going to be its gonna be a long 18 months.
Anyone got any thoughts on this??
If you use ping www.bbc.co.uk -t and check it when you notice a disconnection or slowness, is the ping any different?
Also, try pinging a server in the US for example to see if it's just limited to sites in different regions.
What DNS servers are you using? If your PC is just using 192.168.1.254 (your router) log in to the router to see if you can see what DNS servers it is using. See if manually specifying different DNS servers has a positive effect. There are several you can try on BT's network:
194.72.6.57
194.73.82.242
194.72.9.34
194.74.65.68
...are a few to try.
You could also try using Google's public DNS servers, or some of the root DNS servers such as:
8.8.8.8
8.8.4.4
4.2.2.1
4.2.2.2
Using HH4 so using whatever it sets - primary 194.72.0.98 & secondary 213.120.234.74
Pinging bbc.co.uk gives ping readings like the ones above, a bit erratic - whereas it used to be around the 20ms mark.
Just done another ping test, albeit wirelessly, but nothings changed here and my pings are increasing.
C:\Users\Dave>ping bbc.co.uk -n 25
Pinging bbc.co.uk [212.58.253.67] with 32 bytes of data:
Reply from 212.58.253.67: bytes=32 time=37ms TTL=115
Reply from 212.58.253.67: bytes=32 time=39ms TTL=115
Reply from 212.58.253.67: bytes=32 time=42ms TTL=115
Reply from 212.58.253.67: bytes=32 time=41ms TTL=115
Reply from 212.58.253.67: bytes=32 time=40ms TTL=115
Reply from 212.58.253.67: bytes=32 time=38ms TTL=115
Reply from 212.58.253.67: bytes=32 time=49ms TTL=115
Reply from 212.58.253.67: bytes=32 time=71ms TTL=115
Reply from 212.58.253.67: bytes=32 time=60ms TTL=115
Reply from 212.58.253.67: bytes=32 time=100ms TTL=115
Reply from 212.58.253.67: bytes=32 time=41ms TTL=115
Reply from 212.58.253.67: bytes=32 time=37ms TTL=115
Reply from 212.58.253.67: bytes=32 time=44ms TTL=115
Reply from 212.58.253.67: bytes=32 time=44ms TTL=115
Reply from 212.58.253.67: bytes=32 time=40ms TTL=115
Reply from 212.58.253.67: bytes=32 time=39ms TTL=115
Reply from 212.58.253.67: bytes=32 time=39ms TTL=115
Reply from 212.58.253.67: bytes=32 time=40ms TTL=115
Reply from 212.58.253.67: bytes=32 time=46ms TTL=115
Reply from 212.58.253.67: bytes=32 time=45ms TTL=115
Reply from 212.58.253.67: bytes=32 time=47ms TTL=115
Reply from 212.58.253.67: bytes=32 time=37ms TTL=115
Reply from 212.58.253.67: bytes=32 time=46ms TTL=115
Reply from 212.58.253.67: bytes=32 time=46ms TTL=115
Reply from 212.58.253.67: bytes=32 time=44ms TTL=115
Ping statistics for 212.58.253.67:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 100ms, Average = 46ms
I would appreciate some input as things seem to be getting worse.