Cannot map to a Samba Share, but xp notebook can?

English Network/Internet
1

Hello,

Problem: Cannot get my pda (HTC Mogul) to connect to a samba share.
Behavior: Resco File Explorer (V7.03) keeps asking for a password when I try to map to a samba share.

Basic Setup Information:
ROUTER: Dynamic Type Configuration acting as a DHCP Server. The DNS is Automagic from the IP.
LAPTOP (windows xp): 192.168.1.38 / 255.255.255.0
SAMBA_PC (Suse 11) : 192.168.1.36 / 255.255.255.0
PDA (Sprint Mogul, Windows Mobile 6 Pro): 192.168.1.37 / 255.255.255.0

-----Below is my current smb.conf---------------

smb.conf is the main Samba configuration file. You find a full commented

version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the

samba-doc package is installed.

Date: 2008-06-07

[global]
workgroup = MCHOME
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
map to guest = Bad User
include = /etc/samba/dhcp.conf
logon path = \%L\profiles.msprofile
logon home = \%L%U.9xprofile
logon drive = P:
usershare allow guests = Yes
use spnego = No
[homes]
comment = Home Directories
valid users = %S, %D%w%S
browseable = No
read only = No
inherit acls = Yes
[profiles]
comment = Network Profiles Service
path = %H
read only = No
store dos attributes = Yes
create mask = 0600
directory mask = 0700
[users]
comment = All users
path = /home
read only = No
inherit acls = Yes
veto files = /aquota.user/groups/shares/
[groups]
comment = All groups
path = /home/groups
read only = No
inherit acls = Yes
[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0600
browseable = No
[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin root
force group = ntadmin
create mask = 0664
directory mask = 0775

[linuxpodcasts]
comment = downloaded shows
inherit acls = Yes
path = /home/jason/Podcasts/
read only = No

[lacie]
comment = storage drive
inherit acls = Yes
path = /media/disk/
read only = No

PDA TESTING:

  1. Ping \LINUX-PD\lacie
    Results: 24.A.B.C
    Note: this number is unknown. It is only similar to the Router Configuration in the first number!

  2. Ping 192.168.1.36
    Results with Reply from 192.168.1.36

  3. Ping \LAPTOP
    Results 24.A.B.C
    Note: This is the same number as PDA Testing #1

LAPTOP TESTING:

  1. Ping \LINUX-PD
    Results: 24.A.B.C .Qu1nnLAN
    Note: This is the same number as PDA Testing #1 including the name of the wireless lan!

  2. Ping 192.168.1.36
    Results with reply from 192.168.1.36

  3. Ping 192.168.1.37
    Results with reply from 192.168.1.37

  4. net view \LINUX-PD
    << shows all of the shares , Not Shown, The Command Completed successfully >>

  5. net use g: \LINUX-PD\lacie
    << asks for username / pass. The Command Completed successfully >>

  6. From File MANAGER, I can sucessfully browse the network and view the shares!

From XP > Command Prompt: ipconfig /all
Windows IP config:
Host Name: LAPTOP
Primary DNS Suffix:
Node Type: Unknown
IP Routing Enabled: NO
WINS Proxy Enabled: NO
DNS Suffix Search List: Qu1nnLAN
…
Ethernet adapter wireless Network Connection
Connection Specific DNS Suffix: Qu1nnLAN
…
Connection
DHCP Enabled: Yes
Autoconfig Enabled: Yes
IP Address: 192.168.1.38
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.1
DHCP Server: 192.168.1.1
DNS Servers: 24.W.X.Y
24.W.X.Z

LINUX-PD TESTING: (Includes steps from Chapter 38 of the Samba Checklist)

Ping 192.168.1.37
Results in Reply form 192.168.1.37

linux-pd:~ # smbclient -L LINUX-pd
Enter password:
Domain=[MCHOME] OS=[Unix] Server=[Samba 3.2.0rc1-22.1-1795-SUSE-SL11.0]

Sharename Type Comment

profiles Disk Network Profiles Service
users Disk All users
groups Disk All groups
print$ Disk Printer Drivers
linuxpodcasts Disk downloaded shows
lacie Disk storage drive
IPC$ IPC IPC Service (Samba 3.2.0rc1-22.1-1795-SUSE-SL11.0)
Photosmart_3200 Printer Photosmart 3210
HIDDEN Disk Home Directories
Domain=[MCHOME] OS=[Unix] Server=[Samba 3.2.0rc1-22.1-1795-SUSE-SL11.0]

Server Comment

LAPTOP Pentium M750 1.86GHz, 1GB RAM
LINUX-PD Samba 3.2.0rc1-22.1-1795-SUSE-SL11.0

Workgroup Master

MCHOME LINUX-PD

linux-pd:~ # nmblookup -B LINUX-PD SAMBA
querying SAMBA on 127.0.0.2
192.168.1.36 SAMBA<00>

linux-pd:~ # nmblookup -d 2 ‘*’
added interface eth0 ip=fe80::213:20ff:fecb:7cbb%eth0 bcast=fe80::ffff:ffff:ffff:ffff%eth0 netmask=ffff:ffff:ffff:ffff::
added interface eth0 ip=192.168.1.36 bcast=192.168.1.255 netmask=255.255.255.0
querying * on 192.168.1.255
Got a positive name query response from 192.168.1.36 ( 192.168.1.36 )
192.168.1.36 *<00>

linux-pd:~ # smbclient //LINUX-PD/lacie
Enter HIDDEN password:
Domain=[MCHOME] OS=[Unix] Server=[Samba 3.2.0rc1-22.1-1795-SUSE-SL11.0]
smb: &gt;

linux-pd:~ # nmblookup -M MCHOME
querying MCHOME on 192.168.1.255
192.168.1.36 MCHOME<1d>

Additional Questions:

  1. when in a linux console and you are pinging a IP, how to you stop the continuous pinging?
  2. how do you find the machine name on the PDA similar to how the LINUX-PD = 192.168.1.36?
  3. why is the wireless router name showing up when I ping?

I am at a loss.
I will be posting to a Resco forum as well.
Any suggestions helping this newb would be great.

Thank you for your time
qu1nn

2

anyone have any suggestions?

qu1nn

3

qu1nn wrote:

>
> Hello,
>
> Problem: Cannot get my pda (HTC Mogul) to connect to a samba share.
> Behavior: Resco File Explorer (V7.03) keeps asking for a password when
> I try to map to a samba share.

I’ve found that allowing a windows machine to connect to a samba hosted
share needs a few more options set.

Specifically, for each share you wish to be able to browse/use from a
windows machine (without being prompted to log in), you need to add:

guest ok = yes

If you don’t, you will need to add each windows machine’s username to samba,
and create a password for them as well. This is seperate from the users on
the linux box.

to add a user:
smbpasswd -a USERNAME
{you’ll be prompted for a password}

To add a user with a null password:
smbpasswd -a USERNAME -n

To delete a samba user:
smbpasswd -x USERNAME

the smbpasswd man page (man smbpasswd) is your friend.

You must also be aware of the permissions involved with using guest access
for samba shares too. guest access is based on the ‘other’ permissions
(third triplet), unless you use the ‘force group = somegroup’ and/or ‘force
user = someuser’, which cause samba to access the share with that group or
as that user.

For shares needing write access, remember the ‘read only = no’ and ‘write ok
= yes’ options, also, the ‘force xxx’ options (above) are useful for public
shares.

Loni

–
L R Nix
lornix@lornix.com

4

thank you for responding.
I have it setup so that the same username/pass is used.

Is it not ok to have the same username/password regardless if it is a pda or windows xp?

being able to access from xp notebook is no problem, been able to to that since I originally posted.

The pda cannot access the share for some reason that is driving me nuts.

thank you again
qu1nn

5

qu1nn wrote:

>
> thank you for responding.
> I have it setup so that the same username/pass is used.
>
> Is it not ok to have the same username/password regardless if it is a
> pda or windows xp?
>
> being able to access from xp notebook is no problem, been able to to
> that since I originally posted.
>
> The pda cannot access the share for some reason that is driving me
> nuts.
>
>
> thank you again
> qu1nn
>
>

whatever username/password you choose is fine, having one user/pass for the
two windows machines is a good idea, since you don’t have to remember which
is which.

Can the pda access shares on the XP box? Sometimes that functionality is
limited due to small memory limits in the pda.

–
L R Nix
lornix@lornix.com

6

I had this all in a prior installation of Suse 10.3
unfortunately I never saved the prior samba configuration.
I bet it is something simple that was changed in the suse 11 install, but I cannot figure what it is.
My guess is that it has something to do with how the pda is responding to the router (see PDA Testing Section)

the pda had no problem accessing files on the linux box.

I am not sharing any files on the laptop.

Thank you for your response.
qu1nn

7

qu1nn wrote:

>
> I had this all in a prior installation of Suse 10.3
> unfortunately I never saved the prior samba configuration.
> I bet it is something simple that was changed in the suse 11 install,
> but I cannot figure what it is.
> My guess is that it has something to do with how the pda is responding
> to the router (see PDA Testing Section)
>
>
>
>
> the pda had no problem accessing files on the linux box.
>
> I am not sharing any files on the laptop.
>
> Thank you for your response.
> qu1nn
>
>
qu1nn;

One thing that changed with Samba 3.2.0 was how it handled lanman authorization.
Add to your /etc/samba/smb.conf the parameter “lanman auth = yes” to the
global section. ( In prior versions that was the default.) A couple of weeks
ago someone with a game box had a similar problem, which this cured. Lanman
is the method of Windows 9X and is probably used on most of these small
devices. Be sure to restart the smpd after you change smb.conf, the command
is “rcsmb restart” . All of this needs to be done as root. If you need to
link to the pda from Linux you should also add the parameter “client lanman
auth = yes”

If making these changes does not help, you should look
in /var/log/samba/log.smbd to see what happens when you try to login. ( You
might need to add the parameter “log level =3” to your smb.conf global section
to get more information in the log; after you get things fixed, remove it so
your logs to grow too large.)

P. V.
Only fools rush in where angels fear to tread.

8

PV wrote:

> qu1nn wrote:
>
>>
>> I had this all in a prior installation of Suse 10.3
>> unfortunately I never saved the prior samba configuration.
>> I bet it is something simple that was changed in the suse 11 install,
>> but I cannot figure what it is.
>> My guess is that it has something to do with how the pda is responding
>> to the router (see PDA Testing Section)
>>
>>
>>
>>
>> the pda had no problem accessing files on the linux box.
>>
>> I am not sharing any files on the laptop.
>>
>> Thank you for your response.
>> qu1nn
>>
>>
> qu1nn;
>
> One thing that changed with Samba 3.2.0 was how it handled lanman
> authorization.
> Add to your /etc/samba/smb.conf the parameter “lanman auth = yes” to the
> global section. ( In prior versions that was the default.) A couple of weeks
> ago someone with a game box had a similar problem, which this cured. Lanman
> is the method of Windows 9X and is probably used on most of these small
> devices. Be sure to restart the smpd after you change smb.conf, the command

OOPS: should read " restart the smbd after "
> is “rcsmb restart” . All of this needs to be done as root. If you need to
> link to the pda from Linux you should also add the parameter “client lanman
> auth = yes”
>
> If making these changes does not help, you should look
> in /var/log/samba/log.smbd to see what happens when you try to login. ( You
> might need to add the parameter “log level =3” to your smb.conf global section
> to get more information in the log; after you get things fixed, remove it so
> your logs to grow too large.)

–
P. V.
Only fools rush in where angels fear to tread.

9

wow, something is seriously up:

------------------here is the current samba conf:

[global]
workgroup = MCHOME
map to guest = Bad User
lanman auth = Yes
log level = 3
use spnego = No
printcap name = cups
logon path = \%L\profiles.msprofile
logon drive = P:
logon home = \%L%U.9xprofile
usershare allow guests = Yes
cups options = raw
include = /etc/samba/dhcp.conf

[homes]
comment = Home Directories
valid users = %S, %D%w%S
read only = No
inherit acls = Yes
browseable = No

[profiles]
comment = Network Profiles Service
path = %H
read only = No
create mask = 0600
directory mask = 0700
store dos attributes = Yes

[users]
comment = All users
path = /home
read only = No
inherit acls = Yes
veto files = /aquota.user/groups/shares/

[groups]
comment = All groups
path = /home/groups
read only = No
inherit acls = Yes

[printers]
comment = All Printers
path = /var/tmp
create mask = 0600
printable = Yes
browseable = No

[print$]
comment = Printer Drivers
path = /var/lib/samba/drivers
write list = @ntadmin, root
force group = ntadmin
create mask = 0664
directory mask = 0775

[linuxpodcasts]
comment = downloaded shows
path = /home/jason/Podcasts/
read only = No
inherit acls = Yes

[lacie]
comment = storage drive
path = /media/disk/
read only = No
inherit acls = Yes
------------------from log.smbd:----------------------------------

[2008/08/24 16:53:08, 3] smbd/sec_ctx.c:pop_sec_ctx(432) pop_sec_ctx (0, 0) - sec_ctx_stack_ndx = 0
[2008/08/24 16:53:08, 3] libsmb/ntlm_check.c:ntlm_password_check(373) ntlm_password_check: NO LanMan password set for user jason (and no NT password supplied)
[2008/08/24 16:53:08, 3] libsmb/ntlm_check.c:ntlm_password_check(457)
ntlm_password_check: LM password, NT MD4 password in LM field and LMv2 failed for user jason
[2008/08/24 16:53:08, 2] auth/auth.c:check_ntlm_password(318)
check_ntlm_password: Authentication for user [jason] → [jason] FAILED with error NT_STATUS_WRONG_PASSWORD
[2008/08/24 16:53:08, 3] smbd/error.c:error_packet_set(61)
error packet at smbd/sesssetup.c(1725) cmd=115 (SMBsesssetupX) NT_STATUS_LOGON_FAILURE
[2008/08/24 16:53:33, 3] smbd/sec_ctx.c:set_sec_ctx(324)
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2008/08/24 16:53:33, 2] smbd/server.c:deadtime_fn(1039)
Closing idle connection
[2008/08/24 16:53:33, 3] smbd/server.c:msg_exit_server(223)
got a SHUTDOWN message
[2008/08/24 16:53:33, 3] smbd/sec_ctx.c:set_sec_ctx(324)
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2008/08/24 16:53:33, 3] smbd/connection.c:yield_connection(31)
Yielding connection to
[2008/08/24 16:53:33, 3] smbd/server.c:exit_server_common(944)
Server exit (normal exit)
[2008/08/24 16:55:11, 3] smbd/process.c:check_reload(1877)
Printcap cache time expired.
… there is more but I cut it out.

