1
Vraag
2
Reacties
theorise

Raadgever
  • 17Posts
  • 1Oplossingen
  • 4Likes

Internet valt sporadisch weg

Er zijn momenten dat alles al weken goed werkt, en dan valt het internet plotseling uit. Dit geldt voor zowel bekabelde als draadloze verbindingen. Ik wacht 10-60 minuten en het probleem lost zichzelf op zonder dat ik iets doe (behalve boos worden)

 

Wanneer ik mijn router via wifi ping, zie ik dat het niet alleen een probleem met de internetverbinding is, maar dat mijn hele router in bed lijkt te schijten. Hier is een voorbeeld van een ping naar mijn router:

 

Reply from 192.168.178.1: bytes=32 time=7ms TTL=64 
Reply from 192.168.178.1: bytes=32 time=5ms TTL=64
Reply from 192.168.178.1: bytes=32 time=18ms TTL=64
Reply from 192.168.178.1 : bytes=32 time=7ms TTL=64
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.178.50: Destination host unreachable.
Request timed out.
Reply from 192.168.178.50: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.178.50: Destination host unreachable.
Request timed out.
Reply from 192.168.178.50: Destination host unreachable.
Reply from 192.168.178.1: bytes=32 time=10ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=13ms TTL=64
Reply from 192.168.178.1 : bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time =3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=4ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=4ms TTL=64
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
General failure.
Reply from 192.168.178.50: Destination host unreachable.
Request timed out.
Reply from 192.168.178.50: Destination host unreachable.
Reply from 192.168.178.50: Destination host unreachable.
Reply from 192.168.178.50: Destination host unreachable.
Reply from 192.168.178.50: Destination host unreachable.
Reply from 192.168.178.50: Destination host unreachable.
Reply from 192.168.178.1: bytes=32 time=10ms TTL=64

Any idea what's going on? It's not very helpful if this happens in the middle of work meetings.

Oplossing

Geaccepteerde oplossingen
theorise
topicstarter
Raadgever
  • 17Posts
  • 1Oplossingen
  • 4Likes

After removing the redundant splitter and making the settings changes to the router, it definitely feels like a big improvement, I've only experienced one drop out.

 

For now I am happy and I don't think a technician appointment is necessary.

 

Thanks for checking in!

Bekijk in context

32 Reacties 32
tobiastheebe
Super Expert
Super Expert
  • 12368Posts
  • 753Oplossingen
  • 4769Likes

Zou je een of meerdere foto’s willen plaatsen van AOP (hoofdaansluiting in meterkast of woonkamer) en kabels, plus splitter(s) en signaalversterker, voor zover van toepassing?

Zou je tevens de downstream/upstream/historie-gegevens van het modem willen plaatsen volgens deze instructies?

theorise
topicstarter
Raadgever
  • 17Posts
  • 1Oplossingen
  • 4Likes

Hier zijn foto's van de hoofdverbinding. Ik heb eerder een soortgelijk probleem gehad waarbij je me een nieuwe splitter hebt, die het probleem voor een tijdje oploste. Nu gebeurt het weer zonder dat er iets verandert. De splitter staat achter een kast.:

 

PXL_20220810_120721260.jpgPXL_20220810_120739234.MP.jpg

 

Nadat ik de foto's heb gemaakt, probeer ik in te loggen op mijn router om de details te krijgen waar je om vraagt, maar ik word gewoon plotseling begroet met deze schermen en ik kan ze niet doorgeven, ondanks dat mijn internet momenteel werkt (dit is de eerste keer dat ik dit zie om gebeuren):

 

router.pngrouter2.png

tobiastheebe
Super Expert
Super Expert
  • 12368Posts
  • 753Oplossingen
  • 4769Likes

Het modem is aangesloten op een verouderde contactdoos (waarschijnlijk een GUT 14D), via een overbodige splitter. Je kunt het modem in elk geval direct op deze contactdoos aansluiten.

 

Is deze contactdoos het AOP (de hoofdaansluiting) c.q. is er geen contactdoos aanwezig in de meterkast?

 

De wizard wordt getoond omdat deze ofwel nooit is doorlopen of het modem is teruggezet naar fabrieksinstellingen. Na het doorlopen van de wizard kun je de gevraagde gegevens verzamelen.

theorise
topicstarter
Raadgever
  • 17Posts
  • 1Oplossingen
  • 4Likes

You were right, removing the splitter works perfectly. Also, I had to reboot the router to get past the screens I shared earlier, but ended up getting the information:

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked40.310
2Locked40.300
3Locked40.340
4Locked40.300
5Locked40.310
6Locked40.350
7Locked40.950
8Locked40.360
9Locked40.960
10Locked40.350
11Locked40.360
12Locked38.950
13Locked40.320
14Locked38.970
15Locked40.360
16Locked40.370
17Locked38.950
18Locked38.6200
19Locked38.970
20Locked40.350
21Locked38.930
22Locked38.9150
23Locked38.920
24Locked38.970

 

 

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
13840000043512064 qam4
24520000043.5512064 qam3
35200000044.3512064 qam2
45880000044.8512064 qam1



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000
 
