WM6 and SAMBA

[dah54]

Windows Mobile 6 doesn't play with SAMBA folders, do to a increase security setting for lanmanager passwords. Does anyone know how to connect my WM6 PPC to a SAMBA share? Samba is rejecting my User Name Password, or more likely my PPC is rejecting sending the user name password in the clear to the samba server. So how do I permit this?

60 looks at this, suggest I'm not the only one with the problem....
Anyone else have the problem as well?
I can't connect to a share on a WRT350N so any answers? Anyone else in the same boat?

Thanks

[lyka]

i'm having problem too.

I can explore my pc samba share, but can't explore my asus router share.

tested both total commander and htc network

[WRaymond]

Perhaps this has to do with the way the aforementioned apps handle the SMB protocol. I am using Resco File Explorer and never had any problems with my network. I can connect to SAMBA v2 and v3 shares. All my shares have a strong security policy, and they are on a variety of linux flavours: Fedora Core 4, Fedora 8, Gentoo 2007 and OpenSUSE 10.3.
Could you be more specific on what you describe as "increase security setting for lanmanager passwords"?

[beast0898]

Perhaps this has to do with the way the aforementioned apps handle the SMB protocol. I am using Resco File Explorer and never had any problems with my network. I can connect to SAMBA v2 and v3 shares. All my shares have a strong security policy, and they are on a variety of linux flavours: Fedora Core 4, Fedora 8, Gentoo 2007 and OpenSUSE 10.3.
Could you be more specific on what you describe as "increase security setting for lanmanager passwords"?

Yes you are correct, you need a third party app to correctly connect Samba shares with passwords.

There are plenty of "free" File Explorers that will give you this functionality, the standard file explorer is rubbish, even for open shares.

[dah54]

For Vista it is necessary to do,

Open Control Panel | Switch to classic View | Administrative Tools (icon) | Local Security Policy (right pane) | Continue when prompted | click on Local Policies (left pane) | Click on Security Options | scroll down to Network security: LAN Manager authentication level double click on it.. Then change it to "Send LM & NTLM - use NTLMv2 session security if negotiated" | OK | X |

The above change is necessary to connect to my Linksys WRT350N or to connect to my Magnia SG30 server. With Jwrightmcps Crossbow ROM Update 2.12.06 WWE both the Network Plugin and Resco Explorer 2007 v6.10 and v6.17 fail to transmit the password and user name to the SAMBA shares. The same as Vista does without the above change. I can however connect to a Vista box and access it's files.

[WRaymond]

The following is an excerpt from Resco's File Explorer FAQ:

8.7. I have problems connecting to Windows Server 2003 running as a domain controller.
Windows CE networking is not able to map the drives from the servers using SMB signing.
This can be solved by changing the following setting in the Domain Controller Security Policy under Local Policies --> Security Options
Microsoft Network Server: Digitally sign communications (always): Disabled

8.8. I am not able to map the Linux (or MAC) Samba drive
This problem is similar to 8.7. You need to disable SMB signing. Please try to locate the "smb.conf" file and add the line use spnego = no under section [global]


I guess that you could try relaxing restrictions on your SAMBA shares and use MAC address filtering to be on the safe side. It can be easily done on both your router and server. You can also map a static IP to your Universal and allow it access to your shares based on its IP. This allows you to easily reconfigure SAMBA to accept connections from specific computers.

[lyka]

Resco is not working for me.

Total commander works fine with samba password. The weird thing is that my router has a setup with guest account and no password.

[dah54]

Resco is not working for me.

Total commander works fine with samba password. The weird thing is that my router has a setup with guest account and no password.

Interesting... As far as I can tell, Total Commander, Resco Explorer, File Explor, and the Network Plugin all call the same password manger in WM6 and that manager does not send the passwords in a form that SAMBA understands.

In theory changing the key at HKLM\Comm\SecurityProviders\NTLM\LmCompatibilityLe vel to 2 from 3 should do what I need, and enable the Universal to communicate with my SAMBA server. That it doesn't suggest to me that there is a problem with the LM security provider.