so I see some errors with the user/password, so I figure that I would add another user called jason2 so,

when doing the following as root:
smbpasswd -a jason2
New SMB password:
Retype new SMB password:
Failed to modify password entry for user jason2

so I would guess that something is definately amiss.

any help would be great…

10

qu1nn wrote:

>
> wow, something is seriously up:
>
>
>
> ------------------here is the current samba conf:
>
>
<snip, see previous post>
>
>
> so I see some errors with the user/password, so I figure that I would
> add another user called jason2 so,
>
> when doing the following as root:
> smbpasswd -a jason2
> New SMB password:
> Retype new SMB password:
> Failed to modify password entry for user jason2
>
>
> so I would guess that something is definately amiss.
>
>
> any help would be great…
>
qu1nn;

Is Jason2 a valid linux user? The samba users must also be valid Linux users.
Add a user jason2 and try again. However, “jason” should work. What do you
see with “pdbedit -L” (run as root)? Does it show a user jason? If not run
smbpasswd -a jason; if it does try “smbpasswd jason” and reset the password.
Remember linux is case sensitive.

If you look at this:

>[2008/08/24 16:53:08, 2] auth/auth.c:check_ntlm_password(318)
>check_ntlm_password: Authentication for user [jason] -> [jason]
>FAILED with error NT_STATUS_WRONG_PASSWORD

