ARGOSY - HD363N - Network Storage

Peterwrote:
[quote:9898ef263c]I had tried 2-3 different ports 8004, 1150,
1250...all with the same
result it connects but just doesn't display the folders. Is there
a
better port selection higher in the range, I have the firewall open
on the router (Linkysys) so there shouldn't be any problems or
interference there and like I said when I switch back to the
standard
port 21 it works.

Did you look in a firewall log on your router?[/quote:9898ef263c]

No what would I be looking for exactly, i'm farily new to this area of
networking so most of this is pretty new...any input is appreciated.

Did you look in a firewall log on your router?

No what would I be looking for exactly, i'm farily new to this area of
networking so most of this is pretty new...any input is appreciated.

What port activity got blocked at the exact time you were trying to use FTP.

The Argosy 006-1216 firmware appears to fix the SET-EOF file problem
previously discussed.
I have tried the test procedure that I previously posted with both W98
and W2k, and it no longer leaves the extra lines at the end of the
file with either OS.

Wahoo

segbertwrote:
The Argosy 006-1216 firmware appears to fix the SET-EOF file problem
previously discussed.
I have tried the test procedure that I previously posted with both
W98 and W2k, and it no longer leaves the extra lines at the end of
the file with either OS.

Wahoo

So where do you get the -1216 firmware from, as I can opnly see -1013
on the website.

Mark

ukcobrawrote:

So where do you get the -1216 firmware from, as I can opnly see
-1013 on the website.


Five posts before this one, on the bottom of page 18, Quest posted the
link to get the 006-1216 firmware from Argosy's Tiwan website

BigCity2:

What firmware is your HD363N using?
If I remember right there was a problem with earlier firmware not
properly handling changing the FTP port from 21. If it is not
already, you should upgrade to at least 006-1013 and see if you still
have your ftp problem. I cannot get Firefox to upgrade the firmware
properly, although others report no problems, but IE has always
worked for me. There is also brand new firmware, 006-1216, available.
See previous posts for links to it.

Ok, I uploaded the new firmware and tried ftp-ing to the HDD and I
still cannot log on to it on any other port than 21. I triead port
50,000 forwarded the range of 49000-52000 w/ TCP protocol and it
never logs in. But like I said I switch it to the standard FTP port
21 and it works fine. Is there a setting on the router i'm missing
for using the other port? The router log shows the IP and the
destination port but nothing other than that.

OK, mine works OK with a different FTP port, but I am not going
through a router.
I would suggest that temporarily you put the NAS on the same subnet as
the PC with the FTP client, so you don't have to go through a router
to get to it.

I am using 006-1216 firmware, and WSftp
I have it configured for a fixed IP address.
I went into FTP Service in the administration console.
I checked Enable under FTP server, and left the port at 21 to start
with, then did [Apply].
I clicked the [Add Account] button, entered the account name, and
clicked [Add]
I selected the new account from the list, and clicked [Modify
Account]
I entered the password, checked Enable and Read Only and hit [Modify]
I moved some shares from the right hand column to the left by
selecting them and pressing [-Add]

I created a profile on WsFTP, using the numeric IP address, the
account name, and password, and it logged in and I browsed some
files.

I went to the FTP Service page of the admin console and changed the
port to 4000, and hit [Apply]

WSftp would not log in with port 21. I changed WSftp to port 4000
under the advanced tab of the profile, logged in, and browsed some
files just fine.

Then I went to write this up, and was bopping back and forth between
the admin console pages and dialogs. Somehow I locked it up. I could
not log in through ftp. When I went in through the network share,
all my files were missing. Reset through the admin console did
nothing. I thought I'd flushed all my files. Removing power from the
NAS box and powering it back up restored things to normal. Therefore,
when you have changed the port and cannot get in, try removing the
power and restoring it and see if that helps.

You should get it working first using the desired alternate port and a
fixed IP with the NAS on the same subnet as the ftp client. Only then
place it where you have to go through the router to get to it, and
you will know that any configuration problems are in the router.

segbertwrote:
OK, mine works OK with a different FTP port, but I am not going
through a router.
I would suggest that temporarily you put the NAS on the same subnet
as the PC with the FTP client, so you don't have to go through a
router to get to it.

I am using 006-1216 firmware, and WSftp
I have it configured for a fixed IP address.
I went into FTP Service in the administration console.
I checked Enable under FTP server, and left the port at 21 to start
with, then did [Apply].
I clicked the [Add Account] button, entered the account name, and
clicked [Add]
I selected the new account from the list, and clicked [Modify
Account]
I entered the password, checked Enable and Read Only and hit
[Modify]
I moved some shares from the right hand column to the left by
selecting them and pressing [-Add]

I created a profile on WsFTP, using the numeric IP address, the
account name, and password, and it logged in and I browsed some
files.

I went to the FTP Service page of the admin console and changed the
port to 4000, and hit [Apply]

WSftp would not log in with port 21. I changed WSftp to port 4000
under the advanced tab of the profile, logged in, and browsed some
files just fine.

Then I went to write this up, and was bopping back and forth between
the admin console pages and dialogs. Somehow I locked it up. I could
not log in through ftp. When I went in through the network share,
all my files were missing. Reset through the admin console did
nothing. I thought I'd flushed all my files. Removing power from the
NAS box and powering it back up restored things to normal. Therefore,
when you have changed the port and cannot get in, try removing the
power and restoring it and see if that helps.

You should get it working first using the desired alternate port and
a fixed IP with the NAS on the same subnet as the ftp client. Only
then place it where you have to go through the router to get to it,
and you will know that any configuration problems are in the router.

I've done everything exactly as you said before with the exception of
doing the hard reboot so I'll give that a shot tonight as well. Can
you connect to the FTP from an outside line like from work or a
friends house? Reason I ask is that I can sit there on my couch and
connect using the outside IP address just fine on any port, but when
I try it from work or have a couple of my buddies try from Indiana or
North Carolina they are unable to "fully" connect. I say
that b/c it will appear that you can log in but then it never
displays the folder directory to upload/download files....

I've done everything exactly as you said before with the exception of
doing the hard reboot so I'll give that a shot tonight as well. Can
you connect to the FTP from an outside line like from work or a
friends house? Reason I ask is that I can sit there on my couch and
connect using the outside IP address just fine on any port,

This needs clarification. You connect to ftp box using outside IP?
What is an "outside IP"? Public IP of your router?
What's your network setup? Is it:
internet - cable/dsl modem - router - local network devices
so IP's a
internet - router Public IP - router Private IP - (FTP box IP; PC IP)

Therefore you probably meant that from PC IP you have connected
susscessfully using "router Public IP:FTP port"?
That's not a valid test. You need someone with internet Public IP try to
access "router Public IP:FTP port". Not from your local network.

but when
I try it from work or have a couple of my buddies try from Indiana or
North Carolina they are unable to "fully" connect. I say
that b/c it will appear that you can log in but then it never
displays the folder directory to upload/download files....