We have a client with a 2003 R2 box that was working perfectly up until 2 weeks ago. One of the software vendors was trying to update the software on the box and then it had no internet connection. Couldn't ping the gateway, couldn't ping printers, couldn't even ping itself. No internet, no file sharing, nothing.
A bit of background on the box;
This box is not a DC, just a member terminal server. It runs sage, and a few other programs mostly for the mac users and for remote users to have access to the databases in the office.
The vendor have no idea what "happened" They thought it was a power surge. 2 new NIC cards later the we still had the same issue. I have thrown all my networking-fu at it and while we can now ping and access file shares, we still have no internet from the box.
It is a DNS resolution issue.
As such, the RPC server complains if you try to create a terminal session. So the box is still down because users cant remotely connect to it. I would like your help in fixing it.
I can restore from a backup, but I don't want to undo any progress the vendor made in setting up new said program. The client have given us some latitude and they are not rushing it (especially since it isn't our fault). I have until the end of the month to either fix / reload from backup / reinstall / etc.
nslookup from the box gives responses. For yahoo or google's multiple servers. You cant ping by name (DNS issue) but you can by ip. You can browse the net by IP, if you can find a site that still allows it.
Tracert will show you the hops and latency, but will not give you the dns names of each hop. So where you normally have the hop then the dns name, the right side of the screen is blank.
We have done all the normal stuff, reset dns, flush ip, flush, cache, netsh reset, restart dns client, rebuild winsosk, replace wsock32.dll and winsosk.dll. We ran a virus scan, tdss, hitman, sas, etc. The windows firewall is enabled but off. Even with it disabled it still doesnt work.
The dns servers for the adapter are pointed to the PDC. If we switch the gateway or dns servers we get the same issue. It isnt an external thing, something is going on with the box itself.
Any suggestions?