kuntz,
This one stumped me for a while.
It wasn’t a problem under RHL9, but network services under Fedora always gave me the same error message.
First, try turning off your firewall and see if network services starts working (i.e., redhat > system settings > server settings >services, scroll down the list to ipchains (probably not running), iptables and ip6tables (if it's present), point to it/them if the box is checked, right click and select “stop”). As a rule of thumb, when something network-related doesn’t seem to be working, turn off the firewall and try it again (and that goes for the firewalls on both ends of the connection).
If network services works with the firewall off and if you are on a network with a master browser on another system, you may just be blocking the connection and will need to add a couple of lines to /etc/sysconfig/iptables to allow the connection.
But I’ll bet that there is no master browser on your network, because the exact same thing happened to me. When I modified etc/sysconfig/iptables to allow all tcp and udp communications to all ports on the local IP address and on the 127.0.0.1 loopback, network services stated working again. It’s an overkill, but it works.
I really don’t understand why the system is trying to protect itself from itself.
When you have time, look through /etc/samba/smb.conf.
It contains a short list of what Samba can do for you. It can be a lot more than a M$ windows file server.
Regarding Fedora functionality, I tend to like it, and it’s worth every penny I paid for it.