NAS540 closing his SSH ports automatcly when i dont have login for 5 days

mike4088

hello all NAS users

is there some-one who also experience this , that SSH an FTP getting disables when you dont login your NAS remotely from the Web ?

i have looking at SSHD_config is there is a command who doing this .. but i didnt found any comand who is doing this .. ?? has anyone also the same problems .

Can i add a command on SSHD.Config who will keeps my port an ftp port open ?

hope someone can help me with this to solve this strange problem

greetings

mike4088

Mijzelf

I'm not aware of that problem. Are you sure it's the NAS, and not your router?

remotely from the Web ?

Have you checked if you can still access the NAS locally?

mike4088

yes me , i have the same issue an changed the time at : ClientAliveInterval and ClientAliveCountMax at sshd-conifg , but the problem persists , if you restart your nas540 , the defaults are restored back in to sshd_config defaaults ,, an the problems is the same again that the ports are closing by no respondings

its better , to changed this in the files who being loaded when the NAS540 will boot an its permanent set .i am still searching where you can do that .

any help is welcome offcourse

Mijzelf

It's hard to understand what you are writing.

Are you able to access the NAS locally or not? And if not, is the webserver still available?

I don't think ClientAliveInterval and ClientAliveCountMax have anything to do with this. These are about keeping an existing session alive, not about closing the server port after some time.

its better , to changed this in the files who being loaded when the NAS540 will boot an its permanent set .i am still searching where you can do that .

Well, you can't. The /etc directory is inside a ramdrive which is compressed stored in the kernel. That ramdrive is extracted on each boot. Only a few files are changed after boot by scripts, like the samba config. But AFAIK sshd_config isn't.

That won't stop you from post boot editing the file (or just replacing it) and restarting the ssh server. But as it will have to be done at each boot, you'd better script it. (Unless you seldom reboot, of course)