Re: [Samba] Samba's Printer Going Off-Line (after a Win98 Machine speaks to it)
Sorry, I just noticed that you said 5L, I was thinking of the larger ones with a LCD on the front. It does have a power save mode that kicks in instantly. Have you tried reinstalling the drivers or checking for newer ones? You might try using an old LaserJet driver that is compatible with the printer. A laserjet II or III driver might work. James Elizabeth Barham wrote: James Hubbard <[EMAIL PROTECTED]> writes: It sounds like a power management problem on the printer. Have you tried disabling power save. I think that model has one. James Hi James, Thank you for responding so quickly. I have not seen any power management option on any of the printer-related dialogs. The closest I can find to anything remotely like a "put printer in powersave mode" is found in win.ini under [PrinterPorts]: // Read PrinterPorts from win.ini.Returned string should be of the // form "driver,port,timeout,timeout", such as "winspool,LPT1:,15,45". From: <http://216.239.37.100/search?q=cache:puy-J3mEMk0C:msdn.microsoft.com/library/en-us/gdi/prntspol_27uc.asp+printerports+win.ini+site:msdn.microsoft.com&hl=en&ie=UTF-8> But that may be in reference to timing out as when the printer does not respond or some other possible error condition: <http://216.239.37.100/search?q=cache:Px6cAqvYsuoC:msdn.microsoft.com/library/en-us/wceddk/htm/_wceddk_global_printer_settings.asp+site:msdn.microsoft.com+timeout+printer&hl=en&ie=UTF-8> Elizabeth -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Samba's Printer Going Off-Line (after a Win98 Machinespeaks to it)
It sounds like a power management problem on the printer. Have you tried disabling power save. I think that model has one. James Elizabeth Barham wrote: Hi, I have a light firewall machine that also acts as a Samba print server for a Win32 host on my intranet. For some reason, if the Win98 machine hasn't printed for an extended length of time, the printer goes off-line. When the Win32 tries to print, the printer throws an error and we have to unplug the printer and then plug it back in. It then tries to finish the print job which doesn't look too pretty (its an HP Laserjet 5L). What is very strange is that that particular machine also is the lpd print server and there are no problems whatsoever printing from an lpd client; the only time the printer goes off-line is after a Win32 client speaks with the Samba Print Server, probably when the Win32 client shows the print dialog. Any ideas on what is causing this problem and possibly a solution? Thank you, Elizabeth -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] firewall
This depends on how restrictive your firewall rules are but why don't you just use this: -A INPUT -p udp -s 192.168.1.0/24 --dport 137:139 -i eth0 -j ACCEPT -A INPUT -p tcp -s 192.168.1.0/24 --dport 137:139 -i eth0 -j ACCEPT I'm not sure what the -m stands for. You'll need to change eth0 to match your internal ethernet card. Make sure you insert this before the reject rules. James Hubbard Justin Georgeson wrote: Ok, so I know from `netstat --ip -lnp` that the only ports smbd and nmbd are using are TCP 139, and UDP 137 and 138. I find it a little odd though that nmbd is bound to both 0.0.0.0 AND my primary interface. My problem is that I can't access shares on a windows machine unless I turn off my firewall. I'm using RH 8 and the 2.2.6-2 RPMs from the web page (working fine so far, barring this firewall thing). I have these rules added in iptables -A INPUT -p tcp -m tcp -s 192.168.1.0/24 --dport 139 --syn -j ACCEPT -A INPUT -p udp -m udp -s 192.168.1.0/24 --dport 137 -j ACCEPT -A INPUT -p udp -m udp -s 192.168.1.0/24 --dport 138 -j ACCEPT tcpdump shows ports TCP 139 and UDP 137 being accessed when I run findsmb. But nothing is listed when I do. If I turn off my firewall, the other machine on the LAN, my windows box, is listed. What am I missing? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] ipsec problem
Do you have hosts allow enabled in the smb.conf? Do you have any firewalling turned on? hosts allow = 192.168.0. James Hubbard Thomas Angst wrote: Hello all together, I've got here a very strange problem. I've set up a vpn with freeswan between two subnets over the internet. Now I can ping from behind to behind. With Windows 98 I can search a computer which is in the other subnet and find the the computer. But...only the other computer is NOT a samba server. Means a w2k or w98 is ok. If I'm looking for the samba in the other subnet, I get no match. But I can proberly use w2k to get access in the other subnet on the samba server. The only combination that not works is win98 to samba (yes smbclient/linux works too). And I was not searching for the computer by name I was only searching by the ip address. Does anybody have an idea what the problem can be? thanks for any answers Thomas Angst -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] How Samba let us down
I think everyone else has suggested that you upgrade to 2.2.6. I too would recommend this. The company where I work had a Win2K box whose print jobs would get dropped depending on how the printing was setup. Upgrading fixed the problem. I sent an e-mail about it about a week ago. If you've already got the drivers installed on the workstations you might want to go ahead and insert the following into the printer section. use client driver=Yes I believe that the mem=nopentium option is not necessary with the newer kernels. As far as browsing goes, you probably do want to get WINS setup and make sure that DNS is configured correctly. I noticed that some of the browsing slowness issues went away when I moved from 2.2.1a to 2.2.5. I don't know what browsing looks like after the upgrade 2.2.6. I only work via ssh, since I'm away at school. I can't actually be there to know what it feels like. Just my little bit of advice. James Hubbard Chris de Vidal wrote: Athlon MP 1.8GHz (mem=nopentium) 2GB ECC SDRAM Tyan S2460(I think?) Antec 450W PS Lots of cooling 5 IBM DeskStar 120GB drives with 8MB caches in RAID 5 3ware 7580(I think?) 8-port hardware RAID 3ware hot-swappable drive cages Intel e1000 Gigabit NIC, full duplex, 1000MBit, autonegotiation off 3com Gigabit switch, autonegotiation off RedHat 7.3 Kernel 2.4.19 with ACL support ext3 with ACL support Samba 2.2.5 with ACL support installed from a recompiled SRPM from the samba.org FTP site. Winbind NO nfs daemon (I hear it's buggy w/ ACLs) We have a variety of clients, from DOS and OS/2 to Windows (9x-2000) and Linux. The server acts as a print spooling area (the actual queues are on an NT server) and scratch area for database programmers to manipulate their flat database files. As far as I know, these files are not commonly accessed by more than one user at a time. THE PROBLEM For the past year, our heaviest-used Netware server has been under more and more stress.. filling up, running out of licenses, slowing down, etc. Preliminary tests using Samba on a fast Linux box showed anywhere from 70% to 1000% speed improvements, depending on the task. The decision was made to switch it to Linux; the whole company is migrating away from Netware and we (as a unit, not speaking for the company) don't want to be completely trapped into Windows if we can help it. The new hardware arrived and more preliminary tests indicated all looked good. We were set to switch last Saturday night. We turned off logins to the Netware box, backed it up, restored it to the new Linux box, set permissions, then made sure the various computers in the building could log in. Yesterday, our first day, was rough. For most of the day we fought random slow browsing with no explanation. Clients would appear to lock up for several seconds. We found some misconfigurations in smb.conf but the problems reappeared. No errors were seen in any machines' logs on debug level 2. I trimmed the smb.conf to a minimal number of options and that seemed to help with the slowness. Today, however, the problem reappeared a few times with no errors in the logs that we could see. The printers were missing some of the records sent to them to print, something that had never happened with Netware. Every time the missing records were different. Occasionally, it would work right. Oplocks (kernel, level I and II) were left to defaults (turned on). THE OUTCOME Sadly, tonight we are installing a Windows NT server. Installing a brand new server is actually cheaper for us than the 8 or so hours of downtime to back up the server, install NT on it, and restore the data to it. We don't want to revert to Netware because so many clients have been reconfigured to log on only to the domain (DOS, OS/2, etc.) and that would require many more hours reversing those changes. Also, some files have been added since leaving Netware. We also decided to proceed to use NT because is more proven in this capacity. CONCLUSION To be fair, the problems could be related to some misconfiguration. I have pasted the smb.conf below. I fear it might just be an oplock problem, but it is not clear what would result if more than one user happened to try to write to a file with them disabled. Every advice we found said to leave them on to prevent corruption and to improve performance. We ran out of time to test it, and feared what failure would bring. Running this: grep -r -B5 -A5 oplock /var/log/samba/ | grep -B5 -A5 error produced only 5 of these errors oplock_break: receive_smb error (Connection reset by peer) from the same DOS machine from 2 days worth of all machines' logs running at debuglevel 1 (some at level 2). I don't know if that is a good indicator of an oplock problem. I can do other greps on request. Unfortunately, we can't test out your suggestions in production, and our off-production testing apparently can't stress it wel
Re: [Samba] Another Shot At It
I don't think that you need the -y -A input -p tcp -s 0/0 -d 0/0 137:139 -j ACCEPT -A input -p udp -s 0/0 -d 0/0 137:139 -j ACCEPT -A input -p tcp -s obi-wan-ip -d luke-ip 137:139 -j ACCEPT -A input -p udp -s obi-wan-ip -d luke-ip 137:139 -j ACCEPT James James Hubbard wrote: Since you've probably enabled the firewall settings when you installed RedHat, you're probably going to need to modify the /etc/sysconfig/ipchains file. This line here is probably causing you the most problem. -A input -p tcp -s 0/0 -d 0/0 0:1023 -y -j REJECT In order to allow smb packets to be accepted you're going to need to open up the ports. The easiest way to do this (I believe) is to insert these 2 lines above the line listed above. -A input -p tcp -s 0/0 -d 0/0 137:139 -y -j ACCEPT -A input -p udp -s 0/0 -d 0/0 137:139 -y -j ACCEPT (Restart ipchains: /etc/rc.d/init.d/ipchains restart) I can't remember if you need the udp or not. This is also opens you up to anybody. You'll probably want to insert the acutal ip addresses of your two other machines in there. This could be a problem though. -A input -p tcp -s obi-wan-ip -d luke-ip 137:139 -y -j ACCEPT -A input -p udp -s obi-wan-ip -d luke-ip 137:139 -y -j ACCEPT ... One way to tell if you're got the smb ports locked down is to go to http://www.grc.com from your linux machine. Click Shields Up. It should tell you whether or not it can see your windows share. After you add the lines to open up the ports, go back to the site and try again. It should tell you the basic stuff like workgroup name. You really should invest in some type of firewalling hardware/software, preferrably something that filter packets before they get to your machines. James Hubbard DJ Busch wrote: After receiving no response to yesterday's message, I tried some more web scouring and more tinkering and dinking around with Samba...and I discovered what may be a major key to my problem... I have 3 PC's...2 are Windoze and 1 is Linux. Windoze machines are likely to understand how to share files across subnets using the same workgroup name...but is Samba as adept? I have a feeling that is at the heart of my problem. I enabled wins support in my smb.conf and assigned the Samba box's IP address as the primary wins server on the WFW box. I also set Samba to be the domain master browser according to the instructions in BROWSING.txt. All of this, alas, was useless as I still couldn't browse the Win-duhs shares from Linux or the Linux shares from Winduhs. I feel that I'm getting much closer to my goal (file sharing without using Windows) and would really appreciate any help any of you can offer. Thanks in advance for any help you can provide. DJ Busch Here is my latest attempt at smb.conf: [global] workgroup = LEGEND netbios name = LUKE server string = Dave's Linux Experiment Gone Wrong interfaces = eth0 bind interfaces only = Yes security = SHARE encrypt passwords = Yes null passwords = Yes log file = /var/log/samba/log.%m debug level = 5 max log size = 50 ;socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 os level = 2 lm announce = yes preferred master = yes domain master = yes dns proxy = No wins support = yes guest account = doodles hosts allow = ALL hosts deny = [homes] comment = Home Directories path = /home read only = No guest ok = Yes [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [hp] path = /var/spool/samba read only = No guest ok = Yes printable = Yes printer name = hp -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Another Shot At It
Since you've probably enabled the firewall settings when you installed RedHat, you're probably going to need to modify the /etc/sysconfig/ipchains file. This line here is probably causing you the most problem. -A input -p tcp -s 0/0 -d 0/0 0:1023 -y -j REJECT In order to allow smb packets to be accepted you're going to need to open up the ports. The easiest way to do this (I believe) is to insert these 2 lines above the line listed above. -A input -p tcp -s 0/0 -d 0/0 137:139 -y -j ACCEPT -A input -p udp -s 0/0 -d 0/0 137:139 -y -j ACCEPT (Restart ipchains: /etc/rc.d/init.d/ipchains restart) I can't remember if you need the udp or not. This is also opens you up to anybody. You'll probably want to insert the acutal ip addresses of your two other machines in there. This could be a problem though. -A input -p tcp -s obi-wan-ip -d luke-ip 137:139 -y -j ACCEPT -A input -p udp -s obi-wan-ip -d luke-ip 137:139 -y -j ACCEPT ... One way to tell if you're got the smb ports locked down is to go to http://www.grc.com from your linux machine. Click Shields Up. It should tell you whether or not it can see your windows share. After you add the lines to open up the ports, go back to the site and try again. It should tell you the basic stuff like workgroup name. You really should invest in some type of firewalling hardware/software, preferrably something that filter packets before they get to your machines. James Hubbard DJ Busch wrote: After receiving no response to yesterday's message, I tried some more web scouring and more tinkering and dinking around with Samba...and I discovered what may be a major key to my problem... I have 3 PC's...2 are Windoze and 1 is Linux. Windoze machines are likely to understand how to share files across subnets using the same workgroup name...but is Samba as adept? I have a feeling that is at the heart of my problem. I enabled wins support in my smb.conf and assigned the Samba box's IP address as the primary wins server on the WFW box. I also set Samba to be the domain master browser according to the instructions in BROWSING.txt. All of this, alas, was useless as I still couldn't browse the Win-duhs shares from Linux or the Linux shares from Winduhs. I feel that I'm getting much closer to my goal (file sharing without using Windows) and would really appreciate any help any of you can offer. Thanks in advance for any help you can provide. DJ Busch Here is my latest attempt at smb.conf: [global] workgroup = LEGEND netbios name = LUKE server string = Dave's Linux Experiment Gone Wrong interfaces = eth0 bind interfaces only = Yes security = SHARE encrypt passwords = Yes null passwords = Yes log file = /var/log/samba/log.%m debug level = 5 max log size = 50 ; socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 os level = 2 lm announce = yes preferred master = yes domain master = yes dns proxy = No wins support = yes guest account = doodles hosts allow = ALL hosts deny = [homes] comment = Home Directories path = /home read only = No guest ok = Yes [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [hp] path = /var/spool/samba read only = No guest ok = Yes printable = Yes printer name = hp -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing W2K net use lpt Fixed
Upgrading from 2.2.5 to 2.2.6rc4 seems to have fixed this problem. James Hubbard James Hubbard wrote: > Hello, > > I've got a problem with printing on a Windows 2K box. Printing from > that box to a samba server via the normal print mechanism works fine. > The problem is when the person needs to print to a lpt port. The > capture succeeds, but when the file is copied to lpt2 it never gets > printed. > > There are other machines that can do the capture and copy to the lpt > port but they are Win 9x. The files being copied are plot files > generated by a cad program. > > I noticed in the How-To that using enumports might be needed to make > using lpt ports work. It's not working though and I'm still getting the > same error message. I've just started using disable spoolss = yes but > that doesn't seem to help either. > > All relevant information is below. Any help is appreciated. > > James Hubbard > > > > This is the command being used to capture the port. > net use lpt2: \\server-bristol\hp450c > > Samba version 2.2.5 > RedHat 7.2 > Windows 2K with the latest service packs. > > smb.conf > [global] > .. >printcap name = /etc/printcap >load printers = yes >enumports command=/home/samba/ports.sh >disable spoolss = yes >printing = lprng > > ... >security = share > > [printers] >comment = All Printers >path = /var/spool/samba >browseable = no >guest ok = yes >writable = no >printable = yes >public = yes >use client driver = yes > > This is the error messages that I'm getting in the log file for that > machine. > > [2002/10/15 14:27:22, 0] lib/fault.c:fault_report(39) > INTERNAL ERROR: Signal 11 in pid 28282 (2.2.5) > Please read the file BUGS.txt in the distribution > [2002/10/15 14:27:22, 0] lib/fault.c:fault_report(41) > === > [2002/10/15 14:27:22, 0] lib/util.c:smb_panic(1092) > PANIC: internal error > [2002/10/15 14:27:26, 0] lib/fault.c:fault_report(38) > === > [2002/10/15 14:27:26, 0] lib/fault.c:fault_report(39) > INTERNAL ERROR: Signal 11 in pid 28631 (2.2.5) > Please read the file BUGS.txt in the distribution > [2002/10/15 14:27:26, 0] lib/fault.c:fault_report(41) > === > [2002/10/15 14:27:26, 0] lib/util.c:smb_panic(1092) > PANIC: internal error > -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
Re: [Samba] Printing W2K net use lpt
I've gotten more detail for the problem that I'm having. This problem occurs on multiple Win 2K machines. I set log level = 8 and got the output for this event. I've attached the output of the log to the end of the message. This error occurs when: 1.) a printer is caputred to a certain port. In this case lpt2 2.) a file is copied to the port James Hubbard P.S. See error log below. I apologize for the length. James Hubbard wrote: > Hello, > > I've got a problem with printing on a Windows 2K box. Printing from > that box to a samba server via the normal print mechanism works fine. > The problem is when the person needs to print to a lpt port. The > capture succeeds, but when the file is copied to lpt2 it never gets > printed. > > There are other machines that can do the capture and copy to the lpt > port but they are Win 9x. The files being copied are plot files > generated by a cad program. > > I noticed in the How-To that using enumports might be needed to make > using lpt ports work. It's not working though and I'm still getting the > same error message. I've just started using disable spoolss = yes but > that doesn't seem to help either. > > All relevant information is below. Any help is appreciated. > > James Hubbard > > > > This is the command being used to capture the port. > net use lpt2: \\server-bristol\hp450c > > Samba version 2.2.5 > RedHat 7.2 > Windows 2K with the latest service packs. > > smb.conf > [global] > .. >printcap name = /etc/printcap >load printers = yes >enumports command=/home/samba/ports.sh >disable spoolss = yes >printing = lprng > > ... >security = share > > [printers] >comment = All Printers >path = /var/spool/samba >browseable = no >guest ok = yes >writable = no >printable = yes >public = yes >use client driver = yes > > This is the error messages that I'm getting in the log file for that > machine. [2002/10/15 17:04:23, 2] smbd/reply.c:reply_sesssetup_and_X(982) Defaulting to Lanman password for mike_r [2002/10/15 17:04:23, 4] smbd/password.c:password_ok(593) Null passwords not allowed. [2002/10/15 17:04:23, 3] smbd/reply.c:reply_sesssetup_and_X(1039) Registered username nobody for guest access [2002/10/15 17:04:23, 6] smbd/reply.c:reply_sesssetup_and_X(1108) Client requested max send size of 65535 [2002/10/15 17:04:23, 3] smbd/process.c:chain_reply(1022) Chained message [2002/10/15 17:04:23, 5] lib/util.c:show_msg(268) size=164 smb_com=0x75 smb_rcls=0 smb_reh=0 smb_err=0 smb_flg=24 smb_flg2=18439 [2002/10/15 17:04:23, 5] lib/util.c:show_msg(276) smb_tid=0 smb_pid=65279 smb_uid=0 smb_mid=46592 smt_wct=4 [2002/10/15 17:04:23, 5] lib/util.c:show_msg(285) smb_vwv[0]=255 (0xFF) [2002/10/15 17:04:23, 5] lib/util.c:show_msg(285) smb_vwv[1]=164 (0xA4) [2002/10/15 17:04:23, 5] lib/util.c:show_msg(285) smb_vwv[2]=8 (0x8) [2002/10/15 17:04:23, 5] lib/util.c:show_msg(285) smb_vwv[3]=1 (0x1) [2002/10/15 17:04:23, 5] lib/util.c:show_msg(291) smb_bcc=31 [2002/10/15 17:04:23, 3] smbd/process.c:switch_message(684) switch message SMBtconX (pid 30505) [2002/10/15 17:04:23, 3] smbd/sec_ctx.c:set_sec_ctx(313) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0 [2002/10/15 17:04:23, 5] smbd/uid.c:change_to_root_user(216) change_to_root_user: now uid=(0,0) gid=(0,0) [2002/10/15 17:04:23, 4] smbd/reply.c:reply_tcon_and_X(335) Got device type ? [2002/10/15 17:04:23, 3] lib/access.c:check_access(318) check_access: no hostnames in host allow/deny list. [2002/10/15 17:04:23, 2] lib/access.c:check_access(327) Allowed connection from (192.168.83.31) [2002/10/15 17:04:23, 4] smbd/password.c:password_ok(593) Null passwords not allowed. [2002/10/15 17:04:23, 3] smbd/password.c:authorise_login(854) authorise_login: ACCEPTED: guest account and guest ok (nobody) [2002/10/15 17:04:23, 3] smbd/service.c:make_connection(491) Connect path is /var/spool/samba [2002/10/15 17:04:23, 3] smbd/sec_ctx.c:push_sec_ctx(281) push_sec_ctx(0, 0) : sec_ctx_stack_ndx = 1 [2002/10/15 17:04:23, 3] smbd/uid.c:push_conn_ctx(285) push_conn_ctx(0) : conn_ctx_stack_ndx = 0 [2002/10/15 17:04:23, 3] smbd/sec_ctx.c:set_sec_ctx(313) setting sec ctx (0, 0) - sec_ctx_stack_ndx = 1 [2002/10/15 17:04:23, 3] smbd/sec_ctx.c:get_current_groups(162) get_current_groups: user is in 1 groups: 99 [2002/10/15 17:04:23, 3] smbd/sec_ctx.c:pop_sec_ctx(420) pop_sec_ctx (0, 0) - sec_ctx_stack_ndx = 0 [2002/10/15 17:04:23, 3] smbd/sec_ctx.c:get_current_groups(162) get_current_groups: user is in 1 groups: 99 [2002/10/15 17:04:23, 5] smbd/connection.c:claim_connection(156) claiming hp450c 0 [2002/10/15 17:04:23, 5] smbd/password.c:create_nt_to
[Samba] Printing W2K net use lpt
Hello, I've got a problem with printing on a Windows 2K box. Printing from that box to a samba server via the normal print mechanism works fine. The problem is when the person needs to print to a lpt port. The capture succeeds, but when the file is copied to lpt2 it never gets printed. There are other machines that can do the capture and copy to the lpt port but they are Win 9x. The files being copied are plot files generated by a cad program. I noticed in the How-To that using enumports might be needed to make using lpt ports work. It's not working though and I'm still getting the same error message. I've just started using disable spoolss = yes but that doesn't seem to help either. All relevant information is below. Any help is appreciated. James Hubbard This is the command being used to capture the port. net use lpt2: \\server-bristol\hp450c Samba version 2.2.5 RedHat 7.2 Windows 2K with the latest service packs. smb.conf [global] .. printcap name = /etc/printcap load printers = yes enumports command=/home/samba/ports.sh disable spoolss = yes printing = lprng ... security = share [printers] comment = All Printers path = /var/spool/samba browseable = no guest ok = yes writable = no printable = yes public = yes use client driver = yes This is the error messages that I'm getting in the log file for that machine. [2002/10/15 14:27:22, 0] lib/fault.c:fault_report(39) INTERNAL ERROR: Signal 11 in pid 28282 (2.2.5) Please read the file BUGS.txt in the distribution [2002/10/15 14:27:22, 0] lib/fault.c:fault_report(41) === [2002/10/15 14:27:22, 0] lib/util.c:smb_panic(1092) PANIC: internal error [2002/10/15 14:27:26, 0] lib/fault.c:fault_report(38) === [2002/10/15 14:27:26, 0] lib/fault.c:fault_report(39) INTERNAL ERROR: Signal 11 in pid 28631 (2.2.5) Please read the file BUGS.txt in the distribution [2002/10/15 14:27:26, 0] lib/fault.c:fault_report(41) === [2002/10/15 14:27:26, 0] lib/util.c:smb_panic(1092) PANIC: internal error -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
