CIFS asks password on host name

[Snufkin]

I have setup CIFS and attempted to configured it so that it doesn't prompt for a password. I want anyone to be able access the shares.

So if I now go and enter \\192.168.10.222 in Windows it works. No password prompt comes up.

If I go and use the host name \\nas it prompts me for a password. Entering guest and no password works , but I don't want to enter anything.

How can I fix this ?

 

[Snufkin]

Some extra info : I have logged the computer into a Windows Domain and the DNS server as an entry for the host name pointing to the IP.

 

[Mirfster]

When you tried this, was it all within the same session? If so, clear your connections and then try just the \\nas

Windows Command: Net Use /Delete *

Also, what happens if you do a nslookup of "nas" (Windows Command: NsLookup NAS)

 

[Snufkin]

I've tried it from more than one computer and I get the same results (Windows 8.1 and Windows 10)

If I do nslookup nas it cannot find it. But if I do nslookup nas.domainname.com it finds it and returns the correct address together with the address of my DNS server.

if however I go \\nas.domainname.com it also prompts me for a password where as the ip doesn't.

 

[Snufkin]

DNS request timed out.
timeout was 2 seconds.
Server: Unknown
Address: 192.168.10.2

Name: nas.domainname.com
Address: 192.168.10.222

 

[Mirfster]

So on your computers, what do you have for "Primary DNS Suffix" or "DNS Suffix Search List"?

 

[Snufkin]

Well ... I suppose it is the defaults : "Append primary and connection specific dns suffixes" and then "append parent suffixes of the primary DNS suffix"

I can ping nas or nas.domainname.com without problems . Just not sure why its keeps asking for a password on the hostname but not on the ip. What is your thinking here? Also computers not on the domain should be able to access the shares without authenticating when using either hostname or ip.

 

[Mirfster]

I am wondering if the clients are considering the share as "Public" or "Private". So, in the systems [Network and Sharing Center]; does it show your network connection as "Private" or "Public". Curious if it is treating the IP differently as opposed to the Name due to have the clients are seeing the network.

 

[Snufkin]

It's seeing it as private.

 

[Snufkin]

Update : Computers logged onto the Windows AD domain ( same domain nas is on) Connects with the hostname or FQDN without prompting for a password. Computers which are not in the domain prompt for a login.

 

[Nick2253]

Did you ever get this resolved? I just started getting this behavior on my FreeNAS, except I'm unable to connect via hostname or FQDN from my domain joined machines. My non-joined machines can connect via FQDN or hostname just fine. I'm able to connect via IP on all of my computers.