Hi, From your description, I assume that you try to access domain network share but prompt a credential for username/password. If so, please let us know which type of user account you used to access the share. Is a domain user or local account user? Meanwhile, please make sure the current user has proper rights for the share folder. Generally, if the client PC joined domain and logged on with a domain account, it does not need to pass additional credentials to the server to access resources. In addition, when using a local account to access domain resources, you will be prompted to enter the user credential for the domain. It is recommended to use domain user to access the domain resources. Hope if it helps, if you have any update or concern, please feel free to let us know. Best Regards, Aiden

I don''t know which forum is appropriate for this question so I will give it a try here. When I authenticate to a Window server with its netbios name successfully,e.g. map drive with \\server\share, the Windows client (whether it is XP or win7) doesn't seem to be able recoginze its FQDN, server.abc.com. So when I map drive with \\server.abc.com\share, it will prompt me for user name and password again, as if it is a different server. I have tested this on W2K8 and W2K3 servers and they all behave the same. Is this normal behavor? If so, is there anyway to aviod this "double" authentication? Thanks

Yes, I am trying to access network share from a domain server and the account being used is domain user account. The user has access to the file. The PC is joined to the domain but there are instances users need to logon locally to their machine and access the network file that way. The thing that puzzled me is that once the user authenticate to the resource, \\server\share, with their domain account, they are still prompted for credential again for the same resource but with the different name \\server.abc.com\share. This happened the other way around too, \\server.abc.com\share then \\server\share.

Well, I am not sure if this is name resolution issue. If it is that, then the OS will not even prompt me for credentials, it will just say server not found or something like that. In fact, I try this with different OS clients (XP and Win7) and they behaved the same.

1. Instead of "authentication" we use term name resolution 2. Nebios over TCP/IP, hostname, ... are resolution mechanisms for netbios name resolution only. They resolve simple name like ITHACA 3. DNS name resolution gives FQDN (fully qualified domain name) that is name with domain suffix eg. ITHACA.ATHENS.GR 4. To view computer on network you use ports from the range 137-139 (I am not goiung into details) but for sharing it suffice to use port 445. DNS record interchange with other DNSs need port 53 opened. Regards Milos PS: There are nice TCP/IP guide available for download not only on the MS sites.

Hi, Thanks for the update. For these users who are logon locally, by default, the domain server will need to authentication the credential when we use the NetBIOS, FQDN or IP address to access the domain share. Even we have input the domain user/password for \\server to access the share, if we try to use \\serverFQDN or \\IPaddress, we will facing the credential again. This is by design, because DC cannot recognize these access requests, we need to provide the domain user information again. Your understanding is highly appreciated. Best Regards, Aiden