Is it possible to reboot a Samba NAS device (Cisco/Linksys NSS4000) using telnet?

0

I have a Samba NAS—Cisco/Linksys NSS4000—that I cannot connect to using UNC paths or drive mapping, and I cannot access the built in web application. But I can ping the device by it’s IP address as well as telnet into it. Is it possible to reboot the device over telnet?

I have tried ports 80, 443, 139, and 8888 and I can successfully telnet into each one. Or at least, I don't get any errors.

Brian

Posted 2015-03-23T22:41:12.520

Reputation: 1

Answers

0

If you can SSH (port 22 normally), you can reboot with reboot now

Julian Knight

Posted 2015-03-23T22:41:12.520

Reputation: 13 389

So far that's the only port I've tried that I cannot telnet to. – Brian – 2015-03-23T22:46:51.253

0

I have a Samba NAS that I cannot connect to using UNC paths or drive mapping, and I cannot access the built in web application. But I can ping the device by it’s IP address as well as telnet into it. Is it possible to reboot the device over telnet?

Generally, what you are describing as a “Samba NAS” is simply a Linux box of some kind running some minimal OS fine-tuned to be a Samba share. So on a Linux box you could reboot the system by using the following command:

sudo shutdown -r now

Or possibly use that same command, but without sudo like this:

shutdown -r now

But on some embedded systems—such as those using BusyBox—using this command would work:

system reboot

But without knowing the exact make/model of the NAS in question, it’s hard to say what the exact command should be.

Also, you would need to have a console/terminal session to the device to actually run those commands. If you are trying to telnet into 80, 443, 139 and 8888 and running commands, that won’t work. When you telnet to ports like that you are just making a protocol connection to whatever service might be running on that port. And if none of them are running a console/terminal session the commands won’t work since ports 80, 443 and 8888 are all web services ports and port 139 is simply a NetBIOS port.

JakeGould

Posted 2015-03-23T22:41:12.520

Reputation: 38 217

Updated original post to say it's an NSS4000. – Brian – 2015-03-23T22:49:12.547

1

The most basic commands are halt and reboot. They come in different flavors but are always present on just about any Linux or UNIX system.

– Daniel B – 2015-03-23T23:01:55.930

I don't think these commands are actually getting passed. I've tried every variation of reboot I can think of over the telnet session, on various ports. – Brian – 2015-03-24T15:27:35.723

@Brian If you are trying to telnet into 80, 443, 139 and 8888 and running commands, that won’t work. When you telnet to ports like that you are just making a protocol connection to whatever service might be running on that port. And if none of them are running a console/terminal session the commands won’t work since ports 80, 443 and 8888 are all web services ports and port 139 is simply a NetBIOS port. – JakeGould – 2015-03-24T16:47:24.283

OK, so it may not be possible after all. The device is pretty locked down so I don't think I'll be able to access the terminal. – Brian – 2015-03-24T17:22:58.563