I have had a Seagate Central NAS system for several years - and use it
for backing up some of the PCs on my network and also for occasional
remote access to my media files when away from home - mainly using the
Tappin app on mobile devices.

I have recently discovered that Seagate stopped supporting remote
access, and turned off the Tappin app in early April.

I guess that a number of readers of these NGs must be affected by this,
and wondered whether anyone has found a solution - other than using
cloud storage. I simply want to be able to access the files stored on
my NAS remotely without needing to leave any computers running when I'm
away from home. Any suggestions?
--
Cheers,
Roger
____________
Please reply to Newsgroup. Whilst email address is valid, it is seldom
checked.

On 5/6/2018 11:14 AM, Roger Mills wrote:
I have had a Seagate Central NAS system for several years - and use it
for backing up some of the PCs on my network and also for occasional
remote access to my media files when away from home - mainly using the
Tappin app on mobile devices.

I have recently discovered that Seagate stopped supporting remote
access, and turned off the Tappin app in early April.

I guess that a number of readers of these NGsÂ* must be affected by this,
and wondered whether anyone has found a solution - other than using
cloud storage. I simply want to be able to access the filesÂ* stored on
my NAS remotely without needing to leave any computers running when I'm
away from home. Any suggestions?

Check to see if your router supports VPN (Virtual Private Network) as a
feature. It needs to have the Server version of the VPN, be it OpenVPN
Server or PPTP Server.

In my case I have a Asus RT-AC68P/U router attached to my Cable modem.
For various reasons I have loaded version 140 of the Tomato firmware
into my router. This allows me to activate either OpenVPN or PPTP
versions of VPN. I personally choose the OpenVPN method as I already
was using the OpenVPN on my PC's to remotely connect to a couple of
charities that I help keep operating. OpenVPN does have a little harder
learning curve than PPTP but for the home user either will work.

With the VPN connection I can remotely connect to any device normally
accessible on my LAN, be it a PC, NAS, or even security cameras. So in
your case all you would have to leave on is the router, NAS, possibly a
Ethernet bridge, and what ever modem you use to connect to the internet.
Should you want to access your PC's than too could be arrange.

For many routers on the market you don't need to change the firmware to
Tomato or DD-WRT as they come with some version of VPN software built
into them. For other models if you are lucky you can upgrade the
firmware to DD-WRT, Tomato, or one of the other alternate firmware that
are out there.

On 06/05/18 17:14, Roger Mills wrote:
I simply want to be able to access the filesÂ* stored on
my NAS remotely without needing to leave any computers running when I'm
away from home. Any suggestions?

Well you need to leave the NAS running.

Id be tempted to rip its disk out and fit to a Pi or equivalent, then
set up ssh access and dynamic DNS and remote passthru on yer router


--
New Socialism consists essentially in being seen to have your heart in
the right place whilst your head is in the clouds and your hand is in
someone else's pocket.

Roger Mills wrote:
I have had a Seagate Central NAS system for several years - and use it
for backing up some of the PCs on my network and also for occasional
remote access to my media files when away from home - mainly using the
Tappin app on mobile devices.

I have recently discovered that Seagate stopped supporting remote
access, and turned off the Tappin app in early April.

I guess that a number of readers of these NGs must be affected by this,
and wondered whether anyone has found a solution - other than using
cloud storage. I simply want to be able to access the files stored on
my NAS remotely without needing to leave any computers running when I'm
away from home. Any suggestions?

Well you could have something like a Raspberry PI left on permanently
to give you access, very little power, no fan or anything.

I'm not sure what OS a 'Seagate Central NAS' runs but if it's Linux
(almost certainly) then you can probably get at it via that somehow.

--
Chris Green
·

On 07/05/2018 17:48, Good Guy wrote:
On 06/05/2018 17:14, Roger Mills wrote:

I guess that a number of readers of these NGs must be affected by
this, and wondered whether anyone has found a solution - other than
using cloud storage. I simply want to be able to access the files
stored on my NAS remotely without needing to leave any computers
running when I'm away from home. Any suggestions?

There are many solutions:

https://www.noip.com/
https://dyn.com/dns/
https://duckdns.org/
http://freedns.afraid.org/
https://www.dynu.com/
http://www.dnsdynamic.org/


Thanks. but these are solutions to a problem which I don't have! I've
got a static WAN IP address - so I don't need any sort of dynamic DNS in
order to address it.


Just because one company stops something it doesn't mean that life must
come to an end. Find different ways of doing things. That's how human
beings have evolved.


Seagate provided a facility whereby you could log on at
access.seagate.com and access the files on your NAS. That may well have
employed some sort of dynamic DNS for those needing it - but that isn't
the issue. They have taken down their server, and withdrawn support for
the Tappin app on portable devices. They apologise for any inconvenience
caused(!) and assure me that my data is quite safe - but can only be
accessed from within my own network.

My router supports Game and Application Sharing - which permits me (for
example) to associate a PPTP server with my Seagate NAS so that - in
theory - anything coming in on port 1723 goes to the NAS. Problem is
that all such connects are refused!

If I log on to the NAS's web interface, it offers me 'Services' of
"Remote Access", "Seagate Media", "DLNA" and "iTunes". The first two of
these are no longer supported and the last two only work on the same LAN
as the NAS.

I've no idea what OS the NAS uses - probably some flavour of Unix/Linux
- but it's pretty thoroughly locked down with no ready access to it. I
*can* FTP to the NAS but that doesn't seem to allow me to do much.
--
Cheers,
Roger
____________
Please reply to Newsgroup. Whilst email address is valid, it is seldom
checked.

