internet disconnecting

Started by stirling, Jun 11, 2008, 22:22:29

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Print
Go Down Pages1 2 All
User actions

stirling

Jun 11, 2008, 22:22:29
dont know if anyone else has mentioned this but over last few days around 6pm uk time my msn has been disconnecting and the server i use for winmx has been dropping connections, this continues for around an hour on and off and i just wondered if theres a particular reason for this, i aint teknikal at all but it does get annoying

Simon

#1
Jun 11, 2008, 22:50:18
I ain't technical either, but someone will be along soon with some advice.  :)
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

stirling

#2
Jun 11, 2008, 23:09:07
glad you came along with the spell checker simon cos i cant spell technical   ;D

David

#3
Jun 11, 2008, 23:10:26
Just for the record mine has been fine tonight no problems at all.hope this helps
Many hammer all over the wall and believe that with each blow they hit the nail on the head.

Simon

#4
Jun 11, 2008, 23:21:19
6pm is a peak time, so it's possible that it could be congestion on your exchange, although BT would undoubtedly deny this.
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

stirling

#5
Jun 11, 2008, 23:23:07
had similar prob while with pipex but with them they told me i was bein throttled and it lasted from 6pm till 11 pm every night

Sebby

#6
Jun 11, 2008, 23:37:12
I've moved this to Help as it'll get more views here I suspect. :)

The first thing to establish is whether you're losing sync or just losing the PPP (or internet) connection. Do you know? If not, what router do you have? You'll be able to tell from the logs, or you may have noticed the lights on the router change; usually there are 2 lights, one for ADSL (representing the connection with the exchange - the "sync") and one for broadband/internet (representing your connection to the ISP). Have you noticed what the lights have been doing?

At this time, I'd say it sounds like sync, and if you're losing sync at a specific time each day, it's likely that something (heating, for example) is interfering.

Anyway, let's clarify exactly what's happening, and we'll take it from there. :)

stirling

#7
Jun 13, 2008, 21:21:54
not too sure how to check but again this evening at 6 pm my net disconnected, and again at 8 30, reason i know is msn keeps cloing down, its starting to get annoying because its happening with frequency now

Sebby

#8
Jun 13, 2008, 21:27:17
To me, it sounds like something is happening at 6pm that is causing a surge of noise, making the router lose sync, but we need to know for sure. Do you know how to access your router's configuration pages? If so, can you find the logs and copy and paste them here? If not, what router is it?

stirling

#9
Jun 13, 2008, 21:29:36
im using the netgear 830dg router, its less than a year old because the experts at pipex told me it was my router, the lights on front are flashin like crazy as im typing, and the server i use for chat on winmx has lost all its connections , i dont know if this helps but its same problem i was having with pipex, althought their tech team actually toild me they disagree with p2p and were physically throttling me back, any help would be much appreciated

Sebby

#10
Jun 13, 2008, 21:34:20
Lights flashing like crazy is normal if you are using the connection. What we need to know is what happens to the lights on the front of the router. Does the "i" go yellow and flash before turning green again? To get the logs, I've got a feeling you login (192.168.0.1 in your internet browser) then go to Diagnostics under Maintenance on the left-hand side. I think it's in there.

stirling

