I have a Server 2008 R2 SP1 machine with a local SQL Server 2008 R2 installation. After changing the computer name I am getting a constant broadcast of name queries for the old computer name from this machine only. I have flushed the dns cache, arp cache, active directory, host files on every machine in the network. I can get the broadcasts to stop by pointing the old name to loopback in the hosts file but I want to fix whatever is causing it as I believe it is also causing issues remotely logging in to the SQL Server with Windows credentials. Any direction would be appreciated. Thanks.

After changing the computer name I am getting a constant broadcast of name queries for the old computer name from this machine only. . The machine you renamed is sending broadcasts for its own "old" name? No other machines seem to be seeking the "old" name? this sounds like you have a product installed, or a configuration implemented, on itself, which still needs to be renamed.Don

That's what I thought. The only thing installed is SQL Server 2008 R2 and I already changed the server name there. I also did a find and replace in the registry and replaced all instances of the old computer name with the new one.

That's what I thought. The only thing installed is SQL Server 2008 R2 and I already changed the server name there. I also did a find and replace in the registry and replaced all instances of the old computer name with the new one. Did you reboot after doing this? That would be required if you have hacking the registry this way. I assume you followed some MS KB article for renaming a SQL server? I also agree with Don, its most likely something installed/configured to still use the old name. The registry is the only place configuration is stored. Look for 3rd, party services, scheduled tasks, COM configurations, etc. Its in there some where, you just have to find it. If you can't find it, your options are few, mostly re-install everything from scratch, starting with the Windows OS, do you workaround (or any other) as a permanent solution, or put in the oldname as an Optional Name into the LanmanServer config. http://social.technet.microsoft.com/Forums/en-US/winserverNIS/thread/e6a5f937-d51b-43c8-b94f-7f24c100b935