Could you provide us with a network trace?

Thanks,

Natalie

Tim wrote:
Windows client is the domain server itself.

Forward and reverse dns lookups resolve properly, and I can ping via the fqdn or IP.

--Tim



On Tue, Nov 18, 2008 at 7:40 PM, Natalie Li <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:

    When you said DNS is all functioning, can I interpret it as both
    the A and PTR RRs of the Solaris system have been added to the
    DNS?  If so, you might want to check the DNS configuration of your
    Windows client to see if it points to the right DNS server.

    Were you able to ping fileserver.domain.com
    <http://fileserver.domain.com> from your Windows client?

    Natalie

    Tim Cook wrote:

        So I've setup the native cifs server to authenticate against
        my AD server at home.  The odd part is, when I now go to map a
        share from a windows system if I use the fqdn of the solaris
        system, it fails, but if I use the IP address, it works.

        IE:

        \\filserver.domain.com <http://filserver.domain.com>\share - fails
        \\10.10.10.10 <http://10.10.10.10>\share - works

        Thoughts?  The dns is all functioning both forward and reverse.



_______________________________________________
cifs-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/cifs-discuss

Reply via email to