#11
Jun 13, 2008, 21:38:25
Thu, 2008-06-12 22:31:46 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Thu, 2008-06-12 22:41:56 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Thu, 2008-06-12 22:52:03 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Thu, 2008-06-12 23:02:11 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Thu, 2008-06-12 23:12:18 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Thu, 2008-06-12 23:22:25 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Thu, 2008-06-12 23:32:32 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Thu, 2008-06-12 23:41:38 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Thu, 2008-06-12 23:51:46 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 00:01:53 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 00:12:00 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 00:22:07 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 00:32:14 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 00:42:21 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 00:52:28 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 01:01:35 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 01:11:59 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 01:22:09 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 01:32:21 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 01:42:34 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 01:51:50 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 02:02:00 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 02:11:57 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 02:21:39 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 02:31:46 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 02:41:53 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 02:52:00 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 03:02:08 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 03:11:36 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 03:21:38 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 03:31:40 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 03:41:40 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 03:52:16 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 04:01:39 - TCP Packet - Source:192.168.0.2,3003 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 05:11:47 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 05:21:38 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 05:31:45 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 05:41:52 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 05:51:59 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 06:02:06 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 06:12:12 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 06:22:14 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 06:32:16 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 06:41:35 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 06:51:43 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 07:01:50 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 07:11:57 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 07:22:05 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 07:32:12 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 07:42:19 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 07:52:26 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 08:02:34 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 08:11:40 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 08:21:47 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 08:31:54 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 08:42:01 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 08:52:08 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 09:02:15 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 09:12:11 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 09:21:39 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 09:32:18 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 09:41:54 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 09:52:34 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 10:02:06 - Send out NTP request to time-g.netgear.com
Fri, 2008-06-13 10:02:08 - Receive NTP Reply from time-g.netgear.com
Fri, 2008-06-13 10:02:35 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 10:12:03 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 10:21:38 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 10:31:46 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 10:41:54 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 10:52:01 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 11:02:09 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 11:12:16 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 11:22:24 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 11:32:31 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 11:42:57 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 11:52:03 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 12:02:20 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 12:11:45 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 12:22:04 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 12:32:21 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 12:42:00 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 12:52:02 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 13:02:18 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 13:12:29 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 13:21:40 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 13:31:53 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 13:42:05 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 13:52:13 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 14:02:22 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 14:11:47 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 14:22:20 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 14:31:49 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 14:42:21 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 14:52:29 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 15:02:36 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 15:11:42 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 15:22:07 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 15:31:47 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 15:41:39 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 15:51:39 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 16:01:41 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 16:11:44 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 16:21:40 - TCP Packet - Source:192.168.0.2,3460 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 16:28:00 - TCP Packet - Source:192.168.0.2,4972 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 16:31:12 - TCP Packet - Source:192.168.0.2,1127 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 16:31:43 - TCP Packet - Source:192.168.0.2,1127 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 16:32:10 - TCP Packet - Source:192.168.0.2,1182 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 16:32:54 - TCP Packet - Source:192.168.0.2,1222 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 16:41:11 - TCP Packet - Source:192.168.0.2,1660 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 16:41:39 - TCP Packet - Source:192.168.0.2,1660 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 16:51:51 - TCP Packet - Source:192.168.0.2,1660 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 17:01:37 - TCP Packet - Source:192.168.0.2,1660 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 17:11:37 - TCP Packet - Source:192.168.0.2,1660 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 17:21:46 - TCP Packet - Source:192.168.0.2,1660 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 17:31:45 - TCP Packet - Source:192.168.0.2,1660 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 17:41:38 - TCP Packet - Source:192.168.0.2,1660 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 17:51:47 - TCP Packet - Source:192.168.0.2,1660 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 18:02:18 - TCP Packet - Source:192.168.0.2,1660 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 18:12:26 - TCP Packet - Source:192.168.0.2,1660 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 18:22:34 - TCP Packet - Source:192.168.0.2,1660 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 18:31:41 - TCP Packet - Source:192.168.0.2,1660 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 18:41:49 - TCP Packet - Source:192.168.0.2,1660 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 18:51:37 - TCP Packet - Source:192.168.0.2,1660 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 19:01:39 - TCP Packet - Source:192.168.0.2,1660 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 19:11:41 - TCP Packet - Source:192.168.0.2,1660 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 19:21:43 - TCP Packet - Source:192.168.0.2,1660 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 19:23:25 - LCP down.
Fri, 2008-06-13 19:23:32 - Initialize LCP.
Fri, 2008-06-13 19:23:32 - LCP is allowed to come up.
Fri, 2008-06-13 19:24:26 - TCP Packet - Source:192.168.0.2,1660 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 19:24:32 - Initialize LCP.
Fri, 2008-06-13 19:24:32 - LCP is allowed to come up.
Fri, 2008-06-13 19:24:40 - CHAP authentication success
Fri, 2008-06-13 20:13:52 - TCP Packet - Source:192.168.0.2,1197 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 20:21:39 - TCP Packet - Source:192.168.0.2,1197 Destination:192.168.0.2,16698 - [fxserver rule match]
Fri, 2008-06-13 20:30:04 - Administrator login successful - IP:192.168.0.2
Fri, 2008-06-13 20:30:54 - TCP Packet - Source:192.168.0.2,1197 Destination:192.168.0.2,16698 - [fxserver rule match]
not sure if that what you mean sebby but in diagnostics all thats there is ping an ip,perform a dns lookup display the routing table and reboot router, the logs are set seperatly

