cancel
Showing results for 
Search instead for 
Did you mean: 

Broadband speed plummetted today during storm - needs IP profile resetting

Anotherone
Champion
Posts: 19,107
Thanks: 457
Fixes: 21
Registered: ‎31-08-2007

Re: Broadband speed plummetted today during storm - needs IP profile resetting

If we get rid of most of the SNTP entries as they fill the log  that will be more beneficial - just deleting them from a copy isn't a real help.
You need to Telnet in. I also save my commands to a file so I know what I've changed. I use telnet as follows -
telnet -f telnet##.log 192.168.1.254
Then after I'm done I change the ## to a number by renaming the file, so the first one becomes telnet01.log
The polling is set in minutes, so for 24hrly use the following commands -
sntp config poll=1440
saveall
exit
The other little trick I use is to keep all these telnet commands in a text file. So when I want to use them, I just do a copy and paste of the command to the relevant prompt - this saves typing the more complicated ones with the possibility of typos, never mind the problem of sometimes forgetting them Wink
tillydaff
Grafter
Posts: 37
Registered: ‎20-10-2013

Re: Broadband speed plummetted today during storm - needs IP profile resetting

I'm getting stuck now at the telnet prompt. It welcomes me to Telnet, and says 'microsoft telnet>' but it doesn't ask for my login details.
At what point should the:
sntp config poll=1440
saveall
exit
command be entered?  Huh
Anotherone
Champion
Posts: 19,107
Thanks: 457
Fixes: 21
Registered: ‎31-08-2007

Re: Broadband speed plummetted today during storm - needs IP profile resetting

Are you either typing the full telnet command at a command prompt, ie -
telnet -f telnet##.log 192.168.1.254
or if you don't want a copy saved to a file
telnet 192.168.1.254
or at the Telnet prompt (could be OS dependant - type ? for help usually) it's  o  for open
o 192.168.1.254
Only when logged into the 582n with telnet do you type the:
sntp config poll=1440
saveall
exit
If perchance you get a message about already 2 telnet sessions running on the 582n, then follow the instructions and kill one or both.