WinNT 4.0 DNS Only Binds to a Maximum of 15 IP Addresses

• Microsoft Windows NT Server version 4.0

SYMPTOMS

A Windows NT 4.0 Domain Name Service (DNS) server fails to respond to name queries when there are more than 15 IP addresses bound to the Microsoft DNS service.

CAUSE

The DNS server has a hard-coded limit so that it can only bind to 15 IP addresses.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Windows NT version 4.0. This problem was corrected in the latest Microsoft Windows NT 4.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K

MORE INFORMATION

Windows NT 4.0 Service Pack 2 and later no longer includes a hard-coded limit. The limit was in place originally because the DNS server opens a socket for every IP address it binds to, consuming resources. There is a significant memory expense to each one. Customers should be encouraged to use the minimum necessary bindings for best performance. <<BULK-DELIM>>> <<<CONTENTNUM>>> 162850 <<<CONTENTTYPEID>>> 1 <<<TITLE>>> KiXtart Environment Variables Do Not Exist After Script Runs <<<LONGTITLE>>> KiXtart Environment Variables Do Not Exist After Script Runs <<<PRODUCT>>> crossnet <<<PRIORITY>>> <<<SECURITY>>> PUBLIC <<<AUTHOR>>> clifton <<<EDITOR>>> kimberwe <<<EDITSTATUS>>> Released <<<TECH>>> <<<TECHSTATUS>>> Approved <<<EXPIREDATE>>> Dec 31 1999 12:00AM <<<MESSAGE>>> <<<KEYWORD>>> nt16ap nt32ap ntdomain ntdosap NTSrv <<<INTERNALADMIN>>> Win95 CheckKeyword <<<QUESTION>>> <<<PRODVERNUM>>> WinNT:4.0;Windows:95 <<<COMPONENT>>> <<<TECHNOLOGY>>> <<<LINKS>>> 162793 <<<RAIDINFO>>> <<<INCIDENT>>> <<<SWEEPDATE>>> <<<SWEEPSTATUS>>> <<<SOLUTIONTYPE>>> <<<ISSUETYPE>>> kbprb <<<PLATFORM>>> winnt <<<HARDWARE>>> x86 <<<BOILERPLATE>>> <<<PRODUCEDVIEW>>> <<<TEXT>>> The information in this article applies to:

• Microsoft Windows NT Server version 4.0
• Microsoft Windows 95

SYMPTOMS

Environment variables set up through your KiXtart Script do not exist when the script terminates. When you run a KiXtart logon script with a Windows 95 client, environment variables appear to work properly.

CAUSE

The SET command in Windows 95 is only active during the same MS-DOS session. When the current session is closed, the variable is no longer in memory.

NOTE: This is different behavior from a Windows NT client.

RESOLUTION

To use environment variables outside the logon script, use Winset.exe from the Windows 95 compact disc to set global environment variables. See the following article in the Microsoft Knowledge Base for an example of how to use Winset.exe:

   ARTICLE-ID: Q162793
   TITLE     : How to Setup KiXtart Logon Scripts on a Windows 95 Client

MORE INFORMATION

The following excerpt is from the KiXtart documentation:

   Only programs that specifically support this feature (such as ProgMan
   and TaskMan) will have their environment updated. When in doubt about
   a particular program, please ask the supplier of the program whether
   or not his program supports the 'WM_WININICHANGE' message for changes
   to the environment.

Keywords          : kbbug4.00 kbfix4.00.sp2 NTPROTOCOL nttcp kbnetwork
Version           : WinNT:4.0
Platform          : winnt
Issue type        : kbbug
Solution Type     : kbfix