On 07/05/18 23:12, Roger Mills wrote:
Seagate provided a facility whereby you could log on at
access.seagate.com and access the files on your NAS. That may well have
employed some sort of dynamic DNS for those needing it - but that isn't
the issue. They have taken down their server, and withdrawn support for
the Tappin app on portable devices. They apologise for any inconvenience
caused(!) and assure me that my data is quite safe - but can only be
accessed from within my own network.

My router supports Game and Application Sharing - which permits me (for
example) to associate a PPTP server with my Seagate NAS so that - in
theory - anything coming in on port 1723 goes to the NAS. Problem is
that all such connects are refused!

If I log on to the NAS's web interface, it offers me 'Services' of
"Remote Access", "Seagate Media", "DLNA" and "iTunes". The first two of
these are no longer supported and the last two only work on the same LAN
as the NAS.

I've no idea what OS the NAS uses - probably some flavour of Unix/Linux
- but it's pretty thoroughly locked down with no ready access to it. I
*can* FTP to the NAS but that doesn't seem to allow me to do much.

Hmm. A pretty problem.

Obviously there is a way in, but its not well advertised.
It the tappin crap was supposed to work behind a firewall with no
especial configuration, that strongly implies that the NAS istself sets
up and maintains a permanent connection to some seagate cloud.

Bit like skype does


Now if that is the case you wont be able to use that partucular backdoor.


I would try scanning the NAS ports to see which are active.

My guess is that ssh might be open. If its bog standard linux on the
NAS. Try using PUTTY to connect to it. If that works you can use sftp
and its chums if you redirect port 22 to the NAS.


It is not beyond the bounds of reason either to set up port redirection
for SMB services on the router so you can actually mount the NAS across
the internet. TCP ports 139 and 445 and UDP ports 137 and 138 should be
redirected to the NAS box.

Obviously you wont be able to 'scan' for the NAS across the internet, so
you will have to know ip address and tell whatever ****e MS uses to
display shares *for that server*. Or better still use NET USE to mount
the device as a drive etc


It's not very secure though, but I myself have done this years ago as
proof of concept.




--
If you tell a lie big enough and keep repeating it, people will
eventually come to believe it. The lie can be maintained only for such
time as the State can shield the people from the political, economic
and/or military consequences of the lie. It thus becomes vitally
important for the State to use all of its powers to repress dissent, for
the truth is the mortal enemy of the lie, and thus by extension, the
truth is the greatest enemy of the State.

Joseph Goebbels

Roger Mills wrote:
If I log on to the NAS's web interface, it offers me 'Services' of
"Remote Access", "Seagate Media", "DLNA" and "iTunes". The first two of
these are no longer supported and the last two only work on the same LAN
as the NAS.

They "only work on the same LAN as the NAS." because your router
doesn't allow the ports used by them to/from the outside. So you
could open up those ports on the router and get remote access, however
that does have security implications.


I've no idea what OS the NAS uses - probably some flavour of Unix/Linux
- but it's pretty thoroughly locked down with no ready access to it. I
*can* FTP to the NAS but that doesn't seem to allow me to do much.

What doesn't FTP allow you to do that you want to do? You can get
'file explorer' like GUIs that use FTP.

--
Chris Green
·

On 08/05/2018 14:03, Chris Green wrote:


What doesn't FTP allow you to do that you want to do? You can get
'file explorer' like GUIs that use FTP.


The op doesn't actually say what NAS he has but..

https://wiki.debian.org/InstallingDe.../PersonalCloud

gives instructions for putting linux on some Seagate NAS boxes.

Then he has multiple options if it works or buying a synolgy NAS if it
doesn't.

On 08/05/2018 15:57, dennis@home wrote:
On 08/05/2018 14:03, Chris Green wrote:


What doesn't FTP allow you to do that you want to do? You can get
'file explorer' like GUIs that use FTP.


The op doesn't actually say what NAS he has but..

https://wiki.debian.org/InstallingDe.../PersonalCloud

gives instructions for putting linux on some Seagate NAS boxes.

Then he has multiple options if it works or buying a synolgy NAS if it
doesn't.

The model of mine is SRN01C - which does not appear to be one of the
supported models.
--
Cheers,
Roger
____________
Please reply to Newsgroup. Whilst email address is valid, it is seldom
checked.

On 08/05/2018 08:22, The Natural Philosopher wrote:

On 07/05/18 23:12, Roger Mills wrote:

Seagate provided a facility whereby you could log on at
access.seagate.com and access the files on your NAS. ...
... They have taken down their server, and withdrawn
support for the Tappin app on portable devices.

Yes, it seems like it really has gone already:
C:\TEMPping access.seagate.com

Pinging seagateaccess.tappin.com [208.89.184.225] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 208.89.184.225:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

They apologise for any
inconvenience caused(!) and assure me that my data is quite safe - but
can only be accessed from within my own network.

So, as others have suggested, you need think about how to gain access
across your own router.

My router supports Game and Application Sharing - which permits me
(for example) to associate a PPTP server with my Seagate NAS so that -
in theory - anything coming in on port 1723 goes to the NAS. Problem
is that all such connects are refused!

Probably need to open up the firewall on the NAS as well as the one on
the router.

If I log on to the NAS's web interface, it offers me 'Services' of
"Remote Access", "Seagate Media", "DLNA" and "iTunes". The first two
of these are no longer supported and the last two only work on the
same LAN as the NAS.

