Weird problems with Samba in RHEL4

[Reginald0]

Hi, folks!

I recently forced to upgrade my systems from RHEL3 to RHEL4, due to new software requirements, and now I'm having some weird problems with Samba:

1) When I mount Windows shares using smbmount, I can write to a share normally, but if this share contains many files (I still don't know exactly how many files) and I try to list them (using ls or find, for example) the system hangs completely, with no errors displayed or written to logs.

2) Searching on Internet, I read that SMBFS on RHEL4 is a little buggish, and the right way to mount Windows shares is using CIFS. I tried to mount the same shares using mount.cifs and was mounted ok, but when I try to write something, I receive "Input/Output error". When I try to list the files, I receive "CIFS VFS: No task to wake, unknown frame rcvd!".

I choose to use RHEL at my company expecting stability and working packages, but now it seems I was wrong...

Thanks in advance!

Reginald0

 

[zeland]

"I choose to use RHEL at my company expecting stability and working packages, but now it seems I was wrong..."

No! You choses RHEL because you can call RedHat when you have these type of problems. What does RedHat have to say about your issue?

More info:
1. What Windows version?
2. All Windows or just that Windows?
3. What SAMBA version?
4. Can smbclient work?

--== Anything can go wrong. It's just a matter of how far wrong it will go till people think its right. ==--

 

[Reginald0]

zeland, I'm just an IT staff member at my company, so I can't decide what contract deals will be made or not, and my manager didn't want to prolong the contract support with Red Hat for more than a year, so I'm stuck with the trouble...

As for the questions (sorry not to give more details before):

1] Based on your questions, now I suspect that part of the problem lies in here. That specific machine is a SnapServer (

http://www.snapserver.com)

that has a system called SnapOS, which sharing functionality is similar to a Windows 2000, but nothing was changed in that machine, so my big complaint is why was working before the upgrade and not now?

2] Just that pseudo-Windows

3] samba-3.0.10-1.4E, but tried with different versions (older and newer) and the behavior was the same

4] I had not tested before, but smbclient is working, inclusive listing files on the same sharing as smbmount hangs the machine

Thanks for your attention and hope you understand my problem.

 

[zeland]

I can only guess from the information given about snapOS that its some customized version of Linux. When you used smbclient to connect, a line at the top would display something like: Domain=[HOME] OS=[Unix] Server=[Samba 3.0.24-1.fc5]. What does yours say?

I recall back when I was using FC4, SAMBA-3.0.14 started to have cifs semi-functional. Wasn't till SAMBA-3.0.20/21 that everything work without problems.

--== Anything can go wrong. It's just a matter of how far wrong it will go till people think its right. ==--

 

[QatQat]

what happens if you run a full mount command?

try something like this to mount windoz administrative share onto a directory called /mnt/samba

mount -t smbfs -o ip=xxx.xxx.xxx.xxx,username=administrator,password=xxxxxx //yourwindoz_ipaddress/c$ //mnt/samba

QatQat

Life is what happens when you are making other plans.