[Samba] CIFS mount intermittently unavailable: cifs_mount failed w/return code = -5
I have a debian machine called debian and a windows XP machine called server. I have a permanent mounted read-only share called \\server\doc. My /etc/fstab looks like this: //server/doc/opt/chroot/mnt/server cifs credentials=/root/.smbmount,username=medical,uid=medical,file_mode=0755,dir_mode=0755,noserverino 0 0 This works well most of the time but at times I get a input/output error when I try to access this share. My syslog shows the following: Aug 16 15:36:35 debian kernel: [1289131.676869] Status code returned 0xc0d0 NT_STATUS_REQUEST_NOT_ACCEPTED Aug 16 15:36:35 debian kernel: [1289131.676875] CIFS VFS: Send error in SessSetup = -5 Aug 16 15:36:35 debian kernel: [1289131.676899] CIFS VFS: cifs_mount failed w/return code = -5 Aug 16 15:36:46 debian kernel: [1289142.653770] Status code returned 0xc0d0 NT_STATUS_REQUEST_NOT_ACCEPTED Aug 16 15:36:46 debian kernel: [1289142.653775] CIFS VFS: Send error in SessSetup = -5 Aug 16 15:36:46 debian kernel: [1289142.653799] CIFS VFS: cifs_mount failed w/return code = -5 Aug 16 15:37:01 debian kernel: [1289158.491697] Status code returned 0xc0d0 NT_STATUS_REQUEST_NOT_ACCEPTED Aug 16 15:37:01 debian kernel: [1289158.491703] CIFS VFS: Send error in SessSetup = -5 Aug 16 15:37:01 debian kernel: [1289158.491727] CIFS VFS: cifs_mount failed w/return code = -5 Does anyone have any suggestions? Can somebody explain what return code -5 means? I have tried replacing server with its fixed IP address (192.168.0.32), but this does not help. I have even moved all the files to another location on the Windows box and recreated the share, but it still occurs. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] [Solved] Re: networking problem/Domain not available
On Monday, November 29, 2010 09:02:32 am Allen Chen wrote: Did you power off and power on the other 2 old switches? Alllen Well, it appears Allen had the right solution, and I would have stumbled on it by accident. Over the holiday, we had a squirrel commit suicide on a transformer so everything got powered off and later back on. When I changed the cabling today to do the tests suggested by others, it worked! Thanks to all who tried to help me. Robert S wrote: I've got a client - a cheap client - and they want to add a new file server (samba sharing) to their network. They have one samba server already acting as the domain controller (PDC) and file server (and DHCP server). The wiring is a nightmare, and everything is daisy chained through 3 different non- programmable switches. They have no more open ports on any of the switches. Further, the switches are about 40 feet from the servers in another room. My plan was to take the cable that connects the domain controller (PDC), plug that into a new switch as the uplink, then connect both the old and new samba servers (a member server according to testparm) to the same switch. The new switch has all auto-uplink ports, so cross-over, non-cross-over isn't an issue. The problem is when I do this, none of the workstations (XP based) can find the domain controller any more (domain not available). I switch the cables back (remove the switch), everything works fine. Use the switch again, same problem. This means it's not the signorseal problem. For kicks to see if it's a bad cable or switch, I used a live Linux CD on my test workstation (this one is having the problem) when the connection is running through the new switch and it got a lease from the PDC (it's also a DHCP server) and can ping the PDC no problem. This, to me, says it can't be the cable or new switch and is pointing the finger at XP. But what is causing XP to fail? Domain authentications with very tiny TTL??? Any other troubleshooting tips? -- Fail to learn history-repeat it. Fail to learn rights-lose them. Learn both-get screwed by previous two groups. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] networking problem/Domain not available
I've got a client - a cheap client - and they want to add a new file server (samba sharing) to their network. They have one samba server already acting as the domain controller (PDC) and file server (and DHCP server). The wiring is a nightmare, and everything is daisy chained through 3 different non- programmable switches. They have no more open ports on any of the switches. Further, the switches are about 40 feet from the servers in another room. My plan was to take the cable that connects the domain controller (PDC), plug that into a new switch as the uplink, then connect both the old and new samba servers (a member server according to testparm) to the same switch. The new switch has all auto-uplink ports, so cross-over, non-cross-over isn't an issue. The problem is when I do this, none of the workstations (XP based) can find the domain controller any more (domain not available). I switch the cables back (remove the switch), everything works fine. Use the switch again, same problem. This means it's not the signorseal problem. For kicks to see if it's a bad cable or switch, I used a live Linux CD on my test workstation (this one is having the problem) when the connection is running through the new switch and it got a lease from the PDC (it's also a DHCP server) and can ping the PDC no problem. This, to me, says it can't be the cable or new switch and is pointing the finger at XP. But what is causing XP to fail? Domain authentications with very tiny TTL??? Any other troubleshooting tips? -- Fail to learn history-repeat it. Fail to learn rights-lose them. Learn both-get screwed by previous two groups. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] networking problem/Domain not available
On Sunday, November 28, 2010 01:47:02 pm Peter Trifonov wrote: Hi, The problem is when I do this, none of the workstations (XP based) can find the domain controller any more (domain not available). I switch the cables you should check network connectivity. Try pinging the servers from each other and client computers. There may be also firewall issues. With best regards, P. Trifonov I did ping the PDC server from the workstation when running Linux and even got a lease from it. All the lights on the new switch indicate everything is good, and the PDC server can access the Internet. Reboot the workstation into XP, and the workstation can't find the PDC (domain not available).* Since I can have two way traffic with the new switch in place, unless someone can point out a flaw in my logic, it can't be the switch. The switch is also a standard 5 port home switch (not my choice of equipment BTW), and does not include a firewall. And if I remove the switch, and go back to the original connection, with NO other changes (workstation and server), it works. I also considered it could be a bad cable, since I do use a new cable with the switch to connect the server to the new switch. But if it was a bad cable, how can I get a lease through it (and ping)? I should add that the original 3 switches are all different models, but none have any firewall capability. * Since I can't log in, I can't easily test the XP side of things to see if I get a lease, and I'm not in charge of the workstations, so getting the local admin password is not a simple matter. Politics... -- Fail to learn history-repeat it. Fail to learn rights-lose them. Learn both-get screwed by previous two groups. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Re: [Samba] networking problem/Domain not available
Answers are in-line. On Sunday, November 28, 2010 08:31:57 pm Gaiseric Vandal wrote: Is your test PC on the same switch as the samba servers? No. Were you able to look at the event logs on the XP machines? No. Well, not yet. If this problem occurs with the new switch and the PDC but not the new server , the only thing I could think to try would be to lock the server's NIC settings to force 1 speed and 1 duplex mode. For XP machines, Ethernet media detection can cause windows network problems- I know the problem is not with the XP machine but maybe something similar is happening on the server side- pings and dhcp assignments may be more tolerant of a flaky connection. If this only happens when both samba machines are on line then you may have a conflict with which machine is the browser- although that should only affect clients just coming on line. And WINS usually avoids those issues. No. Both the new file server and the PDC have been online at the same time and working. I could log into the domain and even map the shares on the new file server. This was before they purchased the new switch. I plugged the new file server into a jack on one of the three older switches that had an off computer at the other end of the jack. The PDC is the wins server and the new server is set to use the PDC wins server. Did you copy any private or lock files from one samba server to another ?Are both samba servers the same version? No to both questions. The config file for the new file server is from scratch (well, modified the sample config file). The PDC is samba 3.0.something, while the new file server is samba 3.5.something. I've been on their case about upgrading the PDC, but it's so far fallen on deaf ears. -Original Message- From: samba-boun...@lists.samba.org [mailto:samba-boun...@lists.samba.org] On Behalf Of Chris Gonnerman Sent: Sunday, November 28, 2010 8:32 PM To: samba@lists.samba.org Subject: Re: [Samba] networking problem/Domain not available On 11/28/2010 12:30 PM, Robert S wrote: The problem is when I do this, none of the workstations (XP based) can find the domain controller any more (domain not available). I switch the cables back (remove the switch), everything works fine. Use the switch again, same problem. This means it's not the signorseal problem. I don't know your problem, but I know how I'd proceed... unplug the PDC, then plug the new switch in between it and the other switches, but DON'T plug the new server in yet. Test it. If it works, but stops when you plug in the new server, then your problem is the new server. -- Chris. -- Fail to learn history-repeat it. Fail to learn rights-lose them. Learn both-get screwed by previous two groups. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
[Samba] Recycle does not work in [homes]
I have just upgraded to samba 3.0.8. I've managed to get recycle to work in shares, but it won't work in [homes] shares. I have My Documents pointing to //server/robert. If I delete a file there it does not end up in //server/robert/.recycle. Is there a fix for this or is it intended behaviour? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Recycle does not work in [homes]
Send your conf please. Incidentally - I've done a workaround where /home/user/.documents/RECYCLER is symlinked to a location in /tmp. Seems to achieve a similar result. I'd be interested to know whats happening here though. smb.conf: [global] workgroup = HOME netbios name = MYSERVER server string = Samba Server encrypt passwords = Yes smb passwd file = /etc/samba/private/smbpasswd log file = /var/log/samba.log socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 lock dir = /var/lock/samba printing = cups printcap name = cups time server = yes dos filetimes = yes fake directory create times = yes dos filetime resolution = yes delete readonly = yes vfs object = vscan-clamav,recycle vscan-clamav: config-file = /etc/samba/vscan-clamav.conf recycle: config-file = /etc/samba/recycle.conf [homes] comment = Home Directories path = /home/%S/.documents valid users = %S read only = No browseable = No [public] path = /pub create mask = 774 force group = users read only = No guest ok = Yes browseable = yes [printers] comment = All Printer path = /var/spool/samba browseable = yes printable = yes My recycle.conf: name = .recycle mode = KEEP_DIRECTORIES|VERSIONS|TOUCH maxsize = 1000 exclude = *.tmp|*.temp|*.o|*.obj|~$* excludedir = /tmp|/temp|/cache noversions = *.doc|*.xls|*.ppt -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Re: Recycle does not work in [homes]
You are using samba 2.x. I don't know about recycle there, sorry I'm actually using samba 3.0.8. What makes you think that its 2.x? Is there anything in my config that's right for 2.x and wrong for 3.x?? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Re: Re: Recycle does not work in [homes]
I put the recycle-configuration in every share, I want to activate it for. Didn't seem to work for me. -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba + cups not working (intermittently)
I initially thought this was a cups problem, but looks like samba now . . . I have been using a Brother MFC9880 printer with Samba. Everything has been fine for the last month, until things stopped working recently (on a Monday morning with no intervention over the weekend. Samba log is below: My system: Debian woody Samba-2.2.3a-14.1 cupsys-1.1.14-5woody1 MFC9880 connected to server by USB. This has intermittently happened in the past and can sometimes be fixed by restarting samba/cups, but I can't affort outages in a busy office!! BTW - printing using cups by http (http://debian:631/printers/mfc9880) from windows client works fine - so I think the problem is with samba. Can anybody help?? My smb.conf: [global] workgroup = WORKGROUP server string = %h server (Samba %v) encrypt passwords = true obey pam restrictions = Yes passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spas sword:* %n\n . syslog = 0 log file = /var/log/samba/log.%m max log size = 1000 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 dns proxy = No invalid users = root printing = cups printcap name = cups [homes] comment = Home Directories read only = No create mask = 0700 directory mask = 0700 browseable = No [printers] comment = All Printers path = /tmp printable = Yes browseable = Yes guest only = yes use client driver = yes guest account = smbprint [public] path = /home/apache/files force user = www-data force group = www-data read only = No create mask = 0640 guest ok = Yes The errors in smb.conf: [2004/11/10 13:46:57, 0] printing/print_cups.c:cups_printername_ok(291) Unable to get printer status for mfc9880,winspool,ne04: - client-error-not-found [2004/11/10 13:46:57, 0] smbd/service.c:make_connection(249) robert (192.168.0.7) couldn't find service mfc9880,winspool,ne04: -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Home directory hangs in IE
I have the following configuration my my /etc/samba/smb.conf: [homes] comment = %u home directory path = /home/%U/.documents read only = No create mode = 0600 directory mode = 0700 guest ok = no I have a (hypothetical) user name of myself, and another user on my system is another When I open up Network Neighbourhood in WinXP (SP1) I see the following shares: homes, myself and another When I double click on myself, the browser window hangs for several minutes. When I open homes or another I can browse my home data directory (/home/myself/.documents) without any hangs. There doesn't seem to be anything odd in the logs. Can anybody explain why WinXP hangs on my own share, but not on homes or on another user's home share? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba - XP. Slow log in/out
I have a server running slackware 9.1 and samba samba-2.2.8a and have WinXP Home (SP1) on a client machine. I have all of my users My documents pointing at a subdirectory of their home directories (ie. /home/USER/.documents). All of the users are able to use this with no problems EXCEPT me. When I log in to my user profile in Windows, the system tray takes about 5 minutes to load up. If I try to log out it hangs for about 5 minutes during this time. I am able to prevent this behaviour by pointing My Documents to a folder on the local (C:) hard drive and not using my samba share. Also - when I right-click on My Documents (in XP), go to Properties and change Target to \\SERVER\robert, it hangs for ages when I press Apply or OK. I recently reinstalled my entire XP hard drive and this problem still ocurs. Presumably its not an XP setup problem. Upgrading samba to 3.0.0 makes no difference. My user name is robert, the client computer is called CLIENT and the server is called SERVER (the names are fictitious). Sorry about putting a Windows question on a Unix newsgroup, but the aim of samba is to allow these systems to speak to each other! My /var/log/samba/CLIENT.log looks like this (as you can see there are some strange entries that are specific to my user name (they don't apply to other users): [2003/12/28 11:03:31, 0] smbd/service.c:make_connection(252) CLIENT (192.168.2.20) couldn't find service robert.dll [2003/12/28 11:10:57, 0] printing/print_cups.c:cups_printername_ok(388) Unable to get printer status for rober - client-error-not-found [2003/12/28 11:10:57, 0] smbd/service.c:make_connection(252) CLIENT (192.168.2.20) couldn't find service rober [2003/12/28 11:10:57, 0] printing/print_cups.c:cups_printername_ok(388) Unable to get printer status for robert.dll - client-error-not-found [2003/12/28 11:10:57, 0] smbd/service.c:make_connection(252) CLIENT (192.168.2.20) couldn't find service robert.dll Here are the relevant parts of my smb.conf: [global] workgroup = HOME netbios name = SERVER server string = Samba Server encrypt passwords = Yes log file = /var/log/samba/%m.log log level = 0 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 lock dir = /var/lock/samba printing = cups printcap name = cups invalid users = root browseable = No [homes] comment = Home Directories path = /home/%S/.documents read only = No create mask = 0700 directory mask = 0700 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Fixed (sort of): Re: Samba - XP. Slow log in/out
I don't know how this worked, but if I point My Documents to \\SERVER\homes everything seems to be OK. I still don't know why \\SERVER\robert bombed out. I'd be interested to know why. Robert S [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I have a server running slackware 9.1 and samba samba-2.2.8a and have WinXP Home (SP1) on a client machine. I have all of my users My documents pointing at a subdirectory of their home directories (ie. /home/USER/.documents). All of the users are able to use this with no problems EXCEPT me. When I log in to my user profile in Windows, the system tray takes about 5 minutes to load up. If I try to log out it hangs for about 5 minutes during this time. I am able to prevent this behaviour by pointing My Documents to a folder on the local (C:) hard drive and not using my samba share. Also - when I right-click on My Documents (in XP), go to Properties and change Target to \\SERVER\robert, it hangs for ages when I press Apply or OK. I recently reinstalled my entire XP hard drive and this problem still ocurs. Presumably its not an XP setup problem. Upgrading samba to 3.0.0 makes no difference. My user name is robert, the client computer is called CLIENT and the server is called SERVER (the names are fictitious). Sorry about putting a Windows question on a Unix newsgroup, but the aim of samba is to allow these systems to speak to each other! My /var/log/samba/CLIENT.log looks like this (as you can see there are some strange entries that are specific to my user name (they don't apply to other users): [2003/12/28 11:03:31, 0] smbd/service.c:make_connection(252) CLIENT (192.168.2.20) couldn't find service robert.dll [2003/12/28 11:10:57, 0] printing/print_cups.c:cups_printername_ok(388) Unable to get printer status for rober - client-error-not-found [2003/12/28 11:10:57, 0] smbd/service.c:make_connection(252) CLIENT (192.168.2.20) couldn't find service rober [2003/12/28 11:10:57, 0] printing/print_cups.c:cups_printername_ok(388) Unable to get printer status for robert.dll - client-error-not-found [2003/12/28 11:10:57, 0] smbd/service.c:make_connection(252) CLIENT (192.168.2.20) couldn't find service robert.dll Here are the relevant parts of my smb.conf: [global] workgroup = HOME netbios name = SERVER server string = Samba Server encrypt passwords = Yes log file = /var/log/samba/%m.log log level = 0 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 lock dir = /var/lock/samba printing = cups printcap name = cups invalid users = root browseable = No [homes] comment = Home Directories path = /home/%S/.documents read only = No create mask = 0700 directory mask = 0700 -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
