- 2,787
- 520
- NAS
- DS 718+, 2x-DS 720+
- Router
- RT2600ac
- Operating system
- Windows
- Mobile operating system
- iOS
Last edited:
For the first time in Quite a long time, my ISP had an outage.... (Actually a tree fell across a power line, breaking the one power line up the mountain we live on... and since the ISP's Converters & Amps don't have backup power....)
4+ hours. Our UPS's kept things going the 30 seconds until our generator switched over..... No disruption in power.... here!!
This is just the exact type of situation that would have caused the 2600 (In Prior Firmware's) to stop looking for an IP from the modem....
The modem kept trying to lock, and eventually did.... but the 2600 never got an IP. It ceased to try - after a while.... Power cycling the Modem was futile.... Router still didn't look for an IP from Modem.... You had to power cycle or Reset the 2600 to have it work properly again.... The modem did not need to be power cycled at all!
This was quite evident after Hurricane Helene, when the entire ISP's Infrastructure was in tatters.... Folks tell me 90% of hardware was eventually replaced... Lots of water damage... (Multiple ISP Buildings in cities affected by great flooding -- as most cities are by rivers, in addition to all the downed trees everywhere) So there was a lot of 'Ups and Downs' as infrastructure and fiber's and cables were repaired.... This created the perfect storm for the 2600 to become "Punch Drunk" as I referred to it.... This is all History)
Years ago (actually 6-8 months before Helene) I approached support of ISP and Synology... on this.... ISP at first didn't want to help, until I asked them to ask their manager's, who found history of same types of calls from others... and then said they'd help..... Synology Support did help for a while, but then blamed it on ISP, and refused to talk to Support from ISP, when that became an option.... ISP Support then stated, and via Modem Diagnostics, I confirmed wih modem MFG Support.... that ISP has not ever altered the boot or operational code to my (or ISP Said: any modem).... So it's not anything ISP related..... (!!)
I kept submitting information on it to Synology Support (by then this was after Helene, and wow did it ISP Maintenance happen often enough -- that I found a work around and a way to cause it to occur!!!
I then heard from others who had different Synology Routers, and different ISP's -- with same symptoms! They approached Synology, who blamed ISP... My neighbors with other MFG Routers do not see this failure to get iP like 2600 does.... after ISP Maintenance.... Kinda Points a finger!!!
Work around: Schedule a Daily Reset.... that kept down time to less than a day.... and more importantly:
A WAY TO RE-CREATE THE ISSUE: DISCONNECT MODEM RF INPUT, and leave it off for a few hours.... then re-connect it!!! Submitted both to Synology Support... They refused to try my modem RF disconnect idea...
At this point Synology Support pointed at ISP, but wouldn't talk to them... and I was becoming so frustrated I stopped informing Synology...
THEN after a SRM Update, It stopped happening (I turned off the Daily Reset! to test occasionally) THEY ACTUALLY FIXED IT IN SRM, but even when I contacted them they said they had done NOTHING....
About then The ISP Finished the Infastructure updates and fiber/cable feed fixes.... and for nearly 8 months system was solid..... UNTIL LAST NIGHT'S STORM!!!
2600 after 4+ hours of modem unlock 2600 IMMEDIATELY Connected after Power was returned (Power feeds returned to Fibre amps between ISP building ~8-9 miles away to Cable converter 4 miles away from us - further up the mountain than we are), and Cable AMPS in between Fiber/Cable converter 4 miles away to our development.... and 4.4 miles To Our House...
I CONFIRM YET AGAIN -- That even though Synology Support has told me repeatedly that they have NOT done anything to fix this..... A RECENT SRM UPDATE HAS FIXED THIS ISSUE !!!
I LOVE POSTING SUCCESSFUL RESOLUTION CONFIRMATION POSTS LIKE THIS!!!!
4+ hours. Our UPS's kept things going the 30 seconds until our generator switched over..... No disruption in power.... here!!
This is just the exact type of situation that would have caused the 2600 (In Prior Firmware's) to stop looking for an IP from the modem....
The modem kept trying to lock, and eventually did.... but the 2600 never got an IP. It ceased to try - after a while.... Power cycling the Modem was futile.... Router still didn't look for an IP from Modem.... You had to power cycle or Reset the 2600 to have it work properly again.... The modem did not need to be power cycled at all!
This was quite evident after Hurricane Helene, when the entire ISP's Infrastructure was in tatters.... Folks tell me 90% of hardware was eventually replaced... Lots of water damage... (Multiple ISP Buildings in cities affected by great flooding -- as most cities are by rivers, in addition to all the downed trees everywhere) So there was a lot of 'Ups and Downs' as infrastructure and fiber's and cables were repaired.... This created the perfect storm for the 2600 to become "Punch Drunk" as I referred to it.... This is all History)
Years ago (actually 6-8 months before Helene) I approached support of ISP and Synology... on this.... ISP at first didn't want to help, until I asked them to ask their manager's, who found history of same types of calls from others... and then said they'd help..... Synology Support did help for a while, but then blamed it on ISP, and refused to talk to Support from ISP, when that became an option.... ISP Support then stated, and via Modem Diagnostics, I confirmed wih modem MFG Support.... that ISP has not ever altered the boot or operational code to my (or ISP Said: any modem).... So it's not anything ISP related..... (!!)
I kept submitting information on it to Synology Support (by then this was after Helene, and wow did it ISP Maintenance happen often enough -- that I found a work around and a way to cause it to occur!!!
I then heard from others who had different Synology Routers, and different ISP's -- with same symptoms! They approached Synology, who blamed ISP... My neighbors with other MFG Routers do not see this failure to get iP like 2600 does.... after ISP Maintenance.... Kinda Points a finger!!!
Work around: Schedule a Daily Reset.... that kept down time to less than a day.... and more importantly:
A WAY TO RE-CREATE THE ISSUE: DISCONNECT MODEM RF INPUT, and leave it off for a few hours.... then re-connect it!!! Submitted both to Synology Support... They refused to try my modem RF disconnect idea...
At this point Synology Support pointed at ISP, but wouldn't talk to them... and I was becoming so frustrated I stopped informing Synology...
THEN after a SRM Update, It stopped happening (I turned off the Daily Reset! to test occasionally) THEY ACTUALLY FIXED IT IN SRM, but even when I contacted them they said they had done NOTHING....
About then The ISP Finished the Infastructure updates and fiber/cable feed fixes.... and for nearly 8 months system was solid..... UNTIL LAST NIGHT'S STORM!!!
2600 after 4+ hours of modem unlock 2600 IMMEDIATELY Connected after Power was returned (Power feeds returned to Fibre amps between ISP building ~8-9 miles away to Cable converter 4 miles away from us - further up the mountain than we are), and Cable AMPS in between Fiber/Cable converter 4 miles away to our development.... and 4.4 miles To Our House...
I CONFIRM YET AGAIN -- That even though Synology Support has told me repeatedly that they have NOT done anything to fix this..... A RECENT SRM UPDATE HAS FIXED THIS ISSUE !!!
I LOVE POSTING SUCCESSFUL RESOLUTION CONFIRMATION POSTS LIKE THIS!!!!
