Windows 10: Not able to access the server using the command \\Server but able to access using the IP...

Hi;I am having a Windows Server 2003. This is connected to our domain controller which is on Windows server 2012 R2. I am not able to access the server using the command \\SERVERNAME but I am able to access the server using \\IPAddress.When I run the NSLOOKUP command the server name is resolved. I am able to ping to the server with the IP address as well as with the host name. This is really creating a major problem for me. Could any body please suggest me what should I do to resolve the issue.In the event log I am able to see the below errorEvent ID 30800 The client cannot resolve the

:)

 

computer is not able to access the Server

Communication over LAN: scenario: Computer A and Server B at same data network.

a. Suddenly the computer is not able to access the Server B.
What can be the root cause? and steps to solve it?

[moved from de-de]

 

Cannot access server 2003

The problem I am having is that no computer can access the server (with MS windows server 2003 installed) yet it can access all other computers.

By not being able to access it I mean that it cannot be pinged in command prompt. The funny part is, the server DOES come up in "Network" but when I go to double click it it comes up with the usual: "Windows cannot access *name*. Check the spelling of the name. Otherwise, there may be a problem with your network. To try and resolve....press Diagnose"

I have tried to connect via IP address with no results.

The server is running NO firewalls (not even Windows firewall, as it wouldnt even start). It can connect to the network (other computers) or internet with no problems at all.

Also, I have removed DNS/DHCP. The only two "servers" I have running are remote access and Print server.

 

computer is not able to access the Server

What did your System Admin say when you asked them about this?