So you're going to have to hack into the NAS, which means that probably
you'd've done better to post to a Linux NG, but see some suggestions
below anyway.

I've no idea what OS the NAS uses - probably some flavour of
Unix/Linux

Almost certainly an embedded version of Linux.

but it's pretty thoroughly locked down with no ready
access to it.

Apparently at one time not securely locked down at all:
https://www.slashgear.com/seagate-na...hole-08402370/

Oh dear! For starters, try telnet from the relative security of your
own LAN!

I *can* FTP to the NAS but that doesn't seem to allow me
to do much.

Obviously there is a way in, but its not well advertised.

Yes, apparently use telnet!

It the tappin crap was supposed to work behind a firewall with no
especial configuration, that strongly implies that the NAS istself sets
up and maintains a permanent connection to some seagate cloud.

Bit like skype does

Possibly, but that can be disabled now, if the OP can get into the box.

Now if that is the case you wont be able to use that partucular backdoor.

Unless he subverts it in some way.

I would try scanning the NAS ports to see which are active.

My guess is that ssh might be open. If its bog standard linux on the
NAS. Try using PUTTY to connect to it. If that works you can use sftp
and its chumsÂ* if you redirect port 22 to the NAS.

Given that telnet may be able to gain access, I would advise starting
with that.

It is not beyond the bounds of reason either to set up port redirection
for SMB services on the router so you can actually mount the NAS across
the internet. TCP ports 139 and 445 and UDP ports 137 and 138 should be
redirected to the NAS box.

Why would he need Samba/SMB? He makes no specific mention of Windows
devices requiring remote access, only media files, so presumably a
mobile or a tablet, Mac or Android, which are both Linux.

Obviously you wont be able to 'scan' for the NAS across the internet, so
you will have to know ip address and tell whatever ****e MS uses to
display shares *for that server*. Or better still use NET USE to mount
the device as a drive etc

No, no! He doesn't seem to need this at all. NET USE is a (very old
legacy) Windows command to mount a network share as a drive letter.
These days, he wouldn't even need this to connect from a Windows
machine. W9x or older used it, but since 2K+, in fact I suspect even
NT3+, Windows PCs have been able to connect directly using the protocol:
\\Server\Share

It's not very secure though, but I myself have done this years ago as
proof of concept.

I suspect the way forward is to tunnel, but, although I understand the
principles involved, I'm not familiar with the practicalities of this.

Back to the OP:

There are two stages involved in customising/hacking such devices:

1) Gaining access, it sounds as though telnet might work, so try that
first, but failing that, see the next link below.

2) Finding a workable method of subverting the boot process to apply
the desired customisations.

Others already may have done some or all of this work for you. I
haven't read the following, but the equivalent Zyxel section was very
helpful to me:
http://www.nas-central.org/wiki/Seagate_Central

Although the following apply to different devices, if you want brief
descriptions of how the above two stages are attained in practice,
together with some example scripts, see also:

http://www.macfh.co.uk/Test/QNAPNMP1000.html
http://www.macfh.co.uk/Test/ZyxelNSA221.html

Also, although it's probably a bit late for you, for future reference,
the moment I buy anything like this I go online and download and save
locally everything related to it that there is the remotest possibility
that I could ever need - PDF Manuals, firmware upgrades, instructions
for hacking into, files required to do so, etc, etc. Here are some
links to things that might still prove useful to you:

Manual: https://www.manualsearcher.com/seaga...-srn01c/manual
https://www.seagate.com/files/www-co...r-guide-us.pdf
http://knowledge.seagate.com/article...S/FAQ/005532en

The above from:
https://duckduckgo.com/?t=palemoon&q=Seagate+SRN01C+NAS

On 08/05/2018 08:22, The Natural Philosopher wrote:
On 07/05/18 23:12, Roger Mills wrote:
Seagate provided a facility whereby you could log on at
access.seagate.com and access the files on your NAS. That may well
have employed some sort of dynamic DNS for those needing it - but that
isn't the issue. They have taken down their server, and withdrawn
support for the Tappin app on portable devices. They apologise for any
inconvenience caused(!) and assure me that my data is quite safe - but
can only be accessed from within my own network.

My router supports Game and Application Sharing - which permits me
(for example) to associate a PPTP server with my Seagate NAS so that -
in theory - anything coming in on port 1723 goes to the NAS. Problem
is that all such connects are refused!

If I log on to the NAS's web interface, it offers me 'Services' of
"Remote Access", "Seagate Media", "DLNA" and "iTunes". The first two
of these are no longer supported and the last two only work on the
same LAN as the NAS.

I've no idea what OS the NAS uses - probably some flavour of
Unix/Linux - but it's pretty thoroughly locked down with no ready
access to it. I *can* FTP to the NAS but that doesn't seem to allow me
to do much.

Hmm. A pretty problem.

Obviously there is a way in, but its not well advertised.
It the tappin crap was supposed to work behind a firewall with no
especial configuration, that strongly implies that the NAS istself sets
up and maintains a permanent connection to some seagate cloud.

Bit like skype does


Now if that is the case you wont be able to use that partucular backdoor.


I would try scanning the NAS ports to see which are active.

My guess is that ssh might be open. If its bog standard linux on the
NAS. Try using PUTTY to connect to it. If that works you can use sftp
and its chums if you redirect port 22 to the NAS.


It is not beyond the bounds of reason either to set up port redirection
for SMB services on the router so you can actually mount the NAS across
the internet. TCP ports 139 and 445 and UDP ports 137 and 138 should be
redirected to the NAS box.

