Are you trying the fully qualified domain name as in server1.mydomain.com
and not just myserver? It could be a problem with suffixes but if you are
using the fully qualified domain name that is less likely a problem as those
suffixes would be appended to non fully qualified domain names. It would be
a good idea to try and configure it to use primary/parent suffixes instead.
Try nslookup as Bill mentioned and look in the domain zone of the domain
controller, that is the primary preferred dns server of the problem
computer, for the server name you are trying to access to see if there is a
host A record that exists with the correct IP address. Another thing to
check is the hosts file on the problem server to see if there is bad IP
mapping in it for the target server. The hosts file is in the
\%system%\system32\drivers\etc folder and can be opened with notepad.
Your netdiag looks good but you certainly seem to have a name resolution
problem for the target server since you can access it by IP address. My
guess is either their is not a correct record in the dns zone for the domain
for the target server [I believe you said they are in the same domain],
your dns server can not resolve the name, or there is an improper entry in
the hosts file on the problem server. To use nslookup, just enter nslookup
at the command line. If you get some error message, that may simply mean
that you are not using reverse dns zone and nslookup can not reverse resolve
your dns server's IP to a name. Anyhow the IP address of your dns server
would show then and you simply enter a name for it to resolve, either fully
qualified domain name or not. If it can resolve a fully qualified domain
name but not a flat computer name for the same computer, then you have a
problem with dns suffix appending. If it does resolve the computer name,
check that the IP address is correct. If it can not find a fully qualified
domain name then either that dns server is not authoritative for the domain,
can not find or contact the correct domain, or the host A record does not
exist.. --- Steve
"Lee Croucher" <Lee
(E-Mail Removed)> wrote in message
news:E6589187-087D-40FA-818A-(E-Mail Removed)...
> Steve,
>
> After running Netdiag the application passed all the tests with no errors
> and the problem seems to be with the FQDN not the IP address, if you
> connect
> with the IP address then everything works fine, however if you use a UNC
> name
> to connect to the server you get the original error message.
>
> So, to answer your question, if you use \\xxx.xxx.xxx.xx then the server
> will connect the share without any issues, however if you use
> \\<servername>
> then the error "There are currently no logon servers available to service
> the
> login request"
>
> I have also looked at the KB Article KB826902 but this refers to my
> problem
> from a domain controller and this computer is not a domain controller.
>
> Netdiag Output:
>
> ......................................
>
> Computer Name: TEST
> DNS Host Name: test.contoso.com
>
> Netcard queries test . . . . . . . : Passed
>
> Per interface results:
>
> Adapter : Local Area Connection
>
> Netcard queries test . . . : Passed
> AutoConfiguration results. : Passed
> Default gateway test . . . : Passed
> NetBT name test. . . . . . : Passed
> WINS service test. . . . . : Passed
>
>
> Global results:
>
>
> Domain membership test . . . . . . : Passed
> NetBT transports test. . . . . . . : Passed
> Autonet address test . . . . . . . : Passed
> IP loopback ping test. . . . . . . : Passed
> Default gateway test . . . . . . . : Passed
> NetBT name test. . . . . . . . . . : Passed
> Winsock test . . . . . . . . . . . : Passed
> DNS test . . . . . . . . . . . . . : Passed
> Redir and Browser test . . . . . . : Passed
> DC discovery test. . . . . . . . . : Passed
> DC list test . . . . . . . . . . . : Passed
> Trust relationship test. . . . . . : Passed
> Kerberos test. . . . . . . . . . . : Passed
> LDAP test. . . . . . . . . . . . . : Passed
> Bindings test. . . . . . . . . . . : Passed
> Modem diagnostics test . . . . . . : Passed
> IP Security test . . . . . . . . . : Passed
> ......................................
>
> Could the problem be with the DNS entries set to append these DNS
> suffixes,
> instead of Append primary and connection specific DNS suffixes??
>
> May thanks in advance,
>
> Lee Croucher