Can't connect to spd8020 at all

[p.v.solar]

I have a small home network with three computers, a printer and the spd 8020 NAS. Everything works fine and there is no problem reading and writing to the NAS. Now I want to change the settings to make upnp possible. When using the "manage" function I cannot get access to the control. The response from firefox or explorer is "can not connect". so the usual request for name and password does not appear. Using a lanviewer everything is visible, including ip address and mac address of the NAS. Pinging shows no problem. Approching the NAS directly by using the ip gives the same result: no connection.
I am not a computer expert so this was all I could do myself. What else can I do to enter the control page again?

[fvdw]

which firmware are you using on the spd8020 ?

[p.v.solar]

In the Lanview report I see OS version 4.9 (windows NT). I purchased the device in appr. 2006 and did not modify anything. Access to the control page was possible but I left all settings as original. When I purchased a new computer with Windows 7 the problems started. As I expected Win7 to be the problem I disconnected the NAS from the network, reset it to manufacturer defaults and connected it to one computer with Windows NT. No access also so I restored the situation, everyting to the network again.

[fvdw]

So it is the original Philips software
You write in first mail that it has an ip address
Just type in firefox address window the ip address
If then the login window doesn't appear then the web server isn't running menaing a software problem
You did already the factory reset but as far as I remember that function never worked on the Philips software.
If it doesn't work anymore the only route left is take the harddisk and do a new install (see our download topic for spd8020, the guide for installing a new harddisk)

[p.v.solar]

I found the "how to setup a new hard disk for use in the spd8020". Apart from not having linux, I have far too less experience for this type of actions. I'll try to find someone in the neighbourhood to go through the instructions together. This may take some days. I'll let you know the results. Thanks so far.

[fvdw]

you could try also to connect with via SSH. There is a ssh client that runs on windows (Putty).
If the ssh server still runs on the spd8020 you might be able to login via that (username: root password: giveit2me)
You will then get a Linux command prompt letting you investigate what the problem could be.
If the ssh server also doesn't work then no other choice then the new disk procedure remains

[p.v.solar]

Hi,

Thanks for the "easy" way. This is what I got:

BusyBox v1.01 (2007.09.20-14:14+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

-sh: can't access tty; job control turned off
# help

Built-in commands:
-------------------
. : alias bg break cd chdir command continue eval exec exit export
false fg getopts hash help jobs kill let local pwd read readonly
return set shift times trap true type ulimit umask unalias unset
wait

This all means nothing to me but hopefully you see some entrance.

Just to be sure: The problem started after installing a new computer with windows 7 on the network. I know I do not have the highest rights to access files and functions. Some locations are forbidden even in admin mode, I have to go back to the supplier if I want to have modifications there (e.g. setting other partitions to the hard disk) Could it be that windows 7 has taken over the NAS and blocks me out?

[fvdw]

It was a long time ago I worked with the philips software :-D

It is unlikelty that windows 7 blocked you out, the webinterface is using a browser. Did you try to connect by typing in the browser the ip address of your spd8020 ?

Anyhow it could be that the web server is not running
give as command

Code: Select all

ps

or

ps -ef

This should list the programs running
and see if httpd is listed and smbd and nmbd in the list of running programs
if httpd is not running try to start it using

Code: Select all

/usr/bin/httpd -f httpd.conf -d /etc

If it runs try if you can log in

[p.v.solar]

It starts to become fun to go so deep in the operation.

Here are the results:
PID Uid VmSize Stat Command
1 root 352 S init
2 root SWN [ksoftirqd/0]
3 root SW< [events/0]
4 root SW< [khelper]
5 root SW< [kthread]
9 root SW< [kblockd/0]
12 root SW [khubd]
26 root SW [swapper]
44 root SW [pdflush]
45 root SW [pdflush]
47 root SW< [aio/0]
46 root SW [kswapd0]
168 root SW [scsi_eh_0]
191 root SW [kjournald-sda1]
207 root SW [kjournald-sda5]
342 root 1028 S /usr/sbin/nmbd -D -l /var/log/samba
345 root 1440 S /usr/sbin/smbd -D -l /var/log/samba
350 root 396 S /sbin/udhcpc -b -i egiga0 -s /etc/api/api_dhcpc.php d
357 root 688 S /usr/sbin/smbd -D -l /var/log/samba
359 root 180 S < /sbin/udevd
362 root 428 S /usr/sbin/noflushd -n 15 /dev/sda
365 root SW [kjournald-sda6]
378 root 484 S dropbear
387 root 232 S < /usr/sbin/syncawayd -n 3
407 root 376 S zxtract
423 root 444 S N mrvlqosd
434 root 456 S /usr/bin/fanctld -l 45 -u 50 /dev/sda
439 root 436 S /usr/sbin/btnsctld
442 root 440 S /usr/bin/discoverd
462 root 656 S /bin/sh
562 root 2604 S /usr/sbin/smbd -D -l /var/log/samba
616 root 948 S dropbear
617 root 696 S -sh
628 root 604 R ps
# /usr/bin/httpd -f httpd.conf -d /etc
Syntax error on line 511 of /etc/httpd.conf:
/etc/httpd.conf:511: <?xpacket> was not closed.
#
I hope this means something repairable.

[fvdw]

the web server is not running and it seems you http.conf file is corrupt, I am at work now will look to it this evening to see what can be done to restore the file