From: leefi@microsoft.com (lee fisher)
Subject: installing TCP/IP under Windows NT
Date: 27 Jul 92 04:43:04 GMT
Organization: microsoft corp., redmond, wa

i replied someone via email in response to a few messages about TCP/IP 
installation problems, but the email bounced. anyway, a few others are
asking similar questions, and might benefit from this info...

in general, if you are trying to get TCP/IP to work, you should install
via the normal SETUP program, not DOS2NT (its much easier).  then you
should make sure the normal workstation software (netbeui, not yet tcp/ip)
works (view servers, connect to server and do i/o, etc). then, once you're
sure that the MAC driver is working with this already-installed transport,
try to install TCP/IP. make sure to 'net start tcpipsvc'. append a
'/trace' switch if this fails.  once the TCP/IP service is starting, try
to ping someone. look in the registry to make sure the IP masks are proper
for your environment.  then you should be golden (fingers crossed).

anway, the q&a from the bounced email:

> I've been having problems getting my machine hooked up to our lan.
> First off: We have a LanMan 2.1 server that I'd like to be able to see.
> Is this the feature that is turned off in this NT release?  If not, does
> anyone have experience with getting things going.  The net seems to have
> installed OK.

no, my NT machine sees my DOS LAN Manager 2.1 machine just fine. can you 
see anything (LM21 server, NT servers, anything?) what MAC driver? look 
for a tranceiver internal/external problem.

> Second: I've followed the instructions to get telnet running on TCP/IP.
> I get the network started and I can go as far as getting the telnet
> prompt on the terminal program... but I can't seem to open a connection.
> Ideas... anyone?

can you PING anyone? can they ping you? here is a msg, i think is in
the readme, about using the TCP/IP utilities. maybe it will help.

----- snip ----- snip ----- snip ----- snip ----- snip ----- snip -----
Instructions for using TCP/IP and utilities.

The Network Control Panel Applet should be used to install and
configure TCP/IP. Once this has been completed, TCP/IP can be
initialized by entering:

net start tcpipsvc

Messages will be displayed which will indicate the success or failure
of the initialization. If this step fails, more detailed information
as to the cause of the failure can be obtained by entering:

net start tcpipsvc /trace

A window will pop up and diagnostic information will be displayed.

Once the tcpip service has been successfully started, the standard
utilities can be used as normal. The only exception is the telnet
utility, more on this later.

The standard utility set provided with NT consists of arp, ftp,
netstat, ping, rcp, rexec, route, rsh and tftp. Most of these will
print usage help if invoked with the -? option.

Telnet has been modified to work with the windows terminal program.
To use telnet, make sure that tcpip has been initialized. Then
enter:

telnet

You may then run the terminal program and select TELNET in the
Communications menu.

You will be greeted with a prompt of

telnet>

You may enter telnet commands or help for more info.
----- snip ----- snip ----- snip ----- snip ----- snip ----- snip -----

and a second message:

> Well, I managed to get all the LanMan stuff fat and happy.  I can see
> LanMan servers and they can see me! Great!
> 
> Now to be able to connect to TCP/IP ...
> 
> I get as far as the telnet prompt.  WHen I try "open xx.x.xxx.xx" ( where
> the x's are the ip address of the machine I'm trying to connect to) I
> get a connect failed message.
> 
> 1) How do I configure the TCP/IP to work... I'm not sure about all the
> DNS stuff so currently it's all blank.

how did you install TCP/IP, via SETUP, via REGINIT and tcpip.ini, or
by manually editing via REGEDIT? hopefully, you used SETUP and installed
the TCP/IP driver via Network Control Panel App. setting up via SETUP
sets up the registry properly for the Network Control Panel App to work.
if you've setup via DOS2NT, you can't use the NCPA, and you have to
use REGINI and the TCP/IP ini file to initialize the registry for the
transport (and update your MAC driver).

regardless, if you're already setup, you can edit the registry via
regedit.exe, select the HKEY_LOCAL_MACHINE window, and go down into
\SYSTEM\CurrentControlSet\Services\TCPIP, and edit that section.
for more info, use the tcpip ini file as a guide to what needs to
be changed. (it should be changed in SETUP (or before using REGINI), 
so you don't have to get into REGEDIT.

> 2) Is there support for a host table?

c:\winnt\system\drivers\etc\*. not sure right now, but i think the
registry might improperly point to c:\winnt\tcp or something like
that, you can fix this in regedit (or copy the files to that
subdirectory).
__
Lee Fisher, (not a spokesperson for) Microsoft Corp., Redmond, WA, USA
leefi@microsoft.com, {uunet,uw-beaver,sun,sco,decvax}!microsoft!leefi
c=us;admd=mci;prmd=msft;o=smtp;dda=rfc-822=leefi, +1.206.936.8621



Newsgroups: comp.os.ms-windows.programmer.win32