Can not access to same share place declared by Samba from 2 different computers

[GoogleCodeExporter]

Hi,
First I want to congratulate you on this alternate firmware. To me it allows to 
see the NAS323 under an admin point of view and, finally we can play with it... 
and break it as well....:-) Weel good job!!
This being sais I have the followiung issue:

Issue: Can not access to same share place declared by Samba from 2 different 
computers
What steps will reproduce the problem?
1. The DSN has a share named DNS323_SHARE using samba. This share place can be 
accessed by all users: authorization for all user to access to it.
2. PC_1 can access to the share without any problems by 
refering\\DNS323\DNS_323_SHARE
3. PC_2 cannot access to the share  by refering \\DNS323\DNS_323_SHARE but it 
can access to it by entering \\172.22.22.5\DSN_323_SHARE
4. If I reboot the 2 PC_1 and PC_2 then PC_2 can access to 
\\DNS323\DNS_323_SHARE

I d like to access to this share by only mentioning the name 
\\DNS323\DNS_323_SHARE and not the IP adress from more than one computer: Is 
that possible?

Note 1: closing the windows explorer instead of rebooting the computer does not 
change anything: I still have the issue

Note 2:Is there a cache to be flushed on the PC or on the DNS323? 

Note 3: Is there a Samba setting to apply to get the wished behavior?

What is the expected output? What do you see instead?
I d like to access to the shared resource from the 2 computers concurrently: Is 
it possible?

What Alt-F version are you using? Have you flashed it?
I am using the last one and I have not flashed anything. I just have and reload 
my settings: Alt-F-0.1RC2.tar

What is the box hardware revision level? A1, B1 or C1? (look at the label at 
the box bottom)
I think it is the B1 but I am not sure I will re-validate

What is your disk configuration? Standard, RAID (what level)...
JOBD

What operating system are you using on your computer? Using what browser?
PC_1 is Windows 7 PC_2 is XP and I an using Chrome

Please provide any additional information below.
Also I have the same issue for a share that is authorized only for one user: I 
created a user and assigned the user to the share

In the status WEB page at the bottom I noticed that the share seems mounted to 
my 2 PCs

Thank you for your help and if you need any extra information let me know.

Original issue reported on code.google.com by vincent....@gmail.com on 30 Oct 2012 at 12:18

[GoogleCodeExporter]

I can't reproduce this when using two MS-Vista (and a linux) computers.

> 1. The DSN has a share named DNS323_SHARE using samba. This share place can 
be accessed by all users: authorization for all user to access to it.

Have you hand-edited /etc/samba/smb.conf? Can you please post it?

> 4. If I reboot the 2 PC_1 and PC_2 then PC_2 can access to 
\\DNS323\DNS_323_SHARE

and PC_1 can access it only using the IP?

Can you watch /var/log/samba/log.* for errors? Just use System->Utilities->View 
Logs

This seems to be related to a MS-win name resolution issue, as the share can be 
accessed when using its IP but not its (win) name. Do you have other MS-Win 
computers in the network? Any of them is a winserver?

Original comment by whoami.j...@gmail.com on 30 Oct 2012 at 2:49

[GoogleCodeExporter]

Hi,
I am having inconsistent behavior, I will investigate deeper and will let
you know what I find out something.

Original comment by vincent....@gmail.com on 31 Oct 2012 at 12:59

[GoogleCodeExporter]

Hi,
after doing some more testing in changing the samba configuration without
success I ended up into rebooting the DNS323. After that it never
successfully rebooted: it was stuck somewhere in its starting process and
pushing and waiting on the front button did not stop it. It did not even
had an IP adress, so I had to unplug it. I took the left disk plugged it
into a linux computer, removed the fun_plug file and restarted it. I was
back to the original firmware. But since I really am tempted with some
features that your firmware has I retried to re-install (copy of th
altF.tar file + funplug file into Volume_1) it but firts I deleted the
ALT-f directory from Volume_1 and the directoryes on sdb4 that had been
created: altF, Users, Public etc... And still it stays stuck on during the
starting process

question: what else should I remove to enable it to start using your
firmware?

Note: I also tried the fun plug from Fonz and this one works: I can telnet
and ssh to it.

Thank you in advance

On Tuesday, October 30, 2012, Vincent Leplumey <vincent.leplumey@gmail.com>
wrote:

you know what I find out something.

share place declared by Samba from 2 different computers

can be accessed by all users: authorization for all user to access to it.

\\DNS323\DNS_323_SHARE

System->Utilities->View Logs

can be accessed when using its IP but not its (win) name. Do you have other
MS-Win computers in the network? Any of them is a winserver?

Original comment by vincent....@gmail.com on 4 Nov 2012 at 5:37

