gethostname() Must Support Alternate Computer Names

Article translations Article translations
Article ID: 183832 - View products that this article applies to.
This article was previously published under Q183832
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

SYMPTOMS

When you use the gethostname function in Windows NT, it does not support the ability to use alternate computer names for the computer.

CAUSE

The gethostname function returns the node name instead of the cluster name in the network name resource.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack

STATUS

Microsoft has confirmed this to be a problem in Windows NT Server, Enterprise Edition version 4.0. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.

MORE INFORMATION

The change that was made in GetComputerName to support alternate computer names has been added to gethostname. GetComputerName checks an environment variable. If that variable exists, GetComputerName returns its value instead of the real computer name. The change was made to keep applications from breaking in a cluster.

Properties

Article ID: 183832 - Last Review: February 21, 2014 - Revision: 3.3
APPLIES TO
  • Microsoft Windows NT Server 4.0, Terminal Server Edition
  • Microsoft Windows NT Server 4.0 Enterprise Edition
  • Microsoft Cluster Server 1.1
Keywords: 
kbnosurvey kbarchive kbhotfixserver kbqfe kbfix kbprb KB183832

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com