Re: [Samba] samba 3.5.6 - ''smbclient -U% -Llocalhost' results in error - using hostname works fine, new feature?
On 12/18/2010 09:02 PM, Günter Kukkukk wrote: Am Samstag 18 Dezember 2010, 22:04:34 schrieb David C. Rankin: Guys, I have probably missed an announcement or overlooked something in a changelog, but I just want to confirm what I'm seeing is expected behavior. I run samba in standalone mode and I have always checked operation with smbclient -U% -Llocalhost Now the faithful command returns an error: Connection to localhost failed (Error NT_STATUS_BAD_NETWORK_NAME) snip So what say the experts? New security feature? The returned error NT_STATUS_BAD_NETWORK_NAME just says, that for some reason(s) localhost is not a known network name anymore. Have you looked at your smb.conf option setting of name resolve order = ... The default is: name resolve order = lmhosts wins host bcast Thanks Günter -- you nailed it -- but I still don't understand why??? 23:02 providence:~ smbclient -U% -Llocalhost Connection to localhost failed (Error NT_STATUS_BAD_NETWORK_NAME) 23:02 providence:~ grep resolv /etc/samba/smb.conf name resolve order = wins lmhosts bcast 23:03 providence:~ sudo vi /etc/samba/smb.conf 23:05 providence:~ grep resolv /etc/samba/smb.conf name resolve order = host wins lmhosts bcast 23:05 providence:~ sudo /etc/rc.d/samba restart :: Stopping Samba Server [DONE] :: Starting Samba Server [DONE] 23:05 providence:~ smbclient -U% -Llocalhost Domain=[RLFPLLC] OS=[Unix] Server=[Samba 3.5.6] Sharename Type Comment - --- samba Disk Base Samba Share print$ Disk pdf-gen Printer PDF Generator (only valid users) Son-of-a-... That's amazing. I've been using 'name resolve order = wins lmhosts bcast' since 2.0.2 and never run into this issue. What could have changed? Dunno, but it is simple enough to add host back to name resolve order. Thank you sir :p -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] samba 3.5.6 - ''smbclient -U% -Llocalhost' results in error - using hostname works fine, new feature?
Guys, I have probably missed an announcement or overlooked something in a changelog, but I just want to confirm what I'm seeing is expected behavior. I run samba in standalone mode and I have always checked operation with smbclient -U% -Llocalhost Now the faithful command returns an error: Connection to localhost failed (Error NT_STATUS_BAD_NETWORK_NAME) Simply using the hostname instead of localhost works, and samba continues to work fine. So this is really just confirmation request that what I'm seeing is what I'm supposed to be seeing. [14:55 nirvana:/etc] # smbclient -U% -Lnirvana Domain=[RB_LAW] OS=[Unix] Server=[Samba 3.5.6] Sharename Type Comment - --- IPC$IPC IPC Service (Samba 3.5.6) snip So what say the experts? New security feature? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] matchname messages filling logs - howto stop?
On 01/11/2010 03:34 PM, Сергей wrote: Hello, David Jan 11 13:43:45 nemesis smbd[2247]: matchname: host name/address mismatch: :::192.168.7.127 != Adrienne-PC.rbpllc.com Here is reason by plain English. Which IP-adress have Adrienne-PC.rbpllc.com? Bye. Serg Сергей Thank you for the response. I know there is an IP mismatch. That, I get. What I need your help on is how I tell samba to forget about the old IP address of 192.168.7.127 and learn the correct address for Adrienne-PC? Where is this cached and how do I get rid of it? Samba isn't seeing something correctly. For example, here is the same problem with a machine named reception (in the reception area): Jan 13 12:43:19 nemesis smbd[7449]: Matchname failed on RECEPTION.rbpllc.com :::192.168.7.150 Jan 13 12:50:46 nemesis smbd[7474]: [2010/01/13 12:50:46, 0] lib/util_sock.c:1564(matchname) Jan 13 12:50:46 nemesis smbd[7474]: matchname: host name/address mismatch: :::192.168.7.150 != RECEPTION.rbpllc.com Jan 13 12:50:46 nemesis smbd[7474]: [2010/01/13 12:50:46, 0] lib/util_sock.c:1685(get_peer_name) Jan 13 12:50:46 nemesis smbd[7474]: Matchname failed on RECEPTION.rbpllc.com :::192.168.7.150 Samba is saying there is a mismatch between reception and the IP of 192.168.7.150 -- but that is WRONG! 13:19 nemesis:~ ping reception PING reception.rbpllc.com (192.168.7.150) 56(84) bytes of data. 64 bytes from RECEPTION.rbpllc.com (192.168.7.150): icmp_seq=1 ttl=128 time=3.16 ms 64 bytes from RECEPTION.rbpllc.com (192.168.7.150): icmp_seq=2 ttl=128 time=0.311 ms 64 bytes from RECEPTION.rbpllc.com (192.168.7.150): icmp_seq=3 ttl=128 time=0.309 ms ^C --- reception.rbpllc.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 0.309/1.262/3.166/1.346 ms Here is the dns entry: [13:23 nemesis:/home/david] # sdns $ORIGIN . $TTL 172800 ; 2 days rbpllc.com IN SOA bonza.rbpllc.com. root.bonza.rbpllc.com. ( 2009122700 ; serial 10800 ; refresh (3 hours) 3600 ; retry (1 hour) 604800 ; expire (1 week) 86400 ; minimum (1 day) ) NS bonza.rbpllc.com. NS nemesis.rbpllc.com. MX 0 bonza.rbpllc.com. $ORIGIN rbpllc.com. snip rankin-p35a A 192.168.7.101 $TTL 14400 ; 4 hours RECEPTION A 192.168.7.150 TXT 31070f4d9f3c8435ddf3a0641b740d7fdd snip and the reverse: [13:23 nemesis:/home/david] # cat /var/lib/named/dyn/192.168.7.zone $ORIGIN . $TTL 172800 ; 2 days 7.168.192.in-addr.arpa IN SOA bonza.rbpllc.com. root.bonza.rbpllc.com. ( 2009122700 ; serial 10800 ; refresh (3 hours) 3600 ; retry (1 hour) 604800 ; expire (1 week) 86400 ; minimum (1 day) ) NS bonza.rbpllc.com. NS nemesis.rbpllc.com. $ORIGIN 7.168.192.in-addr.arpa. 101 PTR rankin-p35a.rbpllc.com. snip $TTL 14400 ; 4 hours 150 PTR RECEPTION.rbpllc.com. So why is there a mismatch error filling my logs? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] matchname messages filling logs - howto stop?
Listmates, I have had a few boxes where the 'matchname' message is filling my syslog with one new message ever ~40 seconds or so. No performance problems, just the log annoyance. An example of the messages are: Jan 11 13:43:03 nemesis smbd[2246]: [2010/01/11 13:43:03, 0] lib/util_sock.c:1685(get_peer_name) Jan 11 13:43:03 nemesis smbd[2246]: Matchname failed on Adrienne-PC.rbpllc.com :::192.168.7.127 Jan 11 13:43:45 nemesis smbd[2247]: [2010/01/11 13:43:45, 0] lib/util_sock.c:1564(matchname) Jan 11 13:43:45 nemesis smbd[2247]: matchname: host name/address mismatch: :::192.168.7.127 != Adrienne-PC.rbpllc.com Jan 11 13:43:45 nemesis smbd[2247]: [2010/01/11 13:43:45, 0] lib/util_sock.c:1685(get_peer_name) Jan 11 13:43:45 nemesis smbd[2247]: Matchname failed on Adrienne-PC.rbpllc.com :::192.168.7.127 Jan 11 13:52:22 nemesis smbd[2270]: [2010/01/11 13:52:22, 0] lib/util_sock.c:1564(matchname) Jan 11 13:52:22 nemesis smbd[2270]: matchname: host name/address mismatch: :::192.168.7.127 != Adrienne-PC.rbpllc.com Jan 11 13:52:22 nemesis smbd[2270]: [2010/01/11 13:52:22, 0] lib/util_sock.c:1685(get_peer_name) Jan 11 13:52:22 nemesis smbd[2270]: Matchname failed on Adrienne-PC.rbpllc.com :::192.168.7.127 Jan 11 13:53:04 nemesis smbd[2271]: [2010/01/11 13:53:04, 0] lib/util_sock.c:1564(matchname) Jan 11 13:53:04 nemesis smbd[2271]: matchname: host name/address mismatch: :::192.168.7.127 != Adrienne-PC.rbpllc.com Jan 11 13:53:04 nemesis smbd[2271]: [2010/01/11 13:53:04, 0] lib/util_sock.c:1685(get_peer_name) Jan 11 13:53:04 nemesis smbd[2271]: Matchname failed on Adrienne-PC.rbpllc.com :::192.168.7.127 Jan 11 13:53:46 nemesis smbd[2272]: [2010/01/11 13:53:46, 0] lib/util_sock.c:1564(matchname) Jan 11 13:53:46 nemesis smbd[2272]: matchname: host name/address mismatch: :::192.168.7.127 != Adrienne-PC.rbpllc.com Jan 11 13:53:46 nemesis smbd[2272]: [2010/01/11 13:53:46, 0] lib/util_sock.c:1685(get_peer_name) Jan 11 13:53:46 nemesis smbd[2272]: Matchname failed on Adrienne-PC.rbpllc.com :::192.168.7.127 The message is generated between an XP box and the samba server which is setup in standalone mode. The basic configuration is: [global] workgroup = RB_LAW server string = Samba %v map to guest = Bad User log file = /var/log/samba/log.%m max log size = 100 smb ports = 139 name resolve order = wins lmhosts bcast time server = Yes printcap name = cups disable spoolss = Yes show add printer wizard = No os level = 58 dns proxy = No wins server = 192.168.7.15 admin users = david hosts allow = 192.168.7., 192.168.6., 192.168.8., 192.168.5., 127. [homes] comment = Home Directories read only = No browseable = No browsable = No [samba] comment = Nemesis Law path = /home/samba valid users = @office, anna force group = office read only = No inherit permissions = Yes [printers] comment = All Printers path = /var/spool/samba create mask = 0700 guest ok = Yes printable = Yes use client driver = Yes browseable = No browsable = No [print$] path = /var/lib/samba/drivers write list = @adm, root inherit permissions = Yes guest ok = Yes I have had this same problem on several boxes and I haven't been able to chase down the cause. I get that samba is saying that there is a mismatch between the hostname and the address for the IPV6 address :::192.168.7.127 != Adrienne-PC.rbpllc.com. The problem is I don't know where samba is caching this information or how to prevent samba from considering this box and address to be mismatched. I apologize if this has been asked and answered before, but I haven't had the time to monitor the list on a daily basis as I have had in the past. Could somebody shed some light on how I can solve this problem. I would rather not simply drop the log level to hide the error, I would prefer to fix it. Thanks. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] smbd error: Matchname failed on (machine name)
Listmates, Samba has been trouble free for some time, but I have a very strange error related to one machine on my network that is filling my logs with smb errors. The box in question ripper is a normal WinXP box that is dual-boot with SuSE 10.3. The errors are received every 30 minutes or so: Aug 21 17:04:03 archangel smbd[3116]: [2009/08/21 17:04:03, 0] lib/util_sock.c:matchname(1749) Aug 21 17:04:03 archangel smbd[3116]: matchname: host name/address mismatch: :::192.168.6.149 != ripper.3111skyline.com Aug 21 17:04:03 archangel smbd[3116]: [2009/08/21 17:04:03, 0] lib/util_sock.c:get_peer_name(1870) Aug 21 17:04:03 archangel smbd[3116]: Matchname failed on ripper.3111skyline.com :::192.168.6.149 Aug 21 17:35:53 archangel smbd[3120]: [2009/08/21 17:35:53, 0] lib/util_sock.c:matchname(1749) Aug 21 17:35:53 archangel smbd[3120]: matchname: host name/address mismatch: :::192.168.6.149 != ripper.3111skyline.com Aug 21 17:35:53 archangel smbd[3120]: [2009/08/21 17:35:53, 0] lib/util_sock.c:get_peer_name(1870) Aug 21 17:35:53 archangel smbd[3120]: Matchname failed on ripper.3111skyline.com :::192.168.6.149 There are 10 other boxes on the local subnet 6 are dual-boot WinXP Linux. I don't get this error with any of the others. The server is Archlinux with samba 3.3.7-1. The smb.conf is: [global] use sendfile = No workgroup = rb_law server string = Samba %v printcap name = cups load printers = yes printing = cups show add printer wizard = no disable spoolss = yes log file = /var/log/samba/log.%m max log size = 100 time server = yes admin users = david smb ports = 139 hosts allow = 192.168.7. 192.168.6. 192.168.8. 192.168.5. map to guest = bad user security = user encrypt passwords = yes smb passwd file = /etc/samba/smbpasswd socket options = TCP_NODELAY local master = no os level = 56 name resolve order = wins lmhosts bcast wins server = 192.168.6.17 dns proxy = no usershare allow guests = No [homes] comment = Home Directories browseable = no writable = yes What should I check to try to stop the errors? Both boxes get rebooted fairly regularly and no matter, the error always comes back. Let me know if I can send additional information and I'll be happy to. Thanks. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Broken Pipes openSuSE 10.3 samba-3.3.4
Guys, After upgrade to samba 3.3.4 on openSuSE 10.3, I'm getting: Jul 10 02:05:14 bonza smbd[31942]: [2009/07/10 02:05:14, 0] lib/util_sock.c:write_data(1136) Jul 10 02:05:14 bonza smbd[31942]: [2009/07/10 02:05:14, 0] lib/util_sock.c:get_peer_addr_internal(1676) Jul 10 02:05:14 bonza smbd[31942]: getpeername failed. Error was Transport endpoint is not connected Jul 10 02:05:14 bonza smbd[31942]: write_data: write failure in writing to client 0.0.0.0. Error Broken pipe Jul 10 02:05:14 bonza smbd[31942]: [2009/07/10 02:05:14, 0] smbd/process.c:srv_send_smb(74) Jul 10 02:05:14 bonza smbd[31942]: Error writing 61503 bytes to client. -1. (Transport endpoint is not connected) Jul 10 02:05:14 bonza smbd[31942]: [2009/07/10 02:05:14, 0] lib/util_sock.c:write_data(1136) Jul 10 02:05:14 bonza smbd[31942]: [2009/07/10 02:05:14, 0] lib/util_sock.c:get_peer_addr_internal(1676) Jul 10 02:05:14 bonza smbd[31942]: getpeername failed. Error was Transport endpoint is not connected Jul 10 02:05:14 bonza smbd[31942]: write_data: write failure in writing to client 0.0.0.0. Error Broken pipe Jul 10 02:05:14 bonza smbd[31942]: [2009/07/10 02:05:14, 0] smbd/process.c:srv_send_smb(74) Jul 10 02:05:14 bonza smbd[31942]: Error writing 75 bytes to client. -1. (Transport endpoint is not connected) All file transfers want to stop at 7558640 bytes. I haven't seen broken pipes in years. Any ideas? This server operates in standalone: [global] workgroup = RB_LAW server string = Samba Server %v map to guest = Bad User log level = 1 log file = /var/log/samba/log.%m max log size = 500 smb ports = 139 name resolve order = wins lmhosts bcast time server = Yes socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 printcap name = cups disable spoolss = Yes show add printer wizard = No os level = 80 preferred master = Yes domain master = Yes dns proxy = No wins support = Yes hosts allow = 192.168.7., 192.168.8., 127., 66.76.63.120 [homes] comment = Home Directories read only = No browseable = No Dunno what to check? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] samba 3.3.4-1, lib/util_sock.c:matchname(1749) error??
Listmates, On my Archlinux server with samba 3.3.4-1, I am getting a smbd error that is filling my logs and I'm not sure why. The box 'ripper.3111skyline.com' shown below is a dual boot box and spends most of its life and mom's XP box and masquerades as an openSuSE 10.3 box the rest of the time. There are seven other boxes on this lan with 5 others being dual boot XP/openSuSE or Archlinux and none of the other boxes appear in the logs -- so why ripper? Jun 16 19:38:45 archangel smbd[18210]: [2009/06/16 19:38:45, 0] lib/util_sock.c:matchname(1749) Jun 16 19:38:45 archangel smbd[18210]: matchname: host name/address mismatch: :::192.168.6.149 != ripper.3111skyline.com Jun 16 19:38:45 archangel smbd[18210]: [2009/06/16 19:38:45, 0] lib/util_sock.c:get_peer_name(1870) Jun 16 19:38:45 archangel smbd[18210]: Matchname failed on ripper.3111skyline.com :::192.168.6.149 The smb.conf configures the Arch server in stand-alone mode as a simple file server. [global] use sendfile = No workgroup = rb_law server string = Samba %v printcap name = cups load printers = yes printing = cups show add printer wizard = no disable spoolss = yes log file = /var/log/samba/log.%m max log size = 100 time server = yes admin users = david smb ports = 139 hosts allow = 192.168.8. 192.168.5. 127. 66.76.63.60 map to guest = bad user security = user encrypt passwords = yes smb passwd file = /etc/samba/smbpasswd socket options = TCP_NODELAY local master = no os level = 56 name resolve order = wins lmhosts bcast wins server = 192.168.6.17 dns proxy = no usershare allow guests = No [homes] comment = Home Directories browseable = no writable = yes snip of printers.. I don't know whether there is something stuck in a browse list cache somewhere or whether there is an issue with addressing with this one machine, but I have not been able to solve it and needed to beg a bit of advise from the experts. So what should I check, test, etc. to help figure out what is causing this issue? Thanks in advance for any help. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Where do I get ldapsmb-1.34b.tar.bz2? to build suse 3.3.3 rpm??
Listmates, The openSuSE 10.3 spec file call for ldapsmb-1.34b.tar.bz2, but I can't find it anywhere. What say the gurus? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Win98 - 3.0.28a OK, Win98 - 3.2.7 No Good??
Listmates, I have a perplexing problem. I brought an old Toshiba laptop back from the lakehouse to update it, etc. I also brought the server back to. On out local network, I can see all the boxes in the network from the laptop (hostname: dcrlaptop), but I can only connect to it's normal server (hostname: lakehouse). dcrlaptop is running Win98 and the host I am trying to connect to is running openSuSE 10.3. The exact samba version numbers are 3.0.28a-0.1.104-1670-SUSE-SL10.3 and 3.2.7-0.1.135-2042-SUSE-SL10, respectively. (and yes, they are both on the same 'Workgroup' to make the laptop happy. One thing that is really strange (and that I have seen in about 5 years) is windows shrowing up the good old host/IPC password entry dialog box. I know there was a fix for this back in the 2.0 days, but dang'it, I cant remember a thing about the solution. What are you thought on the fact that 3.2.7 not letting a simple Win98 laptop log into 3.2.7. Obviously, this laptop had never had any issue up through 3.0.28a. What say the gurus on what i should try next? ** an aside: I have two ancient laptops that I try to keep relatively current the first is a dell with an 11 screen (640x480) from either late '95 or early '96 and the other is a Toshiba PIII 800. Both still work fine, that is like the 62 Chevy Pickup your grandparent used to have... ;-) Any help would be greatly appreciated. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Install of Samba 3.2.8-2 rpms failed to restart smbd and nmbd
Listmates: An update of samba via the binary rpms Samba 3.2.8-2.1.140-2082-SUSE-SL11.0 failed to restart the server? This is the first time in years this has happened. Was Lars checking out skirts while building the rpms? Or, was there another problem: Mar 9 11:41:53 ecstasy nmbd[2842]: [2009/03/09 11:41:53, 0] nmbd/nmbd.c:terminate(68) Mar 9 11:41:53 ecstasy nmbd[2842]: Got SIGTERM: going down... Mar 9 11:41:53 ecstasy smbd[24505]: [2009/03/09 11:41:53, 0] lib/fault.c:fault_report(40) Mar 9 11:41:53 ecstasy smbd[24505]: === Mar 9 11:41:53 ecstasy smbd[24505]: [2009/03/09 11:41:53, 0] lib/fault.c:fault_report(41) Mar 9 11:41:53 ecstasy smbd[24505]: INTERNAL ERROR: Signal 7 in pid 24505 (3.2.7-0.1.135-2042-SUSE-SL11.0) Mar 9 11:41:53 ecstasy smbd[24505]: Please read the Trouble-Shooting section of the Samba3-HOWTO Mar 9 11:41:53 ecstasy smbd[24505]: [2009/03/09 11:41:53, 0] lib/fault.c:fault_report(43) Mar 9 11:41:53 ecstasy smbd[24505]: Mar 9 11:41:53 ecstasy smbd[24505]: From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf Mar 9 11:41:53 ecstasy smbd[24505]: [2009/03/09 11:41:53, 0] lib/fault.c:fault_report(44) Mar 9 11:41:53 ecstasy smbd[24505]: === Mar 9 11:41:53 ecstasy smbd[24505]: [2009/03/09 11:41:53, 0] lib/util.c:smb_panic(1663) Mar 9 11:41:53 ecstasy smbd[24505]: PANIC (pid 24505): internal error Mar 9 11:41:54 ecstasy smbd[24505]: [2009/03/09 11:41:54, 0] lib/util.c:log_stack_trace(1767) Mar 9 11:41:54 ecstasy smbd[24505]: BACKTRACE: 22 stack frames: Mar 9 11:41:54 ecstasy smbd[24505]:#0 /usr/sbin/smbd(log_stack_trace+0x1a) [0x7f05e4125dea] Mar 9 11:41:54 ecstasy smbd[24505]:#1 /usr/sbin/smbd(smb_panic+0x1f) [0x7f05e4125ebf] Mar 9 11:41:54 ecstasy smbd[24505]:#2 /usr/sbin/smbd [0x7f05e4110dc0] Mar 9 11:41:54 ecstasy smbd[24505]:#3 /lib64/libpthread.so.0 [0x7f05e1cd5b30] Mar 9 11:41:54 ecstasy smbd[24505]:#4 /lib64/libc.so.6(memcpy+0x35) [0x7f05e02f9c35] Mar 9 11:41:54 ecstasy smbd[24505]:#5 /usr/sbin/smbd [0x7f05e4109ea5] Mar 9 11:41:54 ecstasy smbd[24505]:#6 /usr/sbin/smbd [0x7f05e41056e6] Mar 9 11:41:54 ecstasy smbd[24505]:#7 /usr/sbin/smbd(tdb_find_lock_hash+0x63) [0x7f05e4105803] Mar 9 11:41:54 ecstasy smbd[24505]:#8 /usr/sbin/smbd(tdb_parse_record+0x4d) [0x7f05e410592d] Mar 9 11:41:54 ecstasy smbd[24505]:#9 /usr/sbin/smbd [0x7f05e41023ea] Mar 9 11:41:54 ecstasy smbd[24505]:#10 /usr/sbin/smbd(connections_fetch_entry+0x8f) [0x7f05e41346bf] Mar 9 11:41:54 ecstasy smbd[24505]:#11 /usr/sbin/smbd(yield_connection+0x36) [0x7f05e3f37b56] Mar 9 11:41:54 ecstasy smbd[24505]:#12 /usr/sbin/smbd(close_cnum+0xac) [0x7f05e3f9fd1c] Mar 9 11:41:54 ecstasy smbd[24505]:#13 /usr/sbin/smbd(conn_close_all+0x3d) [0x7f05e3f3efbd] Mar 9 11:41:54 ecstasy smbd[24505]:#14 /usr/sbin/smbd [0x7f05e431df03] Mar 9 11:41:54 ecstasy smbd[24505]:#15 /usr/sbin/smbd [0x7f05e431e0be] Mar 9 11:41:54 ecstasy smbd[24505]:#16 /usr/sbin/smbd [0x7f05e3f9cbe6] Mar 9 11:41:54 ecstasy smbd[24505]:#17 /usr/sbin/smbd [0x7f05e3f9e767] Mar 9 11:41:54 ecstasy smbd[24505]:#18 /usr/sbin/smbd(smbd_process+0x14b) [0x7f05e3f9f1ab] Mar 9 11:41:54 ecstasy smbd[24505]:#19 /usr/sbin/smbd(main+0x1fa2) [0x7f05e43200e2] Mar 9 11:41:54 ecstasy smbd[24505]:#20 /lib64/libc.so.6(__libc_start_main+0xe6) [0x7f05e0297436] Mar 9 11:41:54 ecstasy smbd[24505]:#21 /usr/sbin/smbd [0x7f05e3f25df9] Mar 9 11:41:54 ecstasy smbd[24505]: [2009/03/09 11:41:54, 0] lib/fault.c:dump_core(201) Mar 9 11:41:54 ecstasy smbd[24505]: dumping core in /var/log/samba/cores/smbd Mar 9 11:41:54 ecstasy smbd[24505]: Dumb of core was empty. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Can't modify ms word files with samba 3.3
Jeremy Allison wrote: On Wed, Mar 04, 2009 at 07:29:15PM +0100, Michele Petrazzo - Unipex srl wrote: Jeremy Allison wrote: Ok, that's very helpful and also tells me why I've seen few problem reports of this. Can you try the test patch for 3.3.1 I just published ? The error changes: before I had a Access Deny and now a there's been a network error here is the picture: http://s5.tinypic.com/xcpug6.jpg A wireshark trace between Office2K7 and a Windows server would also be very helpful. I'll do in few minutes and I'll send you it. Ok, I think the following patch should fix the issues you're seeing. It should apply on top of, or in place of my previous patch - shouldn't matter. It causes all opens requiring SEC_RIGHT_SYSTEM_SECURITY to fail as Windows does with NT_STATUS_PRIVILEGE_NOT_HELD, which should cause the client to correctly back down and rety the open without this privilege. Let me know if it works for you ! Thanks, Jeremy. Jeremy, All, I installed 3.3.1 in standalone mode on openSuSE 11.0. No problems reading and writing MS Word files to/from the server with Word 2007 (word 97-03 .doc format) I pulled level 10's just in case anyone wanted to see them for comparison, etc.. (Not that they would show anything that exciting) -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] Bizarre - How did windows user setfacl for a file??
Jeremy Allison wrote: On Thu, Nov 20, 2008 at 02:51:08AM -0600, David C. Rankin wrote: very bad. It causes errors in the backup where the files acl tell the backup that it doesn't have permission to access the files, even though based on the linux file permissions it does. So it is kind of mess. You can always mount the filesystem without the acl flag, then Samba will fall back to only allowing u/g/o permissions. Jeremy. That's what I've done until I find out what applications is setting the acls -- #$%^%#$windows.. Thanks -- David C. Rankin, J.D.,P.E. | Rankin Law Firm, PLLC | Countdown for openSuSE 11.1 510 Ochiltree Street|http://counter.opensuse.org/11.1/small Nacogdoches, Texas 75961| Telephone: (936) 715-9333 | openSoftware und SystemEntwicklung Facsimile: (936) 715-9339 | http://www.opensuse.org/ www.rankinlawfirm.com | -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Bizarre - How did windows user setfacl for a file??
Dennis Clarke wrote: Listmates, In 8 years, since 2.02 (I think), I have never seen this ... You never know, this may be a desired feature. The question is, why is this a bad thing? I am not much of a Windows user and thus I really have to wonder why the ACL's create an issue. This is just a question from me to get some insight into the implications of ACL's delivered to the world via Samba. Also, you did not tell us if the underlying fs was ext3fs or ufs or zfs or what. Dennis Sorry for the late reply, but the ACL are bad to my rsync backup routines -- very bad. It causes errors in the backup where the files acl tell the backup that it doesn't have permission to access the files, even though based on the linux file permissions it does. So it is kind of mess. -- David C. Rankin, J.D.,P.E. | Rankin Law Firm, PLLC | Countdown for openSuSE 11.1 510 Ochiltree Street|http://counter.opensuse.org/11.1/small Nacogdoches, Texas 75961| Telephone: (936) 715-9333 | openSoftware und SystemEntwicklung Facsimile: (936) 715-9339 | http://www.opensuse.org/ www.rankinlawfirm.com | -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Bizarre - How did windows user setfacl for a file??
Greg Byshenk wrote: On Wed, Nov 12, 2008 at 01:46:45AM -0600, David C. Rankin wrote: In 8 years, since 2.02 (I think), I have never seen this behavior out of samba. I run a stand-alone server with WinXP clients. Somehow a legal assistant created (not intentionally mind you) files and directories with ACL attributes set: -rwxrwx---+ 1 cyndy ochiltree 21504 2008-10-28 16:48 AUTHORIZATION - employment.doc* -rwxrwx---+ 1 cyndy ochiltree 12804 2008-10-28 16:48 AUTHORIZATION - employment.pdf* drwxrwx---+ 2 cyndy ochiltree 4096 2008-10-29 16:56 Gregg, Joy/ -rwxrwx---+ 1 cyndy ochiltree 44544 2008-10-28 16:32 POA - BG Contingency New.doc* -rwxrwx---+ 1 cyndy ochiltree 48309 2008-10-28 16:31 POA - BG Contingency New.pdf* drwxrwx---+ 2 cyndy ochiltree 4096 2008-10-29 16:51 Roper, Buddy/ What in the heck? I found the setfacl --remove-all command that gets rid of this, but I'm still left wondering WTF happened in the first place? Moreover, how do I configure samba to make sure this never happens again? My config is: [...] I'm not sure for exactly how long, but Samba has supported extended ACLs for quite some time (if the underlying OS/filesystem has such support). To ensure that it is not there, you can either a) build samba without acl support; or b) disable extended ACLs on the filesystem. As for why it changed for you, I notice that the default configuration is now (for Samba-3.2.4, at least) --with-acl-support Include ACL support (default=auto) ... which I believe means that it will build in ACL support if the system has it. Perhaps this has changed recently? Greg I suspect you are 100% correct. Some of the legal applications that run on the server do use ACLs controls. I suspect this has always been the case, but after 3.2.4, they decided to introduce themselves to me ;-) -- David C. Rankin, J.D.,P.E. | Rankin Law Firm, PLLC | Countdown for openSuSE 11.1 510 Ochiltree Street|http://counter.opensuse.org/11.1/small Nacogdoches, Texas 75961| Telephone: (936) 715-9333 | openSoftware und SystemEntwicklung Facsimile: (936) 715-9339 | http://www.opensuse.org/ www.rankinlawfirm.com | -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Bizarre - How did windows user setfacl for a file??
Listmates, In 8 years, since 2.02 (I think), I have never seen this behavior out of samba. I run a stand-alone server with WinXP clients. Somehow a legal assistant created (not intentionally mind you) files and directories with ACL attributes set: -rwxrwx---+ 1 cyndy ochiltree 21504 2008-10-28 16:48 AUTHORIZATION - employment.doc* -rwxrwx---+ 1 cyndy ochiltree 12804 2008-10-28 16:48 AUTHORIZATION - employment.pdf* drwxrwx---+ 2 cyndy ochiltree 4096 2008-10-29 16:56 Gregg, Joy/ -rwxrwx---+ 1 cyndy ochiltree 44544 2008-10-28 16:32 POA - BG Contingency New.doc* -rwxrwx---+ 1 cyndy ochiltree 48309 2008-10-28 16:31 POA - BG Contingency New.pdf* drwxrwx---+ 2 cyndy ochiltree 4096 2008-10-29 16:51 Roper, Buddy/ What in the heck? I found the setfacl --remove-all command that gets rid of this, but I'm still left wondering WTF happened in the first place? Moreover, how do I configure samba to make sure this never happens again? My config is: [global] use sendfile = No workgroup = rb_law server string = Samba Server %v printcap name = cups load printers = yes printing = cups show add printer wizard = No disable spoolss = yes log file = /var/log/samba/log.%m max log size = 500 smb ports = 139 log level = 1 time server = yes hosts allow = 192.168.7. 192.168.8. 127. 66.76.63.120 map to guest = bad user security = user encrypt passwords = yes smb passwd file = /etc/samba/smbpasswd socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 local master = yes os level = 80 domain master = yes preferred master = yes name resolve order = wins lmhosts bcast wins support = yes dns proxy = no [samba] comment = Base Samba Share path = /home/samba valid users = @ochiltree force group = ochiltree admin users = david browseable = Yes writeable = Yes force create mode = 0770 force directory mode = 0770 What do I need to change? Thanks for any help you can give. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] samba member of workgroup
Fernando wrote: Hello, I want to setup a samba server http://www.linuxquestions.org/questions/#as a member of a workgroup, for example MYWORKGROUP. I want to share a folder, for example /share. This share should be available to example.com domain clients only. Can someone give me a smb.conf for that? Would that do it? [global] workgroup = MYWORKGROUP server string = Samba Server Version %v security = domain hosts allow = .example.com [share] comment = Public Stuff path = /share public = no writable = no printable = no Thank you. Here is what I have used without any problems for the past 8 years. [global] use sendfile = No workgroup = rb_law server string = Samba %v printcap name = cups load printers = yes printing = cups show add printer wizard = no disable spoolss = yes log file = /var/log/samba/log.%m max log size = 100 time server = yes admin users = thomas smb ports = 139 hosts allow = 192.168.7. 192.168.6. 192.168.8. 192.168.5. 127. domain logons = yes map to guest = bad user security = user encrypt passwords = yes smb passwd file = /etc/samba/smbpasswd socket options = TCP_NODELAY local master = yes os level = 69 domain master = yes preferred master = yes name resolve order = wins lmhosts bcast wins support = yes dns proxy = no usershare allow guests = No [homes] comment = Home Directories browseable = no writable = yes [samba] comment = SambaShares - Pictures, Law path = /home/samba valid users = @shoreline, anna force group = shoreline admin users = thomas browseable = Yes writeable = Yes inherit permissions = yes -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] XP cannot read files after upgrade to Debian Samba 3.2.3
Veselin Kantsev wrote: Thank you much Jeremy, Do you know of some temporary workaround that I can use for the time being? Regards, Veselin, The simplest way would be to download a copy of the 3.0.24 that you know will work and install that on the 3.2.3 machine. You don't need to remove 3.2.3, you can simply install 2.0.24 in the default location of /usr/local/samba. You are probably safe with 3.0.31. Just download the tarball at: http://us3.samba.org/samba/ftp/samba-3.0.31.tar.gz If you need 3.0.24: http://us1.samba.org/samba/ftp/old-versions/samba-3.0.24.tar.gz Then simply: (1) tar -xzf samba-3.0.24.tar.gz# untar the source (2) cd samba-3.0.24/src # change to the src directory (3) ./configure # default install in /usr/local/samba ** install any missing packages (gcc, etc..) (4) make (5) make install ** now figure out where your smb.conf and smbpasswd files are stored and where you want you log files. (Usually /etc/samba/ and /var/log) Assumed in step (7) ** make sure you stop 3.2.3 (smbd and nmbd), change to the /usr/local/samba/bin directory then start your new version of each: (6) cd /usr/local/samba/bin # new executable location (7)(a) ./nmbd --daemon --configfile=/etc/samba/smb.conf --log-basename=log.nmb.test (7)(b) ./smbd --daemon --configfile=/etc/samba/smb.conf --log-basename log.smb.test --smb-passwd-file=/etc/samba/smbpasswd --private-dir=/etc/samba If disaster strikes and everything goes bad, not to worry, simply issue the command (8) make revert # Restores original 3.2.3 binaries #+if they were overwritten That's it. Takes about 20 minutes total. Your new self-compiled samba will run just fine until Jeremy is done looking at the problem. It is always good to have this work-around in your hip-pocket just in case a 'new feature' is introduced in the latest release ;-) -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Very Slow!
Jeremy Allison wrote: On Fri, Aug 29, 2008 at 12:54:53PM -0500, Gregory Carter wrote: Oh, and BY THE WAY. I do not want to be a total cynic, but you are expecting samba to replace a software product that the SuSE corporation directly receives MILLIONS in contributions from, said vendor of product it is replacing. (Microsoft.) Lars and Jim at SuSE are both Samba Team members, and there is no question of any corruption or source code changes in SuSE that are detremental to Samba. Whilst not getting into distro-wars, worries about the state of Samba in SuSE is *NOT* a reason to change your distribution from SuSE to any other. Jeremy. That I will personally confirm with flawless samba operation at my office for over 8 years and on SuSE since 8.0. (we just won't mention those older gotchas like rabbit pellet packet fragmentation, that little UID GID snafu or the little bugger in 3.2.1) All of which I can safely say SuSE had nothing to do with;-) Seriously, we have samba running on an older production box with an athlon 2800 and SuSE 10.3. We have no problems at all xfering the video files we deal with on a regular basis. (3 - 8 Gig range) Transferring to or from win machines isn't any noticeably faster or slower than ftp, or rsync. Ah, the beauty of a stand-alone setup -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Very Slow!
Volker Lendecke wrote: On Thu, Aug 28, 2008 at 02:20:09PM -0700, Brian McGrew wrote: socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 Quick try: Remove that. Curious question -- why did you set those options? Volker That is in the default smb.conf distributed with many distros. I have been using: socket options = TCP_NODELAY However, I can't tell any difference in xfers, they all work fine here. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba and Vista Home Prem login problems
Brad Sacks wrote: Hi, Thanks for the replies. I haven't used Samba that much so I appreciate the help. I guess I didn't have logging turned on and I wasn't on 3.2.1. So I got 3.2.1 and turned on logging. This is the error I get when I connect on that share: [2008/08/17 09:35:57, 1] lib/util_sock.c:get_peer_name(1791) get_peer_name: getnameinfo failed for 192.168.1.3 with error Temporary failure in name resolution You have a problem with the 2 computers being able to talk to each other, a name resolution problem. I see you have configured samba to act as a wins server for your network. Is there another MS server acting as a wins server or domain controller? Also, basic name resolution. Are you using /etc/hosts for name resolution or are you using a DNS. If so is it configured properly? Are you using dhcp to get your IP or do you have static IPs assigned? This is where the immediate problem lies. Your config look OK -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba and Vista Home Prem login problems
Ryan Novosielski [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brad Sacks wrote: I have a simple peer to peer setup with security = user. I only have two machines, one Vista and one Linux. I have two shares, one is the tmp folder and I enabled public access, the other is a user owned folder with read, write and execute permissions. I can see my Samba shares from my Vista machine and I can access the tmp folder, but I can't log on to the user protected one. I have encrypted passwords and password level 8. I used force user in the share definition. I can map the drive, but I can't access it. When I try smbclient -L \\Mybox\share -Uuser I can connect to it from the samba machine. I'm sort of at a loss now. I've tried a lot of stuff. Any ideas would be appreciated. What do the logs say about why you can't connect? That's your first stop. Concur. I have vista home premium running and I have now connection problems whatsoever. CIFS was broken for a time in the3.2.0xy version, but it is performing great now on 3.2.1 -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Typo in man mount.cifs - who maintains ?
Samba Team, I'm looking for Steve French's contact info concerning the man page for mount.cifs. There is a small typo to report (double-the): setuids If the CIFS Unix extensions are negotiated with the server the client will attempt to set the effective uid and gid of the local process on newly created files, directories, and devices (create, mkdir, mknod). If the CIFS Unix Extensions are not negotiated, for newly created files and directories instead of using the default uid and gid specified on the the mount, cache the new file´s uid and gid locally which means that the uid for the file can change when the inode is reloaded (or the user remounts the share). I checked the samba-cifs page, but could find his contact. Could somebody please forward this to him. Thanks. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Printing XP - 3.2 Now really slow (just like the old days)
Guys, My wife needed to print something this evening to our normal HP 4 attached to our cups server running samba-3.2.1-0.1.126. Nothing has changed in the last two months going from 3.0.28a to the 3.2.x flavor of samba. However, something has brought printing to its knees. I pulled out all the old tricks, hacked the registry to delete any entries in HKCU\Printers\DevModes and DevModes2 of the type \\server\printer. Removal of the entries didn't change a thing. I captured an ethereal/wireshark trace and I have that available to anyone if interested. Have there been any changes in 3.2.x that would effect printing? It does seem to print once every conceivable timer in window times out, but were talking 120-150 seconds. Any Ideas? -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing XP - 3.2 Now really slow (just like the old days)
David C. Rankin wrote: Guys, Have there been any changes in 3.2.x that would effect printing? It does seem to print once every conceivable timer in window times out, but were talking 120-150 seconds. Any Ideas? Guys, I can confirm, this seems to be an XP only issue. Vista prints just fine to the same server. I have also confirmed the XP behavior on 2 other boxes. In all regards, the behavior is identical, printing basically freezes the application and printer dialog (if open) for about 2.5 minutes until everything in XP times out, then the documents will actually print, but not before you get the grayed boxes and application not responding messages. What can I send you that would help solve this atavistic printing conundrum? Just let me know and I'll be glad to help. Anything so my wife can print. When she needs to print, it seems to be an immediate thing, every time... -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing XP - 3.2 Now really slow (just like the old days)
Jeremy Allison wrote: On Thu, Aug 14, 2008 at 02:01:26AM -0500, David C. Rankin wrote: Guys, My wife needed to print something this evening to our normal HP 4 attached to our cups server running samba-3.2.1-0.1.126. Nothing has changed in the last two months going from 3.0.28a to the 3.2.x flavor of samba. However, something has brought printing to its knees. I pulled out all the old tricks, hacked the registry to delete any entries in HKCU\Printers\DevModes and DevModes2 of the type \\server\printer. Removal of the entries didn't change a thing. I captured an ethereal/wireshark trace and I have that available to anyone if interested. Have there been any changes in 3.2.x that would effect printing? It does seem to print once every conceivable timer in window times out, but were talking 120-150 seconds. Any Ideas? There's a bug with a missing reply_printclose() that just got fixed in the tree by Bartosz Antosik that may be causing this. It could cause print jobs to timeout on the Windows side. Patch is attached, and it will be in 3.2.2. Jeremy. Patch installed and verified -- IT IS FIXED!! Printing again works like a charm from XP. Now all we have to do is wait for the updated rpms from Lars and we can get off of the /usr/local/samba binaries ;-) I don't know how Lars does it. I could not get anything to build from the samba.spec-10.3. The samba-vscan link doesn't work for Source11: So I just applied the patch, compiled and used the default local install. I had no problems with new binaries at all. For anyone else wanting to test building from source on openSuSE, after the build and install to /usr/local/samba, you can use the following command lines to start nmbd and smbd to make use of the remainder of your standard rpm configuration and also keep your normal log files separate: /usr/local/samba/sbin/nmbd --daemon --configfile=/etc/samba/smb.conf --log-basename=log.nmb.test /usr/local/samba/sbin/smbd --daemon --configfile=/etc/samba/smb.conf --log-basename log.smb.test --smb-passwd-file=/etc/samba/smbpasswd --private-dir=/etc/samba -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba just died? smbd/sec_ctx.c:set_sec_ctx(241)
Jeremy Allison wrote: On Mon, Aug 11, 2008 at 06:07:10PM -0500, David C. Rankin wrote: Listmates, Running 3.2.1-0.1.126-1867-SUSE-SL10.3 (in standalone) I was quite surprised samba DOA. Further research show that it died shortly after midnight with the last relevant log entries being: [2008/08/10 00:24:15, 3] smbd/sec_ctx.c:set_sec_ctx(241) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2008/08/10 00:24:15, 3] smbd/connection.c:yield_connection(69) Yielding connection to [2008/08/10 00:24:15, 3] smbd/server.c:exit_server_common(768) After running samba since 2.0.7, this is the first time I have had it just die on me without me doing something to cause it to die. Any thoughts on the matter? Can I provide additional information? This doesn't look like death, but orderly termination. Jeremy. Jeremy, That is the mystery. A further look at syslog shows that the shutdown occurred as part of the package update (at Aug 10 00:01:47): Aug 9 23:42:25 bonza sshd[13848]: Accepted publickey for david from 66.76.63.120 port 51503 ssh2 Aug 9 23:59:39 bonza sudo:david : TTY=pts/1 ; PWD=/home/david ; USER=root ; COMMAND=/usr/bin/zypper up Aug 10 00:01:47 bonza sudo:david : TTY=pts/1 ; PWD=/home/david ; USER=root ; COMMAND=/usr/bin/zypper up -t package Aug 10 00:15:04 bonza syslog-ng[2875]: STATS: dropped 0 Aug 10 00:24:13 bonza shadow[16389]: group already exists - group=ntadmin, by=0 Aug 10 00:24:15 bonza nmbd[2944]: [2008/08/10 00:24:15, 0] nmbd/nmbd.c:terminate(58) Aug 10 00:24:15 bonza nmbd[2944]: Got SIGTERM: going down... The bigger questions is why, during an update, did the package manager fail to restart smbd or nmbd? I'll pass this along to Lars as well. May be a package problem. On all previous updates the services have automatically been restarted, I guess by the post-install script. That didn't happen here. There was no problem with the config, I just issues a simple rscmb restart and (1) found out smbd wasn't running, and (2) it started without any problems or warnings. So it looks like the start command was never given after package update. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba just died? smbd/sec_ctx.c:set_sec_ctx(241)
Listmates, Running 3.2.1-0.1.126-1867-SUSE-SL10.3 (in standalone) I was quite surprised samba DOA. Further research show that it died shortly after midnight with the last relevant log entries being: [2008/08/10 00:24:15, 3] smbd/sec_ctx.c:set_sec_ctx(241) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2008/08/10 00:24:15, 3] smbd/connection.c:yield_connection(69) Yielding connection to [2008/08/10 00:24:15, 3] smbd/server.c:exit_server_common(768) After running samba since 2.0.7, this is the first time I have had it just die on me without me doing something to cause it to die. Any thoughts on the matter? Can I provide additional information? -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Fwd: [opensuse] Re: [Samba] [ANNOUNCE] Samba 3.2.1 Available for Download]
== Release Announcements = This is the second stable release of Samba 3.2. 3.2.1 fixed the problem in a stand-alone setup described in the 7/3/08 thread concerning: upgrade from cifs-mount-3.2.0-24.1.121 to cifs-mount-3.2.0-24.1.122 on a openSuSE 10.3 x86_64 machine broke mount -t cifs Great work! -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] update to cifs-mount-3.2.0-24.1.122 from .121 broke mount.cifs [.123 is still broken]
Linux Addict wrote: sorry.. not related to this thread at all. Just curious how did you got 3.2 rpms. I spent lot of time with makerpms.sh but it was keep complaning about libmsrpc. Thanks.. Sorry for the late reply, All of the latest Samba rpms for openSuSE are here: http://us1.samba.org/samba/ftp/Binary_Packages/SuSE/3.0/ Courtesy of Lars Mueller.. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] update to cifs-mount-3.2.0-24.1.122 from .121 broke mount.cifs [.123 is still broken]
David C. Rankin wrote: David C. Rankin wrote: David C. Rankin wrote: David C. Rankin wrote: Jerry, Jeremy, et. al. Last night's upgrade from cifs-mount-3.2.0-24.1.121 to cifs-mount-3.2.0-24.1.122 on a openSuSE 10.3 x86_64 machine broke mount -t cifs. Now attempting to mount shares results in the following: 11:10 alchemy/home/david/bin] # mount.cifs -v //nirvana/david /mnt/nirvana-david -o username=david,uid=1000,password=notmypass parsing options: username=david,uid=1000,password=notmypass Mounting the DFS root for domain not implemented yet No ip address specified and hostname not found Huh? Can I get .121 back? This is purely a client issue. Nothing is showing in the server logs with log level = 10. Client only has entries in /var/log/messages showing that the mount command was entered: Jul 3 10:51:46 alchemy sudo:david : TTY=pts/1 ; PWD=/home/david/bin ; USER=root ; COMMAND=/sbin/mount.cifs -v //nirvana/david /mnt/nirvana-david -o username=david,uid=1000,password=notmypass Help. Let me know what else I can send and I'll be happy to do it. Thanks. Guys, I did a downgrade to the latest in openSuSE/update (3.0.26a) and all works as it should. It's confirmed, whatever changes were made to cifs-mount-3.2.0-24.1.122 broke it. Let me know if I can send anything else. Does anyone know if this was fixed in the .123 release? Yes, David, Now that you mention it, I have the answer! I installed: cifs-mount-3.2.0-24.1.123 samba-winbind-32bit-3.2.0-24.1.123 samba-3.2.0-24.1.123 samba-32bit-3.2.0-24.1.123 samba-client-3.2.0-24.1.123 samba-client-32bit-3.2.0-24.1.123 and cifs is still broken. Upon install all of the Linux-to-Linux cifs mounts immediately fail and cannot be remounted until all samba/cifs packages are downgraded to the only available openSuSE alternative of 3.0.26a--bummer. Am I the only one affected by this??? Is there a workaround? Can I check/send anything else to help fix this? I have confirmed the issue with others on the openSuSE list. For those interested, a bug was filed with Novell: https://bugzilla.novell.com/show_bug.cgi?id=408624 -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] update to cifs-mount-3.2.0-24.1.122 from .121 broke mount.cifs [.123 is still broken]
David C. Rankin wrote: David C. Rankin wrote: David C. Rankin wrote: Jerry, Jeremy, et. al. Last night's upgrade from cifs-mount-3.2.0-24.1.121 to cifs-mount-3.2.0-24.1.122 on a openSuSE 10.3 x86_64 machine broke mount -t cifs. Now attempting to mount shares results in the following: 11:10 alchemy/home/david/bin] # mount.cifs -v //nirvana/david /mnt/nirvana-david -o username=david,uid=1000,password=notmypass parsing options: username=david,uid=1000,password=notmypass Mounting the DFS root for domain not implemented yet No ip address specified and hostname not found Huh? Can I get .121 back? This is purely a client issue. Nothing is showing in the server logs with log level = 10. Client only has entries in /var/log/messages showing that the mount command was entered: Jul 3 10:51:46 alchemy sudo:david : TTY=pts/1 ; PWD=/home/david/bin ; USER=root ; COMMAND=/sbin/mount.cifs -v //nirvana/david /mnt/nirvana-david -o username=david,uid=1000,password=notmypass Help. Let me know what else I can send and I'll be happy to do it. Thanks. Guys, I did a downgrade to the latest in openSuSE/update (3.0.26a) and all works as it should. It's confirmed, whatever changes were made to cifs-mount-3.2.0-24.1.122 broke it. Let me know if I can send anything else. Does anyone know if this was fixed in the .123 release? Yes, David, Now that you mention it, I have the answer! I installed: cifs-mount-3.2.0-24.1.123 samba-winbind-32bit-3.2.0-24.1.123 samba-3.2.0-24.1.123 samba-32bit-3.2.0-24.1.123 samba-client-3.2.0-24.1.123 samba-client-32bit-3.2.0-24.1.123 and cifs is still broken. Upon install all of the Linux-to-Linux cifs mounts immediately fail and cannot be remounted until all samba/cifs packages are downgraded to the only available openSuSE alternative of 3.0.26a--bummer. Am I the only one affected by this??? Is there a workaround? Can I check/send anything else to help fix this? -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] update to cifs-mount-3.2.0-24.1.122 from .121 broke mount.cifs
David C. Rankin wrote: David C. Rankin wrote: Jerry, Jeremy, et. al. Last night's upgrade from cifs-mount-3.2.0-24.1.121 to cifs-mount-3.2.0-24.1.122 on a openSuSE 10.3 x86_64 machine broke mount -t cifs. Now attempting to mount shares results in the following: 11:10 alchemy/home/david/bin] # mount.cifs -v //nirvana/david /mnt/nirvana-david -o username=david,uid=1000,password=notmypass parsing options: username=david,uid=1000,password=notmypass Mounting the DFS root for domain not implemented yet No ip address specified and hostname not found Huh? Can I get .121 back? This is purely a client issue. Nothing is showing in the server logs with log level = 10. Client only has entries in /var/log/messages showing that the mount command was entered: Jul 3 10:51:46 alchemy sudo:david : TTY=pts/1 ; PWD=/home/david/bin ; USER=root ; COMMAND=/sbin/mount.cifs -v //nirvana/david /mnt/nirvana-david -o username=david,uid=1000,password=notmypass Help. Let me know what else I can send and I'll be happy to do it. Thanks. Guys, I did a downgrade to the latest in openSuSE/update (3.0.26a) and all works as it should. It's confirmed, whatever changes were made to cifs-mount-3.2.0-24.1.122 broke it. Let me know if I can send anything else. Does anyone know if this was fixed in the .123 release? -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] update to cifs-mount-3.2.0-24.1.122 from .121 broke mount.cifs
Jerry, Jeremy, et. al. Last night's upgrade from cifs-mount-3.2.0-24.1.121 to cifs-mount-3.2.0-24.1.122 on a openSuSE 10.3 x86_64 machine broke mount -t cifs. Now attempting to mount shares results in the following: 11:10 alchemy/home/david/bin] # mount.cifs -v //nirvana/david /mnt/nirvana-david -o username=david,uid=1000,password=notmypass parsing options: username=david,uid=1000,password=notmypass Mounting the DFS root for domain not implemented yet No ip address specified and hostname not found Huh? Can I get .121 back? This is purely a client issue. Nothing is showing in the server logs with log level = 10. Client only has entries in /var/log/messages showing that the mount command was entered: Jul 3 10:51:46 alchemy sudo:david : TTY=pts/1 ; PWD=/home/david/bin ; USER=root ; COMMAND=/sbin/mount.cifs -v //nirvana/david /mnt/nirvana-david -o username=david,uid=1000,password=notmypass Help. Let me know what else I can send and I'll be happy to do it. Thanks. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] update to cifs-mount-3.2.0-24.1.122 from .121 broke mount.cifs
David C. Rankin wrote: Jerry, Jeremy, et. al. Last night's upgrade from cifs-mount-3.2.0-24.1.121 to cifs-mount-3.2.0-24.1.122 on a openSuSE 10.3 x86_64 machine broke mount -t cifs. Now attempting to mount shares results in the following: 11:10 alchemy/home/david/bin] # mount.cifs -v //nirvana/david /mnt/nirvana-david -o username=david,uid=1000,password=notmypass parsing options: username=david,uid=1000,password=notmypass Mounting the DFS root for domain not implemented yet No ip address specified and hostname not found Huh? Can I get .121 back? This is purely a client issue. Nothing is showing in the server logs with log level = 10. Client only has entries in /var/log/messages showing that the mount command was entered: Jul 3 10:51:46 alchemy sudo:david : TTY=pts/1 ; PWD=/home/david/bin ; USER=root ; COMMAND=/sbin/mount.cifs -v //nirvana/david /mnt/nirvana-david -o username=david,uid=1000,password=notmypass Help. Let me know what else I can send and I'll be happy to do it. Thanks. Guys, I did a downgrade to the latest in openSuSE/update (3.0.26a) and all works as it should. It's confirmed, whatever changes were made to cifs-mount-3.2.0-24.1.122 broke it. Let me know if I can send anything else. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Home Lan computer browser(s)
Skip Guenter wrote: Reading this list makes me think my questions are child's play for ya'll. */1) //Should I have more than one computer browser on my lan /*/(~16 machines)/*/?/* You are thinking about the computer that will hold the master browse list for netbios name resolution. The answer to your question - NO, there is no need. One of the samba servers on your lan will win the browse election and become the master browser. Each other machine will hold a copy of the browse list. If the master dies, then the normal election rules apply and another box will become the master. The master can serve thousands of clients. (hundreds at least) There is no need for a backup. Netbios name resolution has nothing to do with a Primary Domain Controller (PDC) or Backup Domain Controller (BDC). os level = nnn (0 to 255) preferred master = yes/no domain master = yes/no local master = yes/no For the box that is the samba server, presumably the one that is always on, Just set the os level higher than that of the other boxes. Browse election rules are discussed at: http://www.oreilly.com/catalog/samba2/book/ch07.html Setting os level greater than 32 will insure that your samba box will win the election over all Win boxes. My problem is I'm not sure how the settings should vary from primary to backup. To have one of the samba machines be primary (let's say the machine I'm calling C20) would these parms work: /*2) If so, can you help me with these settings? */ C20... the primary computer browser? os level = 36 preferred master = yes domain master = yes local master = yes Then on C19... the backup computer browser? os level = 35 preferred master = ?? domain master = ?? local master = ?? I think this would make C20 win an election but would this make them both win an election over the winXP machine should one come on-line with computer browser set on? Are there better settings and / or are some of these not needed for my little world? Thanx, Skip Weedhopper, just read http://www.oreilly.com/catalog/samba2/book/ch07.html and all will become clear ;-) -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] get Samba Server via VPN from windows XP
Engi Zoltán wrote: Hi, I have network in my office with Samba server on Debian Linux. I would like to get the folders and files in this server from my home with Windows XP. So, I done the VPN connection. I think, it works good. In the VPN connection Samba Server's ip address is 192.168.2.1 and net mask is 255.255.255.255. The client's ip address is 192.168.2.6. and netmask is 255.255.255.252. I can ping the server from the client and back too. The workgrupname in the smb.conf and windows XP are same. The problem is that I can't see the linux computer in the network place on the Windows XP. Why? Sincerely, Zoli Here is my post from 3/17/08 on the topic. It does work great, even from network neighborhood: Jon Theil Nielsen wrote: My goal is to make VPN access to our Samba PDC (FreeBSD 7.0) so that users can access there home shares from Windows clients. I have read the instructions at http://samba.org/ftp/unpacked/lorikeet/pppd/final-report.pdf, but I can't make it work. snip Regards, Jon Jon, I do it this way: pptp VPN server /etc/pptpd.conf option /etc/ppp/options.pptp debug (comment out after testing) localip 192.168.7.12 remoteip 192.168.7.2-5 pidfile /var/run/pptpd.pid /etc/ppp/options.pptp lock noauth nobsdcomp lcp-echo-failure 10 lcp-echo-interval 10 /etc/ppp/options name bonza.rbpllc.com noipdefault noauth lock local lcp-echo-interval 30 lcp-echo-failure 4 lcp-max-configure 60 lcp-restart 2 idle 600 noipx file /etc/ppp/filters proxyarp ms-dns 192.168.7.15 ms-wins 192.168.7.15 refuse-chap refuse-mschap /etc/ppp/pap-secrets * bonza.rbpllc.com username yourserver.yourdomain.com password * /etc/ppp/chap-secrets username * password * Of course, use your own information and get rid of the in the pap and chap-secret files. Good luck. This works like a charm. Just don't forget to open [port 1723] in your firewall and router for accessing the server locally as well as remotely. Also, you may need: # TAG: bcrelay if bcrelay eth0 in /etc/pptpd.conf if you are running an older version of pptpd to improve remote browsing. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] VPN server and logon to Samba PDC
Jon Theil Nielsen wrote: My goal is to make VPN access to our Samba PDC (FreeBSD 7.0) so that users can access there home shares from Windows clients. I have read the instructions at http://samba.org/ftp/unpacked/lorikeet/pppd/final-report.pdf, but I can't make it work. snip Regards, Jon Jon, I do it this way: pptp VPN server /etc/pptpd.conf option /etc/ppp/options.pptp debug (comment out after testing) localip 192.168.7.12 remoteip 192.168.7.2-5 pidfile /var/run/pptpd.pid /etc/ppp/options.pptp lock noauth nobsdcomp lcp-echo-failure 10 lcp-echo-interval 10 /etc/ppp/options name bonza.rbpllc.com noipdefault noauth lock local lcp-echo-interval 30 lcp-echo-failure 4 lcp-max-configure 60 lcp-restart 2 idle 600 noipx file /etc/ppp/filters proxyarp ms-dns 192.168.7.15 ms-wins 192.168.7.15 refuse-chap refuse-mschap /etc/ppp/pap-secrets * bonza.rbpllc.com username yourserver.yourdomain.com password * /etc/ppp/chap-secrets username * password * Of course, use your own information and get rid of the in the pap and chap-secret files. Good luck. This works like a charm. Just don't forget to open [port 1723] in your firewall and router for accessing the server locally as well as remotely. Also, you may need: # TAG: bcrelay if bcrelay eth0 in /etc/pptpd.conf if you are running an older version of pptpd to improve remote browsing. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] VPN server and logon to Samba PDC
Jon Theil Nielsen wrote: 2008/3/17, David C. Rankin [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: Jon Theil Nielsen wrote: My goal is to make VPN access to our Samba PDC (FreeBSD 7.0) so that users can access there home shares from Windows clients. I have read the instructions at http://samba.org/ftp/unpacked/lorikeet/pppd/final-report.pdf, but I can't make it work. snip Regards, Jon Jon, I do it this way: pptp VPN server /etc/pptpd.conf option /etc/ppp/options.pptp debug (comment out after testing) localip 192.168.7.12 http://192.168.7.12 remoteip 192.168.7.2-5 pidfile /var/run/pptpd.pid /etc/ppp/options.pptp lock noauth nobsdcomp lcp-echo-failure 10 lcp-echo-interval 10 /etc/ppp/options name bonza.rbpllc.com http://bonza.rbpllc.com noipdefault noauth lock local lcp-echo-interval 30 lcp-echo-failure 4 lcp-max-configure 60 lcp-restart 2 idle 600 noipx file /etc/ppp/filters proxyarp ms-dns 192.168.7.15 http://192.168.7.15 ms-wins 192.168.7.15 http://192.168.7.15 refuse-chap refuse-mschap /etc/ppp/pap-secrets * bonza.rbpllc.com http://bonza.rbpllc.com username yourserver.yourdomain.com http://yourserver.yourdomain.com password * /etc/ppp/chap-secrets username * password * Of course, use your own information and get rid of the in the pap and chap-secret files. Good luck. This works like a charm. Just don't forget to open [port 1723] in your firewall and router for accessing the server locally as well as remotely. Also, you may need: # TAG: bcrelay if bcrelay eth0 in /etc/pptpd.conf if you are running an older version of pptpd to improve remote browsing. Thanks, David Just a few questions before I try this solution. Are you on FreeBSD too? As far as I understand, the main configuration file here is /usr/local/etc/pptpd.conf. Or should it live in /etc/? What does the line file /etc/ppp/filters refer to? Can you use this configuration to join a Samba domain? Regards, Jon Jon, It doesn't matter where the conf file goes. That is determined at compile time with the ./configure options. If your setup wants it in /usr/local, then that's where it goes. I'm running Linux, but as far as pptpd is concerned it shouldn't care. You may just have to adjust the path information to work with your setup. I would just make the configuration changes and start pptpd. You will get all the messages you need in /var/log/messages or /var/log/syslog depending on your setup. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] cifs verses smbfs for Linux clients
Michael Lueck wrote: I am somewhat confused... I understand that the preferred method to mount a Samba share with a Linux client is to use mount -t cifs rather than mount -t smbfs. I get the impression that smbfs is samba.org developed code where as cifs is from elsewhere. Thus the point of confusion. Why is samba.org not developing the preferred code in this case? A sub question to that main one is a nagging thought of needing to add the Debian / Ubuntu smbfs package to Linux client systems issuing mount -t cifs. If cifs really is from elsewhere, and smbfs is bad evil, why the interdependency? Thanks! If I recall correctly smbfs was deprecated in favor of cifs when cifs was made a permanent part of the kernel in the 2.4 or 2.4-2.6 kernel. This provided a uniform way to implement an smbfs mount through the kernel instead or relying on package dependent smbmount. Whether you are doing: mount -t smbfs; or mount -t cifs (also mount.cifs) your are accomplishing the same thing. I used smbmount for a long time, then cifs was made the standard and I have used cifs since then. I have no complaints. From man mount: Since various versions of the smbmount program have different calling conventions, /sbin/mount.smbfs may have to be a shell script that sets up the desired call. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbd errors in syslog - how to get rid of them? {solved}
Niki Hammler wrote: David C. Rankin schrieb: David C. Rankin wrote: Listmates, I know the following are harmless, but how do I keep them from filling up my syslog? log level = 03. They still appear with log level = 1. Any thoughts? The logs: Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0] lib/util_sock.c:get_peer_addr(1232) Jan 23 22:01:30 bonza smbd[16474]: getpeername failed. Error was smb ports = 139 in the Globals section of smb.conf Are there any disadvantages when setting this options? I know that Windowsclients can't communicate over 445 any more but is there a disadvantage? Niki Not that I have experienced. We have about 12 windows boxes working happily from 2 linux boxes and after added the port and shutting down all the chatter ofer 445, I think it works better! -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] smbd errors in syslog - how to get rid of them? {solved}
David C. Rankin wrote: Listmates, I know the following are harmless, but how do I keep them from filling up my syslog? log level = 03. They still appear with log level = 1. Any thoughts? The logs: Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0] lib/util_sock.c:get_peer_addr(1232) Jan 23 22:01:30 bonza smbd[16474]: getpeername failed. Error was smb ports = 139 in the Globals section of smb.conf -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] smbd errors in syslog - how to get rid of them?
Listmates, I know the following are harmless, but how do I keep them from filling up my syslog? log level = 03. They still appear with log level = 1. Any thoughts? The logs: Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0] lib/util_sock.c:get_peer_addr(1232) Jan 23 22:01:30 bonza smbd[16474]: getpeername failed. Error was Transport endpoint is not connected Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0] lib/util_sock.c:get_peer_addr(1232) Jan 23 22:01:30 bonza smbd[16474]: getpeername failed. Error was Transport endpoint is not connected Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0] lib/access.c:check_access(327) Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0] lib/util_sock.c:get_peer_addr(1232) Jan 23 22:01:30 bonza smbd[16474]: getpeername failed. Error was Transport endpoint is not connected Jan 23 22:01:30 bonza smbd[16474]: Denied connection from (0.0.0.0) Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0] lib/util_sock.c:get_peer_addr(1232) Jan 23 22:01:30 bonza smbd[16474]: getpeername failed. Error was Transport endpoint is not connected Jan 23 22:01:30 bonza smbd[16474]: Connection denied from 0.0.0.0 Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0] lib/util_sock.c:write_data(562) Jan 23 22:01:30 bonza smbd[16474]: write_data: write failure in writing to client 192.168.7.143. Error Connection reset by peer Jan 23 22:01:30 bonza smbd[16474]: [2008/01/23 22:01:30, 0] lib/util_sock.c:send_smb(769) Jan 23 22:01:30 bonza smbd[16474]: Error writing 5 bytes to client. -1. (Connection reset by peer) -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Can't see my home directory
Anne Wilson wrote: On Sunday 20 Jan 2008, David C. Rankin wrote: Anne Wilson wrote: On Sunday 20 January 2008 19:58:29 John Drescher wrote: On Jan 20, 2008 2:54 PM, Anne Wilson [EMAIL PROTECTED] wrote: I have a strange problem. I use samba for most of my network activity, even though most of it is linux to linux. On every machine except this laptop I can see my home directory on the file/print/mail server. On this laptop I can see all the other shares, but not my home directory. Since everything works on the others, the server end must be OK. That puts the problem fair and square onto this laptop, but I've run out of ideas for checking. I now need kicking in the right direction, please. What do you mean can not see? I can't browse the home directory in konqueror, and I can't attach to it in korganizer. Also what version of samba are you using? 3.0.25b Anne, At this point, I would test compiling from source and see if the problem remains. You can do it in about 5 minutes. (1) download the latest samba-rev#.tar.gz; (2) unzip it with tar -xzf samba-rev#.tar.gz (3) change into the new samba-rev# directory (4) actually read/browse the README file (5) cd into the new samba-rev#/source directory (6) run sh autogen.sh (7) For Mandriva 2005LE, the ./configure was: ./configure --prefix=/usr --infodir=/usr/share --mandir=/usr/share --with-configdir=/etc/samba --with-privatedir=/etc/samba --target=i686 To check, just make sure smbclient is in /usr/bin, smbd and nmbd are in /usr/sbin and smb.conf is in /etc/samba. If so the above configure will work (8) make make install (9) restart samba and test (10) if it doesn't work, or all goes awry, then just: make revert and it will reload your current 3.0.25b Before I do this - The laptop that cannot read the server is running 3.0.25b. The server is running 3.0.24. Does that make any difference/ I assume that you meant me to do this install on the laptop (client) ? Anne No, I was talking about the server. I can't recall if it was 3.0.23, .24, or .25, but somewhere in there problems were introduced that effects the SID/GID and caused a number of problems. Since it doesn't take that long, I'd do both server and laptop. That is the rub about mandriva, nobody is building samba rpms anymore. I built samba from source for the past 2 years on 2005LE, until I replaced the server with openSuSE 10.3. Wonderful support for samba rpms. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Can't see my home directory
Anne Wilson wrote: On Tuesday 22 January 2008 14:03:55 David C. Rankin wrote: I was talking about the server. I can't recall if it was 3.0.23, .24, or .25, but somewhere in there problems were introduced that effects the SID/GID and caused a number of problems. Since it doesn't take that long, I'd do both server and laptop. It's odd, though, that the problem only affects this one laptop. The ancient laptop that was my stopgap while this was being repaired didn't have the problem, and I had Mandriva 2008 on that as well. That is the rub about mandriva, nobody is building samba rpms anymore. I built samba from source for the past 2 years on 2005LE, until I replaced the server with openSuSE 10.3. Wonderful support for samba rpms. I'm tempted to leave this for the moment. I'm just configuring a new server box with CentOS. I shall see tomorrow whether samba gives me full access to that box. If it does, I'll not worry about the out-going one. I HATE mysteries! Anne They're just somethings in this world, you just can't explain...Charley Daniels Band -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Can't see my home directory
Anne Wilson wrote: On Sunday 20 January 2008 19:58:29 John Drescher wrote: On Jan 20, 2008 2:54 PM, Anne Wilson [EMAIL PROTECTED] wrote: I have a strange problem. I use samba for most of my network activity, even though most of it is linux to linux. On every machine except this laptop I can see my home directory on the file/print/mail server. On this laptop I can see all the other shares, but not my home directory. Since everything works on the others, the server end must be OK. That puts the problem fair and square onto this laptop, but I've run out of ideas for checking. I now need kicking in the right direction, please. What do you mean can not see? I can't browse the home directory in konqueror, and I can't attach to it in korganizer. Also what version of samba are you using? 3.0.25b Anne, At this point, I would test compiling from source and see if the problem remains. You can do it in about 5 minutes. (1) download the latest samba-rev#.tar.gz; (2) unzip it with tar -xzf samba-rev#.tar.gz (3) change into the new samba-rev# directory (4) actually read/browse the README file (5) cd into the new samba-rev#/source directory (6) run sh autogen.sh (7) For Mandriva 2005LE, the ./configure was: ./configure --prefix=/usr --infodir=/usr/share --mandir=/usr/share --with-configdir=/etc/samba --with-privatedir=/etc/samba --target=i686 To check, just make sure smbclient is in /usr/bin, smbd and nmbd are in /usr/sbin and smb.conf is in /etc/samba. If so the above configure will work (8) make make install (9) restart samba and test (10) if it doesn't work, or all goes awry, then just: make revert and it will reload your current 3.0.25b -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Home directory problem
Anne Wilson wrote: In the thread Network Path was not found Michael Heydon wrote: quote When you have security = share you don't authenticate as a user and as such you don't have a home directory. I would suggest sticking with user level security, share level is a left over from the 9x days and is pretty much obsolete. /quote I have checked, and my line is definitely security = user. However, I still can't see my /home, even though I can see all the other shares. What other conditions can cause this? Anne Anne, I bet you have changed the default permission for your home directories from 0755 (rwxr-xr-x) to something else. If I recall you need world r-x for this to work with homes configured in smb.conf as: [homes] comment = Home Directories browseable = no writable = yes Give it a shot. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Home directory problem
Anne Wilson wrote: On Thursday 17 January 2008 17:45:45 David C. Rankin wrote: Anne Wilson wrote: In the thread Network Path was not found Michael Heydon wrote: quote When you have security = share you don't authenticate as a user and as such you don't have a home directory. I would suggest sticking with user level security, share level is a left over from the 9x days and is pretty much obsolete. /quote I have checked, and my line is definitely security = user. However, I still can't see my /home, even though I can see all the other shares. What other conditions can cause this? Anne Anne, I bet you have changed the default permission for your home directories from 0755 (rwxr-xr-x) to something else. I forgot to answer that bit - drwxr-xr-x 48 anneusers4096 2008-01-17 18:56 anne/ Besides, if one laptop can read and write to it, the other one should also. And it can, if I use smb4k to launch it in konqueror. Anne Yes, It has been a while, good to hear from you again. From your home permissions it appears you have bolted from mdk, unless they have picked up the openSuSE group scheme ;-) I don't know what to tell you on the homes issue. Most kernels have dropped smbfs support in favor of cifs. What I have been doing linux-to-linux is using mount.cifs for samba shares in the following fashion: mount.cifs //host/theusername /mnt/mountpoint/ -o username=theusername,uid=1000,password=pass I'm sure their is a more automated way to do this, but with only 10 people in the office it isn't a problem. I haven't used smb4k, but I have seen others that have successfully. Without smb4k, I use konqueror and just type smb://host into the address bar and it shows all shares including the the users home dir that can be linked, etc... Someone smarter than I will have to add more to the discussion. Again, good to hear from you! -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] time server = yes
Adam Williams wrote: I want my XP clients to update their clocks from my samba server. I have time server = yes in smb.conf, and running ntpd on the server, but my clients aren't updating their clocks. I tried running the command manually logged in as a domain user: net time /setsntp:10.8.2.3 but it just says System error 5 has occurred. Access is denied. Any ideas? As an admin user, from the command prompt in windows try: net time \\server /set /yes It has worked for me for years. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Re: Unusable performance over WAN (part 2)
James Lamanna wrote: On 10/7/07, Volker Lendecke [EMAIL PROTECTED] wrote: On Sun, Oct 07, 2007 at 09:31:23AM -0700, James Lamanna wrote: Server sends 1500 byte packet Client sends 52 bye ACK Server sends 1500 byte packet Client sends 52 byte ACK etc.. Can anyone think of a reason for this? I did not find a link spontaneously, but Windows sometimes falls back to something that we call rabbit pellet mode. Maybe google shows up something for you. Volker I actually see that behavior using smbclient from a linux machine, so its not necessarily Windows related. -- James James, Volker, See: http://www.linuxarkivet.se/mlists/mandrake-expert/0309/msg00162.html -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] 3.0.26a RPM install on Suse 10.2 Generates Warnings
Jerry, All: Don't know what they mean, but... During install of 3.0.26a on opensuse 10.2 libGammu warning were received as follows: [root Rankin-P35a:/home/david/Documents/linux/updates/samba/samba-3.0.26a] # rpm -Uvh *.rpm warning: cifs-mount-3.0.26a-0.1.82.i586.rpm: Header V3 DSA signature: NOKEY, key ID 414a57c3 Preparing...### [100%] 1:cifs-mount ### [ 8%] 2:samba-client warning: /etc/samba/smb.conf created as /etc/samba/smb.conf.rpmnew ### [ 15%] /sbin/ldconfig: /usr/lib/libGammu.so.0 is not a symbolic link Updating etc/sysconfig/network/dhcp... 3:samba ### [ 23%] 4:libsmbclient ### [ 31%] /sbin/ldconfig: /usr/lib/libGammu.so.0 is not a symbolic link 5:libmsrpc ### [ 38%] /sbin/ldconfig: /usr/lib/libGammu.so.0 is not a symbolic link 6:ldapsmb### [ 46%] 7:libmsrpc-devel ### [ 54%] 8:libsmbclient-devel ### [ 62%] 9:samba-krb-printing ### [ 69%] Starting SuSEconfig, the SuSE Configuration Tool... Running module permissions only Reading /etc/sysconfig and updating the system... Executing /sbin/conf.d/SuSEconfig.permissions... Finished. 10:samba-pdb ### [ 77%] 11:samba-python ### [ 85%] 12:samba-vscan### [ 92%] 13:samba-winbind ### [100%] /sbin/ldconfig: /usr/lib/libGammu.so.0 is not a symbolic link /sbin/ldconfig: /usr/lib/libGammu.so.0 is not a symbolic link /sbin/ldconfig: /usr/lib/libGammu.so.0 is not a symbolic link /sbin/ldconfig: /usr/lib/libGammu.so.0 is not a symbolic link /sbin/ldconfig: /usr/lib/libGammu.so.0 is not a symbolic link I believe libGammu was installed via RPM as a requirement for kmobiletools. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] 3.0.26a Standalone Up 3 day no complaints!
Jerry, 3.0.26a in standalone mode has been up for 3 days and so far no problems and no repeat of 3.0.25c Going Nuts... -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.0.26a Available for Download
messages. CONCLUSION //root/bonza/home/david/Documents/linux/updates/src/samba-3.0.26a/source smbclient -U% -L localhost Domain=[RB_LAW] OS=[Unix] Server=[Samba 3.0.26a] Sharename Type Comment - --- samba Disk Base Samba Share office Disk Shared Office Files rankin Disk Rankin Law Firm PLLC scans Disk Scanned Images from Copier allen Disk T Stefan Allen bertin Disk Darren Bertin guilloryDisk David Guillory jointcases Disk Joint Client Files lawtoolsDisk Case Development - Summation forms Disk Shared Forms and Briefs computerDisk Computer Drivers and Software closed Disk Closed Case Files print$ Disk pdf-gen Printer PDF Generator (only valid users) IPC$IPC IPC Service (Samba Server 3.0.26a) Domain=[RB_LAW] OS=[Unix] Server=[Samba 3.0.26a] Server Comment ---- BONZASamba Server 3.0.26a LISHALisha PROVIDENCE Samba 3.0.25b-0.1.68-1378-SUSE-SL10.0 RANKIN-XPRankin's Computer RECEPTIONDell 2400 2.6 GHz STEFAN-PCstefan-laptop WorkgroupMaster ---- RB_LAW BONZA (downloaded, configured, made and installed in less time than it took to write this mini howto ;-) -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.0.25c Going Nuts on our Network???
] comment = Darren Bertin path = /home/samba/bertin valid users = @bertin, @roberts admin users = david force group = roberts read only = No inherit permissions = Yes [guillory] comment = David Guillory path = /home/samba/guillory valid users = @guillory admin users = david force group = guillory read only = No inherit permissions = Yes [jointcases] comment = Joint Client Files path = /home/samba/joint valid users = @ochiltree admin users = david force group = ochiltree read only = No inherit permissions = Yes [lawtools] comment = Case Development - Summation path = /home/samba/visionary valid users = @ochiltree admin users = david force group = ochiltree read only = No inherit permissions = Yes [forms] comment = Shared Forms and Briefs path = /home/samba/forms valid users = @ochiltree admin users = david force group = ochiltree read only = No inherit permissions = Yes [computer] comment = Computer Drivers and Software path = /home/samba/computer valid users = @ochiltree admin users = david force group = ochiltree read only = No inherit permissions = Yes [closed] comment = Closed Case Files path = /home/samba/closed valid users = @ochiltree admin users = david force group = ochiltree read only = No inherit permissions = Yes [printers] comment = All Printers path = /var/spool/samba create mask = 0700 guest ok = Yes printable = Yes browseable = No [print$] path = /var/lib/samba/printers write list = @adm, root inherit permissions = Yes guest ok = Yes [pdf-gen] comment = PDF Generator (only valid users) path = /var/tmp printable = Yes printing = bsd print command = /usr/share/samba/scripts/print-pdf %s %H/pdf //%L/%u %m %I %J lpq command = /bin/true lprm command = lprm -P'%p' %j I am still looking for the traffic. My server keep crashing is crashing more often than usual, and I am still looking for the culprit. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Linux Kernel VESA Video Modes for 1440x900
Jan, List: Is there any way we can compile a kernel to include the VESA Video Modes for 1440x900 resolution so that we can pass grub VGA=867 for 1440x900. This will all me to work in runlevel 3 without the screen resolution being stretched from 1024x768 to 1440x900. The stretch causes everything to be distorted. The necessary VESA modes and numbers are: 1440x900 (dec; hex) -- 16 color --; -- 256 color (864; 0x360) 15 bit (865; 0x361) 16 bit (866; 0x362) 24 bit (867; 0x363) 32 bit (868; 0x364) There is also the new widescreen resolution of 1600x1050, but I do not have the vesa modes for that resolution. I would like to learn how to do this, or if this is something that has to be done by the kernel folks, I would ask that they consider including this capability in the future kernels. The sources for the information contained in this document were: o /usr/src/linux-2.6.22.3-ccj53/Documentation/i386/boot.txt o /usr/src/linux-2.6.22.3-ccj53/Documentation/kernel-parameters.txt o http://en.wikipedia.org/wiki/VESA_BIOS_Extensions -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Linux Kernel VESA Video Modes for 1440x900
David C. Rankin wrote: Jan, List: Is there any way we can compile a kernel to include the VESA Video Modes for 1440x900 resolution so that we can pass grub VGA=867 for 1440x900. This will all me to work in runlevel 3 without the screen resolution being stretched from 1024x768 to 1440x900. The stretch causes everything to be distorted. The necessary VESA modes and numbers are: snip Samba Team, Please Disregard! I pushed the 'tab' key on samba instead of suse. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankinlawfirm.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] SAMBA Team - Still no SiSE rpms for 3.0.25c
Jerry, all; Is anyone still building rpms for SuSE? They used to be built the same day of the release, now they are trailing far behind. Is Lars still with opensuse and still building?? -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] SAMBA Team - Still no SiSE rpms for 3.0.25c
John H Terpstra wrote: On Friday 24 August 2007 08:57, Volker Lendecke wrote: On Fri, Aug 24, 2007 at 08:40:33AM -0500, John H Terpstra wrote: Is anyone still building rpms for SuSE? They used to be built the same day of the release, now they are trailing far behind. Is Lars still with opensuse and still building?? I run OpenSUSE 10.2 x86_64 - you can download the RPMS from: ftp://ftp.primastasys.com/pub/ Note: To build x86 (32-bit) binaries, just fetch the SRPM file, then built on your own system by running: Alternatively, try ftp.sernet.de. Not alternativly - SerNet is the preferred location. - john T. John T. Why are there different packages being built for SuSE between the samba.org repo and the ftp.sernet.de repo??? Specifically, here are the differences: www.samba.org binaries for SuSE 10.0 not included in sernet.de: cifs-mount-3.0.25b-1.1.72.i586.rpm ldapsmb-1.34b-80.1.72.i586.rpm libmsrpc-3.0.25b-1.1.72.i586.rpm libmsrpc-devel-3.0.25b-1.1.72.i586.rpm samba-krb-printing-3.0.25b-1.1.72.i586.rpm samba-pdb-3.0.25b-1.1.72.i586.rpm samba-python-3.0.25b-1.1.72.i586.rpm samba-vscan-0.3.6b-4.12.72.i586.rpm ftp.sernet.de binaries for SuSE 10.0 not included in the samba.org binaries: samba3-cifsmount-3.0.25c-33.i586.rpm samba3-debuginfo-3.0.25c-33.i586.rpm samba3-doc-3.0.25c-33.i586.rpm samba3-utils-3.0.25c-33.i586.rpm Obviously, the only one that is troublesome is the cifsmount package. Won't the naming difference screw up the Yast database by allowing two different versions of cifs to be installed under different package names?? Or, is Yast smart enough to figure that out? Just a curiosity... -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba 3.0.25c Going Nuts on our Network???
Jeremy Allison wrote: On Fri, Aug 24, 2007 at 04:22:14PM -0500, David Rankin wrote: Sure Jerry, They are attached. One is a 18 second capture, the second is a 60 second capture. Is any linux process writing into that directory or changing the directory timestamp ? Jeremy. No, at the time I made the capture, the system was sitting at idle and ethereal was the only thing active. I specifically made sure that there was nothing active on the link between 192.168.7.15 and .98. Further, the entire net was slowing down. I apologize that the dump was from the wireless card that couldn't be put into promiscuous mode, but such is life. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Samba Team - 3.0.25c Seems Well in Standalone
Jerry, Everybody: 3.0.25c compiled from source on a mandriva 2005le server in my no (AD, LDAP, Kerbose) environment. A full day of production and nothing more that a whimper out of the system. So, at least in my case 3.0.25c looks good. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
