• February 25, 2025, 10:07:13 AM
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

This Forum Beta is ONLY for registered owners of D-Link products in the USA for which we have created boards at this time.

Author Topic: Cannot access via putty (fun_plug -installation)  (Read 12902 times)

Nigge

  • Level 1 Member
  • *
  • Posts: 12
Cannot access via putty (fun_plug -installation)
« on: November 28, 2012, 12:36:49 AM »

Hi!

I tried to install funplug on my DNS-320.
I downloaded the two files from a tutorial and put them in the root of the NAS.
and rebooted it. The files were extracted correctly it seems.
But when I try to log in using putty nothing happens.
My ip of the NAS is 192.168.1.19
So in putty i enter that IP and select telnet and port 23.
and then open... the putty command window opens, but nothing happens... and after about 10 seconds putty closes...

What am I doing wrong?...
Logged

albert

  • Level 5 Member
  • *****
  • Posts: 510
    • SoHo NAS Forum
Re: Cannot access via putty (fun_plug -installation)
« Reply #1 on: November 28, 2012, 05:37:23 AM »

Check ffp.log for clue.

BTW, did you telnet in only after all the LED light activity have stopped?
Logged
D-Link DNS-320 rev A1 (FW: 2.05) [FFP-0.7]
PCI NAS-01G (FW: Encore ENNHD-1000 4.10)
PCI NAS-01G (FW: OpenNAS 1.9]

Nigge

  • Level 1 Member
  • *
  • Posts: 12
Re: Cannot access via putty (fun_plug -installation)
« Reply #2 on: November 28, 2012, 05:42:18 AM »

Yes I waited for about an hour the second time I tried...

I will attach the log file as soon as I get home
Logged

Nigge

  • Level 1 Member
  • *
  • Posts: 12
Re: Cannot access via putty (fun_plug -installation)
« Reply #3 on: November 28, 2012, 05:51:43 AM »

Ok I got hold of the log file via FTP... here it is:
Code: [Select]
**** fun_plug script for DNS-323 (2008-08-11 tp@fonz.de) ****
**** fun_plug script modded by Uli (2012-02-21 ffp@wolf-u.li) ****
Tue Nov 27 19:06:02 CET 2012
ln -snf /mnt/HD/HD_a2/ffp /ffp
* Installing /mnt/HD/HD_a2/fun_plug.tgz ...
* OK
* Running /ffp/etc/fun_plug.init ...
* Running /ffp/etc/rc ...
* /ffp/start/SERVERS.sh inactive
* /ffp/start/portmap.sh inactive
* /ffp/start/nfsd.sh inactive
* /ffp/start/LOGIN.sh inactive
* /ffp/start/telnetd.sh ...
Starting /ffp/sbin/telnetd -l /ffp/bin/sh
* /ffp/start/sshd.sh inactive
* /ffp/start/rsyncd.sh inactive
* /ffp/start/kickwebs.sh inactive
* /ffp/start/lighttpd.sh inactive
* /ffp/start/inetd.sh inactive
* /ffp/start/fp_master.sh inactive
*  OK
**** fun_plug script for DNS-323 (2008-08-11 tp@fonz.de) ****
**** fun_plug script modded by Uli (2012-02-21 ffp@wolf-u.li) ****
Tue Nov 27 19:13:54 CET 2012
ln -snf /mnt/HD/HD_a2/ffp /ffp
* Installing /mnt/HD/HD_a2/fun_plug.tgz ...
* OK
* Running /ffp/etc/fun_plug.init ...
* Running /ffp/etc/rc ...
* /ffp/start/SERVERS.sh inactive
* /ffp/start/portmap.sh inactive
* /ffp/start/nfsd.sh inactive
* /ffp/start/LOGIN.sh inactive
* /ffp/start/telnetd.sh ...
Starting /ffp/sbin/telnetd -l /ffp/bin/sh
* /ffp/start/sshd.sh inactive
* /ffp/start/rsyncd.sh inactive
* /ffp/start/kickwebs.sh inactive
* /ffp/start/lighttpd.sh inactive
* /ffp/start/inetd.sh inactive
* /ffp/start/fp_master.sh inactive
*  OK
**** fun_plug script for DNS-323 (2008-08-11 tp@fonz.de) ****
**** fun_plug script modded by Uli (2012-02-21 ffp@wolf-u.li) ****
Tue Nov 27 19:28:06 CET 2012
ln -snf /mnt/HD/HD_a2/ffp /ffp
* Running /ffp/etc/fun_plug.init ...
* Running /ffp/etc/rc ...
* /ffp/start/SERVERS.sh inactive
* /ffp/start/portmap.sh inactive
* /ffp/start/nfsd.sh inactive
* /ffp/start/LOGIN.sh inactive
* /ffp/start/telnetd.sh ...
Starting /ffp/sbin/telnetd -l /ffp/bin/sh
* /ffp/start/sshd.sh inactive
* /ffp/start/rsyncd.sh inactive
* /ffp/start/kickwebs.sh inactive
* /ffp/start/lighttpd.sh inactive
* /ffp/start/inetd.sh inactive
* /ffp/start/fp_master.sh inactive
*  OK
**** fun_plug script for DNS-323 (2008-08-11 tp@fonz.de) ****
Tue Nov 27 19:53:45 CET 2012
ln -snf /mnt/HD/HD_a2/ffp /ffp
* Installing /mnt/HD/HD_a2/fun_plug.tgz ...
* OK
* Running /ffp/etc/fun_plug.init ...
* Running /ffp/etc/rc ...
* /ffp/start/syslogd.sh inactive
* /ffp/start/SERVERS.sh inactive
* /ffp/start/portmap.sh inactive
* /ffp/start/unfsd.sh inactive
* /ffp/start/nfsd.sh inactive
* /ffp/start/ntpd.sh inactive
* /ffp/start/LOGIN.sh inactive
* /ffp/start/telnetd.sh ...
Starting /ffp/sbin/telnetd -l /ffp/bin/sh
* /ffp/start/sshd.sh inactive
* /ffp/start/rsyncd.sh inactive
* /ffp/start/mediatomb.sh inactive
* /ffp/start/kickwebs.sh inactive
* /ffp/start/lighttpd.sh inactive
* /ffp/start/inetd.sh inactive
* /ffp/start/fp_master.sh inactive
*  OK
Logged