Obviously you wont be able to 'scan' for the NAS across the internet, so
you will have to know ip address and tell whatever ****e MS uses to
display shares *for that server*. Or better still use NET USE to mount
the device as a drive etc


It's not very secure though, but I myself have done this years ago as
proof of concept.


Thanks for your comments.

I have made *some* progress with FTP. There are two shares on the NAS -
a public one which accepts an anonymous ftp connection, and a private
one which requires a username and password. I can point my AceFTP PRO
client at either of these, and see the folders and files. That's from
within my own network, of course.

I've done a port scan, and found a number of ports open:

22 OpenSSH
110 ?
139 Samba
143 ?
443 OpenSSL
445 Samba (again)
548 Netatalk
993 ?
995 ?

Do any of these look promising as a means of getting remote access to my
files? If so, which ones, and what client software/apps would I need to
use on (a) Windows and (B) Android?
--
Cheers,
Roger
____________
Please reply to Newsgroup. Whilst email address is valid, it is seldom
checked.

Roger Mills wrote:
On 08/05/2018 08:22, The Natural Philosopher wrote:
On 07/05/18 23:12, Roger Mills wrote:
Seagate provided a facility whereby you could log on at
access.seagate.com and access the files on your NAS. That may well
have employed some sort of dynamic DNS for those needing it - but that
isn't the issue. They have taken down their server, and withdrawn
support for the Tappin app on portable devices. They apologise for any
inconvenience caused(!) and assure me that my data is quite safe - but
can only be accessed from within my own network.

My router supports Game and Application Sharing - which permits me
(for example) to associate a PPTP server with my Seagate NAS so that -
in theory - anything coming in on port 1723 goes to the NAS. Problem
is that all such connects are refused!

If I log on to the NAS's web interface, it offers me 'Services' of
"Remote Access", "Seagate Media", "DLNA" and "iTunes". The first two
of these are no longer supported and the last two only work on the
same LAN as the NAS.

I've no idea what OS the NAS uses - probably some flavour of
Unix/Linux - but it's pretty thoroughly locked down with no ready
access to it. I *can* FTP to the NAS but that doesn't seem to allow me
to do much.

Hmm. A pretty problem.

Obviously there is a way in, but its not well advertised.
It the tappin crap was supposed to work behind a firewall with no
especial configuration, that strongly implies that the NAS istself sets
up and maintains a permanent connection to some seagate cloud.

Bit like skype does


Now if that is the case you wont be able to use that partucular backdoor.


I would try scanning the NAS ports to see which are active.

My guess is that ssh might be open. If its bog standard linux on the
NAS. Try using PUTTY to connect to it. If that works you can use sftp
and its chums if you redirect port 22 to the NAS.


It is not beyond the bounds of reason either to set up port redirection
for SMB services on the router so you can actually mount the NAS across
the internet. TCP ports 139 and 445 and UDP ports 137 and 138 should be
redirected to the NAS box.

Obviously you wont be able to 'scan' for the NAS across the internet, so
you will have to know ip address and tell whatever ****e MS uses to
display shares *for that server*. Or better still use NET USE to mount
the device as a drive etc


It's not very secure though, but I myself have done this years ago as
proof of concept.


Thanks for your comments.

I have made *some* progress with FTP. There are two shares on the NAS -
a public one which accepts an anonymous ftp connection, and a private
one which requires a username and password. I can point my AceFTP PRO
client at either of these, and see the folders and files. That's from
within my own network, of course.

I've done a port scan, and found a number of ports open:

22 OpenSSH
110 ?
139 Samba
143 ?
443 OpenSSL
445 Samba (again)
548 Netatalk
993 ?
995 ?

Do any of these look promising as a means of getting remote access to my
files? If so, which ones, and what client software/apps would I need to
use on (a) Windows and (B) Android?

I'm thinking you want to work your network foo on Port 22.

https://serverfault.com/questions/74...-does-sftp-use

"As SFTP runs as a subsystem of SSH it runs on whatever
port the SSH daemon is listening on"

"SFTP transfers all data over the SSH connection.
No additional port is used."

Paul

On 09/05/2018 19:42, Paul wrote:
Roger Mills wrote:


I have made *some* progress with FTP. There are two shares on the NAS
- a public one which accepts an anonymous ftp connection, and a
private one which requires a username and password. I can point my
AceFTP PRO client at either of these, and see the folders and files.
That's from within my own network, of course.

I've done a port scan, and found a number of ports open:

22 OpenSSH
110 ?
139 Samba
143 ?
443 OpenSSL
445 Samba (again)
548 Netatalk
993 ?
995 ?

Do any of these look promising as a means of getting remote access to
my files? If so, which ones, and what client software/apps would I
need to use on (a) Windows and (B) Android?

I'm thinking you want to work your network foo on Port 22.

https://serverfault.com/questions/74...-does-sftp-use

"As SFTP runs as a subsystem of SSH it runs on whatever
port the SSH daemon is listening on"

"SFTP transfers all data over the SSH connection.
No additional port is used."

Paul

Thanks. I had come to the same conclusion - and have made *some*
progress using sftp on Port 22, but still have a way to go.

As noted before, when connecting tom the NAS from within my own
network, I can use bog-standard FTP on Port 21. I can access the Private
share on the NAS by supplying the correct username and password, and can
access the Public share by using an anonymous logon.

In order to access the NAS from outside my network (Android tablet using
Android phone-generated hotspot) using sftp, I have told my router to
assign port 22 to the NAS. I can then access the Private share ok, by
supplying the username and password. But I'm stuck with the Public
share. I haven't found any way of using sftp anonymously, so I can't get
in. I've tried several Android sftp client apps - the most promising one
being AndFTP - but to no avail.