theorise
topicstarter
Raadgever
  • 17Posts
  • 1Oplossingen
  • 4Likes

General Configuration

Network access
Allowed
Maximum Number of CPEs
2
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
bac1010001064c38d82d266b


Primary Downstream Service Flow

SFID640658
Max Traffic Rate374500000
Max Traffic Burst42600
Min Traffic Rate0


Primary Upstream Service Flow

SFID640657
Max Traffic Rate37450000
Max Traffic Burst42600
Min Traffic Rate0
Max Concatenated Burst42600
Scheduling Type

BestEffort

 

Network Log

Time Priority Description

10/08/2022 17:00:11noticeLAN login Success;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 16:00:46criticalNo Ranging Response received - T3 time-out;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 15:08:50noticeLAN login Success;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:58:50criticalNo Ranging Response received - T3 time-out;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:58:49criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:58:49criticalRanging Request Retries exhausted;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:58:5criticalNo Ranging Response received - T3 time-out;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:48:52Warning!RCS Partial Service;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:48:49Warning!Lost MDD Timeout;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:48:45criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:48:45Warning!RCS Partial Service;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:48:44criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:12:45Warning!RCS Partial Service;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:11:3noticeTLV-11 - unrecognized OID;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:09:50criticalNo Ranging Response received - T3 time-out;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:08:51criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:04:3criticalNo Ranging Response received - T3 time-out;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:03:39criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:03:39criticalRanging Request Retries exhausted;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:02:55criticalNo Ranging Response received - T3 time-out;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
theorise
topicstarter
Raadgever
  • 17Posts
  • 1Oplossingen
  • 4Likes
 
General Configuration
Network access
allowed
Maximum Number of CPEs
2
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
config file
bac1010001064c38d82d266b


Primary Downstream Service Flow

SFID640658
Max Traffic Rate374500000
Max Traffic Burst42600
Min Traffic Rate0


Primary Upstream Service Flow

SFID640657
Max Traffic Rate37450000
Max Traffic Burst42600
Min Traffic Rate0
Max Concatenated Burst42600
Scheduling Type

BestEffort

 

Network Log

timepriorityDescription
10/08/2022 17:00:11noticeLAN login Success;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 16:00:46criticalNo Ranging Response received - T3 timeout;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM- VER=3.0;
10/08/2022 15:08:50noticeLAN login Success;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:58:50criticalNo Ranging Response received - T3 timeout;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM- VER=3.0;
10/08/2022 14:58:49criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM -VER=3.0;
10/08/2022 14:58:49criticalRanging Request Retries exhausted;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:58:5criticalNo Ranging Response received - T3 timeout;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM- VER=3.0;
10/08/2022 14:48:52Warning!RCS Partial Service;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:48:49Warning!Lost MDD Timeout;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:48:45criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER =3.0;
10/08/2022 14:48:45Warning!RCS Partial Service;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:48:44criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER =3.0;
10/08/2022 14:12:45Warning!RCS Partial Service;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:11:3noticeTLV-11 - unrecognized OID;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0 ;
10/08/2022 14:09:50criticalNo Ranging Response received - T3 timeout;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM- VER=3.0;
10/08/2022 14:08:51criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79; CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:04:3criticalNo Ranging Response received - T3 timeout;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM- VER=3.0;
10/08/2022 14:03:39criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM -VER=3.0;
10/08/2022 14:03:39criticalRanging Request Retries exhausted;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM-VER=3.0;
10/08/2022 14:02:55criticalNo Ranging Response received - T3 timeout;CM-MAC=4c:38:d8:2d:26:6b;CMTS-MAC=00:01:5c:6c:34:79;CM-QOS=1.1;CM- VER=3.0;
tobiastheebe
Super Expert
Super Expert
  • 12368Posts
  • 753Oplossingen
  • 4769Likes

I was already contemplating switching to English after reading the final line of your initial message. Glad to read that removing the splitter appears to have made a positive difference.

 

Downstream and upstream data are looking good, although the first downstream table is missing.

 

Did you the check the meter cupboard for the presence of a coax outlet? If the coax outlet in the living room is the AOP (main outlet), i.e. no outlet is present inside the meter cupboard, it should ideally be replaced with a btv 01-SET, which requires a technician appointment.

theorise
topicstarter
Raadgever
  • 17Posts
  • 1Oplossingen
  • 4Likes

Sorry, I was using Google translate before and sometimes missed something.

 

It is a very old house, the meter cupboard is not typical and does not contain anything to do with the internet.  I believe that the living room outlet is the main (and only) outlet, as I've searched under the front door and also find no entry point.

 