stirling

#12
Jun 13, 2008, 21:48:08
Status TxPkts RxPkts Collisions Tx B/s Rx B/s Up Time
WAN PPPoA 93762 92761 0 1652 10323 01:22:14
LAN 10M/100M 33916299 31415773 0 34 128 780:45:31
WLAN 11M/54M 1158069 674453 0 383 20 780:45:21


ADSL Link Downstream Upstream
Connection Speed 7648 kbps 448 kbps
Line Attenuation 12 db 3 db
Noise Margin 15 db 25 db

sorry sebby i think this is what your after

stirling

#13
Jun 13, 2008, 21:52:14
i will watch it but often you can hear pc fan  kick in then it drops?  never noticed the light changin coulour though

Sebby

#14
Jun 13, 2008, 21:53:38
The stats look okay, though with attenuation of 12dB, you should be achieving full sync without question. Your noise margin is 15dB, which suggests that the exchange has increased the target figure due to instability (it does this to make the router sync lower, and hence increase stability - but in your case, this should not be necessary).

The logs don't reveal an awful lot, but that could just be that Netgears don't report losses of sync. But the stats do point to instability, so I'd say the likelihood is that there is a noise source causing you to lose sync (this is not to do with the ISP, be it IDNet or whoever).

What I would say is watch the router at 6pm tomorrow and see if the "i" light goes orange, and we'll take it from there. :)

This fan you mention - where is that noise coming from? The router?

stirling

#15
Jun 13, 2008, 21:55:40
could the server i use for winmx be causing this problem at all? ive hosted chat on there for 5 years but its only past 9 months ive had a problem

Sebby

#16
Jun 13, 2008, 22:03:35
I'd very much doubt it. If you are losing sync, this is the connection between you and the exchange (as a result of which the connection between the exchange and the ISP is lost). A loss in sync typically occurs when the SNRM (Signal-to-Noise Ratio Margin) falls to a level where the router cannot hold sync anymore, and it falls due to increased noise. The fact that it's happening at 6pm daily suggests that there is something happening (boiler coming on, etc) that is causing a surge of noise.

So, although your stats are good, something is not quite right. Let us know what happens tomorrow. :)

stirling

#17
Jun 13, 2008, 22:10:56
if it will help ill get logs everytime connections drop throught the day and paste them here and thanx for the help sebby

Sebby

#18
Jun 13, 2008, 22:13:13
I'm not sure it will. The bit of the logs you posted we're interested in are where is says "LCP down", but this refers to the connection between the exchange and the ISP, and at this stage it's unclear whether the router is losing sync too - it could just be that Netgear routers don't report this, so it's best to keep an eye on the router tomorrow and report back. :)

stirling

#19
Jun 13, 2008, 22:17:54
i may have been wrong then about the time because on the logs lcp going down was at 19 23, only thing i can think fo that kicks in at that time is sky plus?

Sebby

#20
Jun 13, 2008, 22:20:54
It could well be Sky; Sky boxes are notoriously noisy, assuming you have got it connected to the phone line. Is it definitely filtered? If so, it's worth disconnecting it from the phone line for a few days and see if the problem disappears. If it does, there are solutions (double filtering, etc), hopefully. :)

Rik

#21
Jun 14, 2008, 10:08:24
The down time is only 7-8 seconds, so I'm guessing it's a PPP problem.
Rik
--------------------

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

stirling

#22
Jun 14, 2008, 19:53:29
checking logs again lcp went down at 3 45 am and again at 9 01 this morning, i have hoovered dust from pc fans and left pc off for ten hours to cool down, ive now ran virus scans and restarted everything and will let you know what happens,  again thanks for the help

Sebby

#23
Jun 14, 2008, 20:14:33
It shouldn't be a PC problem; it were a USB modem, then it could be, but a router is a separate device. I'm still curious as to whether you are losing sync; Rik made a good point that now makes it looks as if it's not.

It might be worth dropping support an email to clarify. They'll be able to tell you from their logs, and if it is just the PPP dropping, they may want to raise it with BT.

stirling

