DHCP, DNS WITH DOS 6.22
Mauricio Toro
I'm TARZAN :)
I have DOS 6.22 with Client Microsoft for DOS 3.0, and need to work with DHCP and DNS for a TCP/IP connection, I can't to set the TCP/IP protocol for a connection for domain, only i can see the other host for youre IP ADDRESS and not for the DOMAIN .
Could you Help me please.
-- R. Mauricio Toro O. mailto:mt...@abello.dic.uchile.cl
Megabrain
you may need to cache the netbios name and
IP address for the domain in the lmhosts file with
the #pre setting in lmhosts.
# Copyright (c) 1993-1995 Microsoft Corp.
#
# This is a sample LMHOSTS file used by the Microsoft TCP/IP for Windows
# NT.
#
# This file contains the mappings of IP addresses to NT computernames
# (NetBIOS) names. Each entry should be kept on an individual line.
# The IP address should be placed in the first column followed by the
# corresponding computername. The address and the comptername
# should be separated by at least one space or tab. The "#" character
# is generally used to denote the start of a comment (see the exceptions
# below).
#
# This file is compatible with Microsoft LAN Manager 2.x TCP/IP lmhosts
# files and offers the following extensions:
#
# #PRE
# #DOM:<domain>
# #INCLUDE <filename>
# #BEGIN_ALTERNATE
# #END_ALTERNATE
# \0xnn (non-printing character support)
#
# Following any entry in the file with the characters "#PRE" will cause
# the entry to be preloaded into the name cache. By default, entries are
# not preloaded, but are parsed only after dynamic name resolution
fails.
#
# Following an entry with the "#DOM:<domain>" tag will associate the
# entry with the domain specified by <domain>. This affects how the
# browser and logon services behave in TCP/IP environments. To preload
# the host name associated with #DOM entry, it is necessary to also add
a
# #PRE to the line. The <domainis always preloaded although it will not
# be shown when the name cache is viewed.
#
# Specifying "#INCLUDE <filename>" will force the RFC NetBIOS (NBT)
# software to seek the specified <filenameand parse it as if it were
# local. <filenameis generally a UNC-based name, allowing a
# centralized lmhosts file to be maintained on a server.
# It is ALWAYS necessary to provide a mapping for the IP address of the
# server prior to the #INCLUDE. This mapping must use the #PRE
directive.
# In addtion the share "public" in the example below must be in the
# LanManServer list of "NullSessionShares" in order for client machines
to
# be able to read the lmhosts file successfully. This key is under
#
\machine\system\currentcontrolset\services\lanmanserver\parameters\nullsessionshares
# in the registry. Simply add "public" to the list found there.
#
# The #BEGIN_ and #END_ALTERNATE keywords allow multiple #INCLUDE
# statements to be grouped together. Any single successful include
# will cause the group to succeed.
#
# Finally, non-printing characters can be embedded in mappings by
# first surrounding the NetBIOS name in quotations, then using the
# \0xnn notation to specify a hex value for a non-printing character.
#
# The following example illustrates all of these extensions:
#
# 102.54.94.97 rhino #PRE #DOM:networking #net group's DC
# 102.54.94.102 "appname \0x14" #special app
server
# 102.54.94.123 popular #PRE #source server
# 102.54.94.117 localsrv #PRE #needed for the
include
#
#
128.135.220.13 lpd #PRE
#
#
# #BEGIN_ALTERNATE
# #INCLUDE \\localsrv\public\lmhosts
# #INCLUDE \\rhino\public\lmhosts
# #END_ALTERNATE
#
# In the above example, the "appname" server contains a special
# character in its name, the "popular" and "localsrv" server names are
# preloaded, and the "rhino" server name is specified so it can be used
# to later #INCLUDE a centrally maintained lmhosts file if the
"localsrv"
# system is unavailable.
#
# Note that the whole file is parsed including comments on each lookup,
# so keeping the number of comments to a minimum will improve
performance.
# Therefore it is not advisable to simply add lmhosts file entries onto
the
# end of this file.
DOCUMENT:Q121044 09-SEP-1996 [crossnet]
TITLE :NBTSTAT -R Parameter May Fail in Microsoft TCP/IP-32
PRODUCT :Windows for Workgroups and Windows NT Networking Issues
PROD/VER:1.00
OPER/SYS:WINDOWS
KEYWORDS:kbnetwork kbbug1.00
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft TCP/IP-32 for Windows for Workgroups, version 3.11
- Microsoft Windows for Workgroups version 3.11
----------------------------------------------------------------------
SYMPTOMS
========
The NBTSTAT -R command may not appear to function properly in Microsoft
TCP/IP-32. If you attempt to purge and reload the NetBIOS name cache
using
NBTSTAT -R, the remote name table may be purged without reloading the
NetBIOS name cache from the LMHOSTS file.
The NBTSTAT -R command appears to function properly and generates the
following message:
Successful purge and preload on the NBT Remote Cache Name Table.
However, the NBTSTAT -C command shows that the cache has been purged,
but
the values in the LMHOSTS suffixed with #PRE have not been loaded.
WORKAROUND
==========
You can work around this problem by enabling the LmHostFile parameter in
SYSTEM.INI:
1. In the Network window, double-click the Network Setup icon, or use
the
arrow keys to select Network Setup, and then press ENTER.
2. In the Network Drivers dialog box, choose the Drivers button.
3. In the Network Drivers list, select Microsoft TCP/IP-32 3.11, and
then
choose the Setup button.
4. In the Microsoft TCP/IP-32 3.11 setup dialog box, choose the Advanced
button, and then select the Enable LMHOSTS Lookup check box.
Note that this parameter is not enabled by default when you install
Windows
for Workgroups version 3.11 with the Microsoft TCP/IP-32 protocol.
STATUS
======
Microsoft has confirmed this to be a problem in Microsoft TCP/IP-32. We
are
researching this problem and will post new information in the Microsoft
Knowledge Base as it becomes available.
Additional reference words: wfw wfwg prodtcp32 1.00
KBCategory: kbnetwork kbbug1.00
KBSubcategory: ntprotocol nttcp
--
================,,,=========================
===============(o o)========================
===========oOO==(_)==OOo====================
mega...@cyberdude.com
Not an Intel Employee
Not a Microsoft Employee
Just a User.
Your Mileage May Vary. :)
===========ooooO==Ooooo=====================
===========( )==( )=====================
============\ (====) /======================
=============\_)==(_/=======================