RE: [Samba] weird stat()
On Sun, 2002-12-22 at 20:34, Erick Calder wrote: so what matter is the kernel you have not samba version sorry if I didn't provide all relevant info. client host: RH 7.2 (2.4.18-18.7 kernel), samba 2.2.1a-4 server host: RH 7.0 (2.4.9 kernel), samba 2.0.10-0.7 However, this seem a kernel bug in smbfs if this is a bug in the kernel... the question on which side: the client (which is rather recent) or the server (which is a little older)... and in either case then I should be posting to which mailing list? well try to upgrade the server to 2.2.7a and see if thins change. I think we fixed some bugs with dos times in 2.2.x series. Btw why do you use smb to share beetwen 2 unix machines? Currently nfs is still better as it respect unix semantics ... Simo. -- Simo Sorce - [EMAIL PROTECTED] Xsec s.r.l. via Durando 10 Ed. G - 20158 - Milano tel. +39 02 2399 7130 - fax: +39 02 700 442 399 signature.asc Description: This is a digitally signed message part
RE: [Samba] weird stat()
well try to upgrade the server to 2.2.7a and see if thins change. I think we fixed some bugs with dos times in 2.2.x series. I imagine you're running a later server... maybe you could test it for me? it's simple just do a stat dir on a directory from its parent and compare it to when you do a stat *... on my system and some RH 8.0 systems others have tested the results vary by 1 sec, consistently. Btw why do you use smb to share beetwen 2 unix machines? Currently nfs is still better as it respect unix semantics ... yeah, I reverted to NFS since this little fiasco... I wanted samba because I have a mixed env and didn't want two servers running... sigh. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Simo Sorce Sent: Monday, December 23, 2002 12:14 AM To: Erick Calder Cc: [EMAIL PROTECTED] Subject: RE: [Samba] weird stat() On Sun, 2002-12-22 at 20:34, Erick Calder wrote: so what matter is the kernel you have not samba version sorry if I didn't provide all relevant info. client host: RH 7.2 (2.4.18-18.7 kernel), samba 2.2.1a-4 server host: RH 7.0 (2.4.9 kernel), samba 2.0.10-0.7 However, this seem a kernel bug in smbfs if this is a bug in the kernel... the question on which side: the client (which is rather recent) or the server (which is a little older)... and in either case then I should be posting to which mailing list? well try to upgrade the server to 2.2.7a and see if thins change. I think we fixed some bugs with dos times in 2.2.x series. Btw why do you use smb to share beetwen 2 unix machines? Currently nfs is still better as it respect unix semantics ... Simo. -- Simo Sorce - [EMAIL PROTECTED] Xsec s.r.l. via Durando 10 Ed. G - 20158 - Milano tel. +39 02 2399 7130 - fax: +39 02 700 442 399 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] ÌؼÛÐÂÊé-298ÔªÂòÒ»×ùͼÊé¹Ý
ΪӽÓÊ¥µ®¡¢Ôªµ©£¬ÉîÛÚÍøÂçÊéµêÌØÍƳöÒ»Åúµç×ÓͼÊé¼°ÌؼÛÐÂÊé,µÍÖÁ1ÕÛ¡£ÄúÖ»Ð軨298Ôª¼´¿ÉÓµÓÐÒ»×ù3000²áͼÊéµÄ¼ÒͥͼÊé¹Ý¡£ »áÒé¡¢¸öÈ˽»ÍùÖеÄÀ¡Ôù¾«Æ· ¸öÈËÊղصÄÕäÆ·¡¢Ñ§Ï°µÄ¹¤¾ßÊé µ¥Î»½±ÀøÔ±¹¤µÄÉϼѽ±Æ·¼°¼ÍÄîÆ· ¹Ø°®º¢×ӳɳ¤µÄÌùÉíÀñÎï µç×ÓͼÊéĿ¼£º ¼ÒÍ¥²ØÊ鼯½õ£¨10CD£©298Ôª ÖлªÀúÊ·È«¼¯£¨11CD£©268Ôª ÖÐÍâÎÄѧÃûÖø1000²¿£¨12CD£© 268Ôª Öлª´«ÊÀ²ØÊ飨5CD£© 98Ôª ÖлªÑÞÇéÎĿ⣨4CD£© 98Ôª ÖлªÀúÊ·ÎĿ⣨7CD£© 168Ôª Öлª¾µäÎĿ⣨13CD£©328Ôª ÖлªÕäϡС˵ÎĿ⣨8CD£© 228Ôª ÖйúС°Ù¿ÆÈ«Ê飨1CD£© 38Ôª ÖйúÏÖ´úÎÄѧÃûÖø¾µä¶þ£¨1CD£© 38Ôª ÖÐѧÉú±Ø¶ÁÖÐÍâÎÄѧÃûÖø£¨1CD£© 38Ôª ѧÉú´Çº£´ÇÔ´£¨2CD£© 48Ôª ÊÀ½çÃûÈË´«¼ÇÎÄѧ£¨1CD£© 38Ôª ÏÖÔÚµã»÷½øÈëÉîÛÚÍøÂçÊéµê£º¡¡http://www.szbookshop.com --- ʹÓü«ÐÇÓʼþȺ·¢£¬ÎÞÐëͨ¹ýÓʼþ·þÎñÆ÷£¬Ö±´ï¶Ô·½ÓÊÏ䣬ËٶȾø¶ÔÒ»Á÷£¡ ÏÂÔØÍøÖ·£ºhttp://love2net.51.net/£¬¸ü¶àÃâ·ÑµÄ³¬¿áÈí¼þµÈÄãÀ´Ï¡¡ INFORMATION This message has been sent using a trial-run version of the TSmtpRelayServer Delphi Component. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] using %g or %G in an include
Does this problem in the new 2.2.7a? For some reason I not able to do the include with %g nor %G, but it works find for %m. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] can not connect to the shared printer
Hi there, I'm learning Samba and I really appreciate somebody out there can help me out. I'm using RedHat advanced server and a windows 2000. I created a workgroup on samba and only samba machine and win2k machine are members. I shared the printer attached to the Linux. From win2k PC, I can see the workgroup, but I can not find the samba host from the workgroup, nor does the printer. The smb.conf is attached. I run smbclient -NL hostname and it shows the printer under the Sharename. If I run net view //hostname, it returns that: System error 53 has occured, the network pass was not found I setup the samba 2 days ago, and the same problem happened then and now. BTW, I can mount a windows share from Linux, so I guess samba is running. Thanks and merry Christmas. Xiaodong # Samba config file created using SWAT # from localhost.localdomain (127.0.0.1) # Date: 2002/12/23 10:01:26 # Global parameters [global] workgroup = XGROUP server string = Birch Samba Server encrypt passwords = Yes log file = /var/log/samba/%m.log max log size = 500 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 dns proxy = No printing = lprng [homes] comment = Home Directories valid users = %S read only = No create mask = 0664 directory mask = 0775 browseable = No [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [hpdeskjet940c] comment = HP Deskjet 940c attached to Birch path = /var/spool/samba guest account = zhangx read only = No guest ok = Yes printable = Yes printer name = hpdeskjet940c oplocks = Yes share modes = Yes
[Samba] NULL files in Samba
We are using Samba 2.2.3a across a dedicated T-1 to a co-lo facility, and every so often, when we attempt to copy over a existing file at the co-lo (win2k to Samba share), we get a file with NULLS in it. Has anyone seen this behavior, and if so, what did you do to combat the problem? -Bill -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] can not connect to the shared printer
On Mon, 2002-12-23 at 16:23, Xiaodong Zhang wrote: Hi there, Hi, I'm learning Samba and I really appreciate somebody out there can help me out. I'm using RedHat advanced server and a windows 2000. I created a workgroup on samba and only samba machine and win2k machine are members. I shared the printer attached to the Linux. From win2k PC, I can see the workgroup, but I can not find the samba host from the workgroup, nor does the printer. The smb.conf is attached. I run smbclient -NL hostname and it shows the printer under the Sharename. If I run net view //hostname, it returns that: System error 53 has occured, the network pass was not found I setup the samba 2 days ago, and the same problem happened then and now. BTW, I can mount a windows share from Linux, so I guess samba is running. The fact that you can mount a samba share from Linux means nothing, this is not dependant upon whether you have the smbd running. This is so you dont have to have smbd running on every client machine (there are mixed OS networks). The mount command using the -t smbfs depends totally on whether the smbfs was compiled into the kernel under File Systems. The way to test whether the daemon is running would be to run: ps aux | grep smbd This should show you whether the smbd is running. If it is try restarting it and looking in the Samba logs for any errors, if it isnt then look it up. Thanks and merry Christmas. Xiaodong HTH and a Merry Christmas to you (if you celebrate it), Shak # Samba config file created using SWAT # from localhost.localdomain (127.0.0.1) # Date: 2002/12/23 10:01:26 # Global parameters [global] workgroup = XGROUP server string = Birch Samba Server encrypt passwords = Yes log file = /var/log/samba/%m.log max log size = 500 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 dns proxy = No printing = lprng [homes] comment = Home Directories valid users = %S read only = No create mask = 0664 directory mask = 0775 browseable = No [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [hpdeskjet940c] comment = HP Deskjet 940c attached to Birch path = /var/spool/samba guest account = zhangx read only = No guest ok = Yes printable = Yes printer name = hpdeskjet940c oplocks = Yes share modes = Yes -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Windows notification
Good morning everyone, Does anyone know of a way for Samba, or Linux, to send a notification to Windows users, as they log in, that there password has or is expiring in a certain number of days? I've thought about sending a network broadcast using Samba, but I have no idea how to do it automatically, based on a 60 day password life and X number of days warning before it expiring. Right now, I have to send an email to everyone warning them about password expiration. that gets kind of old. Thanks for the help! Darin Bawden, Technical Support Spectrum Software, Inc -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Windows notification
On Mon, 2002-12-23 at 08:50, Darin Bawden wrote: Does anyone know of a way ... to send a notification to Windows users, as they log in, that there password has or is expiring in a certain number of days? This would also be of interest to me... -Gord -- Gordon Pritchard, P.Eng. | Institute of Electrical and Research Labs Manager| Electronics Engineers Simon Fraser University, Surrey | Quarter Century Wireless Ass'n [EMAIL PROTECTED] | Telephone Pioneers of America phone: 604.586.6186 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] xp problem
At 08:27 PM 12/21/2002 +, you wrote: Pippo, We will need more information than this to help you. Please explain in detail what happens when you try to access the WinXP machine from Win2K and vica versa. You need to explain how your samba is configured as well as how the Win2K/XP systems are configured. Without this information we would be jst guessing - not very productive. Sorry, but I don't quite understand. I thought I had explained my setup fairly concisely. The Win2k and XP boxes are configured for workgroup file and printer sharing. There is no domain or domain server. FBSD is running samba as a file and printer server. I can only see the XP machine in My Network Places and the samba connection to the FBSD machine. When FBSD is running, I can connect from the XP machine both for file and printer access. When I try to connect to one of the other computers in the workgroup, I get the message: the path could not be found. Perhaps I am not clear enough: Before installing XP_Pro, I was able to see and connect between Win2K machines as well as the FBSD both for file shareing and printing. After installing XP, I can ping between the machines, I can map to the shares, I can print from the XP but I can no longer see the machines in the WORKGROUP on Network Neighborhood or Network Places (Childish nomenclature by MS). If I disconnect FBSD from the LAN, the Windows machines can, once again, intercommunicate. Perhaps I should dump the NetBEUI protocol on Windows and just map the shares on each machine. (Kindof a pain, IYAM) Maybe I just don't understand what the relationship should be between the samba machine and the others. The static address (192.168.1.240) of the FBSD machine show up as WORKSTATION and not as COMPUTER_NAME. If I may make an observation, it looks to me that MS is getting kprogressively bloated an unecessarily complicated as it evolves. I am trying to get away from it as much as possible but that is a little difficult as too many common people are still brainwashed by MS. Please let me know what specifics I should provide. I have been searching the documentation and the HOW_TO's with little success. Pippo On Sat, 21 Dec 2002 [EMAIL PROTECTED] wrote: I would appreciate it if someone can point me in the right direction. I am having a problem connecting to other computers on my LAN. Configuration is this: 1. XP machine, 2 Win2K's, 1 FreeBSD running Samba (current or latest version). From XP, I can connect and read/write and print to FBSD but cannot connect to Win2k's. Win2k's cannot connect to XP. I suspect it has to do with the domain master and the os level settings for, when the FBSD machine is off, connections between XP and Win2k are ok. What do I have to to to be able to connect to Win2k's at the same time as the FBSD (Samba)? I am not running a domain, workgroup only. :)) Thanks in advance, Pippo -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] xp problem
On Mon, 23 Dec 2002 [EMAIL PROTECTED] wrote: Ok. Let's try again. 1. Please send me your smb.conf file from the FBSD machine. 2. Please send me the output of the following on FBSD: ifconfig -a 3. Please send me the output of the following on your MS Windows MAchines: ipconfig /a 4. What is the name of the workgroup or domain on each of the MS Windows Machines. 5. What are the MS Windows machine names? 6. What protocols are installed on the MS Windows machines? Pleas email this info to me at [EMAIL PROTECTED]. - John T. At 08:27 PM 12/21/2002 +, you wrote: Pippo, We will need more information than this to help you. Please explain in detail what happens when you try to access the WinXP machine from Win2K and vica versa. You need to explain how your samba is configured as well as how the Win2K/XP systems are configured. Without this information we would be jst guessing - not very productive. Sorry, but I don't quite understand. I thought I had explained my setup fairly concisely. The Win2k and XP boxes are configured for workgroup file and printer sharing. There is no domain or domain server. FBSD is running samba as a file and printer server. I can only see the XP machine in My Network Places and the samba connection to the FBSD machine. When FBSD is running, I can connect from the XP machine both for file and printer access. When I try to connect to one of the other computers in the workgroup, I get the message: the path could not be found. Perhaps I am not clear enough: Before installing XP_Pro, I was able to see and connect between Win2K machines as well as the FBSD both for file shareing and printing. After installing XP, I can ping between the machines, I can map to the shares, I can print from the XP but I can no longer see the machines in the WORKGROUP on Network Neighborhood or Network Places (Childish nomenclature by MS). If I disconnect FBSD from the LAN, the Windows machines can, once again, intercommunicate. Perhaps I should dump the NetBEUI protocol on Windows and just map the shares on each machine. (Kindof a pain, IYAM) Maybe I just don't understand what the relationship should be between the samba machine and the others. The static address (192.168.1.240) of the FBSD machine show up as WORKSTATION and not as COMPUTER_NAME. If I may make an observation, it looks to me that MS is getting kprogressively bloated an unecessarily complicated as it evolves. I am trying to get away from it as much as possible but that is a little difficult as too many common people are still brainwashed by MS. Please let me know what specifics I should provide. I have been searching the documentation and the HOW_TO's with little success. Pippo On Sat, 21 Dec 2002 [EMAIL PROTECTED] wrote: I would appreciate it if someone can point me in the right direction. I am having a problem connecting to other computers on my LAN. Configuration is this: 1. XP machine, 2 Win2K's, 1 FreeBSD running Samba (current or latest version). From XP, I can connect and read/write and print to FBSD but cannot connect to Win2k's. Win2k's cannot connect to XP. I suspect it has to do with the domain master and the os level settings for, when the FBSD machine is off, connections between XP and Win2k are ok. What do I have to to to be able to connect to Win2k's at the same time as the FBSD (Samba)? I am not running a domain, workgroup only. :)) Thanks in advance, Pippo -- John H Terpstra Email: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] SAMBA PDC
I followed the procedure to configure SAMBA as a PDC as outlined in samba/swat.cgi/swat/using_samba/ch06_05.html on my Linux server. My domain name is COFRNY, and I expected a COFRNY.SID to be generated. However, MACHINE.SID was generated instead. Furthermore, I cannot see the COFRNY domain listed within MS Networks on my XP workstation. Any ideas on what I did wrong? Here is the procedure in detail: [global] workgroup = COFRNY domain logons = yes security = user os level = 34 local master = yes preferred master = yes domain master = yes For Windows NT clients you must also ensure that Samba is using encrypted passwords: encrypted passwords = yes Furthermore, also exclusively for Windows NT clients, create Trust accounts which allow a machine to log in to the PDC itself. Create a dummy account in the /etc/passwd file with the following entry: city-f5pfa29xta$:*:1000:900:Trust Account:/dev/null:/dev/null Note that we have also disabled the password field by placing a * in it. This is because Samba will use the smbpasswd file to contain the password instead, and we don't want anyone to telnet into the machine using that account. Additionally, '1000' is the UID of the account for the encrypted password database. Next, add the encrypted password using the smbpasswd command, as follows: # smbpasswd -a -m city-f5pfa29xta Added user city-f5pfa29xta$ Password changed for user city-f5pfa29xta$ The -m option specifies that a machine trust account is being generated. The smbpasswd program will automatically set the initial encrypted password as the NetBIOS name of the machine in lowercase letters. When specifying this option on the command line, do not put a dollar sign after the machine name - it will be appended automatically. Once the encrypted password has been added, Samba is ready to handle domain logins from a NT client. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SAMBA PDC
Kenneth, You did not mention the samba version. Suspect you are using 2.2.x. Did you apply the WinXP_SignOrSeal.reg registry update? You will need to as XP defaults to this and samba-2.2.x does not support it yet. - John T. On Mon, 23 Dec 2002, Kenneth Illingsworth wrote: I followed the procedure to configure SAMBA as a PDC as outlined in samba/swat.cgi/swat/using_samba/ch06_05.html on my Linux server. My domain name is COFRNY, and I expected a COFRNY.SID to be generated. However, MACHINE.SID was generated instead. Furthermore, I cannot see the COFRNY domain listed within MS Networks on my XP workstation. Any ideas on what I did wrong? Here is the procedure in detail: [global] workgroup = COFRNY domain logons = yes security = user os level = 34 local master = yes preferred master = yes domain master = yes For Windows NT clients you must also ensure that Samba is using encrypted passwords: encrypted passwords = yes Furthermore, also exclusively for Windows NT clients, create Trust accounts which allow a machine to log in to the PDC itself. Create a dummy account in the /etc/passwd file with the following entry: city-f5pfa29xta$:*:1000:900:Trust Account:/dev/null:/dev/null Note that we have also disabled the password field by placing a * in it. This is because Samba will use the smbpasswd file to contain the password instead, and we don't want anyone to telnet into the machine using that account. Additionally, '1000' is the UID of the account for the encrypted password database. Next, add the encrypted password using the smbpasswd command, as follows: # smbpasswd -a -m city-f5pfa29xta Added user city-f5pfa29xta$ Password changed for user city-f5pfa29xta$ The -m option specifies that a machine trust account is being generated. The smbpasswd program will automatically set the initial encrypted password as the NetBIOS name of the machine in lowercase letters. When specifying this option on the command line, do not put a dollar sign after the machine name - it will be appended automatically. Once the encrypted password has been added, Samba is ready to handle domain logins from a NT client. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- John H Terpstra Email: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Cannot connect to the shared printer
On Mon, 2002-12-23 at 16:23, Xiaodong Zhang wrote: Hi there, Hi, I'm learning Samba and I really appreciate somebody out there can help me out. I'm using RedHat advanced server and a windows 2000. I created a workgroup on samba and only samba machine and win2k machine are members. I shared the printer attached to the Linux. From win2k PC, I can see the workgroup, but I can not find the samba host from the workgroup, nor does the printer. The smb.conf is attached. I run smbclient -NL hostname and it shows the printer under the Sharename. If I run net view //hostname, it returns that: System error 53 has occured, the network pass was not found I setup the samba 2 days ago, and the same problem happened then and now. BTW, I can mount a windows share from Linux, so I guess samba is running. The fact that you can mount a samba share from Linux means nothing, this is not dependant upon whether you have the smbd running. This is so you dont have to have smbd running on every client machine (there are mixed OS networks). The mount command using the -t smbfs depends totally on whether the smbfs was compiled into the kernel under File Systems. The way to test whether the daemon is running would be to run: ps aux | grep smbd This should show you whether the smbd is running. If it is try restarting it and looking in the Samba logs for any errors, if it isnt then look it up. Thanks and merry Christmas. Xiaodong HTH and a Merry Christmas to you (if you celebrate it), Shak # Samba config file created using SWAT # from localhost.localdomain (127.0.0.1) # Date: 2002/12/23 10:01:26 # Global parameters [global] workgroup = XGROUP server string = Birch Samba Server encrypt passwords = Yes log file = /var/log/samba/%m.log max log size = 500 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 dns proxy = No printing = lprng [homes] comment = Home Directories valid users = %S read only = No create mask = 0664 directory mask = 0775 browseable = No [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [hpdeskjet940c] comment = HP Deskjet 940c attached to Birch path = /var/spool/samba guest account = zhangx read only = No guest ok = Yes printable = Yes printer name = hpdeskjet940c oplocks = Yes share modes = Yes -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SAMBA PDC
Thank you for replying. You are correct in that the version of SAMBA is 2.2.1 . I was not aware of the WinXP_SignOrSeal.reg registry update. However, I am aware of WinXP SP1 which has been applied. I suspect that the WinXP_SignOrSeal.reg registry update is separate from SP1. I will attempt to obtain the registry update and apply it to the XP workstation. Any direction you can give on this issue would be greatly appreciated. Here is an additional observation: From the SAMBA Troubleshooting Guide, I have encountered the precise anomaly that I am experiencing: Symptom:It is possible to ping the HOST from the client (on port 7; the echo port) but the client is unable to obtain the list of shares on HOST. [I can ping either the IP addr or the NetBIOS name of the server from the workstation]. Cause: Traffic on one or more of the NetBIOS-over-TCP ports (137, 138, 139) are blocked. To verify this, type one of the following commands: nbtstat -A 172.17.60.6 If this command shows a list of NetBIOS names, then port 137 is open. Otherwise, it is blocked. [The COFR3 server is listed along with the COFRNY domain as shown in the separate section below]. Resolution: Find the router, firewall, switch or other device that is blocking ports 137-139 and reconfigure it. UDP traffic must be permitted on ports 137 and 138, and TCP traffic must be permitted on port 139. [Since this Linux server is a Virtual Machine, could this be interpreted as an issue with its TCP/IP configuration?]. I could not run a traceroute on the workstations NetBIOS name from the Linux server as it was an unknown host. However, I was able to obtain the following using the workstations leased IP address: traceroute to 172.16.4.251 (172.16.4.251), 30 hops max, 38 byte packets 1 172.17.60.5 (172.17.60.5) 7.462 ms 0.812 ms 0.678 ms 2 172.16.4.251 (172.16.4.251) 3.379 ms 23.449 ms 5.059 ms Here are the results of the nbstat command above: C:\nbtstat -A 172.17.60.6 Local Area Connection: Node IpAddress: [172.16.4.251] Scope Id: [] NetBIOS Remote Machine Name Table Name Type Status - COFR3 00 UNIQUE Registered COFR3 03 UNIQUE Registered COFR3 20 UNIQUE Registered ..__MSBROWSE__.01 GROUP Registered COFRNY 00 GROUP Registered COFRNY 1B UNIQUE Registered COFRNY 1C GROUP Registered COFRNY 1D UNIQUE Registered COFRNY 1E GROUP Registered MAC Address = 00-00-00-00-00-00 COFR3 is the NetBIOS name of the server, and COFRNY is the workgroup name that I am trying to use to set up the domain. John H Terpstra [EMAIL PROTECTED] 12/23/02 12:48PM Kenneth, You did not mention the samba version. Suspect you are using 2.2.x. Did you apply the WinXP_SignOrSeal.reg registry update? You will need to as XP defaults to this and samba-2.2.x does not support it yet. - John T. On Mon, 23 Dec 2002, Kenneth Illingsworth wrote: I followed the procedure to configure SAMBA as a PDC as outlined in samba/swat.cgi/swat/using_samba/ch06_05.html on my Linux server. My domain name is COFRNY, and I expected a COFRNY.SID to be generated. However, MACHINE.SID was generated instead. Furthermore, I cannot see the COFRNY domain listed within MS Networks on my XP workstation. Any ideas on what I did wrong? Here is the procedure in detail: [global] workgroup = COFRNY domain logons = yes security = user os level = 34 local master = yes preferred master = yes domain master = yes For Windows NT clients you must also ensure that Samba is using encrypted passwords: encrypted passwords = yes Furthermore, also exclusively for Windows NT clients, create Trust accounts which allow a machine to log in to the PDC itself. Create a dummy account in the /etc/passwd file with the following entry: city-f5pfa29xta$:*:1000:900:Trust Account:/dev/null:/dev/null Note that we have also disabled the password field by placing a * in it. This is because Samba will use the smbpasswd file to contain the password instead, and we don't want anyone to telnet into the machine using that account. Additionally, '1000' is the UID of the account for the encrypted password database. Next, add the encrypted password using the smbpasswd command, as follows: # smbpasswd -a -m city-f5pfa29xta Added user city-f5pfa29xta$ Password changed for user city-f5pfa29xta$ The -m option specifies that a machine trust account is being generated. The smbpasswd program will automatically set the initial encrypted password as the NetBIOS
[Samba] (no subject)
Hello. I am running Samba version 2.2.5 on Redhat Linux 8.0, kernel version 2.4.18-14. Encrypted passwords = yes; security = user; wins server =169.254.1.2; netbios name = SambaServer. My client is Windows 2000, service pack 3. I am only able to browse my samba shares only if I use the ip address of my samba server. For example on Winddows 2000 I run: NET USE \\169.254.1.1, I can see the shares, I am also able to map drives, all is good. If I run NET USE \\SambaServer, using the netbios name, I get 'Access Denied'. I've checked the log files and saw that bind succeeded on both ports 137,139. Under [Global] Settings I've added 'guest ok = yes'; 'guest account = ftp'. Both user accounts exist in /etc/passwd and smbpasswd files. I've checked iptables and opened up ports 137,138,139 tcp/udp. I am able to anonymously view shares locally on my SambaServer when I run 'smbclient -U% -L SambaServer'. The Windows 2000 Server is the domain master browser, local master browser and WINS server. I've upped the logging on the SambaServer and saw that browse.dat gets updated with everyones netbios/ip addresses. The WINS server is also update with the netbios/ip name pairs. When I run: NET USE \\169.254.1.1 on the Windows 2000 box, Samba's logs show that is negotiates protocols and selects NT LM 0.1.2. The defaut protocol for Windows 2000. Fine. It then validates my user accout, the user I am logged on as on Windows 2000, which by the way has the same username/password/case as on the linux box. It passes. It then checks my password. The SMB hash is the same and the NT hash and there you have it I can see the list of shares on the SambaServer. If I run: NET USE \\SambaServer (name not ip address), it does not get past protocol negotiation. It does not check my user or password and I get Access is deniedSystem error 5 has occurred. Is there something wrong with guest access with this version on Samba? Any thoughts?? _ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] slo2.4
Hi My name is Dilip Patel and I have question as below; I am running Sun operating system Solaris 2.4 and need to use samba to windows, So can use samba version 2.2.7 compile on solaris-8 OS? If not then what are my choices to on sol2.4 OS? Can you please replay? I really appreciate your help OR Is any technical support available for Samba. Thanks again and have great happy holidays. .Dilip Patel Voice: 630-521-3284 Pager: 877-463-7334 HOUSEHOLD -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] What the difference between
Could someone please explain What the difference is between, Samba-2.2.2-3.3mdk.i586.rpm and Samba-client-2.2.2-3.3mdk.i586.rpm and Samba-common-2.2.2-3.3mdk.i586.rpm Which one do i need to upgrade my samba server on lm8.1 many thanks Ken -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SAMBA PDC
On Mon, 23 Dec 2002, Kenneth Illingsworth wrote: Thank you for replying. You are correct in that the version of SAMBA is 2.2.1 . Strongly suggest you update to samba-2.2.7a as there have been MANY fixes and updates since 2.2.1. You can obtain the RPM packages from the samba FTP sites. I was not aware of the WinXP_SignOrSeal.reg registry update. However, I am aware of WinXP SP1 which has been applied. I suspect that the WinXP_SignOrSeal.reg registry update is separate from SP1. I will attempt to obtain the registry update and apply it to the XP workstation. Any direction you can give on this issue would be greatly appreciated. Attached. It can be found in all recent releases of samba in the docs/Registry directory. Send me your smb.conf file to [EMAIL PROTECTED] and I will try to help you. - John T. Here is an additional observation: From the SAMBA Troubleshooting Guide, I have encountered the precise anomaly that I am experiencing: Symptom: It is possible to ping the HOST from the client (on port 7; the echo port) but the client is unable to obtain the list of shares on HOST. [I can ping either the IP addr or the NetBIOS name of the server from the workstation]. Cause:Traffic on one or more of the NetBIOS-over-TCP ports (137, 138, 139) are blocked. To verify this, type one of the following commands: nbtstat -A 172.17.60.6 If this command shows a list of NetBIOS names, then port 137 is open. Otherwise, it is blocked. [The COFR3 server is listed along with the COFRNY domain as shown in the separate section below]. Resolution: Find the router, firewall, switch or other device that is blocking ports 137-139 and reconfigure it. UDP traffic must be permitted on ports 137 and 138, and TCP traffic must be permitted on port 139. [Since this Linux server is a Virtual Machine, could this be interpreted as an issue with its TCP/IP configuration?]. I could not run a traceroute on the workstations NetBIOS name from the Linux server as it was an unknown host. However, I was able to obtain the following using the workstations leased IP address: traceroute to 172.16.4.251 (172.16.4.251), 30 hops max, 38 byte packets 1 172.17.60.5 (172.17.60.5) 7.462 ms 0.812 ms 0.678 ms 2 172.16.4.251 (172.16.4.251) 3.379 ms 23.449 ms 5.059 ms Here are the results of the nbstat command above: C:\nbtstat -A 172.17.60.6 Local Area Connection: Node IpAddress: [172.16.4.251] Scope Id: [] NetBIOS Remote Machine Name Table Name Type Status - COFR3 00 UNIQUE Registered COFR3 03 UNIQUE Registered COFR3 20 UNIQUE Registered ..__MSBROWSE__.01 GROUP Registered COFRNY 00 GROUP Registered COFRNY 1B UNIQUE Registered COFRNY 1C GROUP Registered COFRNY 1D UNIQUE Registered COFRNY 1E GROUP Registered MAC Address = 00-00-00-00-00-00 COFR3 is the NetBIOS name of the server, and COFRNY is the workgroup name that I am trying to use to set up the domain. John H Terpstra [EMAIL PROTECTED] 12/23/02 12:48PM Kenneth, You did not mention the samba version. Suspect you are using 2.2.x. Did you apply the WinXP_SignOrSeal.reg registry update? You will need to as XP defaults to this and samba-2.2.x does not support it yet. - John T. On Mon, 23 Dec 2002, Kenneth Illingsworth wrote: I followed the procedure to configure SAMBA as a PDC as outlined in samba/swat.cgi/swat/using_samba/ch06_05.html on my Linux server. My domain name is COFRNY, and I expected a COFRNY.SID to be generated. However, MACHINE.SID was generated instead. Furthermore, I cannot see the COFRNY domain listed within MS Networks on my XP workstation. Any ideas on what I did wrong? Here is the procedure in detail: [global] workgroup = COFRNY domain logons = yes security = user os level = 34 local master = yes preferred master = yes domain master = yes For Windows NT clients you must also ensure that Samba is using encrypted passwords: encrypted passwords = yes Furthermore, also exclusively for Windows NT clients, create Trust accounts which allow a machine to log in to the PDC itself. Create a dummy account in the /etc/passwd file with the following entry: city-f5pfa29xta$:*:1000:900:Trust Account:/dev/null:/dev/null Note that we have also disabled the password field by placing a * in it. This is because Samba will use the smbpasswd file to contain the password instead, and we don't want anyone to telnet into the machine using
RE: [Samba] What the difference between
Samba is the server.. Samba-client is the client used to connect to remote servers Samba-common are common files used by both the server and client. I personally would upgrade all 3 at the same time... but you can just upgrade Samba and Samba-common. -Original Message- From: Ken Walker [mailto:[EMAIL PROTECTED]] Sent: Monday, December 23, 2002 2:58 PM To: '[EMAIL PROTECTED]' Subject: [Samba] What the difference between Could someone please explain What the difference is between, Samba-2.2.2-3.3mdk.i586.rpm and Samba-client-2.2.2-3.3mdk.i586.rpm and Samba-common-2.2.2-3.3mdk.i586.rpm Which one do i need to upgrade my samba server on lm8.1 many thanks Ken -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] slo2.4
On Mon, 23 Dec 2002, Dilip X. Patel wrote: Hi My name is Dilip Patel and I have question as below; I am running Sun operating system Solaris 2.4 and need to use samba to windows, So can use samba version 2.2.7 compile on solaris-8 OS? Yes you can build samba-2.2.7a on Solaris. It will work. If not then what are my choices to on sol2.4 OS? Can you please replay? I really appreciate your help OR Is any technical support available for Samba. No problems. You are welcome. - John T. -- John H Terpstra Email: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] What the difference between
Ken, No difference, you need them all - together they make up samba-2.2.2 for Mandrake. Mandrake (like other Linux vendors) split up the files over a group of packages. - John T. On Mon, 23 Dec 2002, Ken Walker wrote: Could someone please explain What the difference is between, Samba-2.2.2-3.3mdk.i586.rpm and Samba-client-2.2.2-3.3mdk.i586.rpm and Samba-common-2.2.2-3.3mdk.i586.rpm Which one do i need to upgrade my samba server on lm8.1 many thanks Ken -- John H Terpstra Email: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Print queue not viewable from Windows XP
Actually, I suspect you need to fool with lpd.perms to allow other users to delete print jobs. Unless of course you have guest logins for the printer share. Joel -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] SAMBA 2.2.7a and Windows XP
I've been having these really annoying issues ever since I started to configure SAMBA with Windows XP. As it seems the XP-machine detects the SAMBA-share on occasions, and even manages to connect to it; but only for a while. I have found no clue whatsoever why it connects only sometimes. It seems that when the Windows XP machine is just booted, it normally gets access to the Linux-machine, but after just a while it looses the access. I'm also running a Windows 98SE-machine on the very same network, however the connection between Linux --- Windows98SE seems to be flawless. It detects, browses, downloads, etc. without the slightest problem. To go back to the issue, I'm on a 10Mbit Broadband connection, and my IP is assigned by DHCP, I'm always on the same C-net. Locally the network runs at 100Mbit... (switched), and here's what's strange. WHEN I run regular TCP-transfers to the Linux system (such as FTP, etc.) ; the transferrate is relevant to that of a 10Mbit connection (it seems as it goes outside the LAN, and connects that way. _BUT_ when I get 'connected' on SAMBA, it accelerates and behaves like a 100Mbit network. As I said, these occasions occur erratically; so I cannot really find a common denominator. Sometimes it happens just when I transfer the very last of the files (over FTP). My first conclusion is that there's something wrong with the Windows XP configuration, but I seem to have tried most of the logical solutions... I've switched off NetBIOS, NetBEUI, (and ON, in all combinations), but it doesn't seem to do anything but either limit the percentage to 0 (zero) when I manage to connect. I've also tried using: \\samba.host.ext\ ; and that doesn't work (I suppose it has to do with my ISP has blocked port 139, to prevent people from accessing eachothers shares across apartments) I've tried to remove the external TP-connection, but to no avail. I really believe that it has to do with Windows XP. Someone told me it had to do with LmCompatibilityLevel... but I cannot draw any conclusions there either. I've really tried to find a solution, but I just can't do it. I really need some help here =( [EMAIL PROTECTED] for direct e-mail -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Error Saving Certain Files in Profile from Win XP PRO
John H Terpstra wrote: On Sat, 21 Dec 2002, ___cliff rayman___ wrote: running samba 2.2.7 on linux as a PDC. client box is win XP PRO SP1. When shutting down windows i am getting an error message as follows (paraphrased since it lasts for 30 seconds and disappears no matter what you do **#$#$ ): Problem saving profile Documents and Settings/Start Menu/Programs/ Accessoreis/Entertainment/Windows Media Player.lnk drives me nuts. In the latter case, nothing short of re-installation of the Win NT/2K/XP machines seems to solve the problem. ouch Another thing I found is that if the debug level is set to 0 when the client first negotiates roaming profile handling then no problems ensue, but if the debug level is set to 3 or more during first negotiation of yes - i have been running at log level 10 to flush out all the problems that i have been having. so, when i jointed the domain, i was at log level 10. roaming profile handling for a freshly installed Win2K/XP system, then about 2 out of 3 stations will experience a problem. That problem could be anything from: 1. Pop-up of notepad with the contents of what looks like a .ini file this occurs with one of the login names from that machine, but so far, not the others Secondly, embedding of '.' (dots) in a NetBIOS name is a very bad practice. If your Win2K clients use DNS for name resolution and your DNS domain is thecompany.com, then the above NetBIOS names would map to mars.genwax.test.thecompany.com the fully qualified domain name of this server is mars.genwax.test. i know that is kind of strange, but this is a test server, on a test network, so it has its own ip addresses, domain, and netbios names. i changed it to simply mars, and it did not change any of the system behavior. os level = 99 Why 99? An OS level of 33 is more than enough and setting it higher does not add anything. This is trivial so please ignore. My comment is just FYI. got it from page 6 of the Unofficial Samba How-To. -- ___cliff [EMAIL PROTECTED]http://www.genwax.com/ -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Method for joining machines to PDC without using root
currently, in order to join a win XP machine to a samba PDC, you have to use the root account (although you can use an smbpasswd and not the linux password). is there any way to set up another account to do this one particular task (one without uid=0)?. if we have users in remote places, i do not want to have to go over to their work station just to log them on the the domain. alsoi don't want to give them a login and password that could compromise the system the samba is running on (linux). i think the answer is no from some of the information i found by googling, but i wanted to verify the answer here. my only other option would be to issue a: smbpasswd root make a temporary password, talk someone into joining a domain on the phone, immediately change the password back so it is secure. -- ___cliff [EMAIL PROTECTED]http://www.genwax.com/ -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] tmp in profile
Hi, I used samba as PDC. When some users (not all users) log off ,itcreated prfxxx.tmp(ex. prf127.tmp,prfEC.tmp) in their profiles (in /profiles/user/SendTo/prf127.tmp). Almost it occured with users which can't update profiles because cannot copy file 3r Floppy(A).lnk. Thank you.With Yahoo! Mail you can get a bigger mailbox -- choose a size that fits your needs
Re: [Samba] Method for joining machines to PDC without using root
On Mon, 23 Dec 2002, ___cliff rayman___ wrote: currently, in order to join a win XP machine to a samba PDC, you have to use the root account (although you can use an smbpasswd and not the linux password). is there any way to set up another account to do this one particular task (one without uid=0)?. No. It has to be done as a 'root' privilidged account from samba's perspective. ie: NT Administrator (which maps to root). As you noted, the smb password for root does not need to be the same as the system root password. if we have users in remote places, i do not want to have to go over to their work station just to log them on the the domain. alsoi don't want to give them a login and password that could compromise the system the samba is running on (linux). i think the answer is no from some of the information i found by googling, but i wanted to verify the answer here. You have your verification. Got a better suggestion? Send us your patches and we will look at them. my only other option would be to issue a: smbpasswd root make a temporary password, talk someone into joining a domain on the phone, immediately change the password back so it is secure. No different from NT/2K really. - John T. -- John H Terpstra Email: [EMAIL PROTECTED] -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Method for joining machines to PDC without using root
John H Terpstra wrote: On Mon, 23 Dec 2002, ___cliff rayman___ wrote: You have your verification. Got a better suggestion? Send us your patches and we will look at them. i know, suggestions are cheap, good patches are like diamonds :-) if the problem is smbpasswd permissions, perhaps it can be set to mode 660 instead of 600, and with a group something like domainadd. any user with domainadd group, can add a windows box to the domain. users can be created in this special group that could do nothing else but add windows boxes to the domain. no logins - no share permissions etc.. i did look at the code, but it is way over my head without several hundred hours of study. :-) my only other option would be to issue a: smbpasswd root make a temporary password, talk someone into joining a domain on the phone, immediately change the password back so it is secure. No different from NT/2K really. i assumed that this was a samba requirement and not a windows requirement. -- ___cliff [EMAIL PROTECTED]http://www.genwax.com/ -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
http://localhost:901
Dear Sirs I install and configure xinetd.conf,but i can not load http://localhost:901 please help me. regards Pedram Dehghani System Administrator SG Co.
http://localhost:901
dear dan i cannot load the swatin http://localhost:901 i have give error : The connection was refused when attempting to contact localhost:901 please help me. regards Pedram Dehghani System Administrator SG Co.
Re: http://localhost:901
Original Message - From: root [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, December 23, 2002 12:26 PM Subject: http://localhost:901 dear dan i cannot load the swatin http://localhost:901 i have give error : The connection was refused when attempting to contact localhost:901 Read this: http://www.security-forums.com/forum/viewtopic.php?t=249 Then ask again when you have a clue. Thanks. Shaolin * This email has been checked by the altohiway e-Sweeper Service *
[PATCH] and question - net rpc shutdown
Hi!
This patch corrects a problem with the default comment for net rpc
shutdown.
(diff against 3.0)
My power off - problem persists because net rpc shutdown is similar to
InitiateSystemShutdown, which is not able to power off the computer. In
my research I've found out that powering off needs a Remote API call (if
my interpretations of the data on the wire are correct). Is there any
function in Samba which can send a remote API call?
Thanks
Willi
Index: utils/net.c
===
RCS file: /cvsroot/samba/source/utils/net.c,v
retrieving revision 1.43.2.8
diff -u -r1.43.2.8 net.c
--- utils/net.c 12 Nov 2002 23:20:49 - 1.43.2.8
+++ utils/net.c 23 Dec 2002 18:45:15 -
@@ -68,6 +68,7 @@
int opt_port = 0;
int opt_maxusers = -1;
char *opt_comment = ;
+BOOL opt_comment_specified = False;
int opt_flags = -1;
int opt_jobid = 0;
int opt_timeout = 0;
@@ -446,7 +447,7 @@
{myname, 'n', POPT_ARG_STRING, opt_requester_name},
{conf,'s', POPT_ARG_STRING, servicesf},
{server, 'S', POPT_ARG_STRING, opt_host},
- {comment, 'C', POPT_ARG_STRING, opt_comment},
+ {comment, 'C', POPT_ARG_STRING, opt_comment,'C'},
{maxusers,'M', POPT_ARG_INT,opt_maxusers},
{flags, 'F', POPT_ARG_INT,opt_flags},
{jobid, 'j', POPT_ARG_INT,opt_jobid},
@@ -487,6 +488,9 @@
*p = 0;
opt_password = p+1;
}
+ break;
+ case 'C':
+ opt_comment_specified = True;
break;
default:
d_printf(\nInvalid option %c (%d)\n,
(char)opt, opt);
Index: utils/net.h
===
RCS file: /cvsroot/samba/source/utils/net.h,v
retrieving revision 1.7.2.1
diff -u -r1.7.2.1 net.h
--- utils/net.h 15 Jul 2002 10:35:23 - 1.7.2.1
+++ utils/net.h 23 Dec 2002 18:45:25 -
@@ -38,6 +38,7 @@
extern int opt_maxusers;
extern char *opt_comment;
+extern BOOL opt_comment_specified;
extern int opt_flags;
extern char *opt_comment;
Index: utils/net_rpc.c
===
RCS file: /cvsroot/samba/source/utils/net_rpc.c,v
retrieving revision 1.14.2.10
diff -u -r1.14.2.10 net_rpc.c
--- utils/net_rpc.c 20 Dec 2002 20:21:31 - 1.14.2.10
+++ utils/net_rpc.c 23 Dec 2002 18:45:34 -
@@ -1478,7 +1478,7 @@
if (force) {
flgs |= REG_FORCE_SHUTDOWN;
}
- if (opt_comment) {
+ if (opt_comment_specified) {
msg = opt_comment;
}
if (opt_timeout) {
Re: [PATCH] and question - net rpc shutdown
On Mon, 23 Dec 2002, Willi Mann wrote: Hi! This patch corrects a problem with the default comment for net rpc shutdown. (diff against 3.0) My power off - problem persists because net rpc shutdown is similar to InitiateSystemShutdown, which is not able to power off the computer. In my research I've found out that powering off needs a Remote API call (if my interpretations of the data on the wire are correct). Is there any function in Samba which can send a remote API call? Do you mean a RAP call? The net function does them. Regards - Richard Sharpe, rsharpe[at]ns.aus.com, rsharpe[at]samba.org, sharpe[at]ethereal.com, http://www.richardsharpe.com
smbwrapper use of port 139 vs 445... Ok to force to 139?
My last known problem with smbwrapper on Linux is that sometimes hosts in a workgroup, or shares on a host, are not returned by the cli_Net*Enum() functions. On another list (debian.something), there is currently a discussion of the fact that using port 445 can cause this problem, and in fact, when I force the port to 139, the problem goes away. I'm not terribly familiar with the protocol differences between what's sent on port 139 and what's sent on port 445. *Specifically for the purposes of smbwrapper...* 1. Is there a reason not to force the port number to 139? 2. Is there any service provided on port 445, not provided on port 139, that's required for smbwrapper to return the correct data? 3. Are there any servers that don't provide port 139 service at all? 4. If #3 is yes, what about trying 139 and falling back to 445 rather than the current implementation which is the other way around? Thanks, Derrell
Re: smbwrapper use of port 139 vs 445... Ok to force to 139?
On Mon, Dec 23, 2002 at 02:51:08PM -0500, [EMAIL PROTECTED] wrote: My last known problem with smbwrapper on Linux is that sometimes hosts in a workgroup, or shares on a host, are not returned by the cli_Net*Enum() functions. On another list (debian.something), there is currently a discussion of the fact that using port 445 can cause this problem, and in fact, when I force the port to 139, the problem goes away. I'm not terribly familiar with the protocol differences between what's sent on port 139 and what's sent on port 445. *Specifically for the purposes of smbwrapper...* 1. Is there a reason not to force the port number to 139? 2. Is there any service provided on port 445, not provided on port 139, that's required for smbwrapper to return the correct data? 3. Are there any servers that don't provide port 139 service at all? 4. If #3 is yes, what about trying 139 and falling back to 445 rather than the current implementation which is the other way around? I understand the reason for using 445 as primary and falling back to 139 is that it's much more efficient (both on setup and during data transfer) than doing it the other way around. For the purposes of getting a browse list, connecting to port 139 is a must. There are ways to get the equivalent of a browse list via AD, but I don't think it's LDAP-only, so port 445 doesn't even do any good in this regard. For the actual enumeration of and connecting to shares, port 445 is likely to give some performance increase due to the lower protocol overhead. You can also configure newer Windows machines (XP at least) to *not* support NetBIOS at all, in which case they'll only be listening on port 445. OTOH, there are also plenty of older machines (NT4 and below) that are 139-only. Theoretically, it might be optimal to use port 139 to collect browse lists, and then use 445-else-139 for everything else. Barring that, I think 139-else-445 would be the best option. -- Steve Langasek postmodern programmer msg05067/pgp0.pgp Description: PGP signature
Re: smbwrapper use of port 139 vs 445... Ok to force to 139?
Steve Langasek [EMAIL PROTECTED] writes: For the purposes of getting a browse list, connecting to port 139 is a must. There are ways to get the equivalent of a browse list via AD, but I don't think it's LDAP-only, so port 445 doesn't even do any good in this regard. For the actual enumeration of and connecting to shares, port 445 is likely to give some performance increase due to the lower protocol overhead. You can also configure newer Windows machines (XP at least) to *not* support NetBIOS at all, in which case they'll only be listening on port 445. OTOH, there are also plenty of older machines (NT4 and below) that are 139-only. If an XP or other new machine is configured to not support port 139, and it becomes a master browser then how would one get the browse list? Theoretically, it might be optimal to use port 139 to collect browse lists, and then use 445-else-139 for everything else. Barring that, I think 139-else-445 would be the best option. This may be possible to do. The function where cli_initialize() and cli_connect() are called, is passed a server name and a share name. The share name seems to be IPC$ for every call I've seen into here, but is likely a real share name when opening a regular file. I have occasionally seen a server name of IPC$ as well. I suppose I could trace and determine which case is caused by which type of enumeration. Do you know offhand in which case(s) of server and share names I'm looking for a browse list? What if I do 139-else-445 if share is IPC$, and do 445-else-139 otherwise? Thanks, Derrell
Re: smbwrapper use of port 139 vs 445... Ok to force to 139?
On Mon, Dec 23, 2002 at 03:53:08PM -0500, [EMAIL PROTECTED] wrote: For the purposes of getting a browse list, connecting to port 139 is a must. There are ways to get the equivalent of a browse list via AD, but I don't think it's LDAP-only, so port 445 doesn't even do any good in this regard. For the actual enumeration of and connecting to shares, port 445 is likely to give some performance increase due to the lower protocol overhead. You can also configure newer Windows machines (XP at least) to *not* support NetBIOS at all, in which case they'll only be listening on port 445. OTOH, there are also plenty of older machines (NT4 and below) that are 139-only. If an XP or other new machine is configured to not support port 139, and it becomes a master browser then how would one get the browse list? If NetBIOS is disabled, the machine won't participate in browse elections, so it will never become the master browser. If NetBIOS is enabled, I believe that AD-aware machines are given a slight edge (in the form of the 'os level' option) in the browse election. Theoretically, it might be optimal to use port 139 to collect browse lists, and then use 445-else-139 for everything else. Barring that, I think 139-else-445 would be the best option. This may be possible to do. The function where cli_initialize() and cli_connect() are called, is passed a server name and a share name. The share name seems to be IPC$ for every call I've seen into here, but is likely a real share name when opening a regular file. I have occasionally seen a server name of IPC$ as well. I suppose I could trace and determine which case is caused by which type of enumeration. Do you know offhand in which case(s) of server and share names I'm looking for a browse list? What if I do 139-else-445 if share is IPC$, and do 445-else-139 otherwise? AFAIK, the share name will always be IPC$ for server enumeration, but I don't know what other side effects this approach might have. Certainly, the IPC$ share name would be used for other things which are not NetBIOS-dependent. -- Steve Langasek postmodern programmer msg05069/pgp0.pgp Description: PGP signature
Re: [PATCH] and question - net rpc shutdown
Richard Sharpe wrote: On Mon, 23 Dec 2002, Willi Mann wrote: Hi! This patch corrects a problem with the default comment for net rpc shutdown. (diff against 3.0) My power off - problem persists because net rpc shutdown is similar to InitiateSystemShutdown, which is not able to power off the computer. In my research I've found out that powering off needs a Remote API call (if my interpretations of the data on the wire are correct). Is there any function in Samba which can send a remote API call? Do you mean a RAP call? The net function does them. Regards - Richard Sharpe, rsharpe[at]ns.aus.com, rsharpe[at]samba.org, sharpe[at]ethereal.com, http://www.richardsharpe.com The function I'd need is the ExitWindowsEx winapi function. I don't think that rap provides what I need. If you want to help me, there are the links to the initial messages of my problem: http://lists.samba.org/pipermail/samba-technical/2002-December/041366.html http://lists.samba.org/pipermail/samba-technical/2002-December/041369.html One mistake is in that postings: The shutdown method provided in w2k works if the local and the remote user have the same usernames and passwords, it is not requrired that they are in the same domain. Thanks Willi Mann
Swat File
Dear Sir i can not find swat file in the /usr/local/sbin/ ,what can i do ? please help me. Regards Pedram Dehghani System Administrator SG Co.
ÌؼÛÐÂÊé-298ÔªÂòÒ»×ùͼÊé¹Ý
ΪӽÓÊ¥µ®¡¢Ôªµ©£¬ÉîÛÚÍøÂçÊéµêÌØÍƳöÒ»Åúµç×ÓͼÊé¼°ÌؼÛÐÂÊé,µÍÖÁ1ÕÛ¡£ÄúÖ»Ð軨298Ôª¼´¿ÉÓµÓÐÒ»×ù3000²áͼÊéµÄ¼ÒͥͼÊé¹Ý¡£ »áÒé¡¢¸öÈ˽»ÍùÖеÄÀ¡Ôù¾«Æ· ¸öÈËÊղصÄÕäÆ·¡¢Ñ§Ï°µÄ¹¤¾ßÊé µ¥Î»½±ÀøÔ±¹¤µÄÉϼѽ±Æ·¼°¼ÍÄîÆ· ¹Ø°®º¢×ӳɳ¤µÄÌùÉíÀñÎï µç×ÓͼÊéĿ¼£º ¼ÒÍ¥²ØÊ鼯½õ£¨10CD£©298Ôª ÖлªÀúÊ·È«¼¯£¨11CD£©268Ôª ÖÐÍâÎÄѧÃûÖø1000²¿£¨12CD£© 268Ôª Öлª´«ÊÀ²ØÊ飨5CD£© 98Ôª ÖлªÑÞÇéÎĿ⣨4CD£© 98Ôª ÖлªÀúÊ·ÎĿ⣨7CD£© 168Ôª Öлª¾µäÎĿ⣨13CD£©328Ôª ÖлªÕäϡС˵ÎĿ⣨8CD£© 228Ôª ÖйúС°Ù¿ÆÈ«Ê飨1CD£© 38Ôª ÖйúÏÖ´úÎÄѧÃûÖø¾µä¶þ£¨1CD£© 38Ôª ÖÐѧÉú±Ø¶ÁÖÐÍâÎÄѧÃûÖø£¨1CD£© 38Ôª ѧÉú´Çº£´ÇÔ´£¨2CD£© 48Ôª ÊÀ½çÃûÈË´«¼ÇÎÄѧ£¨1CD£© 38Ôª ÏÖÔÚµã»÷½øÈëÉîÛÚÍøÂçÊéµê£º¡¡http://www.szbookshop.com --- ʹÓü«ÐÇÓʼþȺ·¢£¬ÎÞÐëͨ¹ýÓʼþ·þÎñÆ÷£¬Ö±´ï¶Ô·½ÓÊÏ䣬ËٶȾø¶ÔÒ»Á÷£¡ ÏÂÔØÍøÖ·£ºhttp://love2net.51.net/£¬¸ü¶àÃâ·ÑµÄ³¬¿áÈí¼þµÈÄãÀ´Ï¡¡ INFORMATION This message has been sent using a trial-run version of the TSmtpRelayServer Delphi Component.
Re: talloc_init_named
On Mon, Dec 23, 2002 at 08:52:44AM +0100, Stefan (metze) Metzmacher wrote: At 15:58 22.12.2002 +, you wrote: On Sun, Dec 22, 2002 at 10:45:02AM +0100, Stefan (metze) Metzmacher wrote: Hi Jeremy, please run 'grep talloc_init_named source/*/*.c' and 'grep talloc_init() source/*/*.c' please really run it... Done. Jeremy.
CVS update: samba/source/auth
Date: Mon Dec 23 23:53:55 2002 Author: jra Update of /data/cvs/samba/source/auth In directory dp.samba.org:/tmp/cvs-serv3852/auth Modified Files: auth_winbind.c Log Message: Finish adding strings to all talloc_init() calls. Jeremy. Revisions: auth_winbind.c 1.13 = 1.14 http://www.samba.org/cgi-bin/cvsweb/samba/source/auth/auth_winbind.c?r1=1.13r2=1.14
CVS update: samba/source/lib
Date: Mon Dec 23 23:53:55 2002 Author: jra Update of /data/cvs/samba/source/lib In directory dp.samba.org:/tmp/cvs-serv3852/lib Modified Files: talloc.c Log Message: Finish adding strings to all talloc_init() calls. Jeremy. Revisions: talloc.c1.44 = 1.45 http://www.samba.org/cgi-bin/cvsweb/samba/source/lib/talloc.c?r1=1.44r2=1.45
CVS update: samba/source/libsmb
Date: Mon Dec 23 23:53:55 2002 Author: jra Update of /data/cvs/samba/source/libsmb In directory dp.samba.org:/tmp/cvs-serv3852/libsmb Modified Files: netlogon_unigrp.c Log Message: Finish adding strings to all talloc_init() calls. Jeremy. Revisions: netlogon_unigrp.c 1.5 = 1.6 http://www.samba.org/cgi-bin/cvsweb/samba/source/libsmb/netlogon_unigrp.c?r1=1.5r2=1.6
CVS update: samba/source/modules
Date: Mon Dec 23 23:53:55 2002 Author: jra Update of /data/cvs/samba/source/modules In directory dp.samba.org:/tmp/cvs-serv3852/modules Modified Files: mysql.c Log Message: Finish adding strings to all talloc_init() calls. Jeremy. Revisions: mysql.c 1.1 = 1.2 http://www.samba.org/cgi-bin/cvsweb/samba/source/modules/mysql.c?r1=1.1r2=1.2
CVS update: samba/source/python
Date: Mon Dec 23 23:53:55 2002 Author: jra Update of /data/cvs/samba/source/python In directory dp.samba.org:/tmp/cvs-serv3852/python Modified Files: py_lsa.c py_samr.c py_smb.c py_spoolss_drivers.c py_spoolss_ports.c py_spoolss_printers.c Log Message: Finish adding strings to all talloc_init() calls. Jeremy. Revisions: py_lsa.c1.15 = 1.16 http://www.samba.org/cgi-bin/cvsweb/samba/source/python/py_lsa.c?r1=1.15r2=1.16 py_samr.c 1.11 = 1.12 http://www.samba.org/cgi-bin/cvsweb/samba/source/python/py_samr.c?r1=1.11r2=1.12 py_smb.c1.7 = 1.8 http://www.samba.org/cgi-bin/cvsweb/samba/source/python/py_smb.c?r1=1.7r2=1.8 py_spoolss_drivers.c1.20 = 1.21 http://www.samba.org/cgi-bin/cvsweb/samba/source/python/py_spoolss_drivers.c?r1=1.20r2=1.21 py_spoolss_ports.c 1.13 = 1.14 http://www.samba.org/cgi-bin/cvsweb/samba/source/python/py_spoolss_ports.c?r1=1.13r2=1.14 py_spoolss_printers.c 1.24 = 1.25 http://www.samba.org/cgi-bin/cvsweb/samba/source/python/py_spoolss_printers.c?r1=1.24r2=1.25
CVS update: samba/source/sam
Date: Mon Dec 23 23:53:56 2002 Author: jra Update of /data/cvs/samba/source/sam In directory dp.samba.org:/tmp/cvs-serv3852/sam Modified Files: gums_api.c Log Message: Finish adding strings to all talloc_init() calls. Jeremy. Revisions: gums_api.c 1.3 = 1.4 http://www.samba.org/cgi-bin/cvsweb/samba/source/sam/gums_api.c?r1=1.3r2=1.4
CVS update: samba/source/torture
Date: Mon Dec 23 23:53:56 2002 Author: jra Update of /data/cvs/samba/source/torture In directory dp.samba.org:/tmp/cvs-serv3852/torture Modified Files: samtest.c Log Message: Finish adding strings to all talloc_init() calls. Jeremy. Revisions: samtest.c 1.12 = 1.13 http://www.samba.org/cgi-bin/cvsweb/samba/source/torture/samtest.c?r1=1.12r2=1.13
CVS update: samba/source/utils
Date: Mon Dec 23 23:53:56 2002 Author: jra Update of /data/cvs/samba/source/utils In directory dp.samba.org:/tmp/cvs-serv3852/utils Modified Files: rpccheck.c Log Message: Finish adding strings to all talloc_init() calls. Jeremy. Revisions: rpccheck.c 1.6 = 1.7 http://www.samba.org/cgi-bin/cvsweb/samba/source/utils/rpccheck.c?r1=1.6r2=1.7
CVS update: samba/source/lib
Date: Mon Dec 23 23:54:09 2002 Author: jra Update of /data/cvs/samba/source/lib In directory dp.samba.org:/tmp/cvs-serv3844/lib Modified Files: Tag: SAMBA_3_0 talloc.c Log Message: Finish adding strings to all talloc_init() calls. Jeremy. Revisions: talloc.c1.38.2.3 = 1.38.2.4 http://www.samba.org/cgi-bin/cvsweb/samba/source/lib/talloc.c?r1=1.38.2.3r2=1.38.2.4
CVS update: samba/source/nsswitch
Date: Mon Dec 23 23:54:09 2002 Author: jra Update of /data/cvs/samba/source/nsswitch In directory dp.samba.org:/tmp/cvs-serv3844/nsswitch Modified Files: Tag: SAMBA_3_0 winbindd_nss.h Log Message: Finish adding strings to all talloc_init() calls. Jeremy. Revisions: winbindd_nss.h 1.21.2.4 = 1.21.2.5 http://www.samba.org/cgi-bin/cvsweb/samba/source/nsswitch/winbindd_nss.h?r1=1.21.2.4r2=1.21.2.5
CVS update: samba/source/passdb
Date: Mon Dec 23 23:54:09 2002 Author: jra Update of /data/cvs/samba/source/passdb In directory dp.samba.org:/tmp/cvs-serv3844/passdb Modified Files: Tag: SAMBA_3_0 pdb_mysql.c Log Message: Finish adding strings to all talloc_init() calls. Jeremy. Revisions: pdb_mysql.c 1.4.2.4 = 1.4.2.5 http://www.samba.org/cgi-bin/cvsweb/samba/source/passdb/pdb_mysql.c?r1=1.4.2.4r2=1.4.2.5
CVS update: samba/source/libsmb
Date: Mon Dec 23 23:54:09 2002 Author: jra Update of /data/cvs/samba/source/libsmb In directory dp.samba.org:/tmp/cvs-serv3844/libsmb Modified Files: Tag: SAMBA_3_0 netlogon_unigrp.c Log Message: Finish adding strings to all talloc_init() calls. Jeremy. Revisions: netlogon_unigrp.c 1.4.2.1 = 1.4.2.2 http://www.samba.org/cgi-bin/cvsweb/samba/source/libsmb/netlogon_unigrp.c?r1=1.4.2.1r2=1.4.2.2
CVS update: samba/source/python
Date: Mon Dec 23 23:54:10 2002 Author: jra Update of /data/cvs/samba/source/python In directory dp.samba.org:/tmp/cvs-serv3844/python Modified Files: Tag: SAMBA_3_0 py_lsa.c py_samr.c py_smb.c py_spoolss_drivers.c py_spoolss_ports.c py_spoolss_printers.c Log Message: Finish adding strings to all talloc_init() calls. Jeremy. Revisions: py_lsa.c1.14.2.2 = 1.14.2.3 http://www.samba.org/cgi-bin/cvsweb/samba/source/python/py_lsa.c?r1=1.14.2.2r2=1.14.2.3 py_samr.c 1.10.2.2 = 1.10.2.3 http://www.samba.org/cgi-bin/cvsweb/samba/source/python/py_samr.c?r1=1.10.2.2r2=1.10.2.3 py_smb.c1.2.2.3 = 1.2.2.4 http://www.samba.org/cgi-bin/cvsweb/samba/source/python/py_smb.c?r1=1.2.2.3r2=1.2.2.4 py_spoolss_drivers.c1.18.2.3 = 1.18.2.4 http://www.samba.org/cgi-bin/cvsweb/samba/source/python/py_spoolss_drivers.c?r1=1.18.2.3r2=1.18.2.4 py_spoolss_ports.c 1.11.2.3 = 1.11.2.4 http://www.samba.org/cgi-bin/cvsweb/samba/source/python/py_spoolss_ports.c?r1=1.11.2.3r2=1.11.2.4 py_spoolss_printers.c 1.23.2.2 = 1.23.2.3 http://www.samba.org/cgi-bin/cvsweb/samba/source/python/py_spoolss_printers.c?r1=1.23.2.2r2=1.23.2.3
CVS update: samba/source/rpcclient
Date: Mon Dec 23 23:54:10 2002 Author: jra Update of /data/cvs/samba/source/rpcclient In directory dp.samba.org:/tmp/cvs-serv3844/rpcclient Modified Files: Tag: SAMBA_3_0 samsync.c Log Message: Finish adding strings to all talloc_init() calls. Jeremy. Revisions: samsync.c 1.15.2.5 = 1.15.2.6 http://www.samba.org/cgi-bin/cvsweb/samba/source/rpcclient/samsync.c?r1=1.15.2.5r2=1.15.2.6
CVS update: samba/source/utils
Date: Mon Dec 23 23:54:10 2002 Author: jra Update of /data/cvs/samba/source/utils In directory dp.samba.org:/tmp/cvs-serv3844/utils Modified Files: Tag: SAMBA_3_0 rpccheck.c Log Message: Finish adding strings to all talloc_init() calls. Jeremy. Revisions: rpccheck.c 1.6 = 1.6.2.1 http://www.samba.org/cgi-bin/cvsweb/samba/source/utils/rpccheck.c?r1=1.6r2=1.6.2.1
CVS update: samba/docs/docbook/projdoc
Date: Tue Dec 24 01:41:10 2002 Author: jelmer Update of /home/cvs/samba/docs/docbook/projdoc In directory dp.samba.org:/tmp/cvs-serv11036/projdoc Modified Files: pdb_mysql.sgml samba-doc.sgml Log Message: Add note about storing mysql passwords in smb.conf Revisions: pdb_mysql.sgml 1.2 = 1.3 http://www.samba.org/cgi-bin/cvsweb/samba/docs/docbook/projdoc/pdb_mysql.sgml?r1=1.2r2=1.3 samba-doc.sgml 1.18 = 1.19 http://www.samba.org/cgi-bin/cvsweb/samba/docs/docbook/projdoc/samba-doc.sgml?r1=1.18r2=1.19
CVS update: samba/docs
Date: Tue Dec 24 02:01:35 2002 Author: jelmer Update of /home/cvs/samba/docs In directory dp.samba.org:/tmp/cvs-serv12007 Modified Files: docs-status Log Message: Put in actual status Revisions: docs-status 1.10 = 1.11 http://www.samba.org/cgi-bin/cvsweb/samba/docs/docs-status?r1=1.10r2=1.11
