[Samba] Cannot share MSAccess DB after upgrade 3.0.5 to 3.0.8
) NT_STATUS_OBJECT_NAME_NOT_FOUND [2004/12/17 12:21:08, 5] lib/util.c:show_msg(464) [2004/12/17 12:21:08, 5] lib/util.c:show_msg(474) size=35 smb_com=0xa2 smb_rcls=52 smb_reh=0 smb_err=49152 smb_flg=136 smb_flg2=51201 smb_tid=1 smb_pid=1268 smb_uid=100 smb_mid=2048 smt_wct=0 smb_bcc=0 [2004/12/17 12:21:08, 6] lib/util_sock.c:write_socket(449) write_socket(5,39) [2004/12/17 12:21:08, 6] lib/util_sock.c:write_socket(452) write_socket(5,39) wrote 39 Note the error message NT_STATUS_OBJECT_NAME_NOT_FOUND. Can someone more familiar with the log content help me understand why Samba is refusing to acknowledge the file's existence to its users? Thanks, Lane Beneke __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Cannot share MSAccess DB after upgrade 3.0.5 to 3.0.8
Well, it turns out that the smbstatus/Access column/0x3 condition is not the cause of the problem. (I still don't understand the significance of that column.) A simple upgrade from 3.0.5 to 3.0.8 broke file sharing on a MSAccess 2k database (Win2k and WinXP clients.) There are Paradox databases on the same file-share that are working fine. The log files show no errors. I'm about to try increasing the debug level, but can anyone give me a clue in the meantime? Thanks, Lane Beneke --- Lane Beneke wrote: This is really strange. The samba server in question is a domain member server on a Windows NT 4.0 Domain network. It runs Gentoo 2004.3 with a 2.4.24 kernel. The Gentoo server was upgraded from Samba 3.0.5 to 3.0.8 last night. After the upgrade, the server had to be re-joined to the domain. After that, everything appeared to be working. This morning we found that the MSAccess database files can no longer be shared if the database users open the MDB file containing the tables. The first user in can use the database, and databases that are externally linked to the database in question can share the data just fine. (Weirdness) A quick look at smbstatus output reveals that no oplocks are placed on the MDB or the LDB files. However, the Access column of the smbstatus output shows 0x2019f for all files except the MDB files, which show 0x3. Does anyone know what this means? 32748 DENY_NONE 0x3 RDWR NONE /samba/common/smc.mdb 32748 DENY_NONE 0x2019f RDWR NONE /samba/common/smc.ldb Help! Lane Beneke __ Do you Yahoo!? Yahoo! Mail - Easier than ever with enhanced search. Learn more. http://info.mail.yahoo.com/mail_250 __ Do you Yahoo!? Take Yahoo! Mail with you! Get it on your mobile phone. http://mobile.yahoo.com/maildemo -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] Cannot share MSAccess DB after upgrade 3.0.5 to 3.0.8
This is really strange. The samba server in question is a domain member server on a Windows NT 4.0 Domain network. It runs Gentoo 2004.3 with a 2.4.24 kernel. The Gentoo server was upgraded from Samba 3.0.5 to 3.0.8 last night. After the upgrade, the server had to be re-joined to the domain. After that, everything appeared to be working. This morning we found that the MSAccess database files can no longer be shared if the database users open the MDB file containing the tables. The first user in can use the database, and databases that are externally linked to the database in question can share the data just fine. (Weirdness) A quick look at smbstatus output reveals that no oplocks are placed on the MDB or the LDB files. However, the Access column of the smbstatus output shows 0x2019f for all files except the MDB files, which show 0x3. Does anyone know what this means? 32748 DENY_NONE 0x3 RDWR NONE /samba/common/smc.mdb 32748 DENY_NONE 0x2019f RDWR NONE /samba/common/smc.ldb Help! Lane Beneke __ Do you Yahoo!? Yahoo! Mail - Easier than ever with enhanced search. Learn more. http://info.mail.yahoo.com/mail_250 -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
[Samba] XP Pro timeout
Windows XP Pro clients are timing out when attempting to use either a file or printer share on my Samba 3.0.5 server. Any graphical application will fall into a seemingly endless timeout when attempting to access the Samba server. Print jobs will stay in the XP print queue for as much as 1/2 hour, and then print normally. The odd thing is that access from any non-graphical application (cmd.exe) on the XP clients is instantaneous. Two XP Pro workstations (version 2002, SP1) are exhibiting this behaviour. The rest of the company (Win2k, Win98, Win95, WinNT) is working fine. There are no other XP workstations on the network. The Samba server was upgraded from 2.2.8a last Friday. The upgrade worked fine for two working days before this problem showing up today. Included below are many of the specifics of my installation, and current log file excerpts for your scrutiny. Thanks in advance for any help you may provide. Lane Beneke; IT Manager Stephenson Millwork Co., Inc. - THE PLAYERS - Problem Clients - Windows XP Pro Version 2002 SP1 PDC - Windows NT Server Version 4.0 SP6 File Server - Linux 2.4.24 w/Samba 3.0.5 - RECENT EVENTS - 5 days ago - Samba upgraded from 2.2.8a to 3.0.5 Yesterday - Everything working fine, including XP clients Today - Several reboots of XP clients - LOG.SMBD LOG FILE - [2004/07/28 09:48:46, 0] lib/util_sock.c:get_peer_addr(978) getpeername failed. Error was Transport endpoint is not connected - CLIENT LOG FILE - [2004/07/28 09:20:20, 1] smbd/service.c:make_connection_snum(619) smc158 (192.168.42.109) connect to service WorkOrder3 initially as user rick (uid=1026, gid=100) (pid 28420) [2004/07/28 09:21:13, 1] smbd/service.c:close_cnum(801) smc158 (192.168.42.109) closed connection to service WorkOrder3 [2004/07/28 09:32:05, 1] smbd/service.c:close_cnum(801) smc158 (192.168.42.109) closed connection to service estimating [2004/07/28 09:32:13, 1] smbd/service.c:close_cnum(801) smc158 (192.168.42.109) closed connection to service rick [2004/07/28 09:32:13, 1] smbd/service.c:close_cnum(801) smc158 (192.168.42.109) closed connection to service common [2004/07/28 09:37:13, 0] lib/util_sock.c:get_peer_addr(978) getpeername failed. Error was Transport endpoint is not connected [2004/07/28 09:37:13, 0] lib/util_sock.c:write_socket_data(413) write_socket_data: write failure. Error = Connection reset by peer [2004/07/28 09:37:13, 0] lib/util_sock.c:write_socket(438) write_socket: Error writing 4 bytes to socket 22: ERRNO = Connection reset by peer [2004/07/28 09:37:13, 0] lib/util_sock.c:send_smb(630) Error writing 4 bytes to client. -1. (Connection reset by peer) [2004/07/28 09:37:13, 1] smbd/service.c:make_connection_snum(619) smc158 (192.168.42.109) connect to service rick initially as user rick (uid=1026, gid=100) (pid 30492) [2004/07/28 09:37:15, 1] smbd/service.c:make_connection_snum(619) smc158 (192.168.42.109) connect to service estimating initially as user rick (uid=1026, gid=100) (pid 30492) - SAMBA CONFIGURATION FILE - # Samba config file created using SWAT # from 192.168.42.108 (192.168.42.108) # Date: 2004/07/23 21:56:29 # Global parameters [global] workgroup = DOMAIN netbios name = SERVER-BACKUP server string = Backup Server security = DOMAIN update encrypted = Yes null passwords = Yes password server = server passwd program = /usr/bin/passwd %u passwd chat = *New\sUNIX\spassword:* %n\n*Retype\snew\sUNIX\spassword:* %n\n . unix password sync = Yes syslog = 0 log file = /var/log/samba/log.%m max log size = 1000 time server = Yes socket options = IPTOS_LOWDELAY TCP_NODELAY add user script = /usr/sbin/useradd -d /home/%u -g 100 -m %u ; smbpasswd -a %u preferred master = No local master = No domain master = No dns proxy = No wins server = 192.168.42.250 idmap uid = 1-10999 idmap gid = 11000-11999 invalid users = root printer admin = root, Administrator, lane create mask = 0770 hosts allow = 192.168.42 hosts deny = 192.168.42.254 [homes] comment = Home Directories read only = No veto files = /Maildir/ browseable = No [common] comment = Open Share (G: Drive) path = /home/samba/common read only = No create mask = 0777 directory mask = 0777 guest ok = Yes [print$] comment = Point-n-Print Drivers path = /var/cache/samba/print invalid users = admin users = lane write list = root, Administrator, lane create mask = 0774 guest ok = Yes [pplabels] comment = Used only by DOS version of Product Planner path = /tmp printable = Yes printing = lprng print command = /usr/bin/pplabels %s %U %J [print2pdf
[Samba] RE: XP Pro timeout; we have a winner - webclient service
Thanks to Jason Balicki for the correct fix to this problem. The 'webclient' service in Windows XP, somehow interferes with access to the Samba server. With the service stopped and disabled, the clients are working again. Lane Beneke; IT Manager Stephenson Millwork Co., Inc. -Original Message- From: Lane Beneke [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 28, 2004 12:42 PM To: '[EMAIL PROTECTED]' Subject: XP Pro timeout Windows XP Pro clients are timing out when attempting to use either a file or printer share on my Samba 3.0.5 server. Any graphical application will fall into a seemingly endless timeout when attempting to access the Samba server. Print jobs will stay in the XP print queue for as much as 1/2 hour, and then print normally. The odd thing is that access from any non-graphical application (cmd.exe) on the XP clients is instantaneous. Two XP Pro workstations (version 2002, SP1) are exhibiting this behaviour. The rest of the company (Win2k, Win98, Win95, WinNT) is working fine. There are no other XP workstations on the network. The Samba server was upgraded from 2.2.8a last Friday. The upgrade worked fine for two working days before this problem showing up today. Included below are many of the specifics of my installation, and current log file excerpts for your scrutiny. Thanks in advance for any help you may provide. Lane Beneke; IT Manager Stephenson Millwork Co., Inc. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
