DNS-323 Rev.A1 inaccessible

[Dimitrios G. Panagiotidis]

Hello all, I need help to recover my DNS-323 from being inaccessible over my local home network. Although a scanner will find the box at its old (known) IP address (and even retrieves its MAC address) trying to access using a browser (and typing the IP) gives me the following error:

This site can’t be reached 192.168.1.3 

refused to connect.

Try:

• Checking the connection
• Checking the proxy and the firewall

ERR_CONNECTION_REFUSED 

It all happened when I was using a network scanner utility looking up another host when I noticed that the D-Link's host name instead of the expected 'DNS323' was displayed as DND323 (!?) (e.g. D instead of S so it looks like a typo by me, but never noticed it before). 

So, I plugged its IP address into a browser and successfully accessed the interface and 'Status Page'; opened the Host page but the name was the expected one: DNS323. I was really baffled when I noticed that there is a field "Domain Name" where it said "localnet" which I do not recall setting up myself.

Anyways, since I do not have a domain in my home network, I blanked that entry, clicked submit and expecting the interface would take a minute or two to return, I walked away (bathroom break) when my house experienced a  ~30 +/- sec power outage. Though the box is on a (albeit old) UPS I returned to find it with power off (?!?) Apparently the UPS's battery was too old to sustain aux power (my bad!) so the Alt-F config has been apparently corrupted.

I tried the 3 sec "trick" pushing the R first and then the L button to do a clean restart/shutdown etc., but it did not help. Box will restart, network LED flickers, both drive buttons flash simultaneously once per 2 sec but the box does not respond to its original IP. I'm also assuming the FS is now "dirty" and needs a file check, that is, after I'm able to restore network access to the box. 

What is your advice to recover:

1. Push reset for 10+ sec and try to Telnet to port 29? I will need instructions how to do that: What Telnet client to use and if successfully connected how to restore the proper configuration.

2. Push reset for 20+ sec and then hope the box will receive an IP address from the DHCP server on my router (I have configured the router to always give a specific IP to the box) and then set everything from scratch.

3. Or, maybe there is an easier way?

Thanks so much for your time and help with all this! 

[Dimitrios G. Panagiotidis]

Ok, apparently the port is 26 not 29 and the proper procedure is outlined here:

"How to recover from Lost access after power outage

If the box can be accessed through MS-Windows (Samba/SMB/CIFS), but ftp/ssh/telnet/webUI etc can't be used, then 'inetd' is not being run. Press the back recessed reset button for more than 10 seconds but less than 20 seconds (the two front leds should start flashing twice a second) and you can telnet the box at port 26 as the 'root' without password. Then execute the command 'rcinetd start' and if it starts OK then the webUI should be accessible. Don't forget to "save settings"."

Problem is the box is NOT accessible at all via none of the methods listed above. I guess I should try the 110 sec reset + telnet at port 26 and if that doesn't work then do a complete reset and start from scratch. Hopefully my files are still intact. Please advise, thanks!

==

--
You received this message because you are subscribed to a topic in the Google Groups "Alt-F" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/alt-f/YDGk41KtGpQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to alt-f+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/alt-f/de3991d7-bd93-40c1-8d68-88312c80a8b3n%40googlegroups.com.

[Tom Schmidt]

Since Alt-F is mostly installed in the flash memory of the DNS-323, you could remove your disk drives from the system while it is powered off to proceed with your troubleshooting.  That will prevent any potential for any "new" data corruption on the filesystems on the disk drives.

Tom

You received this message because you are subscribed to the Google Groups "Alt-F" group.
To unsubscribe from this group and stop receiving emails from it, send an email to alt-f+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/alt-f/CALG6-FROjTk8h_DptiYBh1QKmfsm5Jc8PdLHOP9v-mrF89%2BDMA%40mail.gmail.com.

[Dimitrios G. Panagiotidis]

Tom thank you for the quick reply, so what would be your recommended approach: Telnet to Port 26 and run the command to start inetd or do a complete reset? My alt-f had a very simple set up. Of course that assumes that these two methods are the only two available to me at this point, correct?!

--
Dimi Pana

   

To view this discussion visit https://groups.google.com/d/msgid/alt-f/CAP7YgkzbwQ-r0qdcxo_RafD415rd4L0WqkuZt-aBaLzu%3D3_WRw%40mail.gmail.com.