Any ideas?
--
Cheers,
Roger
____________
Please reply to Newsgroup. Whilst email address is valid, it is seldom
checked.

Roger Mills wrote:
On 09/05/2018 19:42, Paul wrote:
Roger Mills wrote:


I have made *some* progress with FTP. There are two shares on the NAS
- a public one which accepts an anonymous ftp connection, and a
private one which requires a username and password. I can point my
AceFTP PRO client at either of these, and see the folders and files.
That's from within my own network, of course.

I've done a port scan, and found a number of ports open:

22 OpenSSH
110 ?
139 Samba
143 ?
443 OpenSSL
445 Samba (again)
548 Netatalk
993 ?
995 ?

Do any of these look promising as a means of getting remote access to
my files? If so, which ones, and what client software/apps would I
need to use on (a) Windows and (B) Android?

I'm thinking you want to work your network foo on Port 22.

https://serverfault.com/questions/74...-does-sftp-use

"As SFTP runs as a subsystem of SSH it runs on whatever
port the SSH daemon is listening on"

"SFTP transfers all data over the SSH connection.
No additional port is used."

Paul

Thanks. I had come to the same conclusion - and have made *some*
progress using sftp on Port 22, but still have a way to go.

As noted before, when connecting tom the NAS from within my own
network, I can use bog-standard FTP on Port 21. I can access the Private
share on the NAS by supplying the correct username and password, and can
access the Public share by using an anonymous logon.

In order to access the NAS from outside my network (Android tablet using
Android phone-generated hotspot) using sftp, I have told my router to
assign port 22 to the NAS. I can then access the Private share ok, by
supplying the username and password. But I'm stuck with the Public
share. I haven't found any way of using sftp anonymously, so I can't get
in. I've tried several Android sftp client apps - the most promising one
being AndFTP - but to no avail.

Any ideas?

The user manual doesn't hint at any controls being available,
so a Zen-like "it is what it is", is all I can manage as an
answer :-)

If you forward the FTP port... you'll be sorry :-)
So that's not the answer.

Paul

Roger Mills wrote:

On 09/05/2018 19:42, Paul wrote:
Roger Mills wrote:


I have made *some* progress with FTP. There are two shares on the NAS
- a public one which accepts an anonymous ftp connection, and a
private one which requires a username and password. I can point my
AceFTP PRO client at either of these, and see the folders and files.
That's from within my own network, of course.

I've done a port scan, and found a number of ports open:

22 OpenSSH
110 ?
139 Samba
143 ?
443 OpenSSL
445 Samba (again)
548 Netatalk
993 ?
995 ?

Do any of these look promising as a means of getting remote access to
my files? If so, which ones, and what client software/apps would I
need to use on (a) Windows and (B) Android?

I'm thinking you want to work your network foo on Port 22.

https://serverfault.com/questions/74...-does-sftp-use

"As SFTP runs as a subsystem of SSH it runs on whatever
port the SSH daemon is listening on"

"SFTP transfers all data over the SSH connection.
No additional port is used."

Paul

Thanks. I had come to the same conclusion - and have made *some*
progress using sftp on Port 22, but still have a way to go.

As noted before, when connecting tom the NAS from within my own
network, I can use bog-standard FTP on Port 21. I can access the Private
share on the NAS by supplying the correct username and password, and can
access the Public share by using an anonymous logon.

In order to access the NAS from outside my network (Android tablet using
Android phone-generated hotspot) using sftp, I have told my router to
assign port 22 to the NAS. I can then access the Private share ok, by
supplying the username and password. But I'm stuck with the Public
share. I haven't found any way of using sftp anonymously, so I can't get
in. I've tried several Android sftp client apps - the most promising one
being AndFTP - but to no avail.

Any ideas?

I don't know *how* to do it, but I think that you need to set up
smb.conf so that the public share accepts your login credentials as a
synonym for anonymous/guest access. This creates no extra security risk
and I think it only needs a fairly simple user alias statement. But my
memory is hazy.



--

Roger Hayter

On Sat, 12 May 2018 22:47:43 +0100, Roger Mills
wrote:

On 09/05/2018 19:42, Paul wrote:
Roger Mills wrote:


I have made *some* progress with FTP. There are two shares on the NAS
- a public one which accepts an anonymous ftp connection, and a
private one which requires a username and password. I can point my
AceFTP PRO client at either of these, and see the folders and files.
That's from within my own network, of course.

I've done a port scan, and found a number of ports open:

22 OpenSSH
110 ?
139 Samba
143 ?
443 OpenSSL
445 Samba (again)
548 Netatalk
993 ?
995 ?

Do any of these look promising as a means of getting remote access to
my files? If so, which ones, and what client software/apps would I
need to use on (a) Windows and (B) Android?

I'm thinking you want to work your network foo on Port 22.

https://serverfault.com/questions/74...-does-sftp-use

"As SFTP runs as a subsystem of SSH it runs on whatever
port the SSH daemon is listening on"

"SFTP transfers all data over the SSH connection.
No additional port is used."

Paul

Thanks. I had come to the same conclusion - and have made *some*
progress using sftp on Port 22, but still have a way to go.

As noted before, when connecting tom the NAS from within my own
network, I can use bog-standard FTP on Port 21. I can access the Private
share on the NAS by supplying the correct username and password, and can
access the Public share by using an anonymous logon.