albert

  • Level 5 Member
  • *****
  • Posts: 510
    • SoHo NAS Forum
Re: Cannot access via putty (fun_plug -installation)
« Reply #4 on: November 28, 2012, 06:46:47 AM »

Looking at the log, it appear that the installation keep repeating itself. Use Windows Explorer on Volume_1 and check if the file - fun_plug.tgz is no longer there.
Logged
D-Link DNS-320 rev A1 (FW: 2.05) [FFP-0.7]
PCI NAS-01G (FW: Encore ENNHD-1000 4.10)
PCI NAS-01G (FW: OpenNAS 1.9]

Nigge

  • Level 1 Member
  • *
  • Posts: 12
Re: Cannot access via putty (fun_plug -installation)
« Reply #5 on: November 28, 2012, 06:54:04 AM »

I just checked, there is nog tgz file present in the root
Logged

albert

  • Level 5 Member
  • *****
  • Posts: 510
    • SoHo NAS Forum
Re: Cannot access via putty (fun_plug -installation)
« Reply #6 on: November 28, 2012, 07:57:43 AM »

Just to check, I assumed you're accessing it within your LAN not WAN (Internet).
Logged
D-Link DNS-320 rev A1 (FW: 2.05) [FFP-0.7]
PCI NAS-01G (FW: Encore ENNHD-1000 4.10)
PCI NAS-01G (FW: OpenNAS 1.9]

Nigge

  • Level 1 Member
  • *
  • Posts: 12
Re: Cannot access via putty (fun_plug -installation)
« Reply #7 on: November 28, 2012, 09:14:11 AM »

Just to check, I assumed you're accessing it within your LAN not WAN (Internet).

Yes, inside the LAN (of course  ;) )
Logged

Nigge

  • Level 1 Member
  • *
  • Posts: 12
Re: Cannot access via putty (fun_plug -installation)
« Reply #8 on: November 28, 2012, 11:27:47 PM »

Ok, lets update this...

I made a mistake;-) there wasnt really a problem...
I was so used to using 192.168.1.xxx as local IP since we do that at work...
But at home I use 192.168.0.xxx...

So I just tried to connect via putty to an invalid ip-adress...

Problem solved, many thanks for your help:)


Logged