|
||||||
| Forums FAQ | Members List | Search | Today's Posts | Mark Forums Read |
| Network/Internet Questions about internet applications, network configuration, usage (SAMBA, network printing, NFS) |
![]() |
|
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
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) ------------------------------------------ 1) Ping 192.168.1.37 Results in Reply form 192.168.1.37 2) 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 3) linux-pd:~ # nmblookup -B LINUX-PD __SAMBA__ querying __SAMBA__ on 127.0.0.2 192.168.1.36 __SAMBA__<00> 4) 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> 5) 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: \> 6) 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
__________________
Pentium D 820, 2.80GHz, Intel D945PSN ATX, evga geforce 7600GT 256MB PCIE, Geil DDR2, (1GB x 2) Dual Channel 667MHz Suse 11 x86-64bit |
|
|||
|
anyone have any suggestions?
qu1nn
__________________
Pentium D 820, 2.80GHz, Intel D945PSN ATX, evga geforce 7600GT 256MB PCIE, Geil DDR2, (1GB x 2) Dual Channel 667MHz Suse 11 x86-64bit |
|
||||
|
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 |
|
|||
|
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
__________________
Pentium D 820, 2.80GHz, Intel D945PSN ATX, evga geforce 7600GT 256MB PCIE, Geil DDR2, (1GB x 2) Dual Channel 667MHz Suse 11 x86-64bit |
|
||||
|
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 |
|
|||
|
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
__________________
Pentium D 820, 2.80GHz, Intel D945PSN ATX, evga geforce 7600GT 256MB PCIE, Geil DDR2, (1GB x 2) Dual Channel 667MHz Suse 11 x86-64bit |
|
|||
|
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. |
|
|||
|
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. |
|
|||
|
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 op_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....
__________________
Pentium D 820, 2.80GHz, Intel D945PSN ATX, evga geforce 7600GT 256MB PCIE, Geil DDR2, (1GB x 2) Dual Channel 667MHz Suse 11 x86-64bit |
|
|||
|
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 |
![]() |
|
| Bookmarks |
| Thread Tools | |
| Display Modes | |
|
|