D-Link DNS323 NAS / Ubuntu 8.10 cannot connect windows share

Bug #301794 reported by james

This bug report was converted into a question: question #58004: D-Link DNS323 NAS / Ubuntu 8.10 cannot connect windows share.

18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Undecided
Unassigned

Bug Description

New problem with Ubuntu 8.1 connecting to password-protected share.

Trying to connect to dlink dns-323 nas, but get error message...

"Could not display "smb://192.168.0.137/share/".
Error: Failed to to mount Windows share.
Please slect another viewer and try again.

2 ways that I tried to connect
1) Connect to Server --> Windows share; enter IP of nas & folder share --> then enter user and pwd
2) In nautilus enter --> smb://192.168.0.137/share --> enter user and pwd

Worked well with 8.04, and hardware is unchanged.

Revision history for this message
Louis-Xavier Brusset (lxbrusset) wrote :

Hello I got similar problem since I migrated from 8.04 to 8.10

I noticed that I can connect to a TRUE smb server (Igot a PC under Windows XP Pro) but it crashes with my FREECOM Network Drive.

I looked into Samba logs and I found this in /var/log/samba/log.winbindd-idmap :

[2008/12/02 19:13:40, 1] winbindd/idmap_tdb.c:idmap_tdb_alloc_init(371)
  idmap uid range missing or invalid
  idmap will be unable to map foreign SIDs
[2008/12/02 19:13:40, 0] winbindd/idmap.c:idmap_alloc_init(831)
  ERROR: Initialization failed for alloc backend, deferred!
[2008/12/02 19:13:40, 1] winbindd/idmap_tdb.c:idmap_tdb_alloc_init(371)
  idmap uid range missing or invalid
  idmap will be unable to map foreign SIDs
[2008/12/02 19:13:40, 0] winbindd/idmap.c:idmap_alloc_init(831)
  ERROR: Initialization failed for alloc backend, deferred!
[2008/12/02 19:14:23, 1] winbindd/idmap_tdb.c:idmap_tdb_alloc_init(371)
  idmap uid range missing or invalid
  idmap will be unable to map foreign SIDs
[2008/12/02 19:14:23, 0] winbindd/idmap.c:idmap_alloc_init(831)
  ERROR: Initialization failed for alloc backend, deferred!
[2008/12/02 19:14:23, 1] winbindd/idmap_tdb.c:idmap_tdb_alloc_init(371)
  idmap uid range missing or invalid
  idmap will be unable to map foreign SIDs
[2008/12/02 19:14:23, 0] winbindd/idmap.c:idmap_alloc_init(831)
  ERROR: Initialization failed for alloc backend, deferred!
[2008/12/02 19:14:23, 1] winbindd/idmap_tdb.c:idmap_tdb_alloc_init(371)
  idmap uid range missing or invalid
  idmap will be unable to map foreign SIDs
[2008/12/02 19:14:23, 0] winbindd/idmap.c:idmap_alloc_init(831)
  ERROR: Initialization failed for alloc backend, deferred!
[2008/12/02 19:14:23, 1] winbindd/idmap_tdb.c:idmap_tdb_alloc_init(371)
  idmap uid range missing or invalid
  idmap will be unable to map foreign SIDs
[2008/12/02 19:14:23, 0] winbindd/idmap.c:idmap_alloc_init(831)
  ERROR: Initialization failed for alloc backend, deferred!

Revision history for this message
Thierry Carrez (ttx) wrote :

DNS323 seems affected by bug 286828, could you try the workaround described at:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/286828/comments/62

Changed in samba:
status: New → Incomplete
Revision history for this message
Louis-Xavier Brusset (lxbrusset) wrote :

Excuse me bit if I understood well this workaround needs a server update ?

As my Freecom Network drive is like a blackbox and no firmware update is available I am blocked ...

Is there something I can do to tell my client that my SMB server is a pile of Old faulty code ?

All that I see are my two errors :
  idmap uid range missing or invalid
  idmap will be unable to map foreign SIDs

Revision history for this message
Thierry Carrez (ttx) wrote :

Louis-Xavier:
The workaround in comment 2 was proposed to the original poster, since he owns a DNS323 and they are known to be affected by bug 286828.
Your issue might be a bit different, since you get specific idmap errors in your logs. Could you please file a separate bug ? We'll merge them if analysis reveals that it is indeed the same bug.

Revision history for this message
james (jwucsd) wrote :

Thanks TC!!

Revision history for this message
rirad (rirad) wrote :

This problem was studies by cebesius and he found that the samba server version in dns-323 does not support the new authentication protocol used by ubuntu 8.10 but expects the weaker lanman. (see http://ubuntuforums.org/showpost.php?p=6238553&postcount=5)

The fix is to add this line to /etc/samba/smb.conf below the [global] section:

client lanman auth = yes

This worked for my ch3snas as well which is very similar to the dns-323.

Revision history for this message
james (jwucsd) wrote :

I used the above fix from cebesius via rirad - works great for dns-323 & ubuntu 8.1.

Many thanks!

Thierry Carrez (ttx)
Changed in samba:
status: Incomplete → Invalid
Revision history for this message
J Posey (jpo) wrote :

I have a DNS-323 which worked most (but not all) of the time with Hardy, but quit working in 10.04.

adding

client lanman auth = yes

to the [global] section of smb.conf seems to have resolved the problem as long as I use the IP address of the DNS (I've done a few other things, configuring the DNS to the same user name as my 10.04 system, changing the domain name ("workgroup" in winspeak) in smb.conf and in the DNS-323 configuration to match in case, but don't know if they matter).

HOWEVER: my LAN has never worked except when the router is configured as the DHCP server, so I never know the IP address of the DNS-323. Is there an easy way to find out? 192.168.0.102 works. RAID1-FDFA2B does not.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers