• October 23, 2019, 07:47:20 PM
  • 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.

Pages: [1] 2 3

Author Topic: Shares are not accessible after reboot (1.08)  (Read 19239 times)

Ita_gsxr

  • Level 1 Member
  • *
  • Posts: 9
Shares are not accessible after reboot (1.08)
« on: August 13, 2010, 06:50:27 AM »

My network:

Modem ADSL
router > NETGEAR WNR3500v2
NAS DNS-323 with two Seagate ST3500320AS/500Gb - firmware 1.08
#1 PC  - Windows XP Sp3
#2 PC  - Windows XP Sp3

After the DNS has booted it's not possible to access any network share.
Sometimes NAS is visible in the workgroup but not accessible, other times it's not even there.
I can see the shares and acces them only if i use the IP instead of the unit name in windows explorer.
Easysearch_v4.7 see the DNS, see shares but it's not able to map drives.

I tried To restore default settings end to reboot but nothing solved.

The ONLY solution I found is to log on to the DNS, go to the NETWORK ACCESS section and modify one rule, then magically the NAS appear in the network and all the shares become accessible. Probably this operation force a samba restart.

Am I the only one to experience this problem???
Logged

scaramanga

  • Level 2 Member
  • **
  • Posts: 99
Re: Shares are not accessible after reboot (1.08)
« Reply #1 on: August 13, 2010, 09:46:19 AM »

Yes, this sounds familiar.
Especially that part where using host name (\\my-nas\Volume_1) doesn't work but using IP (\\192.168.x.y\Volume_1) does.

Now that I'm almost (almost) done tinkering with it I won't reboot it often so didn't give it much thought. But you're not alone.
Logged
DNS-323 HW Rev. C1 FW 1.08 fun_plug 0.5
2 x Western Digital WD10EARS-00Y5B1 in Standard mode
(LLC changed to 5 minutes. Partitions aligned to 4K boundary)

gunrunnerjohn

  • Level 11 Member
  • *
  • Posts: 2717
Re: Shares are not accessible after reboot (1.08)
« Reply #2 on: August 13, 2010, 10:01:22 AM »

This sounds more like an issue with master browsers than a NAS issue. 
Logged
Microsoft MVP - Windows Desktop Experience
Remember: Data you don't have two copies of is data you don't care about!
PS: RAID of any level is NOT a second copy.

Ita_gsxr

  • Level 1 Member
  • *
  • Posts: 9
Re: Shares are not accessible after reboot (1.08)
« Reply #3 on: August 13, 2010, 12:35:49 PM »

This sounds more like an issue with master browsers than a NAS issue. 

I thought the same but "nbtstat -a" show me that the only master browser it's PC#1. If I shutdown PC#1 the DNS-323 become the new master browser.
I'm now thinking that perhaps it could be a conflict between PC#1 and DNS323 in the election of the master browser. Infact PC#1 is already in use when the dns-323 boot. Tomorrow I'll try to shutdown all the PC before powering up the 323.
Then I'll let you know.

Thanks.
Logged

Ita_gsxr

  • Level 1 Member
  • *
  • Posts: 9
Re: Shares are not accessible after reboot (1.08)
« Reply #4 on: August 13, 2010, 12:47:23 PM »

Now that I'm almost (almost) done tinkering with it I won't reboot it often so didn't give it much thought. But you're not alone.

Well, at least now I know that It's not a problem of my unit :(
Logged

gunrunnerjohn

  • Level 11 Member
  • *
  • Posts: 2717
Re: Shares are not accessible after reboot (1.08)
« Reply #5 on: August 13, 2010, 12:58:36 PM »

I know I had a number of issues with the DNS-321, the DNS-323, and my Synology DS209 fighting it out to see who would be the master browser.  I finally loaded fun_plug and disabled the master browser capability on the DNS-321 and DNS-323.  I finally beat them into submission and now my DISKSTATION assumes the role alone.


LANscanner v1.3 - ScottiesTech.Info

Scanning LAN...