it looks like you are just not sending the correct password.

–
P. V.
“The entropy of a closed system can never decrease”, 2nd Law of Thermodynamics

11

Thanks for Responding PV.

OK when I do pdbedit -L as root I get the following:

pdbedit -L

jason:1000:Jason MyLastNameHere
root:0:root

I have to be sending the correct password because it is the same one that is used in the Notebook. Plus this can be proven at the command prompt with smbclient -L:

smbclient -L LINUX-PD
Enter jason’s password:
Domain=[MCHOME] OS=[Unix] Server=[Samba 3.2.0rc1-22.1-1795-SUSE-SL11.0]

    Sharename       Type      Comment
    ---------       ----      -------
    profiles        Disk      Network Profiles Service
    users           Disk      All users
    groups          Disk      All groups
    print$          Disk      Printer Drivers
    linuxpodcasts   Disk      downloaded shows
    lacie           Disk      storage drive
    IPC$            IPC       IPC Service (Samba 3.2.0rc1-22.1-1795-SUSE-SL11.0)
    Photosmart_3200 Printer   Photosmart 3210
    jason           Disk      Home Directories

Domain=[MCHOME] OS=[Unix] Server=[Samba 3.2.0rc1-22.1-1795-SUSE-SL11.0]

    Server               Comment
    ---------            -------
    HP_MCNOTE            Pentium M750 1.86GHz, 1GB RAM
    LINUX-PD             Samba 3.2.0rc1-22.1-1795-SUSE-SL11.0

    Workgroup            Master
    ---------            -------
    MCHOME               HP_MCNOTE

