Last night we have been desperately trying to make smbclient download a bunch of files from a win 2k machine. Currently we are clueless and are about to give up.
The problem is as follows:
We have a Linux machine that has to gather a bunch of files every night. Previously we had a win 98 box and that one never gave a problem. We now had to upgrade to use newer software.
First step: connection
smbclient //bashful/hrofft -U Administrator
The connection opens as it should and we are able to do a command like 'ls'
Then we try to get a file
smb /> mget 1.png
At that point it goes terribly wrong. It takes ages, and then the transfer fails with a timeout error. After that, as usual for windows machines, any communication becomes impossible. A simple ls delivers a timeout too until we close the smbclient and start a new one.
The same occurs when we try to put a file
No firewalls are on the systems, all permissions are set open to scratch out this as possible reason.
We then ended up with a packet sniffer and recorded an attempt. Everything goes nice as it should. The transfer opens and the Linux machine asks for the file. The win2k machine sends the file. Resends it, resends it, resends it, then a few moments later the Linux box ask for the file again and after 20 seconds the Linux box just closes the communication due to no success. We feel like somehow our packets end up in /dev/null
I took my vector laptop and had exactly the same problem with the latest samba version around. We patched win2k up to service pack 4, but problem persists.
We googled the error and found a few people complaining about the same in mailing lists but no one really knows a solution.
Anyone got the slightest idea whats going wrong here?