<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
<tt>Michael Brown wrote:</tt>
<blockquote type="cite" cite="mid:201003202013.59733.mbrown@fensystems.co.uk">
<title>Re: [gPXE] sanbootconf hostname setting</title>
<!-- Converted from text/plain format -->
<p><tt><font size="2">...However, I think it<br>
would be useful if sanbootconf could store the hostname *somewhere* in
the<br>
registry; this would allow a user who wants auto-renaming machines to<br>
implement it without requiring specific knowledge of the iBFT.<br>
</font></tt></p>
</blockquote>
<tt><br>
Agreed. A good place might be in sanbootconf's registry key,
Parameters\ subkey.<br>
<br>
</tt>
<blockquote type="cite" cite="mid:201003202013.59733.mbrown@fensystems.co.uk">
<p><tt><font size="2">...Do you know if Windows separates the
concepts of "computer name" and "TCP/IP<br>
hostname"?</font></tt></p>
</blockquote>
<tt><br>
The TCP/IP hostname is what you see in a few areas:<br>
- 'ipconfig /all'<br>
- My Computer -> Properties -> Computer Name tab<br>
<br>
When manually hacking the TCP/IP hostname, you might see the following
error event in the Event Viewer's System Event Log:<br>
<br>
-----<br>
Attempt to update DNS Host Name of the computer object in Active
Directory failed. The updated value was 'foo.xxx.yyy.net'. The
following error occurred: <br>
The parameter is incorrect. <br>
<br>
For more information, see Help and Support Center at
<a href="http://go.microsoft.com/fwlink/events.asp" class="moz-txt-link-freetext">http://go.microsoft.com/fwlink/events.asp</a>.<br>
-----<br>
<br>
However, the hostname does indeed get registered with DNS if the
corresponding check-mark is set for the network adapter. An
*.in-addr.arpa 'dig' confirms the reverse-lookup registration, as the
previous hostname DNS registration appears to be removed.<br>
<br>
The computer's SYSTEM account still appears to have access to domain
network resources (such as shares) with the TCP/IP hostname hacked, but
the AD computer account's name is not changed, possibly due to the
error mentioned above. I wouldn't think that's really a Good Thing.<br>
<br>
There's also the whole NetBIOS name business... :S<br>
<br>
</tt>
<blockquote type="cite" cite="mid:201003202013.59733.mbrown@fensystems.co.uk">
<p><tt><font size="2">...As a related question, when Windows uses
DHCP, does it honour DHCP option 12<br>
in any way?</font></tt></p>
</blockquote>
<tt><br>
A look at HKLM\SYSTEM\CCS\Services\Dhcp\Parameters\Options\ suggests
that Windows does not use DHCP option 12 ("hostname") at all. In
there, we find the options that the DHCP client service makes a note of
in the Tcpip service's Parameters\ key. A look around here[1] and
here[2] seem to confirm that.<br>
<br>
- Shao Miller<br>
<br>
[1] <a href="http://support.microsoft.com/kb/121005" class="moz-txt-link-freetext">http://support.microsoft.com/kb/121005</a><br>
[2] <a href="http://technet.microsoft.com/en-us/library/cc958941.aspx" class="moz-txt-link-freetext">http://technet.microsoft.com/en-us/library/cc958941.aspx</a><br>
</tt>
</body>
</html>