We help IT Professionals succeed at work.

Server 2008 R2 - Can Connect to Server By IP, but not computer name

I am having an issue with a Server 2008 R2 terminal server. Our domain controller is a 2003 Small business server. I can get to my domain controller by IP, but not by computer name. One of the fixes I found online was to disable Netbois over TCP/IP, but that just gives me a different error message. When I have Netbois set as default I get:

Error Code: 0x80070035
The network Path was not found

When i have it disabled I get:

\\Servername
A device attached to the system is not functioning.

I can reboot the server and it will temporaily fix it, but it's only for a day or so. I have tried many things that people attribute for this and have only gotten it to work for a few weeks before it would come back up.  Things that I have tried so far include getting rid of symantec corporate totally and disabling IPv6 totally. These would seem to fix it only to have it come up again. Any help is greatly appreciated.
Comment
Watch Question

Top Expert 2005

Commented:
It's a resolution problem.  The server isn't registered in DNS properly or your workstation isn't using your DNS server.Anything inside your network needs to use your own DNS server - never put an external DNS IP address on any of your NICs.  Rely on either root hints from your DNS server or setup a Forwarder to your ISP for queries outside your network.

Commented:
DNS. As Netman66 stated. Verify that your client's are pointed to your internal DNS server. Also, verify that all records are present and correct for your servers. If you run nslookup <Servername> What output do you get?
Top Expert 2012

Commented:
Enable TCP\IP over Netbios.

Make sure like netman said you should be only pointing to internal DNS servers.

Top Expert 2012

Commented:
Make sure you have not disable the Firewall service either.

Author

Commented:
I have the correct DNS server listed when I do an nslookup and it the DNS server listed on the NIC. The windows firewall services is turned on, but windows firewall is disabled. With Enable Netbois over TCP/IP I get the same result as the default setting of the network path was not found.
Top Expert 2012

Commented:
Did you run the Symantec removal tool?

http://service1.symantec.com/support/tsgeninfo.nsf/docid/2005033108162039

Is it Symantec Endpoint? If is download cleanwipe tool.

Author

Commented:
I didn't but symantec corporate is not removed using the removal tool. The removal tool is for their home products only. Symantec has been uninstalled off this server for a month with no issues and it came back so I don't think its related to Symantec.
Top Expert 2012

Commented:
Take a look at the below link which will give you a removal tool.

http://www.technibble.com/repair-tool-of-the-week-norton-removal-tool/


Make sure you have the most updated drivers and firmware installed
Top Expert 2012

Commented:
Top Expert 2005

Commented:
I don't think this has anything to do with Symantec - it's gone.

This is purely a DNS issue.

Author

Commented:
dariusg - That is the Norton removal tool for their home anti-virus products and does not remove symantec corporate. This has  been completely uninstalled and was working for weeks with no issues. Now it is happening every other day so I'm 99.9% sure it has nothing to do with symantec.

Netman- The DNS looks correct to me. Our DNS is ran on our small business server and that is what the terminal server is pointing to. Is there anything you'd like me to try and post results for?
Top Expert 2012

Commented:
Did you read the second link that I posted? What I'm telling you is that I have been in the same situation you have been weeks of working network after removing Symantec then out of no where started to have issues.
Top Expert 2005

Commented:
Please post (and scrub) the output of the following commands:

dcdiag /v > C:\dcdiag.txt

and

netdiag /v > C:\netdiag.txt

Top Expert 2005

Commented:
Try this first:

dnscmd /Config /EnableEDnsProbes 0

Author

Commented:
None of the commands worked. Dcdiag is built into server 08, but only if it's a domain controller. The terminal server is not a domain controller. Netdiag apparently isn't in server 08? dnscmd also did not work. The terminal server is not a DNS server.
Top Expert 2005

Commented:
Run them on the DC.  You may need to install the Support Tools.

Author

Commented:
I ran all these commands on the domain controller. The only thing is I had to set a script for the server to reboot before the days work so they could get into the drives. Now that I have done this I will remove the script for rebooting and check in and see if it happens over the weekend.
netdiag.txt
dcdiag.txt
Top Expert 2005
Commented:
Two errors - the first in DCDIAG, the second in NetDiag.

Run a Net Start IsmServ to start this service.  Check and make sure it's set to Automatic (Intersite Messaging Service).

* Checking Service: IsmServ

        IsmServ Service is stopped on [UNLANDSERVER]

Next error relates to WINS - there's an entry on the server's nic for it, but it isn't responding.  Remove the entry or fix WINS.

Testing the WINS server

        Server Local Area Connection

            Sending name query to primary WINS server 192.168.1.230 - Failed

            There is no secondary WINS server defined for this adapter.

Lastly, it appears this entire forest was once Windows 2000 - is this correct?  If so, then I need a screenshot of your DNS Forward Lookup top level zones.  I have a feeling we need to fix the _msdcs zone.

Advise.

Author

Commented:
I've been working with Microsoft on this issue. Netman got me on the right track. I am still worried it's going to come back so I can't say for sure I have the absolute solution.