NT3.51 WS to NT4.0 Server Problem

Posted on 1998-11-17
Medium Priority
Last Modified: 2013-12-28
When trying to connect an NT3.51 workstation to an NT4.0 Server I can ping the server from the workstation, but can't connect to the server neither via explorer nor throuh the connect function. The TCP/IP name or the DNS name of the server can not be seen by the explorer, however it can be pinged.
Question by:danaweb
LVL 13

Accepted Solution

Mirkwood earned 300 total points
ID: 1794816
Test the following
- Make sure that Netbios is enabled.
- Install WINS on the server.
- Make sure that the server has the Master Browser property set to Yes.
- Make sure that the Object Browser is active on both machines.

Expert Comment

ID: 1794817
Try using an lmhosts file by doing the following
create a text file in the following location and call it lmhosts with no extension
substitute the directory name for where your nt is installed MYSERVER #PRE#DOM:MYDOMAIN

Have you gone into server manager and added the win 3.51 server in nt 4.0?  This also maybe the trick.

Substitute names for your server and domain, I think this may solve your problem and allow you to connect to the server, you will need to reboot the server once you create the file and place it in the etc folder.

LMHOSTS File Format

The LMHOSTS FILE FORMAT is used to standardize mappings between Windows NT NetBIOS names and IP addresses. The LMHOSTS file format is compatible with the file syntax used for name resolution by LAN Manager.

NOTE: Comments in the LMHOSTS file are preceded by the '#' character. If the first several characters following the '#' character match one of the keywords in the following example, a special command is executed.

The following sample LMHOSTS file is provided by Windows NT Server for reference, and is located in the \%SYSTEMROOT%\SYSTEM32\DRIVERS\ETC directory:

# 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 computer names
# (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 computer name
# 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>
# \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 <domain> is 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 <filename> and parse it as if it were
# local. <filename> is 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 addition 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:
# rhino #PRE #DOM:networking #net group's DC
# 'appname \0x14' #special app server
# popular #PRE #source server
# localsrv #PRE #needed for the include
# #INCLUDE \\localsrv\public\lmhosts
# #INCLUDE \\rhino\public\lmhosts
# 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.


Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

This article provides a step by step guide (with screenshots) showing how to create a new local (test) Administrator user profile in Windows 10 for troubleshooting purposes, and then how to remove it.
This tutorial is about creating a new Microsoft Online User Profile account along with how to transfer your files and settings. You may be faced with this situation if your existing user profile has become corrupted.
Windows 8 comes with a dramatically different user interface known as Metro. Notably missing from the new interface is a Start button and Start Menu. Many users do not like it, much preferring the interface of earlier versions — Windows 7, Windows X…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

600 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question