DISKSTATION       192.168.0.144  00-00-00-00-00-00  WORKGROUP  MASTER
DNS-321           192.168.0.143  00-00-00-00-00-00  WORKGROUP
DNS-323           192.168.0.142  00-00-00-00-00-00  WORKGROUP
MAIN              192.168.0.26  00-04-4B-19-8A-0C  WORKGROUP
Logged
Microsoft MVP - Windows Desktop Experience
Remember: Data you don't have two copies of is data you don't care about!
PS: RAID of any level is NOT a second copy.

scaramanga

  • Level 2 Member
  • **
  • Posts: 99
Re: Shares are not accessible after reboot (1.08)
« Reply #6 on: August 13, 2010, 03:39:05 PM »

I finally loaded fun_plug and disabled the master browser capability on the DNS-321 and DNS-323.  I finally beat them into submission and now my DISKSTATION assumes the role alone.

Interesting. Wasn't aware of that.
Was checking out /etc/samba/smb.conf but, strangely, didn't find any reference to the relevant values (local master, preferred master, os level).

I am on the right track, right? Need to add "local master = no" to smb.conf's global stanza before nmbd starts (or restart it). Need to do it from ffp/start.
« Last Edit: August 13, 2010, 03:44:26 PM by scaramanga »
Logged
DNS-323 HW Rev. C1 FW 1.08 fun_plug 0.5
2 x Western Digital WD10EARS-00Y5B1 in Standard mode
(LLC changed to 5 minutes. Partitions aligned to 4K boundary)

gunrunnerjohn

  • Level 11 Member
  • *
  • Posts: 2717
Re: Shares are not accessible after reboot (1.08)
« Reply #7 on: August 14, 2010, 06:50:43 AM »

You are correct, you need to tell them they're not the master, and have no right to become the master. :)

About halfway down the page on this site: http://www.phrison.com/dns-323-setup-with-sheevaplug/, you'll find the instructions for making SAMBA configuration changes stick through reboots.  Using that technique, I put that line into the smb.conf file, and it's worked for me.
Logged
Microsoft MVP - Windows Desktop Experience
Remember: Data you don't have two copies of is data you don't care about!
PS: RAID of any level is NOT a second copy.

scaramanga

  • Level 2 Member
  • **
  • Posts: 99
Re: Shares are not accessible after reboot (1.08)
« Reply #8 on: August 14, 2010, 08:24:09 AM »

You are correct, you need to tell them they're not the master, and have no right to become the master. :)

About halfway down the page on this site: http://www.phrison.com/dns-323-setup-with-sheevaplug/, you'll find the instructions for making SAMBA configuration changes stick through reboots.  Using that technique, I put that line into the smb.conf file, and it's worked for me.

The method described there is a bit heavy-handed. Replacing smb.conf with a pre-edited file means I'll probably need to revisit that file whenever I make changes to network shares. I suggest making changes on the fly, using sed, along these lines:
Code: [Select]
/ffp/bin/sed -e '/\[ global \]/alocal master = no' /etc/samba/smb.conf > /tmp/smb.confIf you're unfamiliar with sed, what it does is:
1. Read the /etc/samba/smb.conf file.
2. Finds the line(s) containing the text "[ global ]" (need to escape the '[' and ']') and adds (appends) after them the text "local master = no"
For multiple lines, use multiple commands like so:
Code: [Select]
/ffp/bin/sed -e '/\[ global \]/alocal master = no' -e '/\[ global \]/apreferred master = no' /etc/samba/smb.conf > /tmp/smb.conf
After that - swap the files (preferably keep original someplace for troubleshooting)
« Last Edit: August 14, 2010, 08:27:32 AM by scaramanga »
Logged
DNS-323 HW Rev. C1 FW 1.08 fun_plug 0.5
2 x Western Digital WD10EARS-00Y5B1 in Standard mode
(LLC changed to 5 minutes. Partitions aligned to 4K boundary)

gunrunnerjohn

  • Level 11 Member
  • *
  • Posts: 2717
Re: Shares are not accessible after reboot (1.08)
« Reply #9 on: August 14, 2010, 08:32:13 AM »

That's more elegant, but I don't change my shares, so it's a moot point. :)

