LinuxQuestions.org - Windows 7 can't write to RHEL 3 server when files greater then 1kb

- Linux - Server (https://www.linuxquestions.org/questions/linux-server-73/)

- - Windows 7 can't write to RHEL 3 server when files greater then 1kb (https://www.linuxquestions.org/questions/linux-server-73/windows-7-cant-write-to-rhel-3-server-when-files-greater-then-1kb-794915/)

Windows 7 can't write to RHEL 3 server when files greater then 1kb

hi community,

we are running a Red Hat Enterprise Linux ES release 3 (Taroon Upd 5) Kernel 2.4.21-32.ELsmp since several years. The server hosts an old ERP system who will be replaced at the end of the year.

However it is necessary that some collegues are able to write some files to that server regulary. Since we are running Windows 7 on several machines, those users aren't anymore able to write to the samba share. Getting files from the share works fine.

But the problem seems not to be situated at the samba service because also the transfer using SSH (WINSCP) from any Win7 system to the server doesn't work.

During testing we recogniced that transfering files smaller then 1kb works fine ... any file greater then 1kb ends up in an connection abort. This works with samba and also using SSH.

All the workarounds editing some registry entries in Win7 for improving the interoperability between vista / win7 and samba don't work for us ... and also seem not to be the source of the problem.

Is there a general known incompatibility between our RHEL version / kernel and Windows 7 regarding file transfers?

We are grateful for any tip or hint - please excuse my pure linux knowledge.

Regards Thomas

here are some logs from the samba log files ... not that we think this is the main problem, but these are the only log files where we are able to see a direct connection between transfering a file and the reaction of the server

transfering a file smaller then 1kb:

Code:

[2010/03/12 12:27:04,  1] smbd/service.c:1240(close_cnum)

  192.168.1.151 (192.168.1.151) closed connection to service msdos

[2010/03/12 12:27:08,  1] smbd/service.c:1063(make_connection_snum)

  192.168.1.151 (192.168.1.151) connect to service msdos initially as user nobody (uid=99, gid=99) (pid 12801)

[2010/03/12 12:27:09,  1] smbd/service.c:1063(make_connection_snum)

  192.168.1.151 (192.168.1.151) connect to service msdos initially as user nobody (uid=99, gid=99) (pid 12802)

[2010/03/12 12:27:43,  1] smbd/service.c:1240(close_cnum)

  192.168.1.151 (192.168.1.151) closed connection to service msdos

transfering a file greater than 1kb >> this results in a win7 error message where we hit the cancel button

Code:

[2010/03/12 12:28:51,  0] lib/util_sock.c:539(read_fd_with_timeout)

[2010/03/12 12:28:51,  0] lib/util_sock.c:1491(get_peer_addr_internal)

  getpeername failed. Error was Der Socket ist nicht verbunden

  read_fd_with_timeout: client 0.0.0.0 read error = Die Verbindung wurde vom Kommunikationspartner zurückgesetzt.

[2010/03/12 12:28:51,  1] smbd/service.c:1240(close_cnum)

  192.168.1.151 (192.168.1.151) closed connection to service msdos

[2010/03/12 12:28:51,  1] smbd/service.c:1063(make_connection_snum)

  192.168.1.151 (192.168.1.151) connect to service msdos initially as user nobody (uid=99, gid=99) (pid 12873)

Would someone consider any other standard log files where we might find some hints to the source of our problem?

What is the Windows 7 error message 'where we hit the cancel button'?

My german is a bit rusty, but it appears there is a socket error on the samba side, followed by a connection closed error, which I am guessing is because you choose to cancel.

What version of Samba is your server running?
Anything below Samba 3.3.2 will need the Windows 7 Security Policy changes below. Samba 3.3.2 or newer should just work.

Have you tried this on your Windows 7 machines?

Quote:

Go to: Control Panel -> Administrative Tools -> Local Security Policy
Select: Local Policies -> Security Options

As shown in Figure 1, there are two settings to change.
"Network security: LAN Manager authentication level" -> Send LM & NTLM responses
"Minimum session security for NTLM SSP" -> uncheck: Require 128-bit encryption

Since your Samba server plays nice with older versions of Windows, I think it is fairly obvious that the error is caused by good old Microsoft and not Samba. Upgrading your Samba version to at least 3.3.2 would be the way to 'fix' it on the server side.

Thanks for your reply.

Yes we also found this hint with the LM & NTLM responses and the encryption level in the internet and already tried it out. We also tried to update our samba server last night and have now this version running - problems still occuring.

actual version is 3.4.7

What do you think about the SSH transfer - here is exactly the same problem present. Files smaller then 1kb can be transfered by samba and SSH ... greater than 1kb ... both ways result in a timeout.

Also the problem only occurs when transfering from Win7 to RHEL the other way round works fine.

Is there a system log file on the linux server where we might find more informations? The Win7 protocols have no events logged.

What errors do you get during the SSH Transfers? Do logs show anything for the SSH failures?

Since you can download from the server, but not upload to it. I know there can be problems with speed when connecting to samba from windows. Is this over a LAN? Any routing involved??

Have you tried temporarily turning off the Windows 7 firewall?

Is Samba providing file shares only or acting as a Domain Controller as well?

Perhaps wireshark on the Windows 7 machine and or tcpdump on the linux box would yield some information???

You could also turn up the logging in Samba and see if it shows anything.

You might check /var/log/messages or any logs that relate to kernel, firewall, or network (this can depend on how the system was configured)

Hope this helps.

I tried to transfered a file greater then 1kb which wasn't able to transfer from Win7 to the samba share and found this log entries in the /var/log/messages

Code:

Mar 15 16:58:19 ebbsrv smbd[29693]: [2010/03/15 16:58:19,  0] lib/util_sock.c:539(read_fd_with_timeout) 

Mar 15 16:58:19 ebbsrv smbd[29693]: [2010/03/15 16:58:19,  0] lib/util_sock.c:1491(get_peer_addr_internal) 

Mar 15 16:58:19 ebbsrv smbd[29693]:  getpeername failed. Error was Der Socket ist nicht verbunden 

Mar 15 16:58:19 ebbsrv smbd[29693]:  read_fd_with_timeout: client 0.0.0.0 read error = Die Verbindung wurde vom Kommunikationspartner zurückgesetzt. 

Mar 15 16:58:53 ebbsrv smbd[29713]: [2010/03/15 16:58:53,  0] lib/util_sock.c:539(read_fd_with_timeout) 

Mar 15 16:58:53 ebbsrv smbd[29713]: [2010/03/15 16:58:53,  0] lib/util_sock.c:1491(get_peer_addr_internal) 

Mar 15 16:58:53 ebbsrv smbd[29713]:  getpeername failed. Error was Der Socket ist nicht verbunden 

Mar 15 16:58:53 ebbsrv smbd[29713]:  read_fd_with_timeout: client 0.0.0.0 read error = Die Verbindung wurde vom Kommunikationspartner zurückgesetzt.

next i tried to transfer the same file using SSH (WINSCP) and found nothing then the SSH session in the log ... no errors - but the transfer also failed

Code:

Mar 15 17:18:14 ebbsrv sshd(pam_unix)[30651]: session opened for user root by (uid=0)

Mar 15 17:19:21 ebbsrv sshd(pam_unix)[30651]: session closed for user root

I will check the network traffic as you supposed me to do, but perhabs someone can give me a hint where to problem might be by the socket errors above. Is our RHEL kernel just incompatible with Windows 7?

As reply to the questions "never say never" asked:
- same LAN
- no routing between
- win7 firewall is off while in the windows domain
- there is no domain functionality used by the linux server, the pdc is a windows 2k3 server