As you noted, FTP includes the concept of anonymous login. However, SFTP
(which is part of the SSH suite) has no such thing as anonymous login.
With SSH (and of course SFTP), all access starts with properly logging
into a specific account.

There are workarounds, usually involving replacing a security module on
the SSH server so that all logins, no matter what, are allowed, but that
would be a security hole of large proportions.

In order to access the NAS from outside my network (Android tablet using
Android phone-generated hotspot) using sftp, I have told my router to
assign port 22 to the NAS. I can then access the Private share ok, by
supplying the username and password. But I'm stuck with the Public
share. I haven't found any way of using sftp anonymously, so I can't get
in. I've tried several Android sftp client apps - the most promising one
being AndFTP - but to no avail.

Any ideas?

I would say you should create or use a 'private' account on the NAS as
if it were public, meaning just share the password for that account and
put the public stuff there.

--

Char Jackson

On 12/05/2018 22:47, Roger Mills wrote:


Any ideas?

Get a pi zero w and setup a VPN so your NAS appears as a local devices
when you log in from the internet.

You can set the firewall to only allow access to the NAS if you want.

They cost about £17 with a PSU.

You could even put your NAS disk in a USB case and use the pi as a NAS
server if speed isn't a problem.

On 13/05/2018 09:25, dennis@home wrote:
On 12/05/2018 22:47, Roger Mills wrote:


Any ideas?

Get a pi zero w and setup a VPN so your NAS appears as a local devices
when you log in from the internet.

You can set the firewall to only allow access to the NAS if you want.

They cost about £17 with a PSU.

You could even put your NAS disk in a USB case and use the pi as a NAS
server if speed isn't a problem.

Many routers have built in VPN servers - and for that matter can share a
USB HDD over the network. The Pi may not be needed at all.

SteveW

On 13/05/2018 13:57, Steve Walker wrote:
On 13/05/2018 09:25, dennis@home wrote:
On 12/05/2018 22:47, Roger Mills wrote:


Any ideas?

Get a pi zero w and setup a VPN so your NAS appears as a local devices
when you log in from the internet.

You can set the firewall to only allow access to the NAS if you want.

They cost about £17 with a PSU.

You could even put your NAS disk in a USB case and use the pi as a NAS
server if speed isn't a problem.

Many routers have built in VPN servers - and for that matter can share a
USB HDD over the network. The Pi may not be needed at all.

SteveW

Most routers are full of bugs and security holes so I wouldn't trust
them. What was the last time you got a security fix for your router?

On 13/05/2018 21:05, dennis@home wrote:
On 13/05/2018 13:57, Steve Walker wrote:
On 13/05/2018 09:25, dennis@home wrote:
On 12/05/2018 22:47, Roger Mills wrote:


Any ideas?

Get a pi zero w and setup a VPN so your NAS appears as a local
devices when you log in from the internet.

You can set the firewall to only allow access to the NAS if you want.

They cost about £17 with a PSU.

You could even put your NAS disk in a USB case and use the pi as a
NAS server if speed isn't a problem.

Many routers have built in VPN servers - and for that matter can share
a USB HDD over the network. The Pi may not be needed at all.

SteveW

Most routers are full of bugs and security holes so I wouldn't trust
them. What was the last time you got a security fix for your router?

I've had 3 updates to its firmware in the last 2 years.

SteveW

On Sunday, 6 May 2018 17:14:17 UTC+1, Roger Mills wrote:
I have had a Seagate Central NAS system for several years - and use it
for backing up some of the PCs on my network and also for occasional
remote access to my media files when away from home - mainly using the
Tappin app on mobile devices.

I have recently discovered that Seagate stopped supporting remote
access, and turned off the Tappin app in early April.

I guess that a number of readers of these NGs must be affected by this,
and wondered whether anyone has found a solution - other than using
cloud storage. I simply want to be able to access the files stored on
my NAS remotely without needing to leave any computers running when I'm
away from home. Any suggestions?
--
Cheers,
Roger


Put them on Emails addressed to yourself.

On 03/03/2019 15:15, wrote:
If anyone is still interested, I have some insight with this Seagate problem.

I had the same issues so figured its ok to stream my media onto my Roku, but the Seagate app is just horrible to use. Bare with me this is relevant.. after more digging I found a thread explaining how the newer firmware's we are advised to install have a disabled second DNLA media app for the NAS. I flashed it back to an earlier version without losing data and now have a full on version of Twonky 7.2.8. I used port forwarding on my router to make the external access functional. Also I opened up the SMB functions and FTP access and a now have a very controllable media server that makes that seagate app look pathetic. My ISP assigns my internet service with a dynamic IP which changes now and again. I have used this service (free) https://www.noip.com/free which would work with a VPN as mentioned by Roger. I'm not wanting to pay for a business package, just to obtain a static IP, so this takes care of that little annoyance.

Depending upon your ISP, a static address may be possible and can be cheap.

I used to use Dyn-DNS when I was with SKY, but on moving to Plusnet, a
static IP address cost only £5 to set up and with no monthly fees
afterwards. It simplifies some things a little. It is worth checking
what your ISP can provide.

SteveW

On 24/05/2019 08:42, Steve Walker wrote:
On 03/03/2019 15:15, wrote:
If anyone is still interested, I have some insight with this Seagate
problem.

