J
jean08
Can you get your HD363N to act as an http web server?
Is there a firmware like Unslung that can do that?
Regards
/JZ
Nedal skrev:
Is there a firmware like Unslung that can do that?
Regards
/JZ
Nedal skrev:
N
Nedal
Alvoo
The last firmware version of the HD363N NAS drive i
121
The last firmware version of the HD363N NAS drive i
121
A
aauldridge
Today I downloaded firmware version 007-0428 from Argosy's Europea
region at http://www.argosy.nl/product/hd363n.htm.
Included with the .bin file is a Word document that lists 20 fixes
I hope this helps... Ala
region at http://www.argosy.nl/product/hd363n.htm.
Included with the .bin file is a Word document that lists 20 fixes
I hope this helps... Ala
D
dilettante
It gets a bit confusing
I suspect the version numbers might be build dates sans year, as i
1216 meaning December 16 and 0428 meaning April 28
My 1216 has a modify date of March 3, 2006 and the 0428 has May 05
2006. Hmm. Maybe that theory is busted
I guess we might conclude this 0428 is "newer" then. Th
version numbers sure throw me though
I wish I had a list of fixes in 1216 for comparison
I suspect the version numbers might be build dates sans year, as i
1216 meaning December 16 and 0428 meaning April 28
My 1216 has a modify date of March 3, 2006 and the 0428 has May 05
2006. Hmm. Maybe that theory is busted
I guess we might conclude this 0428 is "newer" then. Th
version numbers sure throw me though
I wish I had a list of fixes in 1216 for comparison
F
fixuser
To keep track of which is the most recent firmware release, you shoul
also consider the digit(s) before the date code. Below shows th
sequence of firmware releases that I'm aware of
2005
02-021
03-031
04-031
05-060
06-101
06-121
2006
07-042
Why two 06 versions were released I have no idea
Tritton was doing a pretty good job of tracking firmware histor
(LINK
but they have appeared to stop at 06-1013
also consider the digit(s) before the date code. Below shows th
sequence of firmware releases that I'm aware of
2005
02-021
03-031
04-031
05-060
06-101
06-121
2006
07-042
Why two 06 versions were released I have no idea
Tritton was doing a pretty good job of tracking firmware histor
(LINK
but they have appeared to stop at 06-1013
Q
Quest
if someone has bricked his vgear or bytecc landisk with a ba
firmware. contact me, i can help
if you got a bricked argosy, tritton, fujitsu etc. nas, i might b
able to help as well, but i'm not 100% shure
best regard
Ques
firmware. contact me, i can help
if you got a bricked argosy, tritton, fujitsu etc. nas, i might b
able to help as well, but i'm not 100% shure
best regard
Ques
H
Horst Franke
Q
Quest
Horst Frankewrote
i'm not shure if your dumb or something else, but i'm not advertisin
anything, i'm offering help at no cost
best regard
Ques
i'm not shure if your dumb or something else, but i'm not advertisin
anything, i'm offering help at no cost
best regard
Ques
A
anonymous_user
I have a Tritton nss001. I can not connect to it. I have trie
connecting it directly to a mac and to windows xp. I have trie
connecting it to the switch built into my router and then accessin
it from a mac and win xp. No luck with any of this. If I attach i
to the switch built into my router and then reset the device, I se
the ip address 192.168.1.113 is reserved for 60 seconds. Of course
can not ping the address and after 60 seconds it disappers from m
dhcp clients table and nothing else shows up. I tried the default i
address of 169.254.0.1 provided in the documentation and also a fe
other ip addresses that I found in this forum. Does anyone have an
ideas on what else to try? I am very close to putting this thing i
the garbage
connecting it directly to a mac and to windows xp. I have trie
connecting it to the switch built into my router and then accessin
it from a mac and win xp. No luck with any of this. If I attach i
to the switch built into my router and then reset the device, I se
the ip address 192.168.1.113 is reserved for 60 seconds. Of course
can not ping the address and after 60 seconds it disappers from m
dhcp clients table and nothing else shows up. I tried the default i
address of 169.254.0.1 provided in the documentation and also a fe
other ip addresses that I found in this forum. Does anyone have an
ideas on what else to try? I am very close to putting this thing i
the garbage
H
home_user
I have the INOI NDD version with firmware 04-0317, and this is what
did to connect just yesterday. First, connect directly to your PC'
ethernet port. Be sure to turn off any firewalls, antispyware, o
antivirus applications. Then, change the TCP/IP properties t
disable DHCP on the PC's ethernet adapter. Assign a static IP in th
same subnet as the HD363N, such as 169.254.0.2, open a command windo
and try pinging 169.254.0.1. If you don't get a reply, reset the NA
by holding in the power switch for 30 seconds, until the LED stop
flashing. After I did this, I was able to login to http://storage
and setup the NAS, format the hard drive, and view the drive i
windows explorer. Next step for me is to connect to m
router/switch, and configure it to allow access to the HD363N. Then
I have to configure my firewall and other applications to allo
access. Good luck
did to connect just yesterday. First, connect directly to your PC'
ethernet port. Be sure to turn off any firewalls, antispyware, o
antivirus applications. Then, change the TCP/IP properties t
disable DHCP on the PC's ethernet adapter. Assign a static IP in th
same subnet as the HD363N, such as 169.254.0.2, open a command windo
and try pinging 169.254.0.1. If you don't get a reply, reset the NA
by holding in the power switch for 30 seconds, until the LED stop
flashing. After I did this, I was able to login to http://storage
and setup the NAS, format the hard drive, and view the drive i
windows explorer. Next step for me is to connect to m
router/switch, and configure it to allow access to the HD363N. Then
I have to configure my firewall and other applications to allo
access. Good luck
Q
Quest
if the instruction from home_user should not bring you success, yo
might want to youse a network security analysing tool like cain, t
search for your device
best regard
Ques
might want to youse a network security analysing tool like cain, t
search for your device
best regard
Ques
H
Horst Franke
In news:[email protected] Quest typed:
Ok and then You post things like
referencing "gain" without any further link ;-(
What type of help should this be?
No one would be able to use it without references/links!
Horst
Ok and then You post things like
referencing "gain" without any further link ;-(
What type of help should this be?
No one would be able to use it without references/links!
Horst
Q
Quest
@hors
how about a flash dumb of the bios chip and detailed instructions o
how to reflash the chip using a computer mainboard :-
Ques
how about a flash dumb of the bios chip and detailed instructions o
how to reflash the chip using a computer mainboard :-
Ques
H
Horst Franke
In news:[email protected] Quest typed:
Hi quest, don't understand.
Any BIOS provider I know provides flash update instructions.
And most of the time these will also be presented via
the mainboard homepages.
Horst
how about a flash dumb of the bios chip and detailed instructions on
how to reflash the chip using a computer mainboard
Hi quest, don't understand.
Any BIOS provider I know provides flash update instructions.
And most of the time these will also be presented via
the mainboard homepages.
Horst
A
agfa
Here is what I did after corupting my Storagebird Lan (=Tritton NSS001 =anonymous_user said:
ArgoSy HD363N):
connect it direcly to a PC with fixed IP e.g. 169.254.0.2 (and Subnet 255.255.
0.0)
Try to Ping to 169.254.0.1 (i.e. the NAS). At least this should work. Then I
did a portscan, found an open UDP port and tried a "TFP -i 169.254.0.1 PUT
<firmware.bin>". After waiting a minute or so, I powercycled the NAS and the
web user Interface was accessible again.
agfa
A
agfa
this should be "TFTP -i 169 ...."agfa said:
agfa
D
Dave_M
I recently purchased one of these boxes and loaded a WD250 in it.
After a little difficulty I was able to get it found on my LAN.
But for some reason, I (nor anyone else) can access the box thru FTP.
Get the login screen but it times out.
My ISP (Comcast) says that there are no blocking issues.
Is it the box or FTP?
After a little difficulty I was able to get it found on my LAN.
But for some reason, I (nor anyone else) can access the box thru FTP.
Get the login screen but it times out.
My ISP (Comcast) says that there are no blocking issues.
Is it the box or FTP?
Q
Quest
did you try active FTP ?
D
Dave_M
Uhh, no. All I have used is what is on the NAS box.
It was suggested that I run a FTP client on one of my machines and map
to the NAS box, but that is not what I bought this box for, so that I
could access and share files without having to run computers 24/7.
Can an FTP client be loaded and run on the Argosy box? Or does it just
have a file system with no real OS?
What is "active FTP?"
It was suggested that I run a FTP client on one of my machines and map
to the NAS box, but that is not what I bought this box for, so that I
could access and share files without having to run computers 24/7.
Can an FTP client be loaded and run on the Argosy box? Or does it just
have a file system with no real OS?
What is "active FTP?"
Q
Quest
allmost all ftp clients can use the passive or the active mode.
most ftp clients use the passive mode as default.
this site explains the differences:
http://slacksite.com/other/ftp.html
if you don't want to read all the explanations, here a short version:
if your ftp server has a private ip address, passive ftp does not
work, unless your ftp server is smart enough to tell the client the
public ip.
best regards
Quest
most ftp clients use the passive mode as default.
this site explains the differences:
http://slacksite.com/other/ftp.html
if you don't want to read all the explanations, here a short version:
if your ftp server has a private ip address, passive ftp does not
work, unless your ftp server is smart enough to tell the client the
public ip.
best regards
Quest