I have a machine, Server 2003 Domain Controller, that has network shares on it.XP Pro SP3 machines trying to acess those shares are having some weird issues.When browsing to \\servername\, I get a blank page within Windows Explorer with '0 Objects' listed.When browsing to \\serverIP\, it works properly.When browsing to \\servername.domain-name.local\, it works properly.

Hi Arhineus7,Thank you for posting in windows forums,"When browsing to \\servername\, I get a blank page within Windows Explorer with '0 Objects' listed" , does it open explorer on the target server ??can you please check this behavior on other xp machines and also you can share a folder on xp client and try browing that share folder from another xp client.Have you configured WINS in your setup ??can you please let us know what have you set under " WINS "tab under your network adapter?

Hello arhineus7, From the description, it seems this could be an name resolution issue. We may need to collect some information: 1. Is this Windows XP SP3 a domain client in the Windows Server 2003 domain or is it a workgroup mode computer? 2. If it is a domain client, do you have set Primary DNS suffix as its domain name on the Windows XP client? If you have not set the Primary DNS suffix, please set it up with its domain-name.local in the property. 3. Do you have set the NIC on the client to point it to a DNS server in the domain? I suggest you follow the step in the document to modify the resolution for unqualified DNS names. How to Configure Windows XP TCP/IP to Use DNS http://www.microsoft.com/windowsxp/using/networking/expert/tcpipdns.mspx To modify the resolution behavior for unqualified DNS names 1. To resolve an unqualified name by appending the primary DNS suffix and the DNS suffix of each connection (if configured), click Append primary and connection specific DNS suffixes. If you also want to search the parent suffixes of the primary DNS suffix up to the second-level domain, click to select the Append parent suffixes of the primary DNS suffix check box. 2. To resolve an unqualified name by appending the suffixes from a list of configured suffixes, click Append these DNS suffixes (in order), and then click Add to add suffixes to the list. 3. To configure a connection-specific DNS suffix, type the DNS suffix in DNS suffix for this connection. Append parent suffixes of the primary DNS suffix: this property in the NIC card performs the name resolution which is the best possible solution for your issue. eg: your primary DNS suffix is domain-name.local when you query servername, the DNS resolver queries in this order if you have enabled the options.servername.domain-name.localservernamePlease let us know if this helped.This posting is provided "AS IS" with no warranties, and confers no rights.

Hi,Did you had a chance to go through the suggestions, please take some time to update us the findings.