f9 samba problems

[pfaris]

I am trying to install samba on fedora9. I have encountered two rather large problems:

1. I can see all of the machines on the network and their shares, however, I cannot transfer any files. I get either "file is corrupt" or "bad file descriptor".

2. None of the remote machines can log on to the fedora 9 machine to see its shares. The users have been added as both a linux user and a smb user. The system tells them their passwords are incorrect.

These problems still occur when selinux and the firewall are turned off.

Thanks in advance for any help.

[djblack]

Ditto...what he said. I have not experienced the issue mentioned in his item #1, but item #2 is a definite issue for me. I went straight back to Fedora 8.

[djblack]

Seriously? Nobody else is having issues with Fedora9 as a Samba server?

[glennzo]

Problems come and go here. I have 5 computers in a mixed Linux / Windows XP environment. Sometimes I can network. Sometimes I can't. Samba is tempermental at best and certainly was more stable in F8. Oh well.

[djblack]

Perhaps I'll make another attempt. The only time I've tried using F9 and Samba, was the first 3 or 4 days following the F9 release...and it released with an unstable version of Samba. Maybe if I reinstall clean again, install all the updates (I hear they're plentiful already) and give it a go once again.

[glennzo]

Maybe you should. Most of the time I am able to do whatever I want to do in terms of networking. It's more like I just never know if it will work this time even though it did last time. Generally I can see all computers and connect to them. I can transfer files at will but then there's always the chance that something will go wrong. Right now I can't connect to the Fedora 9 laptop from one of the Fedora 8 desktops. What's up with that? Worked the other day....

Edit: Got to be fair. I see that the laptop's IP address has suddenly changed and I have them all hard coded in /etc/hosts. Maybe I shouldn't use the hosts file.

[bbfuller]

Hello glennzo

It's dependent on having the samba service set up and running on each of the Linux machines, but if you edit the file /etc/nsswitch.conf so that the line that reads:

hosts: files dns

reads

hosts: files wins dns

you should be able to use dhcp for ip addresses and address your machines by name rather than number. Works well here.

I've seen that "Hosts" line with more entries than that. If there are then "wins" should appear in the order immediately after "files".

Incidentally, talking about the firewall as "pfaris" was. That is a pain to get Samba through.

I usually select it as a service to be allowed through during installation but it never works even though it is shown in the list.

I find that if you allow Samba during installation, you need to open the Firewall configuration tool, click "Disable", click"Apply", click "Enable" and click "Apply" again before it works.

[glennzo]

Hello glennzo

It's dependent on having the samba service set up and running on each of the Linux machines, but if you edit the file /etc/nsswitch.conf so that the line that reads:

hosts: files dns

reads

hosts: files wins dns

you should be able to use dhcp for ip addresses and address your machines by name rather than number. Works well here.


I've seen that "Hosts" line with more entries than that. If there are then "wins" should appear in the order immediately after "files".

.Thanks for that bbfuller. I'll give it a shot right now on the three Fedora boxes. Samba is running on all of them and I'm using the hosts file on all of them also.