My environment is a Windows 2003 AD network where I run DHCP/DNS/WINS all on the DCs of the AD network. It's a small network and there are only 2 DCs running those services.
The problem is more of an annoyance and hasn't caused any problems yet.
On the Mac...
In Sharing Preferences the computer name was incorrect. I clicked edit, and gave it the name I wanted and it sticks after reboot.
In Network Preferences - advanced I went into the WINS Settings and entered the NetBIOS name the same as in the sharing preferences, this setting sticks also.
Both settings that I changed above were originally hostnames of other computers on the network, before I specified one, it would get a different hostname every time it would get a new IP address. After specifying for both, they stuck. The only problem now is that when I go into the terminal console, the prompt is another hostname on the network. I issue the hostname command and sure enough it's got the wrong hostname, it is a valid hostname on the network but that machine (laptop) is offsite, ie not connected. I can SU and change the hostname (hostname -s newhostname), and that sticks until I reboot, then it reverts.
I can ping from my windows machine the netbios name of the Mac and it replies properly. When I try to ping -a the IP of the Mac, it resolves to the incorrect hostname I see in the terminal prompt of the Mac.
Initial thoughts are that DHCP issues Wins Server info as part of the scope, and Wins might have this hostname still listed in its DB. I'm not sure though since I don't know much about Wins.
The Mac is not bound to the AD network at all; except for using the AD DHCP/DNS/Wins services.
Has anyone ever seen this behaviour before?