Could there be another reason why the password is rejected? Encryption setting or something incorrect with the config file?

Plus I have tried a ridiculous amount of times on the PDA.
Remember I cut out some of the errors from the log file. If you want me to post more I will.

I may also try to create a new user in LINUX-PD then in SMBPASSWD -a, to see what happens, I will post back.

One thing which continues to bother me is why, when I ping \LINUX-PD from the LAPTOP (192.168.1.x) would I receive the reply address 24.A.B.C ???

Thank you for your time
qu1nn

12

here is a full set of logs after another attempt:

From the LOG.NNDB

[2008/08/24 22:00:00, 2] nmbd/nmbd_elections.c:send_election_dgram(40)
send_election_dgram: Sending election packet for workgroup MCHOME on subnet 192.168.1.36
[2008/08/24 22:00:02, 2] nmbd/nmbd_elections.c:send_election_dgram(40)
send_election_dgram: Sending election packet for workgroup MCHOME on subnet 192.168.1.36
[2008/08/24 22:00:04, 2] nmbd/nmbd_elections.c:send_election_dgram(40)
send_election_dgram: Sending election packet for workgroup MCHOME on subnet 192.168.1.36
[2008/08/24 22:00:04, 2] nmbd/nmbd_elections.c:run_elections(203)
run_elections: >>> Won election for workgroup MCHOME on subnet 192.168.1.36 <<<
[2008/08/24 22:00:04, 2] nmbd/nmbd_become_lmb.c:become_local_master_browser(524)
become_local_master_browser: Awaiting potential browser state. Current state is 5
[2008/08/24 22:02:22, 3] nmbd/nmbd_incomingrequests.c:process_name_registration_request(219)
process_name_registration_request: Name registration for name WM_PDA<00> IP 192.168.1.37 on subnet 192.168.1.36
[2008/08/24 22:02:22, 3] nmbd/nmbd_incomingrequests.c:process_name_registration_request(219)
process_name_registration_request: Name registration for name WM_PDA<00> IP 192.168.1.37 on subnet 192.168.1.36
[2008/08/24 22:02:22, 3] nmbd/nmbd_incomingrequests.c:process_name_registration_request(219)
process_name_registration_request: Name registration for name WM_PDA<00> IP 192.168.1.37 on subnet 192.168.1.36
[2008/08/24 22:02:22, 3] nmbd/nmbd_incomingrequests.c:process_name_registration_request(219)
process_name_registration_request: Name registration for name WM_PDA<00> IP 192.168.1.37 on subnet 192.168.1.36
[2008/08/24 22:03:02, 3] nmbd/nmbd_incomingrequests.c:process_name_query_request(453)
process_name_query_request: Name query from 192.168.1.37 on subnet 192.168.1.36 for name LINUX-PD<20>
[2008/08/24 22:03:02, 3] nmbd/nmbd_incomingrequests.c:process_name_query_request(568)
OK
[2008/08/24 22:03:32, 3] nmbd/nmbd_sendannounce.c:send_host_announcement(207)
send_host_announcement: type 819a03 for host LINUX-PD on subnet 192.168.1.36 for workgroup MCHOME

