Anthony Giggins
2009-Nov-06 02:05 UTC
[Samba] Vista clients having Issues Copying files from Samba Server
Hello, I'm running samba-3.0.33 (samba-3.0.33-3.15.el5_4) On Centos 5.4 and some files have issues being copied from the Samba server to the Vista (Service Pack 1) clients local disk via Windows Explorer, copying too the Samba server also has no issues and copying via the CMD prompt has no problem, I'm getting the following errors 1. Invalid MS-DOS Function http://seven.dorksville.net/gallery/v/Misc+Photos/image001.png.html & 2. invalid file handle (When you click Try Again) http://seven.dorksville.net/gallery/v/Misc+Photos/image002.png.html It will then cycle through these 2 errors each time you click try again. Windows XP does not have any issues with the same files and other files also dont have an issue to the Vista Clients. There are also the following logs generated on the server that correspond to these errors lib/util_sock.c:send_smb(761) Error writing 75 bytes to client. -1. (Broken pipe) lib/util_sock.c:write_data(562) write_data: write failure in writing to client 192.168.0.237. Error Broken pipe lib/util_sock.c:write_data(562) write_data: write failure in writing to client 192.168.0.240. Error Broken pipe Any help or suggestions would be greatly apprieciated. Regards, Anthony
Anthony Giggins
2009-Dec-13 11:08 UTC
[Samba] Vista clients having Issues Copying files from Samba Server
> Hello, > > I'm running samba-3.0.33 (samba-3.0.33-3.15.el5_4) On Centos 5.4 and some > files have issues being copied from the Samba server to the Vista (Service > Pack 1) clients local disk via Windows Explorer, copying too the Samba > server also has no issues and copying via the CMD prompt has no problem, > I'm getting the following errors > > 1. Invalid MS-DOS Function > http://seven.dorksville.net/gallery/v/Misc+Photos/image001.png.html > & > 2. invalid file handle (When you click Try Again) > http://seven.dorksville.net/gallery/v/Misc+Photos/image002.png.html > > It will then cycle through these 2 errors each time you click try again. > > Windows XP does not have any issues with the same files and other files > also dont have an issue to the Vista Clients. > > There are also the following logs generated on the server that correspond > to these errors > > lib/util_sock.c:send_smb(761) Error writing 75 bytes to client. -1. > (Broken pipe) > lib/util_sock.c:write_data(562) write_data: write failure in writing to > client 192.168.0.237. Error Broken pipe > lib/util_sock.c:write_data(562) write_data: write failure in writing to > client 192.168.0.240. Error Broken pipe > > Any help or suggestions would be greatly apprieciated. > > Regards, > > AnthonySeeing as I got not replies I went and upgraded to 3.2.15 from sernet http://ftp.sernet.de/pub/samba/tested/centos/5/repodata/index.html And I'm seeing the same errors on the vista side but here are the logs from the server, Dec 13 11:16:39 newsrv smbd[32555]: [2009/12/13 11:16:39, 0] lib/util_sock.c:read_socket_with_timeout(939) Dec 13 11:16:39 newsrv smbd[32555]: [2009/12/13 11:16:39, 0] lib/util_sock.c:get_peer_addr_internal(1676) Dec 13 11:16:39 newsrv smbd[32555]: getpeername failed. Error was Transport endpoint is not connected Dec 13 11:16:39 newsrv smbd[32555]: read_socket_with_timeout: client 0.0.0.0 read error = Connection reset by peer. are there any known issues with Vista? and is there any known working minimum version? Cheers, Anthony
Moray Henderson
2009-Dec-15 09:21 UTC
[Samba] Vista clients having Issues Copying files from Samba Server
Anthony wrote:>> Please update to Samba 3.4.3 or later. Many Vista and Windows 7support>> related issues have been addressed during the 3.4.x series. >> >> Firstly, if the Samba logs note an invalid function all, that maymean>> an upgrade to a more recent version of Samba is needed. When aWindows>> client notes an invalid function call or an invalid file handle the >> cause may be problems in the network transport layer. >> >> Secondly, note what the Samba server log message says. Shorttranslation>> is: "I was taking to the client, but the client went away and did not >> respond!" The client dropped the connection. In all likelinessthis>> is not a Samba problem and may actually be a network problem. It isa>> problem regularly seen with low-cost ethernet interfaces and cheap >> ether-switches. >> >> Kindest, >> John T. >> >> > >I think I already know the answer to this but do you know of any 3rdparty>repos that would have packages for samba 3.4.x on Centos 5.4? > >Cheers, > >Anthonyftp://ftp.sernet.de/pub/samba/experimental/centos/5/ The 3.4 series should make its way into their recent and tested repositories eventually. Moray. "To err is human.? To purr, feline"