When browse the network NUVNETNAS is the first thing to come up actually, so the server's responding pretty quickly. There is no login prompt for this particular share. However, when I was trying to set up a network share I got a similar error message. My samba account is not similar to my windows account though (user is nasuser :/). When I did have authentication, I had made sure to smbpasswd -a the nasuser.

TO REITERATE THOUGH:
This is just a bare public share and should work as a read-only share that does not require authentication. I am not prompted for a login when I access it but get the error after about 15/20 seconds :/.

Your original post seems to indicate that the link is trying to take you to a non-existant location "NAS_PUBLIC".
What happens if you create user "NAS_PUBLIC" so that there is a folder /home/NAS_PUBLIC to go to?

Sorry I tend to Check things like this rather than assume my configuration is perfect.. It's not troubleshooting if you don't verify.

Just because you can go out through a firewall does not mean you can initiate a connection outside and come back through.

best of luck, I hope your assumptions are correct.

Do you have a Windows XP machine you can try? There are significant differences in networking configurations in Vista.

Unfortunately no all my machines are either running Vista or Windows 7 at this point in time.

P.S. Thanks for all the suggestions everyone's been sending btw.

Could be how windows is responding to auth requests..

3 - "Send NTLMv2 response only"
1 - "Send LM & NTLM - use NTLMv2 session security if negotiated"


Windows Registry

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa "LmCompatibilityLevel"

if that value is set to 3, change it to a 1 and try to connect again.

Have already done that :/ and as I mentioned prior I have a linux-laptop with shares that I can access without issue. I'm 99.9% certain this is a fedora/samba issue at this point. Is there any windows logs I could access that could help me figure out what error specifically caused this issue? The event viewer doesn't seem to log this issue :/.

I'd take a punt on an SELinux issue. Try disabling it temporarily with "setenforce =0" and see if it works. If that fixes the problem, read
follow the instructions and re-enable SELinux with "etenforce 1". These are CentOS5 instructions, but should be good for F10

As for logs, check /var/log/audit/audit.log

In global I have
guest ok = yes

I'm not sure if this would make a difference.

as a stanza, I have

[Samba]
comment = Samba Test Share
path = /tmp/Samba/
browsable = yes
writable = yes
guest ok = yes

I noticed my "guest ok = yes" is different than your "guest only = yes".

If you're worried about SElinux, you could just set it to permissive with the command
# setenforce permissive

Otherwise, there are 4 directives associated with samba.

allow_smb_anon_write
samba_enable_home_dirs
samba_share_nfs
use_samba_home_dirs

I would just disable SElinux for now to remove that as a variable. But you can always setseboot -P <name> 1

Try connecting to your server with ip address instead of hostname. Also, try to create and share a directory in /tmp instead of /home.

Any luck?
What was the solution?

Sorry about the late update (just got around to trying SELinux stuff today. All of the issues I was running into were due to SELinux Policies that weren't checked off. Also I needed to set the guest user on the system to nasuser which had ownership permissions on the files). Thanks for the help everyone!