From the LOG.SMBD
[2008/08/24 22:03:02, 3] smbd/process.c:check_reload(1877)
Printcap cache time expired.
[2008/08/24 22:03:02, 3] printing/pcap.c:pcap_cache_reload(116)
reloading printcap cache
[2008/08/24 22:03:02, 3] printing/pcap.c:pcap_cache_reload(223)
reload status: ok
[2008/08/24 22:03:02, 3] smbd/oplock.c:init_oplocks(875)
init_oplocks: initializing messages.
[2008/08/24 22:03:02, 3] smbd/oplock_linux.c:linux_init_kernel_oplocks(285)
Linux kernel oplocks enabled
[2008/08/24 22:03:02, 3] smbd/process.c:process_smb(1549)
Transaction 0 of length 72 (0 toread)
[2008/08/24 22:03:02, 2] smbd/reply.c:reply_special(425)
netbios connect: name1=LINUX-PD name2=_CERDR2763F507
[2008/08/24 22:03:02, 2] smbd/reply.c:reply_special(432)
netbios connect: local=linux-pd remote=_cerdr2763f507, name type = 0
[2008/08/24 22:03:02, 3] smbd/process.c:process_smb(1549)
Transaction 0 of length 51 (0 toread)
[2008/08/24 22:03:02, 3] smbd/process.c:switch_message(1361)
switch message SMBnegprot (pid 7955) conn 0x0
[2008/08/24 22:03:02, 3] smbd/sec_ctx.c:set_sec_ctx(324)
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2008/08/24 22:03:02, 3] smbd/negprot.c:reply_negprot(568)
Requested protocol [NT LM 0.12]
[2008/08/24 22:03:02, 3] smbd/negprot.c:reply_nt1(373)
not using SPNEGO
[2008/08/24 22:03:02, 3] smbd/negprot.c:reply_negprot(673)
Selected protocol NT LM 0.12
[2008/08/24 22:03:18, 3] smbd/process.c:process_smb(1549)
Transaction 1 of length 244 (0 toread)
[2008/08/24 22:03:18, 3] smbd/process.c:switch_message(1361)
switch message SMBsesssetupX (pid 7955) conn 0x0
[2008/08/24 22:03:18, 3] smbd/sec_ctx.c:set_sec_ctx(324)
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2008/08/24 22:03:18, 3] smbd/sesssetup.c:reply_sesssetup_and_X(1409)
wct=13 flg2=0x9001
[2008/08/24 22:03:18, 3] smbd/sesssetup.c:reply_sesssetup_and_X(1608)
Domain=[MCHOME] NativeOS=[Windows CE 502] NativeLanMan=[Windows CE 502] PrimaryDomain=]
[2008/08/24 22:03:18, 2] smbd/sesssetup.c:setup_new_vc_session(1363)
setup_new_vc_session: New VC == 0, if NT4.x compatible we would close all old resources.
[2008/08/24 22:03:18, 3] smbd/sesssetup.c:reply_sesssetup_and_X(1624)
sesssetupX:name=[MCHOME][jason]@[_cerdr2763f507]
[2008/08/24 22:03:18, 3] auth/auth.c:check_ntlm_password(220)
check_ntlm_password: Checking password for unmapped user [MCHOME][jason]@[_cerdr2763f507] with the new password interface
[2008/08/24 22:03:18, 3] auth/auth.c:check_ntlm_password(223)
check_ntlm_password: mapped user is: [LINUX-PD][jason]@[_cerdr2763f507]
[2008/08/24 22:03:18, 3] smbd/sec_ctx.c:push_sec_ctx(224)
push_sec_ctx(0, 0) : sec_ctx_stack_ndx = 1
[2008/08/24 22:03:18, 3] smbd/uid.c:push_conn_ctx(357)
push_conn_ctx(0) : conn_ctx_stack_ndx = 0
[2008/08/24 22:03:18, 3] smbd/sec_ctx.c:set_sec_ctx(324)
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 1
[2008/08/24 22:03:18, 3] smbd/sec_ctx.c:push_sec_ctx(224)
push_sec_ctx(0, 0) : sec_ctx_stack_ndx = 2
[2008/08/24 22:03:18, 3] smbd/uid.c:push_conn_ctx(357)
push_conn_ctx(0) : conn_ctx_stack_ndx = 1
[2008/08/24 22:03:18, 3] smbd/sec_ctx.c:set_sec_ctx(324)
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 2
[2008/08/24 22:03:18, 3] smbd/sec_ctx.c:pop_sec_ctx(432)
pop_sec_ctx (0, 0) - sec_ctx_stack_ndx = 1
[2008/08/24 22:03:18, 3] smbd/sec_ctx.c:push_sec_ctx(224)
push_sec_ctx(0, 0) : sec_ctx_stack_ndx = 2
[2008/08/24 22:03:18, 3] smbd/uid.c:push_conn_ctx(357)
push_conn_ctx(0) : conn_ctx_stack_ndx = 1
[2008/08/24 22:03:18, 3] smbd/sec_ctx.c:set_sec_ctx(324)
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 2
[2008/08/24 22:03:18, 3] smbd/sec_ctx.c:pop_sec_ctx(432)
pop_sec_ctx (0, 0) - sec_ctx_stack_ndx = 1
[2008/08/24 22:03:18, 3] smbd/sec_ctx.c:push_sec_ctx(224)
push_sec_ctx(0, 0) : sec_ctx_stack_ndx = 2
[2008/08/24 22:03:18, 3] smbd/uid.c:push_conn_ctx(357)
push_conn_ctx(0) : conn_ctx_stack_ndx = 1
[2008/08/24 22:03:18, 3] smbd/sec_ctx.c:set_sec_ctx(324)
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 2
[2008/08/24 22:03:18, 3] smbd/sec_ctx.c:pop_sec_ctx(432)
pop_sec_ctx (0, 0) - sec_ctx_stack_ndx = 1
[2008/08/24 22:03:18, 3] smbd/sec_ctx.c:pop_sec_ctx(432)
pop_sec_ctx (0, 0) - sec_ctx_stack_ndx = 0
[2008/08/24 22:03:18, 3] libsmb/ntlm_check.c:ntlm_password_check(373)
ntlm_password_check: NO LanMan password set for user jason (and no NT password supplied)
[2008/08/24 22:03:18, 3] libsmb/ntlm_check.c:ntlm_password_check(457)
ntlm_password_check: LM password, NT MD4 password in LM field and LMv2 failed for user jason
[2008/08/24 22:03:18, 2] auth/auth.c:check_ntlm_password(318)
check_ntlm_password: Authentication for user [jason] -> [jason] FAILED with error NT_STATUS_WRONG_PASSWORD
[2008/08/24 22:03:18, 3] smbd/error.c:error_packet_set(61)
error packet at smbd/sesssetup.c(1725) cmd=115 (SMBsesssetupX) NT_STATUS_LOGON_FAILURE
[2008/08/24 22:04:02, 3] smbd/sec_ctx.c:set_sec_ctx(324)
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2008/08/24 22:04:02, 2] smbd/server.c:deadtime_fn(1039)
Closing idle connection
[2008/08/24 22:04:02, 3] smbd/server.c:msg_exit_server(223)
got a SHUTDOWN message
[2008/08/24 22:04:02, 3] smbd/sec_ctx.c:set_sec_ctx(324)
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2008/08/24 22:04:02, 3] smbd/connection.c:yield_connection(31)
Yielding connection to
[2008/08/24 22:04:02, 3] smbd/server.c:exit_server_common(944)
Server exit (normal exit)