I had the same issues so figured its ok to stream my media onto my
Roku, but the Seagate app is just horrible to use.Â* Bare with me this
is relevant..Â* after more digging I found a thread explaining how the
newer firmware's we are advised to install have a disabled second DNLA
media app for the NAS.Â* I flashed it back to an earlier version
without losing data and now have a full on version of Twonky 7.2.8.Â* I
used port forwarding on my router to make the external access
functional. Also I opened up the SMB functions and FTP access and a
now have a very controllable media server that makes that seagate app
look pathetic.Â* My ISP assigns my internet service with a dynamic IP
which changes now and again.Â*Â*Â*Â* I have used this service (free)
https://www.noip.com/free which would work with a VPN as mentioned by
Roger.Â* I'm not wanting to pay for a business package, just to obtain
a static IP, so this takes care of that little annoyance.

Depending upon your ISP, a static address may be possible and can be cheap.

I used to use Dyn-DNS when I was with SKY, but on moving to Plusnet, a
static IP address cost only £5 to set up and with no monthly fees
afterwards. It simplifies some things a little. It is worth checking
what your ISP can provide.

SteveW

IDNET provide one for free.

Since te defualt is 'router always on' with most people it seems strange
that the likes of Plusnet charge. It costs them nothing.



--
Ideas are more powerful than guns. We would not let our enemies have
guns, why should we let them have ideas?

Josef Stalin

On 24/05/2019 09:30, The Natural Philosopher wrote:
On 24/05/2019 08:42, Steve Walker wrote:
On 03/03/2019 15:15, wrote:
If anyone is still interested, I have some insight with this Seagate
problem.

I had the same issues so figured its ok to stream my media onto my
Roku, but the Seagate app is just horrible to use.Â* Bare with me this
is relevant..Â* after more digging I found a thread explaining how the
newer firmware's we are advised to install have a disabled second
DNLA media app for the NAS.Â* I flashed it back to an earlier version
without losing data and now have a full on version of Twonky 7.2.8.
I used port forwarding on my router to make the external access
functional. Also I opened up the SMB functions and FTP access and a
now have a very controllable media server that makes that seagate app
look pathetic.Â* My ISP assigns my internet service with a dynamic IP
which changes now and again.Â*Â*Â*Â* I have used this service (free)
https://www.noip.com/free which would work with a VPN as mentioned by
Roger.Â* I'm not wanting to pay for a business package, just to obtain
a static IP, so this takes care of that little annoyance.

Depending upon your ISP, a static address may be possible and can be
cheap.

I used to use Dyn-DNS when I was with SKY, but on moving to Plusnet, a
static IP address cost only £5 to set up and with no monthly fees
afterwards. It simplifies some things a little. It is worth checking
what your ISP can provide.

SteveW

IDNET provide one for free.

Since te defualt is 'router always on' with most people it seems strange
that the likes of Plusnet charge. It costs them nothing.

Maybe charges will be dropped as we move to IPv6. At the moment there is
a shortage of IPv4 addresses and it may be that ISPs don't want everyone
to move to static addresses, as it would restrict their ability to
change allocations and re-organise as and when they need to without
causing disruption.

SteveW

The Linux versión of the Seagate Central NAS is MontaVista Linux, is an embedded linux.

El domingo, 6 de mayo de 2018, 12:48:06 (UTC-5), Chris Green escribió:
Roger Mills wrote:
I have had a Seagate Central NAS system for several years - and use it
for backing up some of the PCs on my network and also for occasional
remote access to my media files when away from home - mainly using the
Tappin app on mobile devices.

I have recently discovered that Seagate stopped supporting remote
access, and turned off the Tappin app in early April.

I guess that a number of readers of these NGs must be affected by this,
and wondered whether anyone has found a solution - other than using
cloud storage. I simply want to be able to access the files stored on
my NAS remotely without needing to leave any computers running when I'm
away from home. Any suggestions?

Well you could have something like a Raspberry PI left on permanently
to give you access, very little power, no fan or anything.

I'm not sure what OS a 'Seagate Central NAS' runs but if it's Linux
(almost certainly) then you can probably get at it via that somehow.

--
Chris Green
·

On 16/10/2019 02:59, wrote:
Can I trouble someone to make a detailed list on how to gain remote
FTP access on the Seagate Central? I thought I set up everything
right, but I can only access the Seagate from within my network.
Once a try it while I'm outsite, the connection times out. I'm using
my external IP address when trying to connect but it's not working.
I do have a DNS host name from noip.com as well, but how do I set
this up on the Seagate Central?

What you need to do is to set up 'port redirection' or 'passthrough' on
your router so that ftp access requests to your external address is
redirected to the internal address of the seagate.



Any help would be greatly appreciated as this is somewhat urgent.

Thanks! Nikki

I would point out that FTP uses two ports so you may need to redirect
port 20 as well as port 21.

Also FTP is just secured by a username+password sent in plain text
across the Internet.

If the seagate will accept sftp that is definitely preferred.

That runs on the ssh port of 22.



--
Gun Control: The law that ensures that only criminals have guns.

Thanks so much for the reply. I forgot to mention that I already set up port forwarding to 22. the error I'm getting in Filezilla is "Connection Refused" when I try to connect remotely. Do you know what I may be doing wrong?

On Wednesday, 16 October 2019 07:07:51 UTC-4, The Natural Philosopher wrote:
On 16/10/2019 02:59, wrote:
Can I trouble someone to make a detailed list on how to gain remote
FTP access on the Seagate Central? I thought I set up everything
right, but I can only access the Seagate from within my network.
Once a try it while I'm outsite, the connection times out. I'm using
my external IP address when trying to connect but it's not working.
I do have a DNS host name from noip.com as well, but how do I set
this up on the Seagate Central?

