Connection problems?

Started by Danni, Jan 28, 2009, 06:23:03

Previous topic - Next topic

0 Members and 2 Guests are viewing this topic.

Print
Go Down Pages 1 ... 5 6 7 8 9 ... 16
User actions

Rik

#150
Jan 30, 2009, 18:42:05
You are, looking at your IP address. So that's odd, as we're in on the same route. Have you forced a re-sync of your router?
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

vitriol

#151
Jan 30, 2009, 18:45:32
Nope.

Connection has been poor for a couple of months now, just not had the time to do much about it.  I did report to IDNet and was advised to test the conection using the engineers socket behind the face plate.  I hate to admit but I've not had the time to do this as of yet.

If I get chance then I'll try doing that over the weekend.

Rik

#152
Jan 30, 2009, 18:47:48
The only other reason I can think of for poor pings would be exchange congestion. :(
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

vitriol

#153
Jan 30, 2009, 18:55:42
While I've been suffering my friends and family members seem to be unaffected and they're all on the same exchange.

Rik

#154
Jan 30, 2009, 18:56:24
Different VP?
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

vitriol

#155
Jan 30, 2009, 19:00:06
Possibly, after I've been down to the refuse centre tomorrow (got loads of stuff to get rid of) then I'll try removing the faceplate and testing the connection.  Thats what I've been advised to do, so I'll do it.  I'll blow a few gig on cr*p game demos and stuff from Xbox Live.  See how it holds up.

Rik

#156
Jan 30, 2009, 19:00:47
Ok, keep us posted.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

dlorde

#157
Jan 30, 2009, 19:37:27
Two evenings running I come home and there's no connection (this time it looks like it dropped out early this morning)... and my ping times don't seem good:

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=180ms TTL=122
Reply from 212.58.224.138: bytes=32 time=168ms TTL=122
Reply from 212.58.224.138: bytes=32 time=174ms TTL=122
Reply from 212.58.224.138: bytes=32 time=112ms TTL=122

Ping statistics for 212.58.224.138:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 112ms, Maximum = 180ms, Average = 158ms

Not very 'always on' really...

Danni

#158
Jan 30, 2009, 19:56:13
Did you not get the email?
IDNet Customer (ex-partner's name): 6th January 2006 - 23rd March 2007
IDNet broadband Customer (my name): 11th June 2008 - 21st April 2010

Now with Be for internets, IDNet for phone.

vitriol

#159
Jan 30, 2009, 20:40:37
Just checked I got it twice.

Sebby

#160
Jan 31, 2009, 00:38:20
Quote from: dlorde on Jan 30, 2009, 19:37:27
Two evenings running I come home and there's no connection (this time it looks like it dropped out early this morning)... and my ping times don't seem good:

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=180ms TTL=122
Reply from 212.58.224.138: bytes=32 time=168ms TTL=122
Reply from 212.58.224.138: bytes=32 time=174ms TTL=122
Reply from 212.58.224.138: bytes=32 time=112ms TTL=122

Ping statistics for 212.58.224.138:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 112ms, Maximum = 180ms, Average = 158ms

Not very 'always on' really...

Been in touch with IDNet yet?

Rik

#161
Jan 31, 2009, 09:27:21
Quote from: dlorde on Jan 30, 2009, 19:37:27
Two evenings running I come home and there's no connection (this time it looks like it dropped out early this morning)

Are you losing sync or dropping PPP?
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Danni

#162
Jan 31, 2009, 09:36:35
My pings are back to normal this morning:

danni@Matilda:~$ ping 212.69.36.10 -c5
PING 212.69.36.10 (212.69.36.10) 56(84) bytes of data.
64 bytes from 212.69.36.10: icmp_seq=1 ttl=59 time=32.6 ms
64 bytes from 212.69.36.10: icmp_seq=2 ttl=59 time=32.0 ms
64 bytes from 212.69.36.10: icmp_seq=3 ttl=59 time=35.2 ms
64 bytes from 212.69.36.10: icmp_seq=4 ttl=59 time=34.6 ms
64 bytes from 212.69.36.10: icmp_seq=5 ttl=59 time=32.0 ms

--- 212.69.36.10 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4000ms
rtt min/avg/max/mdev = 32.044/33.332/35.277/1.365 ms
danni@Matilda:~$
IDNet Customer (ex-partner's name): 6th January 2006 - 23rd March 2007
IDNet broadband Customer (my name): 11th June 2008 - 21st April 2010

Now with Be for internets, IDNet for phone.

Rik

#163
Jan 31, 2009, 09:39:08
That's good, thanks, Danni. :)
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

dlorde

#164
Jan 31, 2009, 13:12:38 Last Edit: Jan 31, 2009, 14:31:34 by Rik
Quote from: Rik on Jan 31, 2009, 09:27:21
Are you losing sync or dropping PPP?
The modem log shows:
...
01/30/2009  19:04:25 If(ATM1) PPP connection ok !
01/30/2009  19:04:23 ATM1 start PPP           
01/30/2009  19:04:23 Dial On Demand(ATM1)     
01/30/2009  19:04:22 ATM1 get IP:<removed - Rik>
01/30/2009  19:04:14 If(ATM1) PPP fail : Unknown error or UI Connect/Disconnect
01/30/2009  19:04:12 ATM1 start PPP           
01/30/2009  19:04:12 Dial On Demand(ATM1)     
01/30/2009  19:03:41 192.168.2.3 login success
...
01/29/2009  22:19:18 NTP Date/Time updated.   
01/29/2009  19:18:17 ATM1 get IP:<removed - Rik>
01/29/2009  19:18:15 If(ATM1) PPP connection ok !
01/29/2009  19:18:13 ATM1 start PPP           
01/29/2009  19:18:13 Dial On Demand(ATM1)     
01/29/2009  19:14:26 sending ACK to 192.168.2.6
01/29/2009  19:11:58 NTP Date/Time updated.   
01/29/2009  19:06:29 Can't find NTP time.     
01/29/2009  19:06:20 ATM1 get IP:<removed - Rik>
01/29/2009  19:06:11 If(ATM1) PPP fail : Unknown error or UI Connect/Disconnect
01/29/2009  19:06:09 ATM1 start PPP           
01/29/2009  19:06:09 Dial On Demand(ATM1)     
01/29/2009  19:05:42 192.168.2.3 login success
01/29/2009  11:30:37 sending ACK to 192.168.2.3
...
01/28/2009  19:07:33 NTP Date/Time updated.   
01/28/2009  19:02:26 If(ATM1) PPP connection ok !
01/28/2009  19:02:25 ATM1 get IP:<removed - Rik>
01/28/2009  19:02:12 ATM1 start PPP           
01/28/2009  19:02:12 Dial On Demand(ATM1)     
01/28/2009  19:02:09 192.168.2.3 login success
...
01/28/2009  12:44:15 ATM1 stop PPP             

dlorde

#165
Jan 31, 2009, 13:19:27
Quote from: Sebby on Jan 31, 2009, 00:38:20
Been in touch with IDNet yet?
Not yet, I thought I'd give it a while to see if it sorts itself out... Pings seem to have recovered:

C:\>ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=23ms TTL=122
Reply from 212.58.224.138: bytes=32 time=34ms TTL=122
Reply from 212.58.224.138: bytes=32 time=24ms TTL=122
Reply from 212.58.224.138: bytes=32 time=53ms TTL=122

Ping statistics for 212.58.224.138:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 23ms, Maximum = 53ms, Average = 33ms

C:\>

Ted

#166
Jan 31, 2009, 13:26:15
Quote from: dlorde on Jan 31, 2009, 13:19:27
Not yet, I thought I'd give it a while to see if it sorts itself out... Pings seem to have recovered:

C:\>ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=23ms TTL=122
Reply from 212.58.224.138: bytes=32 time=34ms TTL=122
Reply from 212.58.224.138: bytes=32 time=24ms TTL=122
Reply from 212.58.224.138: bytes=32 time=53ms TTL=122

Ping statistics for 212.58.224.138:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 23ms, Maximum = 53ms, Average = 33ms

C:\>


You may want to edit your personal ip address out of your previous post :no:
Code Select
Ted
There's no place like 127.0.0.1

Danni

#167
Jan 31, 2009, 14:17:15
Unless it's been edited, I can't see it? Only the BBC one there (and I bet they're used to being spammed with pings :P).
IDNet Customer (ex-partner's name): 6th January 2006 - 23rd March 2007
IDNet broadband Customer (my name): 11th June 2008 - 21st April 2010

Now with Be for internets, IDNet for phone.

Rik

#168
Jan 31, 2009, 14:29:46
It's there, but not for long...
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Rik

#169
Jan 31, 2009, 14:33:07
Quote from: dlorde on Jan 31, 2009, 13:12:38
The modem log shows:
...

Can't really work it out from that, but given the times and the lack of other reports, I'd lean towards a sync drop. What's your downstream attenuation, noise margin and sync speed.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

dlorde

#170
Jan 31, 2009, 16:42:05
Quote from: Rik on Jan 31, 2009, 14:33:07
Can't really work it out from that, but given the times and the lack of other reports, I'd lean towards a sync drop. What's your downstream attenuation, noise margin and sync speed.
It's all looking pretty good speed-wise now:

Actual Data Rate
Up Stream 448 (Kbps.)
Down Stream 7616 (Kbps.)

Noise Margin
Upstream 23 dB
Downstream 12 dB

Attenuation
Upstream 40 dB
Downstream 34 dB

DSL connection rate: 7616 kbps(DOWN-STREAM),  448 kbps(UP-STREAM)
IP profile for line is - 6500 kbps
Actual IP throughput achieved during the test was - 5910 kbps

Rik

#171
Jan 31, 2009, 16:48:47
That looks pretty good. I sense that your noise margin has been set to 12db to stabilise the line, hence the lower sync speed (I suspect you have interleaving on too). If things remain stable, and you can maintain a connection for 14+ days, then your sync speed should increase to 8128.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

#172
Jan 31, 2009, 18:02:49
I reckon it might be interleaving alone that's causing the sync to max out at 7,616k. The margin may be 12dB because the line is so good...

Rik

#173
Jan 31, 2009, 18:07:13
Possible, but given it's 12, I wonder about the target having been changed.
Rik
--------------------

This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

#174
Jan 31, 2009, 18:09:19
Could be. It just seems a bit of a coincidence that the sync would be exactly 7,616k if it was the margin that was the limiting factor.
Print
Go Up Pages 1 ... 5 6 7 8 9 ... 16
User actions