13

****!!!

I created a new user account in YAST: Jason2
did the smbclient -a Jason2
it took the password,

then I went to Resco
redid the following commands:
MENU > FILE > NETWORK > MAP Drive
typed in \LINUX-PD\linuxpodcasts

Selected Permanent Connection
Selected to Connect as a different user
entered username = Jason2
entered password
selected DONE

then it came up with asking me the password for OLD USERNAME jason, I entered the correct username/password and then it worked!

and get this …
when I repeated the process to map the drive using with the ORIGINAL USERNAME jason it then worked as well!!!

I think that it was something definitely in the Resco Explorer application that got cleared out and I will post this at the resco.net forums as a bug.

Thanks for your assistance PV

whahoo!

qu1nn

14

qu1nn wrote:

>
> Thanks for Responding PV.
>
> OK when I do pdbedit -L as root I get the following:
> # pdbedit -L
> jason:1000:Jason MyLastNameHere
> root:0:root
>
> I have to be sending the correct password because it is the same one
> that is used in the Notebook. Plus this can be proven at the command
> prompt with smbclient -L:
>
> SMBCLIENT -L LINUX-PD
> ENTER JASON’S PASSWORD:
> DOMAIN=[MCHOME] OS=[UNIX] SERVER=[SAMBA
> 3.2.0RC1-22.1-1795-SUSE-SL11.0]
>
> SHARENAME TYPE COMMENT
> --------- ---- -------
> PROFILES DISK NETWORK PROFILES SERVICE
> USERS DISK ALL USERS
> GROUPS DISK ALL GROUPS
> PRINT$ DISK PRINTER DRIVERS
> LINUXPODCASTS DISK DOWNLOADED SHOWS
> LACIE DISK STORAGE DRIVE
> IPC$ IPC IPC SERVICE (SAMBA
> 3.2.0RC1-22.1-1795-SUSE-SL11.0)
> PHOTOSMART_3200 PRINTER PHOTOSMART 3210
> JASON DISK HOME DIRECTORIES
> DOMAIN=[MCHOME] OS=[UNIX] SERVER=[SAMBA
> 3.2.0RC1-22.1-1795-SUSE-SL11.0]
>
> SERVER COMMENT
> --------- -------
> HP_MCNOTE PENTIUM M750 1.86GHZ, 1GB RAM
> LINUX-PD SAMBA 3.2.0RC1-22.1-1795-SUSE-SL11.0
>
> WORKGROUP MASTER
> --------- -------
> MCHOME HP_MCNOTE
>
>
>
> Could there be another reason why the password is rejected? Encryption
> setting or something incorrect with the config file?
>
>
>
>
>
> Plus I have tried a ridiculous amount of times on the PDA.
> Remember I cut out some of the errors from the log file. If you want
> me to post more I will.
>
> I may also try to create a new user in LINUX-PD then in SMBPASSWD -a,
> to see what happens, I will post back.
>
> One thing which continues to bother me is why, when I ping \LINUX-PD
> from the LAPTOP (192.168.1.x) would I receive the reply address 24.A.B.C
> ???
>
>
>
> Thank you for your time
> qu1nn
>
>
qu1nn;
Why do you have “use spnego = no” in your smb.conf? Unless there is a really
good reason, I would leave it at the default value of yes, just comment that
line out. (See man smb.conf for information on this parameter.) I doubt that’s
your problem but it could be; for some reason the PDA is sending a bad
password. If you are typing it in correctly, then PDA must be doing something
(cap locks?, non-printing character? ) If you add “guest ok = yes” to the
share(s) you want the PDA to access, then use an invalid login name, you will
be mapped to the guest account ( which in SUSE is set to nobody) and be allowed
access to that (those) share(s). Alternatively, you can change “map to guest =
Bad User” to “map to guest = Bad Password”; this has the drawback that if
someone miss types their password, they will silently be logged in as guest and
wonder why Samba isn’t working. If you take either of these “guest”
alternatives, you need to set the linux permissions so that user “nobody” will
have the correct permissions (“chmod 755” or whatever you want, this is easiest
in the GUI)

