Hi, I am new user of FC4. I had similar problem in my LAN too.
have you checked if your linux hostname is configured properly? SAMBA, SElinux conbination seems to manipulte the hostname or somentihg like that. (I am novice user :-) )
In my case I found out that my hostname set during the installation of FC4 was somehow manipulated when I tried to use samba and selinux. I had to manually set my linux hostname (I used GUI tool) and its everything is working.
because of this hostname thing even my httpd was not working properly.
my problem before was when samba is running, windows clients can locate the machine and browsers can locate served page but when samba is stopped, everything stops also.
I have no idea where the problem lies but its ok now.
--- Stephen Walton stephen.walton@csun.edu wrote:
Daniel J Walsh wrote:
Stephen Walton wrote:
smbclient //machine/swalton
still throws a NT_STATUS_BAD_NETWORK_NAME error
when I try to connect
to my home directory with SELinux set to
"enforcing", and the error
message in the smb log file reads
'/home/swalton' does not exist or is not a
directory, when connecting
to [swalton]
Are you seeing AVC messages in /var/log/messages
or
/var/log/audit/audit.log?
No, but perhaps I need a log level tweaked higher somewhere. It is 100% reliably true that if I use system-config-securitylevel to set SELinux enforcing to off, smbclient works fine, and if I reset SELinux back to enforcing I see the above error messages again. So SELinux is definitely the culprit here somehow.
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
________ ___ __ _____ _____ __ / / /_ _ _ _ \ _ /_/ / / __// __/ /_____/ ___/ ___/
Send instant messages to your online friends http://uk.messenger.yahoo.com