DSM-G600, DNS-3xx and NSA-220 Hack Forum

GailH · 2010-12-13 19:15:32

Hi experts

I got a new DNS-323 a month ago, installed it with a single 1 TB volume (WD Green) in the right bay, and everything was fine.

Recently, I've done two things: a. Installed an additional disk drive in the second bay (by the way, volume numbers got swapped); and installed funplug and started ssh.

Then a new strange phenomenon is happening: after I start the device, the network does not recognize it by its hostname (e.g. dlink-55ea98), but it can be accessed fine using its IP address (using http://192.168.1.168).

Then, after 20-30 minutes of operation, the network recognizes it fine, and it can be accessed using its hostname (e.g. dlink-55ea98).

Same with sharing the volumes from Windows machines.

Any ideas how to have the network recognize it from start?

TIA

Gail

Last edited by GailH (2010-12-13 19:16:05)

scaramanga · 2010-12-13 20:48:33

This sounds like a master browser problem. The complete discussion of this issue and how I solved it is here:
http://forums.dlink.com/index.php?topic=14522.0

Just in case, here's the script I use today (might be the same as the one from that thread, not sure). You'll need fun-plug installed to do this. Fonz' fun-plug contains all the tools this little script needs (namely, sed).

I suggest you do the "right thing" and read some more to get a good understanding what it all means before trying it out, although it "should" be easy to undo this.

Code:

#!/bin/sh

# After rebooting the DNS-323, often you can't access your shares from
# windows machines. This script "should" fix this by adding the following
# three lines to the [ global ] stanza of /etc/samba/smb.conf:
#   domain master = yes
#   local master = yes
#   preferred master = yes
# What this does is make the DNS-323 the master browser of its workgroup,
# subnet and also make it force an election for master browser after it
# is booted.
#
# INPORTANT: If anything goes wrong here, you might not be able to access
#            your data. Only use this if you know how to recover from such
#            a problem by yourself.

#
# Commands
#
echoCmd="/bin/echo"
cpCmd="/bin/cp"
sedCmd="/ffp/bin/sed" # Couldn't get it to work with /bin/sed
smbCmd="/usr/bin/smb"

#
# Files
#
smbConf="/etc/samba/smb.conf"
smbConfBackup="/etc/samba/smb.conf.old"


${echoCmd} "Backing-up ${smbConf} to ${smbConfBackup}"
${cpCmd} -a ${smbConf} ${smbConfBackup}

${echoCmd} "Modifying ${smbConf}"
${sedCmd} -e '/\[ global \]/adomain master = yes' -e '/\[ global \]/alocal master = yes' -e '/\[ global \]/apreferred master = yes' ${smbConfBackup} > ${smbConf}
if test $? -eq 0; then
    ${echoCmd} "Done! Restarting smb and nmb daemons"
    ${smbCmd} restart
else
    ${echoCmd} "Error! Recovering ${smbConf} from backup ${smbConfBackup}"
    ${cpCmd} -fa ${smbConfBackup} ${smbConf}
fi

Last edited by scaramanga (2010-12-13 20:54:35)

DSM-G600, DNS-3xx and NSA-220 Hack Forum

Announcement

#1 2010-12-13 19:15:32

DNS-323 hostname: takes a long time to be known on the network

#2 2010-12-13 20:48:33

Re: DNS-323 hostname: takes a long time to be known on the network

Code:

Board footer