P. V.
“The entropy of a closed system can never decrease”, 2nd Law of Thermodynamics

15

qu1nn wrote:

>
> ****!!!
>
>
>
> I created a new user account in YAST: Jason2
> did the smbclient -a Jason2
> it took the password,
>
> then I went to Resco
> redid the following commands:
> MENU > FILE > NETWORK > MAP Drive
> typed in \LINUX-PD\linuxpodcasts
>
> Selected Permanent Connection
> Selected to Connect as a different user
> entered username = Jason2
> entered password
> selected DONE
>
> then it came up with asking me the password for OLD USERNAME jason, I
> entered the correct username/password and then it worked!
>
> and get this …
> when I repeated the process to map the drive using with the ORIGINAL
> USERNAME jason it then worked as well!!!
>
> I think that it was something definitely in the Resco Explorer
> application that got cleared out and I will post this at the resco.net
> forums as a bug.
>
>
> Thanks for your assistance PV
>
> whahoo!
>
>
>
> qu1nn
>
>
Glad to see you have it working, have a tall cool one to celebrate!

P. V.
“The entropy of a closed system can never decrease”, 2nd Law of Thermodynamics

16

too early to celibrate.

resco is messed up see FAQ HERE

  1. per 8.8 I have to use SPNEGO=No, I tried many times with it set to yes, each time it was a no go.

  2. NEW problem. as can be seen in 8.5 recso holds passwords. I kinda goofed when selecting to save jason2 password as now it is what it holds. I tried to go into YAST user accounts and DISABLE the login of jason2, as an attempt to invalidate the account. I have been completely unsucessful at getting the jason account to be able to map the drive.