It's a good idea anyway, I'll have to consider it.  I hate to fix something that ain't broke right now. :D
Logged
Microsoft MVP - Windows Desktop Experience
Remember: Data you don't have two copies of is data you don't care about!
PS: RAID of any level is NOT a second copy.

scaramanga

  • Level 2 Member
  • **
  • Posts: 99
Re: Shares are not accessible after reboot (1.08)
« Reply #10 on: August 14, 2010, 01:45:30 PM »

I hate to fix something that ain't broke right now. :D
It's hard to argue with that
Logged
DNS-323 HW Rev. C1 FW 1.08 fun_plug 0.5
2 x Western Digital WD10EARS-00Y5B1 in Standard mode
(LLC changed to 5 minutes. Partitions aligned to 4K boundary)

gunrunnerjohn

  • Level 11 Member
  • *
  • Posts: 2717
Re: Shares are not accessible after reboot (1.08)
« Reply #11 on: August 14, 2010, 02:01:40 PM »

I saved your example, it would be handy for modifying any of the configuration files on the fly.  If I ever run into the situation where I need to edit my stuff. I'll try this method. :)

Thanks.
Logged
Microsoft MVP - Windows Desktop Experience
Remember: Data you don't have two copies of is data you don't care about!
PS: RAID of any level is NOT a second copy.

scaramanga

  • Level 2 Member
  • **
  • Posts: 99
Re: Shares are not accessible after reboot (1.08)
« Reply #12 on: August 14, 2010, 04:22:17 PM »

I saved your example, it would be handy for modifying any of the configuration files on the fly.  If I ever run into the situation where I need to edit my stuff. I'll try this method. :)

Thanks.


Glad I could help. sed (short for stream editor) is a wonderful tool, imho it's well worth learning. In this case, I used it to add stuff at a specific location. it can also be used to search and replace and do all sorts of text file manipulation.

Still need to help the original poster Ita_gsxr: Are you following this thread? need help with this?
Logged
DNS-323 HW Rev. C1 FW 1.08 fun_plug 0.5
2 x Western Digital WD10EARS-00Y5B1 in Standard mode
(LLC changed to 5 minutes. Partitions aligned to 4K boundary)

gunrunnerjohn

  • Level 11 Member
  • *
  • Posts: 2717
Re: Shares are not accessible after reboot (1.08)
« Reply #13 on: August 14, 2010, 05:20:45 PM »

I've used SED before, I used to use it to update from one version of the Linux kernel to the next.  Haven't done any Linux work in years, you tend to forget this stuff. :D
Logged
Microsoft MVP - Windows Desktop Experience
Remember: Data you don't have two copies of is data you don't care about!
PS: RAID of any level is NOT a second copy.

Ita_gsxr

  • Level 1 Member
  • *
  • Posts: 9
Re: Shares are not accessible after reboot (1.08)
« Reply #14 on: August 15, 2010, 12:32:42 PM »

Still need to help the original poster Ita_gsxr: Are you following this thread? need help with this?

Hi! I'm Still here :) It's only that I went through an XP install from scratch :((( What a news, eh?

Well. It seems that the problem is really the master election.
I'm wondering why D-Link didn't put the choice to be a Master or not into the LAN SETTING or DEVICE SETTING tab. Wouldn't it be easier for everyone?

Unfortunately I'm not a linux expert. So PLEASE...be patient ;)
If I understand I need to:

1) Install FunPlug (Copy fun_plug and fun_plug.tgz to Volume 1 and reboot)

2) Via Telnet: (/ffp/bin/sed -e '/\[ global \]/alocal master = no' /etc/samba/smb.conf > /tmp/smb.conf)
This should add the line "master = no" into samba and make a backup copy of the orginal smb.conf

This change should be reboot persistent. Right?

Another thing, once installed ffp the telnet server is always running , right? I'm behind a Firewall (NETGEAR WNR3500) but I don't like the idea to leave some door open.
Is it possibile to shutdown the telnet service or uninstall FFP? Should I simply delete files from Volume 1 ???

Many Thanks!!

« Last Edit: August 15, 2010, 12:36:00 PM by Ita_gsxr »
Logged
Pages: [1] 2 3