#24
Jun 16, 2008, 17:23:03
 at sebbys suggestion i dropped support a line on saturday, recieved an acknowledgement at 7 30 monday mornin and a further communication at 30 pm monday saying fault had been raised and sorted at exchange with bt. thank you everyone involved for all your help, youve restored my faith in technical help after the debacle i recieved from my previous isp ;D ;D ;D ;D

Rik

#25
Jun 16, 2008, 17:24:53
That's why we like IDNet so much, stirling, they do look after their customers.  :thumb:
Rik
--------------------

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

Sebby

#26
Jun 16, 2008, 18:42:32
Glad to hear that. Now imagine trying to get an ISP like Tiscali to do that! ;D

Rik

#27
Jun 16, 2008, 18:43:36
You'll need a really vivid imagination, of course. ;D
Rik
--------------------

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

stirling

#28
Jun 24, 2008, 18:19:44
what a week, have been without internet for last week since our last conversation, appears that bt had to change ports for me at exchange, its the same issue i was reporting for nearly 2 years with pipex, idnet sorted it after 2 emails and 3 telephone calls, a big thank you to all involved

Rik

#29
Jun 24, 2008, 18:21:19
Glad to hear it Stirling, that's what we love about them, they take no prisoners when it comes to BT.  >:D

Has the line stabilised yet?
Rik
--------------------

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

stirling

#30
Jun 24, 2008, 18:24:13
not sure yet, only got hoime from work half hour ago but all seems fine, ill be watching router status and see if theres any more connections dropping over next 24 hours but support seem to have got to grips with the issue,  wouldve been faster if the engineer that came out on friday wasnt so insistant that it was my router and left, luckily support knew the problem was in exchange and got it sorted as soon as they recieved the report from bt

Rik

#31
Jun 24, 2008, 18:25:10
That's great. Hopefully, things will stabilise and you may even get a bit more speed.  :thumb:
Rik
--------------------

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

stirling

#32
Jun 24, 2008, 18:37:42
im not sure how to paste my results but ive just done a speed test and its faster than ive ever had, coming in at 6077 kbps download and 378 upload, last one i done before going down, i was down to 4200 download so seems like ive deff made the right choice switching to idnet, with my previous isp i actually recorded a download speed of 80, yes 80 kbps even tho i was paying for 8 meg, so you can imagine my sense of pure joy being able to use my internet and actualy see the pages fill in. lol thanks again everyone

Rik

#33
Jun 24, 2008, 18:39:17
Sounds like a few problems have been solved for you.  :)
Rik
--------------------

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

Sebby

#34
Jun 24, 2008, 19:14:06
I'm glad to hear this is sorted. It's amazing how much influence the ISP can have, even when the issue is down to BT. Quite often, it's just that they can't be bothered to look into it (the ISP, that is). :thumb:

stirling

#35
Jun 24, 2008, 20:14:00
No disrespect to rik, hes been great, but it was down to you sebby for getting the ball moving suggesting i contacted support, i was at stage of coming off the net thinking nothing could ever be done to resolve this so thank you, i have been sitting at pc for 3 hours now and not a flicker so hopefully i can now get back to  having fun and enjoying the internet for what it should be, i might even be able to join in the chat just for the hell of it instead of complaining all the time.

Simon

#36
Jun 24, 2008, 20:34:06
Glad to hear it's all sorted, Stirling.  Now you can relax and enjoy IDNetters!  :thumb:
Simon.
--
This post reflects my own views, opinions and experience, not those of IDNet.

Sebby

#37
Jun 24, 2008, 20:38:47
Quote from: stirling on Jun 24, 2008, 20:14:00
No disrespect to rik, hes been great, but it was down to you sebby for getting the ball moving suggesting i contacted support, i was at stage of coming off the net thinking nothing could ever be done to resolve this so thank you, i have been sitting at pc for 3 hours now and not a flicker so hopefully i can now get back to  having fun and enjoying the internet for what it should be, i might even be able to join in the chat just for the hell of it instead of complaining all the time.

I'm glad I was of assistance. :)

Lance

#38
Jun 24, 2008, 22:32:50
Glad your problems are sorted, Stirling!
Lance
_____

This post reflects my own views, opinions and experience, not those of IDNet.
Print
Go Up Pages1 2 All
User actions