Don't change it back to localhost.localdomain. That is just wrong. What did "hostname" return. Might as well use that. Fedora Core has the hostname set in /etc/sysconfig/network. "HOSTNAME = <yourhostname>". The part before the dot (.) is used as the hostname. Your original hostname (tt0.uuart.com) has a hostname part (tt0) and a domain name part (uuart.com). Where did the uuart.com come from? If you just made it up, maybe drop the .com because "uuart.com" isn't an internet domain. ( As I stated before, uuart.com isn't the "domainname" because "domainname" returns the NIS domain, and since you aren't using NIS you don't have one.)
I have FC6 on an old (Pentium III) dell laptop. Here are my /etc/sysconfig/network's HOSTNAME & /etc/networks files:
HOSTNAME = delllap.jesnet
jschiwal@lmac:~> cat /etc/networks
# networks This file describes a number of netname-to-address
# mappings for the TCP/IP subsystem. It is mostly
# used at boot time, when no name servers are running.
For entries in /etc/nss_switch there will be a cooresponding library file needed. For example if you have a dns entry make sure there is a libnss_dns library installed. It will probably be from a package by the same name.
If you have an "avahi" (zero config) daemon running, then install the "libnss_mdns4_minimal" and "libnss_dns" libraries and use:
hosts: files mdns4_minimal [NOTFOUND=return] dns
This may have more to do with having hosts show up in Linux however.
The "libnss_winbind" corresponds with a winbind entry in nsswitch.conf and libnss_wins with a wins entry.
If you used "wins support = Yes" in your smb.conf, make sure that both the smbd and nmbd daemons are running. If you have users in windows who aren't Linux users, running the winbind daemon may help aleviate the need to map bad users to guest for public shares.
Also use nmap or another port scanner on another computer and determine if ports 139 & 445 are open.
Also run the "firewall & security" config. There is a tab for selinux. Look under samba and see what it says. Billymayday's tip is to disable selinux completely temporarily as a troubleshooting technique. I think you need to reboot after using the "setenforce" command.
Also look in the "Samba 3 HOWTO & Reference" document. I think there is a troubleshooting section that deals with browsing.
Another thing to consider is to set up samba using swat.
A) edit /etc/xinet.d/swat. Edit the "disable = yes" line to "disable = no" line.
B) if xinetd is running, restart it with "sudo killall xinetd"
C) if xinetd is not running start it with "sudo /sbin/service xinetd start" or "sudo /sbin/chkconfig xinetd on"
D) Point your web browser to "http://localhost:901"
The html version of the books I mentioned will be available on the bottom of the intro page.
Also make sure that none of the windows clients have an unused protocol installed such as IPX support. This will cause that host to always be elected as the master browser. If that host has a problem then browsing might not work well.
You might as well post your /etc/samba/smb.conf file. Maybe someone will notice something there.
Start with giving this host a normal hostname and rebooting. Then see if browsing on the Windows hosts starts working.