What you need to do is to set up 'port redirection' or 'passthrough' on
your router so that ftp access requests to your external address is
redirected to the internal address of the seagate.



Any help would be greatly appreciated as this is somewhat urgent.

Thanks! Nikki

I would point out that FTP uses two ports so you may need to redirect
port 20 as well as port 21.

Also FTP is just secured by a username+password sent in plain text
across the Internet.

If the seagate will accept sftp that is definitely preferred.

That runs on the ssh port of 22.



--
Gun Control: The law that ensures that only criminals have guns.

On 16/10/2019 13:30, wrote:
Thanks so much for the reply. I forgot to mention that I already set up port forwarding to 22. the error I'm getting in Filezilla is "Connection Refused" when I try to connect remotely. Do you know what I may be doing wrong?


Make sure that the username and password are correct. Being UNIX, case
probably matters!

I found that I needed to use Port 443 rather than 22. Try telling your
router to forward 443 to the NAS, and then tell FileZilla to use Port 443.

I'm pretty sure that's what I did. I was planning to verify it before
replying but my NAS - having been on the blink for a long time - has
finally died, and refuses to talk to me - even locally. And all attempts
to recover its data by removing its disk and connecting it directly to
my computer have failed. Fortunately there was nothing important on it
which I hadn't already copied to another drive when it first went on the
blink.

I don't know whether other manufacturers' NAS drives are any good, but
my whole experience with this Seagate drive is that it's a pain in the arse!
--
Cheers,
Roger
____________
Please reply to Newsgroup. Whilst email address is valid, it is seldom
checked.

On 20/10/2019 10:52, Roger Mills wrote:
On 16/10/2019 13:30, wrote:
Thanks so much for the reply. I forgot to mention that I already set
up port forwarding to 22. the error I'm getting in Filezilla is
"Connection Refused" when I try to connect remotely. Do you know what
I may be doing wrong?


Make sure that the username and password are correct. Being UNIX, case
probably matters!

I found that I needed to use Port 443 rather than 22. Try telling your
router to forward 443 to the NAS, and then tell FileZilla to use Port 443.

FTP uses port 21 and 22

I'm pretty sure that's what I did. I was planning to verify it before
replying but my NAS - having been on the blink for a long time - has
finally died, and refuses to talk to me - even locally. And all attempts
to recover its data by removing its disk and connecting it directly to
my computer have failed. Fortunately there was nothing important on it
which I hadn't already copied to another drive when it first went on the
blink.

I don't know whether other manufacturers' NAS drives are any good, but
my whole experience with this Seagate drive is that it's a pain in the
arse!


--
Any fool can believe in principles - and most of them do!

On Sun, 20 Oct 2019 11:35:51 +0100, The Natural Philosopher wrote:

FTP uses port 21 and 22

No, it doesn't.

--
My posts are my copyright and if @diy_forums or Home Owners' Hub
wish to copy them they can pay me £1 a message.
Use the BIG mirror service in the UK: http://www.mirrorservice.org
*lightning surge protection* - a w_tom conductor

On 20/10/2019 12:50, Bob Eager wrote:
On Sun, 20 Oct 2019 11:35:51 +0100, The Natural Philosopher wrote:

FTP uses port 21 and 22

No, it doesn't.

My bad. 20 and 21..


--
New Socialism consists essentially in being seen to have your heart in
the right place whilst your head is in the clouds and your hand is in
someone else's pocket.

The Natural Philosopher wrote:

On 20/10/2019 12:50, Bob Eager wrote:
On Sun, 20 Oct 2019 11:35:51 +0100, The Natural Philosopher wrote:

FTP uses port 21 and 22

No, it doesn't.

My bad. 20 and 21..

And commonly nowadays just port 21, to avoid firewall and NAT problems.
There is presumably a way of telling ftp servers you want this mode.

--

Roger Hayter

On 20/10/2019 14:28, Roger Hayter wrote:
The Natural Philosopher wrote:

On 20/10/2019 12:50, Bob Eager wrote:
On Sun, 20 Oct 2019 11:35:51 +0100, The Natural Philosopher wrote:

FTP uses port 21 and 22

No, it doesn't.

My bad. 20 and 21..

And commonly nowadays just port 21, to avoid firewall and NAT problems.
There is presumably a way of telling ftp servers you want this mode.

No rather there is a smartness in router NAT that understands FTP and
will allow the back channel for data.
Some of them anyway.


--
Climate Change: Socialism wearing a lab coat.

On 20/10/2019 11:35, The Natural Philosopher wrote:
On 20/10/2019 10:52, Roger Mills wrote:
On 16/10/2019 13:30, wrote:
Thanks so much for the reply. I forgot to mention that I already set
up port forwarding to 22. the error I'm getting in Filezilla is
"Connection Refused" when I try to connect remotely. Do you know what
I may be doing wrong?


Make sure that the username and password are correct. Being UNIX, case
probably matters!

I found that I needed to use Port 443 rather than 22. Try telling your
router to forward 443 to the NAS, and then tell FileZilla to use Port
443.

FTP uses port 21 and 22


But I was using SFTP which, AIUI, can use Port 22 or Port 443. I
forwarded both of these to the Seagate NAS, and I'm pretty sure that it
was 443 which worked for remote access.

[As I said in an earlier post, I can't go back to check 'cos my NAS is
now dead]

I know I did a port scan on the NAS at the time in order to see which
ports were open and thus worth investigating.
--
Cheers,
Roger
____________
Please reply to Newsgroup. Whilst email address is valid, it is seldom
checked.