[dah54]

The following is an excerpt from Resco's File Explorer FAQ:
8.7. I have problems connecting to Windows Server 2003 running as a domain controller.
Windows CE networking is not able to map the drives from the servers using SMB signing.
This can be solved by changing the following setting in the Domain Controller Security Policy under Local Policies --> Security Options
Microsoft Network Server: Digitally sign communications (always): Disabled

8.8. I am not able to map the Linux (or MAC) Samba drive
This problem is similar to 8.7. You need to disable SMB signing. Please try to locate the "smb.conf" file and add the line use spnego = no under section [global]

I guess that you could try relaxing restrictions on your SAMBA shares and use MAC address filtering to be on the safe side. It can be easily done on both your router and server. You can also map a static IP to your Universal and allow it access to your shares based on its IP. This allows you to easily reconfigure SAMBA to accept connections from specific computers.

Locating the "smb.conf" file and add the line use spnego = no under section [global] makes no difference on the Magnia server, and is not an option on the WRT350N....

[WRaymond]

What version of SAMBA do you have on the Magnia, and on what OS?
Looking at version 3.0.25 comprehensive release notes (http://us3.samba.org/samba/history/samba-3.0.25.html), I found the following bugfix in version 3.0.20:
* BUG 1828: Fixed SPNEGO issues with PocketPC clients.
If upgrading SAMBA doesn't fix your problems, or if you already have the latest version installed (3.0.28), would you mind attaching your smb.conf file?

I read the manual of the Linksys box, but I couldn't find anything conclusive. There are quite a few settings that pertain to the external storage device, perhaps you could try playing around with them to see if anything improves.

[WRaymond]

@ dah54:

So, had any luck yet?

[hocky98]

I have verified that changing the LMCompatibility level from 3 to 2 does indeed work now for WM6. I'm also using a Dell X50v with Maglite's A02 RTM version of WM6. No changes to my samba server with "use spnego = no" in global.

[johnpatcher]

I have verified that changing the LMCompatibility level from 3 to 2 does indeed work now for WM6. I'm also using a Dell X50v with Maglite's A02 RTM version of WM6. No changes to my samba server with "use spnego = no" in global.

Could you please tell us what you actually did? I changed this registry key, but it doesn't work for me.

I love this WM6 but connecting to my NAS is something I won't miss.

[johnpatcher]

Anything new in here? It doesnt work for me with all the great WM6 releases this is really a bad issue.

Changed this registry key, tried several samba versions and configs, but this one drives me crazy.

[johnpatcher]

Come on, anyone must fix this :o.

[lottemann]

A lot of posts in different forums suggest to add a line

use spnego = No

to the smb.conf and thus "disabling SMB signing". This is painfully wrong.
The setting does not affect SMB signing, but the Extended Security Negotiation, which seems to be REQUIRED by WM6.
So putting it to

use spnego = Yes

did the trick here :D:D:D. Please let me know, if this helps anyone else...

Wireshark helped in finding the difference in the SAMBA and WM6 flags in the SMB protocol negotiation.
SMB signing would be required if HKLM\Comm\Redir\SmbSignatureMode would be set to 3, which is not the default. Values 1(default) and 2 should work with and without SMB signing. (http://msdn2.microsoft.com/en-us/library/aa921092.aspx)

[johnpatcher]

Although I didn't change anything (awarently) it works no. I'm using a WM 6.1 image of Lennesh with the following smb.conf:

[global]
netbios name = nas
workgroup = WORKGROUP
server string = network attached storage
load printers = no
show add printer wizard = no
disable spoolss = yes
use client driver = yes
log file = /var/log/%m.log
lock directory = /var/lock
max log size = 0
security = user
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
unix password sync = yes
passwd program = /usr/bin/passwd %u
passwd chat = *New*password* %nn *new*password* %nn *changed*
socket options = IPTOS_LOWDELAY TCP_NODELAY
security mask = 0777
create mask = 0777
fstype = NTFS
max smbd processes = 200
map to guest = Bad User
csc policy = disable
hide dot files = yes
veto files = /lost+found/autobootfs/
block size = 4096
guest ok = no
max connections = 200
getwd cache = Yes
lm announce = yes
lm interval = 120
max xmit = 8192
status = no
deadtime = 0
level2 oplocks = True
dns proxy = no
client code page = 437
character set =
valid chars =
read only = no
browseable = yes
public = yes
writable = yes
force create mode = 0777
force directory mode = 0777
force security mode = 0777
create mask = 0777
acl check permissions = no
unix charset = ISO8859-15
use spnego = no

[misc]
comment = miscellanious things
path = /mnt/misc

[music]
comment = music
path = /mnt/music

[toolz]
comment = tools
path = /mnt/toolz


I'm so happy just now!

[bazzix]

I'm having the same problem with the stock firmware of my Samsung i780
Samba Version 3.0.23c (on a linksys nslu2)

Connecting to my desktop (windows xp pro) works fine, but both seeing or accessing the nslu2's shares are a problem.

Any real solution to this problem? I tried all suggested methods (samba2, spnego, ...)

thanks

[jnjn]

Interesting... As far as I can tell, Total Commander, Resco Explorer, File Explor, and the Network Plugin all call the same password manger in WM6 and that manager does not send the passwords in a form that SAMBA understands.

In theory changing the key at HKLM\Comm\SecurityProviders\NTLM\LmCompatibilityLe vel to 2 from 3 should do what I need, and enable the Universal to communicate with my SAMBA server. That it doesn't suggest to me that there is a problem with the LM security provider.

OK. The correct answer is here:

Change HKLM\Comm\SecurityProviders\NTLM\LmCompatibilityLe vel to 1 from 3, not to 2 (ref: http://msdn.microsoft.com/en-us/library/aa922895.aspx and http://msdn.microsoft.com/en-us/library/aa925018.aspx) as "You can also set the LmCompatibilityLevelServer value to 2 or to 3. Both of these specify that the server will only use NTLM v2. Authentication will fail if the client is not capable of NTLM v2 protocol. For more information, see Authentication Services Registry Settings".

And check to make sure HKLM\Comm\Redir\SmbSignatureMode is set to 0 (not recommended 'cos it may cause problems with windows servers), 1 or 2, but not 3 (ref: http://msdn.microsoft.com/en-us/library/aa921092.aspx).

And you can try to set HKLM\Comm\Redir\AllowedAuthMethods to 3 to see if it makes any difference. To me, 2 works fine.

No need to modify samba configurations if you are running a recent version of samba (3.0.28 right now). Anyway, you can always try to add "use spnego = no" (maybe "client use spnego = no" or "spnego = no" as stated and/or quoted in other posts/web pages, I'm not sure of it.) to see if it makes any difference in your situation/samba version.

[bazzix]

hi there,

i have it set to 2 but doesnt help.. could yo give your working configuration of samba and versions of wm/netwprk plugin etc please? thanks

[jnjn]

hi there,

i have it set to 2 but doesnt help.. could yo give your working configuration of samba and versions of wm/netwprk plugin etc please? thanks

Please tell me you had set which registry entry to 2? I mentioned three items there, and the most important one is the first one which should be set to 1, not to 2.

[bazzix]

I meant that I applied all your reg settings, but didn't work for me. Also all the 'spneg no' statements are present in the smb.conf.

Perhaps I'm still overlooking something, so if you could share your smb.conf?

Thanks

[jnjn]

I meant that I applied all your reg settings, but didn't work for me. Also all the 'spneg no' statements are present in the smb.conf.

Perhaps I'm still overlooking something, so if you could share your smb.conf?

Thanks

yeah, sure. here's my smb.conf, and i'm using samba 3.0.28a.
can you see your samba server in network plugin or resco explorer but cannot expend it? or you can't see your samba server at all?
=======================

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentary and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
#

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = WG

# server string is the equivalent of the NT Description field
server string = JSWR

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
; wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no

# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
interfaces = br0 lo

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
bind interfaces only = true



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
log file = /mnt/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
max log size = 128

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
; syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
; panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
security = user

# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
encrypt passwords = true


smb passwd file = /mmc/config/samba/smbpasswd
username map = /mmc/config/samba/smbusers
; password level = 14
username level = 14


# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
; passdb backend = tdbsam

; obey pam restrictions = yes

; guest account = nobody
; invalid users = root

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
; unix password sync = no

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
; passwd program = /usr/bin/passwd %u
; passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
; pam password change = yes

# This option controls how nsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
; domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
; logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
; logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
load printers = no

# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name = /etc/printcap

# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
; printing = cups
; printcap name = cups

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /mmc/config/samba/smb.conf.%m

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
; domain master = auto

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash

# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
; winbind enum groups = yes
; winbind enum users = yes

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
; usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes







# Case Preservation can be handy - system default is _no_
# NOTE: These can be set on a per share basis
preserve case = yes
short preserve case = yes
# Default case is normally upper case for all DOS files
default case = lower
# Be very careful with case sensitivity - it can break things!
case sensitive = auto



preferred master = yes



#======================= Share Definitions =======================

[homes]
comment = Home Directories
browseable = no
writable = yes

[data]
comment = HTTP server files
valid users = my_user_name
path = /xxxxx
read only = no
public = no

[public]
comment = Public Stuff
path = /xxxxx
public = yes
read only = yes
write list = @root my_user_name

[bazzix]

resco & network plugin doesn't show it at all, i tried the ip address etc. but didn't work
VM Net browser can find the samba machine, but doesn't show any share that should be available..

[johnpatcher]

I think that not the server is the problem, but the client is. In the options of Resco Explorer you can set up the option "Use SMB Signatures" to "never" and disable "Allow cleartext password (no excryption)".

After that it should work just fine, at least it works for me three times ...

[bazzix]

still doesn't work for me.. I'll try upgrading the phone first when there is an official upgrade available, don't want to viod the warranty..

[ftr]

It's strange in resco my computer name is only visible at begining of samba start (forced to restart samba to view computer) but folders shared not visible.

[ethen]

Hi everyone
I cannot access any samba shares. I think that required files (redir.dll,netbios.dll) are missing on my rom (t-mobile branded diamond). Any idea, how to get them and get them working?
Thanks a lot
david

[Fmstrat]

So I have the same problem, sort of. Tried all the mentioned methods around to no avail. Also, I keep seeing people mentioning:

"Change HKLM\Comm\SecurityProviders\NTLM\LmCompatibilityLe vel"

Of course, there is no such key. I'm assuming these people mean LmCompatibilityLevelClient. In either case, doesn't work for me. Also the Comm/Redir folder doesn't even exist in my registry (Touch Pro or Mogul with WM6.1 stock).

So both my devices have the issue. When connecting to a samba share, I get the "can't find resource". When connecting to a Vista share, it locks up the phone after I type in the password for the share and hit OK. This is using Resco.

On an interesting note, the only traffic I see from the phone in Wireshark is a netbios name request. Nothing else when trying to connect to either host.

I have the wifi connection set up to use my "Work" network. I have tried this with Internet but the same things happen.

[onlineemails]

hi guys i had the same problem BUT I had Solved IT
when i set my ip address manually i can see the computers in resco but cannot access their shares but after changing my ip address to automatic (dhcp) i am able to browse the shares very easily no registry changes is needed, but i dont know that it takes that enables me please let me know so i can set my ip address manually.:D

[vince2773]

I had the same problems decribed here and solved them

http://forum.xda-developers.com/showpost.php?p=8232148&postcount=244

HTC HD2 Leo
Stock 1.66 ITA Rom (WinMo 6.5)
Gaz Touch Tools PR 1.4
D-Link DNS-323 Samba NAS