I can easily use the jason2 account in resco to view the files, however I have no permissions (as the linuxpodcasts directory resides under the jason homedirectory)… How do I change the permissions? I right clicked the properties of jason and change so that the group can view and modify content, I also selected to propagate it…however no luck

any suggestions on how to allow jason2 to have full acccess over jason homedir?

thanks again
qu1nn

17

qu1nn wrote:

>
> too early to celibrate.
>
> resco is messed up see FAQ ‘HERE’
> (http://www.resco.net/pocketpc/explorer/faq.asp?faq=network)
>
> 1) per 8.8 I have to use SPNEGO=No, I tried many times with it set to
> yes, each time it was a no go.
>
> 2) NEW problem. as can be seen in 8.5 recso holds passwords. I kinda
> goofed when selecting to save jason2 password as now it is what it
> holds. I tried to go into YAST user accounts and DISABLE the login of
> jason2, as an attempt to invalidate the account. I have been completely
> unsucessful at getting the jason account to be able to map the drive.
>
> I can easily use the jason2 account in resco to view the files, however
> I have no permissions (as the linuxpodcasts directory resides under the
> jason homedirectory)… How do I change the permissions? I right
> clicked the properties of jason and change so that the group can view
> and modify content, I also selected to propagate it…however no luck
>
Did you change the permissions on individual files you wish to share?

> any suggestions on how to allow jason2 to have full acccess over jason
> homedir?
>
>
> thanks again
> qu1nn
>
>

qu1nn;

I assume this is the share in question. If not just forget this message

>[linuxpodcasts]
> comment = downloaded shows
> path = /home/jason/Podcasts/
> read only = No
> inherit acls = Yes

Try adding the parameter “force user = jason” to the share. This should make
all connections to [linuxpodcasts] to act as user jason. Of course this means
that anyone who accesses this share will have access as jason.

Alternatively you could give “other” the desired rights to /home/jason/Podcasts
AND its contents, in this case you probably want to add the parameter “force
create mode = 766” or what ever you want. (Note: r=4,w=2,x=1; thus 766 gives
owner= r+w+x, group = r+w, o=r+w)

–
P. V.
Cogito cogito ergo cogito sum.

18

PV wrote:

> qu1nn wrote:
>
>>
>> too early to celibrate.
>>
>> resco is messed up see FAQ ‘HERE’
>> (http://www.resco.net/pocketpc/explorer/faq.asp?faq=network)
>>
>> 1) per 8.8 I have to use SPNEGO=No, I tried many times with it set to
>> yes, each time it was a no go.
>>
>> 2) NEW problem. as can be seen in 8.5 recso holds passwords. I kinda
>> goofed when selecting to save jason2 password as now it is what it
>> holds. I tried to go into YAST user accounts and DISABLE the login of
>> jason2, as an attempt to invalidate the account. I have been completely
>> unsucessful at getting the jason account to be able to map the drive.
<snip>
I had not read the FAQ when I last replied. As root, try the following:

pdbedit -x -u jason2

This should delete user jason2 from the Samba users (See: man pdbedit ).
Maybe your resco will then allow you to reset the password.

Have you considered leaving your resco unattended in a public place for a few
minutes? :wink:

–
P. V.
Cogito cogito ergo cogito sum.

19

Thank you for your help.
I added the force user command…things are working as I remember that they used to before the adventure began (at least so far).

I will be getting a new hard drive soon and I will end up remapping all of the shares to make things a bit simpler,

Thank you for taking the time to help me out pv

20

qu1nn wrote:

>
> Thank you for your help.
> I added the force user command…things are working as I remember
> that they used to before the adventure began (at least so far).
>
> I will be getting a new hard drive soon and I will end up remapping all
> of the shares to make things a bit simpler,
>
>
> Thank you for taking the time to help me out pv
>
>
qu1nn;

Glad it all works for you. Here is another, somewhat contorted method, that
should work.

  1. Change the samba password for jason to the same password as jason2. You can
    do this as user jason by entering “smbpasswd” it will prompt for the old pass
    word, then allow you to enter a new password. The samba password does not need
    to be the same as your Linux password, so there is no problem resetting it.

  2. As root edit /etc/samba/smbusers, by adding the line “jason = jason2”.
    Entries in this file have the format <linux_name> = <name1> <name2> etc. (any
    number of names separated by a space.) Any login with username <name1> or
    <name2> etc. will be mapped to linux user <linux_name>.

Thus when your PDA logs in as jason2 it will be automatically mapped to user
jason, and as long as the passwords agree, jason2 will magically become jason.

P.S. Don’t forget to reset your log level back to the default.

P. V.
Cogito cogito ergo cogito sum.