Here is the missing downstream table, if it makes any difference:

 

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

160200000011.540256 qam1
261000000011.140256 qam2
361800000011.440256 qam3
46740000001140256 qam10
568200000010.540256 qam11
669000000010.940256 qam12
76980000001140256 qam13
87060000001140256 qam14
97140000001140256 qam15
1072200000010.940256 qam16
1173000000010.540256 qam17
127460000009.838256 qam19
1376200000010.540256 qam21
1477000000010.538256 qam22
1577800000010.840256 qam23
1678600000010.640256 qam24
1779400000010.338256 qam25
1880200000010.338256 qam26
1981000000010.138256 qam27
2081800000010.140256 qam28
2182600000010.138256 qam29
228340000009.538256 qam30
238420000009.538256 qam31
248500000009.338256 qam32

 

tobiastheebe
Super Expert
Super Expert
  • 12368Posts
  • 753Oplossingen
  • 4769Likes

In properties built before ~1990, the AOP was installed in the living room. It is very likely that the outlet in the living room is the AOP, i.e. the modem is installed in the correct location.

 

Because the splitter previously attenuated the signal by ~4 dB, downstream power is now slightly too high on some channels (> 11 dBmV). However, this should not cause noticeable issues.

 

You may consider updating the modem settings according to this topic (in Dutch), in case any stability still occurs.

theorise
topicstarter
Raadgever
  • 17Posts
  • 1Oplossingen
  • 4Likes

I will update the modem settings to the ones you linked to and give it a few days to see if the problem still persists. If it does, then I'll try to book a technician.

 

Thank you very much for the help!

tobiastheebe
Super Expert
Super Expert
  • 12368Posts
  • 753Oplossingen
  • 4769Likes

Glad to help.

 

A technician may also install a 6 dB forward path attenuator to optimize downstream power levels.

Paul
Community Moderator
Community Moderator
  • 13622Posts
  • 1125Oplossingen
  • 4018Likes

Goodmorning @theorise and a warm welcome to our Community,

Too bad that you're having difficulties with the stability of the intenetconnection! It's good that you started a topic to ask for help. I noticed that our expert @tobiastheebe already gave you some good advice to work with. I'm very curious what your findings are and if everything is working properly. Otherwise I can arrange an appointment with a technician. 

theorise
topicstarter
Raadgever
  • 17Posts
  • 1Oplossingen
  • 4Likes

After removing the redundant splitter and making the settings changes to the router, it definitely feels like a big improvement, I've only experienced one drop out.

 

For now I am happy and I don't think a technician appointment is necessary.

 

Thanks for checking in!

Paul
Community Moderator
Community Moderator
  • 13622Posts
  • 1125Oplossingen
  • 4018Likes

@theorise I'm glad that removing te redunant splitter has resolved the problem! We're happy that your connection is working properly again. In case you still experience problems with the connection I suggest we plan the technician. 

theorise
topicstarter
Raadgever
  • 17Posts
  • 1Oplossingen
  • 4Likes

Hi Paul

 

The past two days the internet has been dropping again very frequently (makes it impossible to work). Today the router decided to reset it's name to default somehow.

 

What is the best way for me to arrange a visit from a technician?

Paul
Community Moderator
Community Moderator
  • 13622Posts
  • 1125Oplossingen
  • 4018Likes

@theoris I'm very sorry that the problem still exists! I've checked the historical signal data and I still notice some drops on the signal along with some noise. A technician should come by to fix this problem. I have planned an appointment with a technician for you on Friday the 9th of September between 08:00 and 13:00 o'clock. You are able to reschedule the appointment via Mijn Ziggo > Mijn Gegevens > Mijn Monteursafspraken in case the date doesn't suit you. Please let us know what your findings are after the visit from the technician. 

theorise
topicstarter
Raadgever
  • 17Posts
  • 1Oplossingen
  • 4Likes

No need to apologize, I really appreciate all the help. Thank you for arranging the appointment, the date works for me.

 

I will update the thread after the technician visit.

Paul
Community Moderator
Community Moderator
  • 13622Posts
  • 1125Oplossingen
  • 4018Likes

@theorise Good to read that you appreciate our help. We'll wait for you update after the visit from the technian. We wish you a great day 😉

theorise
topicstarter
Raadgever
  • 17Posts
  • 1Oplossingen
  • 4Likes

The technician came over.

 

He measured the datastream and saw it was 12DB, so he reduced the amount incoming.

He also replaced the box and added a splitter to further reduce the datastream.

 

I will see how things go from here. He said it also looks like the entry point has been moved since the original installation, which could be causing problems. He also mentioned it could be the router.

 

So I have my fingers crossed his changes fix the issue!

E-mail notificaties
Aan Uit

Ontvang een update bij nieuwe reacties in dit topic.