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

[qu1nn]

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]

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)

[qu1nn]

****!!!!!!!



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

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

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

[qu1nn]

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

qu1nn wrote:

>
> too early to celibrate.
>
> resco is messed up see FAQ 'HERE'
> (http://www.resco.net/pocketpc/explor...sp?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.

PV wrote:

> qu1nn wrote:
>
>>
>> too early to celibrate.
>>
>> resco is messed up see FAQ 'HERE'
>> (http://www.resco.net/pocketpc/explor...sp?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? ;-)


--
P. V.
Cogito cogito ergo cogito sum.

[qu1nn]

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 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.