[GoogleCodeExporter]

To fully remove Alt-F, you should delete fun_plug, and the alt-f *and* Alt-F 
folders. Note the casing!
To reinstall, and to avoid possible problems, rename the ffp folder to 
something else.

Reloading fails sometimes, and it is not possible to have any kind of 
diagnostics (other than the alt-f.log file; I would recommend you to flash 
Alt-F instead.

Reloading is much more complex than starting/running ffp, even if both Alt-F 
and ffp use a fun_plug file.

In any case, this kind of issues are best answered in the Alt-F forum, this 
place is intended for bugs. Closing.

Original comment by whoami.j...@gmail.com on 5 Nov 2012 at 2:32

• Changed state: Invalid

[GoogleCodeExporter]

Hi,
Actually I was able to fix my booting issues, I think I know what happened:
1) At a given point I had to reboot my NAS
2) While the NAS was restarting, and maybe after 10 minutes of waiting I
was still not having any aswer to the "ping" command: it was not even on
the network. it was not stoping when I was pressing on the front button
either and it seemed that the hard drive were working hard
3) At that time I considered that something was wrong and it is why unplug
it: no power no runing, and then I took the disc out of the box, plug it on
another computer and remove the fun_plug file from Volume_1 and it was back
again using the old (Dlink firmware). This was at that time I wrote the
last updates

After your recommendation I removed all the directory you mentionned (but
still using the reload method) and an tried again after having set up the
NAS with a static IP adress. This time it booted properly and I was having
access to the administration page AND I noticed that the mount /mnt/mnt0
was being checked for a very long time 30 minute or 1 hour, not really
important just a long time, and during this period of time the /mnt/mnt0
seemed empty: a little scarry... I waited for the check to be completed and
as soon as it was done I was having access to the data I had on the disks.

In summary I think I should have:
 - not trusted the rooter to give the IP adress even if it is set up the
way that it always give to same IP adress to the same Mac adress
 - set up a static IP adress to the NAS
 - waiting long enough and not being worried because it was not responding

Now I am back in business I was able to install minidlna application and
mount a USB drive to the NAS.

1 comments and one question:
- In the post "Announce new Alt-F packages feed" you mention that we have
to change the data in "Configure Feeds". The thing is when we have no Alt-F
supplement packages installed the "Configure Feeds" in not there. I know
that it is mentionned in the same threat after how to change it in your
post from the *"On Wednesday, October 24, 2012 6:26:35 PM UTC+1, Erregend
wrote:"* but it might be usefull to have it mentionned in the first post to
avoid missing the information

- I mounted a USB drive and was able to access to it in read and write
mode. Prior to unplug it I removed the samba sharing and then tried to
"eject" the usb disc from the WEB page "Disc utilities". Nothing happens. I
read in another post that someone had the issue and you say that there
should be a popup window that should say something (I do not recall what it
is). I used Firefox and Chrome and I have the same problem: nothing
happens. So I used the command umount (after a SSH on the NAS) and after in
the "Disc Utilities" instead of Eject it says Load but I have not tried to
load it, it was a little late... Is it a possible way to proceed, meaning
using the umount command to umount the USB drive?

For the samba issue I originally had I will make some more testing to
understand what is going on because sometimes it works some tine it does
not but I can not nail down the scenario. When I find something valid I
will create a post.

Again you did a great job wiht this, it gives a second life to the DNS

Original comment by vincent....@gmail.com on 7 Nov 2012 at 1:30

[GoogleCodeExporter]

I used to use a static IP, but as most users seems to use DHCP I also start 
using DHCP and I have no problems so far, so you might test DHCP again when 
"things" stabilize -- only then, to keep issues separated!

The initial long fsck was due to the box unplug, which means that the 
filesystems were not cleanly unmounted. Data is not available during that time, 
and it takes a lot, it's normal.

I have edited the 1st "Announce new Alt-F packages feed" post as per your 
advise, thanks.

Having Alt-F packages on an external USB disk/pen can avoid "eject" (really 
'umount') to work, as Alt-F uses some folders in the 'Alt-F' packages folder 
hierarchy, and unmount can complain that the filesystem is busy. You was able 
to manually unmount it, but it not always succeed.

This is independent of the pop-up message that should appear when 'eject' is 
hit. As you are not using IE, are you sure that popups are enabled in the 
browser? A popup should always appears saying either "ok to remove" or "busy, 
stop services first", or similar.
Please try again latter on a "normal" pen without ffp/Alt-F packages on it, 
only data.

Thanks (but the ideal place to conduct this conversation is on the forum, so 
other can contribute -- and as the 'issue' is now closed it will not showup in 
the issues list)

Original comment by whoami.j...@gmail.com on 7 Nov 2012 at 5:37