Re: [Samba] mount.cifs doesn't do japanese?
Bjoern> there has been a false assumption that a UTF-8 presentation of Bjoern> a filename never longer than the UTF-16 presentation of the Bjoern> same name. That's fatal for Japanese filenames. This should be Bjoern> fixed in the cifs version which will come with kernel 2.6.9. Is there a fix in patch form? I would like to back-port it to my 2.4.18 system. I absolutely do not have the option of changing my kernel :-( Speaking of which, is the 2.4 code being maintained anywhere? The last revision seems to be from February. Dave -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] mount.cifs doesn't do japanese?
Bjoern> there has been a false assumption that a UTF-8 presentation of Bjoern> a filename never longer than the UTF-16 presentation of the Bjoern> same name. That's fatal for Japanese filenames. This should be Bjoern> fixed in the cifs version which will come with kernel 2.6.9. I have to fix this in my linux-2.4.18 embedded system. Is it sufficient for me to just fix the conditions under which calls to cifs_strfromUCS_le() are made? That function already appears to return a proper length value, it just isn't being used. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] mount.cifs doesn't do japanese?
Bjoern> there has been a false assumption that a UTF-8 presentation of Bjoern> a filename never longer than the UTF-16 presentation of the Bjoern> same name. That's fatal for Japanese filenames. This should be Bjoern> fixed in the cifs version which will come with kernel 2.6.9. I have to use linux-2.4.18 in my embedded system. Any chance I can get this patch for it? Thanks, Dave -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] mount.cifs doesn't do japanese?
On a FC2 system (which includes kernel 2.6.5 and samba-3.0.3), I am able to use "smbmount" to mount filesystems with japanese filenames on them by specifying codepage=cp932. But when I mount with "mount.cifs" the translation from SJIS to UTF-8 isn't done right: # uname -a Linux 5nave 2.6.5-1.358 #1 Sat May 8 09:04:50 EDT 2004 i686 i686 i386 GNU/Linux # smbclient --version Version 3.0.3-5 # mount.cifs --version mount.cifs version: 1.2 # # smbmount //my-server/share /mnt/my-server -o codepage=cp932 Password: # ls -l /mnt/my-server total 4194336 drwxr-xr-x 1 root root 4096 Sep 3 15:24 ææè # umount /mnt/my-server # mount.cifs //my-server/share /mnt/my-server -o codepage=cp932 Password: # ls -l /mnt/my-server total 131072 drwxrwxrwx 1 root root 0 Sep 3 15:24 ææ? # How can I make mount.cifs properly read Japanese filenames? Thanks, Dave -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] smbmounting share with japanese name
I can use "net rpc share" to discover the names of shares on a windows computer that have Japanese characters in them. That works great. Now I want to mount those shares. But when I try to do so, it looks like this: # smbmount //myserver/新しいフォルダ -o iocharset=utf8,codepage=cp932 creating lame upcase table creating lame lowcase table 688: tree connect failed: ERRDOS - ERRnosuchshare (You specified an invalid share name) SMB connection failed # I have tried putting the argument in quotes (both double and single), to no avail. Any suggestions? Dave -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] prevent smbclient from trying 445?
When I use smbclient to access an IOMEGA NAS server, smbclient tries to access port 445 for a full five minutes before timing out: [2004/02/20 17:48:24, 10] lib/gencache.c:gencache_get(262) Returning valid cache entry: key = NBT/NAS_120_1#20, value = 192.168.123.161:0, timeout = Fri Feb 20 17:53:22 2004 [2004/02/20 17:48:24, 5] libsmb/namecache.c:namecache_fetch(201) name nas_120_1#20 found. [2004/02/20 17:48:24, 3] lib/util_sock.c:open_socket_out(698) Connecting to 192.168.123.161 at port 445 [2004/02/20 17:51:38, 2] lib/util_sock.c:open_socket_out(733) error connecting to 192.168.123.161:445 (Connection timed out) Next, smbclient goes on to contact it on port 139, and all works great right away. Can I direct smbclient to not use 445? Anyone have an idea why smbclient is getting stuck in this tar pit for five minutes? Thanks, Dave -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Help! Samba 3.0 can't use null password with OS X
AB> However, the issue as described seems to be the result of misusing AB> the idea of 'null passwords' on the server - ie, storing the null AB> string as a password, rather than setting the 'no password AB> required' flag. If that is the case, why does 2.2.8a work fine? Dave -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Help! Samba 3.0 can't use null password with OS X
When I made the move to 3.0, I noticed that smbclient no longer works with null passwords. Am I missing something? I read the FAQ, which suggests that the server is rejecting the null password. But I know that null passwords work fine for the 2.2.8a client, so the server is not the issue. The FAQ recommends "smbclient -L host -U%", but I don't want to set the username to null. I want a non-null username with a null password. I traced the packets on the two smbclients, and I see several differences. The command I ran was: smbclient //g4-box-1/dood -I 192.168.5.90 -U dood I used the same command on both 2.2.8a and 3.0 systems. Here are the differences I saw in the packets: 1. client sends "Extended Security Negotiation: Extended security negotiation is supported" on 3.0, but not on 2.2.8a 2. 2.2.8a client sends ANSI Password, Unicode Password, and uppercased-account name. Meanwhile, 3.0 client doesn't send either passwords, and sends a lowercased-account name. I think this is actually the key here. 3. the "primary domain" sent by 2.2.8a is the client's default domain, while the "primary domain" sent by 3.0 is the domain of the share being accessed 4. 2.2.8a sends "SMB Command: Session Setup AndX (0x73)" and gets response "NT Status: STATUS_SUCCESS (0x)" 3.0 sends same command and gets response "NT Status: STATUS_LOGON_FAILURE (0xc06d)" Any suggestions how to get 3.0 to work with null passwords? Thanks, Dave -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Security mode 0x03: smbclient-2.2.8a sends password, 3.0 doesn't
Thiago> Don't know why by I had to use a \n before the yes. Now it Thiago> worked. I don't understand --- if you are referring to the smb.conf file, it works fine for me already. It is smbclient-3.0 that doesn't work. Dave -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Security mode 0x03: smbclient-2.2.8a sends password, 3.0 doesn't
I'm having trouble accessing a share using smbclient-3.0. The same share (served by a samba server on linux) is accessible from the same account using smbclient-2.2.8a. Here is the command I'm using to access the share: smbclient '//adventure/dood' -I 192.168.5.11 -U dood The server's smb.conf file includes the following three lines: security = user encrypt passwords = yes null passwords = yes If I change the 'encrypt passwords' to '= no', smbclient-3.0 works fine. The problem is that I have the exact same problem on hosts over which I have no control of the smb.conf file, for example Mac OS X 10.3. 10.3 appears to have the same behavior as my linux samba host with the above three lines in the smb.conf. When I analyze the packets sent between the client and the server, I see the following difference in the frames (see attatchments for full frame decode): samba-2.2.8a sending encrypted null password:Byte Count (BCC): 26 >Account: dood >Primary Domain: WORKGROUP Note that the primary domain is also different: 3.0 uses the default domain WORKGROUP, while 2.2.8a uses the default domain of the client ("ABCD"). What can I do on the CLIENT side to make smbclient-3.0 send the encrypted null password? Thanks, Dave -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] smbclient null-password behavior differs between 3.0 and 2.2.8a
When I made the move to 3.0, I noticed that smbclient no longer works with null passwords. Am I missing something? I read the FAQ, which suggests that the server is rejecting the null password. But I know that null passwords work fine for the 2.2.8a client, so the server is not the issue. The FAQ recommends "smbclient -L host -U%", but I don't want to set the username to null. I want a non-null username with a null password. I traced the packets on the two smbclients, and I see several differences. The command I ran was: smbclient //g4-box-1/dood -I 192.168.5.90 -U dood I used the same command on both 2.2.8a and 3.0 systems. Here are the differences I saw in the packets: 1. client sends "Extended Security Negotiation: Extended security negotiation is supported" on 3.0, but not on 2.2.8a 2. 2.2.8a client sends ANSI Password, Unicode Password, and uppercased-account name. Meanwhile, 3.0 client doesn't send either passwords, and sends a lowercased-account name. I think this is actually the key here. 3. the "primary domain" sent by 2.2.8a is the client's default domain, while the "primary domain" sent by 3.0 is the domain of the share being accessed 4. 2.2.8a sends "SMB Command: Session Setup AndX (0x73)" and gets response "NT Status: STATUS_SUCCESS (0x)" 3.0 sends same command and gets response "NT Status: STATUS_LOGON_FAILURE (0xc06d)" Any suggestions how to get 3.0 to work with null passwords? Thanks, Dave -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Why doesn't my wins.dat list all the LMBs?
Me> Why aren't the LMBs listed in this file? The actual LMBs Me> can be found by running nmblookup on the two subnets: Gerald> This is by design. It's how browsing works. LMB are never Gerald> listed in WINS since there is no need. BY definition an LMB Gerald> is local to a broadcast subnet. LMB sync with the DMB, not Gerald> each other. Thanks, that makes sense. Me> I wanted to know which boxes were the LMBs and the DMB, so I Me> looked into the wins.dat on the WINS server. But in wins.dat, I Me> only see one line that has MSBROWSE in it: Me> Me> "^A^B__MSBROWSE__^B#01" 1066639333 255.255.255.255 e4R Me> Me> Is this supposed to be the DMB? Gerald> No. The DMB is workgroup<0x1b> OK, I can see that entry now. Excellent. So what is the "^A^B__MSBROWSE__^B#01" 1066639333 255.255.255.255 e4R entry for? Dave -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Why doesn't my wins.dat list all the LMBs?
My network looks like this: internet 192.168.0.0/24 router +++- internal 192.168.5.0/24 ||| router +-+--+- LNB--->mswin || (also a | | | client || samba | | || server) | | samba | | samba LNB>linux samba | linux WINS linux mswin client<-LNB I wanted to know which boxes were the LMBs and the DMB, so I looked into the wins.dat on the WINS server. But in wins.dat, I only see one line that has MSBROWSE in it: "^A^B__MSBROWSE__^B#01" 1066639333 255.255.255.255 e4R Is this supposed to be the DMB? Why the 255.255.255.255 address? I would expect there to be a host address there. Why aren't the LMBs listed in this file? The actual LMBs can be found by running nmblookup on the two subnets: # nmblookup -M -B 192.168.0.255 - querying ^A^B__MSBROWSE__^B on 192.168.0.255 192.168.0.13 ^A^B__MSBROWSE__^B<01> 192.168.0.100 ^A^B__MSBROWSE__^B<01> # nmblookup -M -B 192.168.5.255 - querying ^A^B__MSBROWSE__^B on 192.168.5.255 192.168.5.200 ^A^B__MSBROWSE__^B<01> Shouldn't these be registered by the WINS server? How can the LNBs get each others' lists if they can't look up the DMB on the WINS server? How can the DMB find the LMBs if it is not listed on the WINS server? In fact, the LNBs are NOT getting each others' lists: # smbclient -N -L 192.168.5.200 | grep ABCDMEDIA ABCDMEDIAKickin' Media Repository! NOGROUP ABCDMEDIA # smbclient -N -L 192.168.0.13 | grep ABCDMEDIA # As you can see, the LNB on the .5.0/24 network knows about ABCDMEDIA, but the LNB on the .0.0/24 network does not. Obviously something is not configured right. Any suggestions? Dave -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Is wins.dat supposed to list all LMB, or just the DMB?
My network looks like this: internet 192.168.0.0/24 router +++- internal 192.168.5.0/24 ||| router +-+--+- LNB--->mswin || (also a | | | client || samba | | || server) | | samba | | samba LNB>linux samba | linux WINS linux mswin client<-LNB I wanted to know which boxes were the LMBs and the DMB, so I looked into the wins.dat on the WINS server. But in wins.dat, I only see one line that has MSBROWSE in it: "^A^B__MSBROWSE__^B#01" 1066639333 255.255.255.255 e4R Is this supposed to be the DMB? Why the 255.255.255.255 address? I would expect there to be a host address there. Why aren't the LMBs listed in this file? The actual LMBs can be found by running nmblookup on the two subnets: # nmblookup -M -B 192.168.0.255 - querying ^A^B__MSBROWSE__^B on 192.168.0.255 192.168.0.13 ^A^B__MSBROWSE__^B<01> 192.168.0.100 ^A^B__MSBROWSE__^B<01> # nmblookup -M -B 192.168.5.255 - querying ^A^B__MSBROWSE__^B on 192.168.5.255 192.168.5.200 ^A^B__MSBROWSE__^B<01> Shouldn't these be registered by the WINS server? How can the LNBs get each others' lists if they can't look up the DMB on the WINS server? How can the DMB find the LMBs if it is not listed on the WINS server? In fact, the LNBs are NOT getting each others' lists: # smbclient -N -L 192.168.5.200 | grep ABCDMEDIA ABCDMEDIAKickin' Media Repository! NOGROUP ABCDMEDIA # smbclient -N -L 192.168.0.13 | grep ABCDMEDIA # As you can see, the LNB on the .5.0/24 network knows about ABCDMEDIA, but the LNB on the .0.0/24 network does not. Obviously something is not configured right. Any suggestions? Dave -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Understanding the role of DMB/LMB on a net that has a WINS server
John, thank you for your detailed answers. The roles of DMB/LMB are much more clear to me now. I also want to mention that the Samba documentation is excellent, and I learned very much from the NetworkBrowsing.html page. Kudos to you for doing a great documentation job! I have two more questions. The first: Me> I was not able to discover whether nmbd is *required* to be Me> running on a workstation that doesn't publish any shares, and just Me> uses smbclient or smbmount to access other servers' shares. John> Yes, nmbd is required - it provides the name resolution services John> for smbd. But I don't have to run smbd in order to be a client, do I? In fact, I know I don't, because I can run "smbclient //SOMESVR/SOMESHARE" from my linux box, without that box running smbd or nmbd, and somehow the share name and server name gets resolved. So it seems to me that nmbd is *not* required to be running on a workstation that doesn't publish any shares. If that workstation will never be used to publish shares or serve as a master browser, is there any down-side to not installing nmbd? Question two: Are all types of netbios name that are listed in the table in http://ubiqx.org/cifs/Appendix-C.html resolved by a WINS server? For example, I have a windows box that responds to nmblookup like this: # nmblookup -A 192.168.0.111 Looking up status of 192.168.0.111 ABCDMEDIA <00> - M NOGROUP <00> - M ABCDMEDIA <03> - M ABCDMEDIA <20> - M NOGROUP <1e> - M NOGROUP <1d> - M ..__MSBROWSE__. <01> - M Would a WINS server store a record for each of the lines in this response? I saw mention that a WINS server only has to respond with up to 25 name resolutions per request. If a client makes a request for "ABCMEDIA", and if there happens to be more than 25 different records of various ABCMEDIA services, will some of those records not get returned? Thanks again for the excellent docs, Dave -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Understanding the role of DMB/LMB on a net that has a WINS server
John> Have you read chapter 10 of the Samba-HOWTO-Collection.pdf? What I have already read is this: http://us2.samba.org/samba/ftp/cvs_current/docs/htmldocs/NetworkBrowsing.html It looks like they contain the same text as the PDF to which you refer. Is it safe to assume that the HTML version I read is current? John> If this document does not clearly answer your questions please John> let me know so I can fix it. Question 1. Section 10.2 says: "To most people browsing means they can see the MS Windows and Samba servers in the Network Neighborhood, and when the computer icon for a particular server is clicked, it opens up and shows the shares and printers available on the target server." >From this, I gather that "browsing" is the act of enumerating and resolving published share names. Therefore, a workstation that doesn't publish any shares, and just uses smbclient or smbmount to access other servers' shares, must also make use of "browsing." Section 10.7.1 says: "Samba facilitates browsing. The browsing is supported by nmbd and is also controlled by options in the smb.conf file. Samba can act as a local browse master for a workgroup and the ability to support domain logons and scripts is now available." I was not able to discover whether nmbd is *required* to be running on a workstation that doesn't publish any shares, and just uses smbclient or smbmount to access other servers' shares. Question 2. The closest thing I found to a description of the actual process that a client goes through in order to "browse" was in 10.3.2 "TCP/IP without NetBios". This didn't go into any detail about the client's logic, but it did give the search order. Why this chapter is labeled "without NetBios" is unclear, since one of the client steps is to "3. Check the NetBios name cache". I couldn't find where it describes what a name cache is, but I guess it doesn't matter because the section that I really care about is 10.3.1 "NetBIOS over TCP/IP". But 10.3.1 does not go into detail of the client's resolution process. For example: If I have a client that wants to enumerate and access shares on a subnet, and that client knows the IP of the WINS server, is there any need for the client to use the "browsing" services of a DMB or LMB? What is the order of operations of the client? Here is what I imagine to be the case: 1. client asks LMB for a list of all available shares 2. LMB sends client the list of all known shares 3. for each name in the list of known shares, client asks WINS server for the server's IP address 4. WINS server replies with each name resolution I can't find anything in http://us2.samba.org/samba/ftp/cvs_current/docs/htmldocs/NetworkBrowsing.html that describes what is really happening at this level. I also could not find anything that says whether LMBs or DMBs actually do name resolution. I also don't understand why we need LMBs if we can always access a DMB. I also could not find anything in this document that talked about the difference between Microsoft's "B" "M" "P" and "H" hosts. If there is a WINS server, does there still have to be an LMB and DMB? If there is an LMB, why does the client need to access the WINS server directly? Why not just have the LMB do the resolution? It would result in less traffic. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Understanding the role of DMB/LMB on a net that has a WINS server
If I have a client that wants to enumerate and access shares on a subnet, and that client knows the IP of the WINS server, is there any need for the client to use the "browsing" services of a DMB or LMB? What is the order of operations of the client? Here is what I imagine to be the case: 1. client asks LMB for a list of all available shares 2. LMB sends client the list of all known shares 3. for each name in the list of known shares, client asks WINS server for the server's IP address 4. WINS server replies with each name resolution Is there a document which describes the protocol? I have read RFC 1001 and 1002 but they don't give a high-level procedure. I think the process is also slightly different for M and H hosts. If there is a WINS server, does there still have to be an LMB and DMB? If there is an LMB, why does the client need to access the WINS server directly? Why not just have the LMB do the resolution? It would result in less traffic. Thanks, Dave -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: How to find all workgroups being used on a subnet?
John> HAve you checked out 'findsmb' that is supplied as part of Samba? Yes, and I don't think it does what I want. It only does nmblookup '*', which does not return the address of any hybrid mode node that does not have the messenger service (resource "<03>") enabled, which happens to be most of the boxes on our network. If I knew the workgroups of those boxes, I could find the browser and get the registered names. Without the workgroups, I'll never be able to find those boxes. Dave -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] How to find all workgroups being used on a subnet?
I want to discover all the groups currently in use on a subnet. Is there a way to do this with a broadcast request? I know that I could just run nmblookup on every single host on the subnet, but that would take forever. I'd like to just make one or maybe a few calls. I'd like to limit the number of calls I make to no more than one plus the number of workgroups that are in use. Any advice? Dave -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] net view can see server, but nmblookup '*' can't find it!
I have an XP Pro box on my LAN, and I'm trying to figure out why nmblookup '*' can't see it. I'm writing a script that finds all the shares on the LAN and mounts them, and it works great except for this one box. On another windows box, when I run "net view", the XP box is listed as I expect. On my linux box, when I run "nmblookup -A 192.168.0.111" it returns with the correct data about the XP box's shares. But on the linux box, when I run "nmblokup '*'", it returns all the other boxes, linux and windows, except for this one XP box. Here is the output from "nmblookup -d 10 -A 192.168.0.111". Can you see anything that might prevent this box from showing up in "nmblookup '*'"? Initialising global parameters params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf" Processing section "[global]" doing parameter workgroup = BFNX doing parameter hosts allow = 192.168.0. 10.2. 127. doing parameter log file = /var/log/samba/%m.log doing parameter max log size = 0 doing parameter security = share doing parameter socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 doing parameter socket address = 192.168.0.150 doing parameter local master = no doing parameter username map = /etc/samba/smbusers doing parameter dns proxy = no doing parameter encrypt passwords = yes doing parameter null passwords = yes doing parameter domain master = no doing parameter local master = no doing parameter preferred master = no doing parameter server string = rave doing parameter netbios name = rave handle_netbios_name: set global_myname to: RAVE doing parameter interfaces = 192.168.0.150/24 192.168.254.1/24 172.16.50.1/24 10.2.0.1/15 pm_process() returned Yes lp_servicenumber: couldn't find homes set_server_role: ROLE_STANDALONE added interface ip=192.168.0.150 bcast=192.168.0.255 nmask=255.255.255.0 added interface ip=192.168.254.1 bcast=192.168.254.255 nmask=255.255.255.0 added interface ip=172.16.50.1 bcast=172.16.50.255 nmask=255.255.255.0 added interface ip=10.2.0.1 bcast=10.3.255.255 nmask=255.254.0.0 bind succeeded on port 0 socket option SO_KEEPALIVE = 0 socket option SO_REUSEADDR = 1 socket option SO_BROADCAST = 1 Could not test socket option TCP_NODELAY. socket option IPTOS_LOWDELAY = 0 socket option IPTOS_THROUGHPUT = 0 socket option SO_SNDBUF = 65535 socket option SO_RCVBUF = 65535 socket option SO_SNDLOWAT = 1 socket option SO_RCVLOWAT = 1 socket option SO_SNDTIMEO = 0 socket option SO_RCVTIMEO = 0 Socket opened. Looking up status of 192.168.0.111 Sending a packet of len 50 to (192.168.0.111) on port 137 read_udp_socket: lastip 192.168.0.111 lastport 137 read: 193 parse_nmb: packet id = 32431 Received a packet of len 193 from (192.168.0.111) port 137 nmb packet from 192.168.0.111(137) header: id=32431 opcode=Query(0) response=Yes header: flags: bcast=No rec_avail=No rec_des=No trunc=No auth=Yes header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0 answers: nmb_name=*<00> rr_type=33 rr_class=1 ttl=0 answers 0 char .SPACEINVADERS hex 045350414345494E5641444552532020 answers 10 char .D.SPACEINVADERS hex 0044005350414345494E564144455253 answers 20 charD.BFNX hex 2020204400524F4B5520202020202020 answers 30 char ...BFNXhex 2020202000C400524F4B552020202020 answers 40 char ..[R.. hex 2020202020201EC40BDB5B521F00 answers 50 char hex answers 60 char hex answers 70 char ... hex 00 SPACEINVADERS <00> - M SPACEINVADERS <20> - M BFNX<00> - M BFNX<1e> - M -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Linking smbclient and other smb tools dynamically
I couldn't find any documentation about how to make samba dynamically link its executables against libsmbclient.so, or any configure arguments might that turn this on. I saw on the samba-technical list that there was a patch to the samba Makefile.in to enable dynamic linking and that it generated huge size savings. Is that patch my only option if I want to minimize samba's disk footprint? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] dead connection timeouts?
I'm trying to reduce the time it takes the client to determine that a server is unavailable. Is this what "dead connection timeouts" are for? I searched samba's documentation and the web, and found multiple mention of the term "dead connection timeouts," but no description of what they are and how they are used. Regardless of whether "dead connection timeouts" are the answer, what do I need to tweak in order to prevent "ls /some/dead/server/mount" from sleeping for 30 seconds? Thanks, Dave -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Mac "DAVE" server + Linux samba 2.2.8a client = missingfirst char
I'm running stock RH9, which has the samba-2.2.7a-8.9.0 RPM installed on it. My friend has a Mac running OSX and the "DAVE" file sharing software. I can mount his shared folder using the following command: smbmount //tritanium/graphics /mnt/tritanium ...and I can see all the files in that folder when I do "ls /mnt/tritanium." But... The first character of every filename is missing! For example: the file named ".DS_Store" shows up as: -rwxr-xr-x1 root21508 Aug 22 15:21 DS_Store* The folder named "Cats" shows up as: drwxr-xr-x1 root 4096 Jun 22 12:28 ats/ I STFW for some answers but found none. I also RTFS (read the fine source) but could not determine why this was happening. Any suggestions on how I can fix it? Has anyone seen this behavior before? Thanks, Dave -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Can't write mount entrysmbmnt failed: 1
I've compiled and installed samba-2.2.8a on an embedded linux/uClibc
system, and I'm having problems using smbmount. I've appended the
debuglevel=10 output of smbmount. What does smbmount mean when it
says it "Can't write mount entry"? I tried running it under strace to
see what it was writing to, but all I saw was:
rt_sigaction(SIGTERM, {0x1000, [], 0x408160}, {SIG_DFL}, 16) = 0
fork(Process 410 attached
) = 410
[pid 409] wait4(410, Process 409 suspended
Can't write mount entrysmbmnt failed: 1
Which didn't tell me much. Any suggestions?
/ # /bin/smbmount //rave/share /tmp/rave -o username=guest,guest,ro
INFO: Debug class all level = 10 (pid 397 from pid 397)
doing parameter workgroup = ROKU
doing parameter include = /etc/smb.interfaces
params.c:pm_process() - Processing configuration file "/etc/smb.interfaces"
doing parameter interfaces = 192.168.0.159/24
doing parameter server string = d-192.168.0.159
doing parameter netbios name = d-192.168.0.159
handle_netbios_name: set global_myname to: D-192.168.0.159
doing parameter log file = /mnt/flash0/sambalog/%m.log
doing parameter security = share
doing parameter socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
doing parameter dns proxy = no
doing parameter encrypt passwords = yes
doing parameter null passwords = yes
doing parameter domain master = no
doing parameter local master = no
doing parameter preferred master = no
doing parameter map to guest = Bad User
doing parameter guest account = root
doing parameter browseable = yes
doing parameter public = yes
doing parameter writable = yes
doing parameter read only = no
doing parameter printable = no
doing parameter guest ok = yes
doing parameter guest only = yes
doing parameter guest account = root
doing parameter force create mode = 0777
doing parameter force directory mode = 0777
doing parameter force user = root
doing parameter force group = root
pm_process() returned Yes
lp_servicenumber: couldn't find homes
set_server_role: ROLE_STANDALONE
opts: username=guest
opts: guest
opts: ro
mount.smbfs started (version 2.2.8a)
codepage_initialise: client code page = 850
load_client_codepage: loading codepage 850.
Adding chars 0x85 0xb7 (l->u = True) (u->l = True)
Adding chars 0xa0 0xb5 (l->u = True) (u->l = True)
Adding chars 0x83 0xb6 (l->u = True) (u->l = True)
Adding chars 0xc6 0xc7 (l->u = True) (u->l = True)
Adding chars 0x84 0x8e (l->u = True) (u->l = True)
Adding chars 0x86 0x8f (l->u = True) (u->l = True)
Adding chars 0x91 0x92 (l->u = True) (u->l = True)
Adding chars 0x87 0x80 (l->u = True) (u->l = True)
Adding chars 0x8a 0xd4 (l->u = True) (u->l = True)
Adding chars 0x82 0x90 (l->u = True) (u->l = True)
Adding chars 0x88 0xd2 (l->u = True) (u->l = True)
Adding chars 0x89 0xd3 (l->u = True) (u->l = True)
Adding chars 0x8d 0xde (l->u = True) (u->l = True)
Adding chars 0xa1 0xd6 (l->u = True) (u->l = True)
Adding chars 0x8c 0xd7 (l->u = True) (u->l = True)
Adding chars 0x8b 0xd8 (l->u = True) (u->l = True)
Adding chars 0xd0 0xd1 (l->u = True) (u->l = True)
Adding chars 0xa4 0xa5 (l->u = True) (u->l = True)
Adding chars 0x95 0xe3 (l->u = True) (u->l = True)
Adding chars 0xa2 0xe0 (l->u = True) (u->l = True)
Adding chars 0x93 0xe2 (l->u = True) (u->l = True)
Adding chars 0xe4 0xe5 (l->u = True) (u->l = True)
Adding chars 0x94 0x99 (l->u = True) (u->l = True)
Adding chars 0x9b 0x9d (l->u = True) (u->l = True)
Adding chars 0x97 0xeb (l->u = True) (u->l = True)
Adding chars 0xa3 0xe9 (l->u = True) (u->l = True)
Adding chars 0x96 0xea (l->u = True) (u->l = True)
Adding chars 0x81 0x9a (l->u = True) (u->l = True)
Adding chars 0xec 0xed (l->u = True) (u->l = True)
Adding chars 0xe7 0xe8 (l->u = True) (u->l = True)
Adding chars 0x9c 0x0 (l->u = False) (u->l = False)
load_dos_unicode_map: 850
load_unicode_map: loading unicode map for codepage 850.
load_unix_unicode_map: ISO8859-1 (init_done=0, override=0)
load_unicode_map: loading unicode map for codepage ISO8859-1.
added interface ip=192.168.0.159 bcast=192.168.0.255 nmask=255.255.255.0
resolve_lmhosts: Attempting lmhosts lookup for name rave<0x20>
startlmhosts: Can't open lmhosts file /etc/lmhosts. Error was No such file or directory
resolve_hosts: Attempting host lookup for name rave<0x20>
resolve_wins: Attempting wins lookup for name rave<0x20>
wins_srv_count: WINS status: 0 servers.
resolve_wins: WINS server resolution selected and no WINS servers listed.
name_resolve_bcast: Attempting broadcast lookup for name rave<0x20>
bind succeeded on port 0
socket option SO_KEEPALIVE = 0
socket option SO_REUSEADDR = 1
socket option SO_BROADCAST = 1
Could not test socket option TCP_NODELAY.
socket option IPTOS_LOWDELAY = 0
socket option IPTOS_THROUGHPUT = 0
socket option SO_SNDBUF = 65535
socket option SO_RCVBUF = 65535
socket option SO_SNDLOWAT = 1
socket option SO_RCVLOWAT = 1
socket option SO_SNDTIMEO = 0
socket option SO_RCVTIMEO = 0
Sending a packet of len 50 to (192.168.0.255) on port 137
read_udp_sock
