WINS/LMHOSTS

[9826024006]

Hi All,
I have different-2 domains in my NT based network connected with Digital Leased lines...can u pls let me know how can I see all the domains PCs in my Network Neighborhood as I can see for local network....I don't have WINS server....I hv placed a LMHOSTS files for all PCs in my system but still I m not able to see the PCs in Network neigh.

Pls let me know any other way for this.

Thanks

 

[compgirlfhredi]

Without WINS, you need special LMHOSTS entries that designate who all the domain controllers are. This is done in the following convention:
199.199.199.1 ComputerName #PRE #DOMomainName

When a computer is booted, it reads these entries and store them permanently in the NetBIOS name cache until the computer is powered down. (Because of this, it is best that these entries are last in the LMHOSTS file, for subsequent LMHOSTS parsing efficiency.) All computers in the domain needs one of these entries for each domain controller (in the local domain), as well as one for the PDC. Also note the exact order of #PRE #DOM, and that they are capitalized. The other names are not case sensitive.
It is important to note that the main drawback to LMHOSTS browsing is that it does not provide the automatic ability of multi-domain browsing. As previously mentioned, the PDC will query WINS for a list of remote domains and include that information in its browse list. However, the PDC will not parse the LMHOSTS file for the same information, nor will it include other \0x1b entries with the #PRE (cache) directive. Effectively, if your PDC does not query WINS, you will not see other domains through File Manager or Network Neighborhood. However, you can still browse other domains manually, (provided that you know the domain name and that you have special entries in your LMHOSTS file), and there is still a chance that you may browse remote domains based on broadcasts.

Manual Method: this is accomplished by including a \0x1b entry for the PDC of any remote domain you want to browse. This technique applies to Windows NT, Windows 95, and Windows for Workgroups. It is effective because of the following sequence of events, necessary for remote domain browsing:
1. The client determines who the PDC is of the remote domain through the domain<1b> name (for LMHOSTS this is done by having the \0x1b entry; for WINS it would be via query).
2. The client sends a GetBackupList API request to the remote PDC
3. The remote PDC responds with a list of up to three master browsers, potentially including itself.
4. The client sends a NetServerEnum API request to one of the master browsers
5. The master browser responds with his domain-wide browse list.
The &quot;manual way&quot; of getting this browse list is through a command window:
For WinNT computers: c:\net view /domain:<domainname>
For Win95 and WFW: c:\net view /workgroup:<domainname>
Broadcast Method: This works in the case of any network segment that has members of multiple domains. There is a SegMB of each domain on the &quot;mutual&quot; segment, and each SegMB announces its domain via broadcast to a special NetBIOS name <01><02>_MSBROWSE_<02><01>. This broadcast packet includes the domain name and the computer name of the SegMB that announced it.

The SegMBs of other domains (on this mutual segment) listen for this information, and add it to their local browse list. A SegMB on this segment has now &quot;discovered&quot; other domains, and send the discovered information to: the DomMB of his domain, and to local clients (in his domain) that request a browse list.

A client requests the local domain browse list (from a local SegMB) and see the discovered domains in File Manager and Network Neighborhood. When the client selects the discovered domain, he actually requests a browse list directly from the SegMB that made the announcement in the <01><02>_MSBROWSE_<02><01> packet. Furthermore, since this information was also sent to the client's DomMB, it is propagated to SegMB's on other segments that are part of this domain.

Clients on a remote segment can now leverage this information, and browse the remote domain even though there is no remote domain member on their segment. However, this process is very volatile using LMHOSTS files, because you are dependent on the &quot;discovered remote SegMB's&quot; still being active. In a WINS environment, this remote browsing feature is much more stable because WINS provides information about the remote domains to your PDC.

Things to consider:
1. For domain logon and domain browsing to work via LMHOSTS, all computers require an LMHOSTS file that includes entries for all domain controllers and proper \0x1b entries, and the PDC requires an entry for each remote segment master browser (if they are not already listed).
2. Most likely every WAN computer is listed. This could be done most efficiently by having one common LMHOSTS file that is distributed to all clients and servers; however, you must keep it updated with all proper IP address changes, and that could become an administrative burden.
3. Seeing a computer in the browse list does not imply you can connect to it. If it is on your local segment, you can connect through broadcast; if it is on a remote segment, you need an LMHOSTS entry for it.

 

[GlenJohnson]

Silly question, are all clients members of the domain? Do you see any of them? Why not install WINS on one of your servers? How is the rest of the networking set up? DNS, DHCP? Good luck.

Glen A. Johnson
&quot;To fear the worst oft cures the worse.&quot;
William Shakespeare (1564-1616); English dramatist, poet.

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884