Consultor Eletrônico

Status: Unverified

GOAL:

HOSTS,PROTOCOL and SERVICES files ON Windows

GOAL:

KB17365

FACT(s) (Environment):

Windows

FIX:

Progress error messages that refer to TCP/IP errors
typically use UNIX terminology and subdirectory syntax. For
instance:

Unable to find server with protocol "tcp" in /etc/services.
(777)

This error message is misleading when it is displayed in
Windows 95 or Windows NT. Those systems have different
subdirectory names. The HOSTS file and SERVICES file are not
in /ETC. They normally are in a subdirectory below the
Windows default directory. To confuse things a bit further,
there is no standard for the name of the Windows
subdirectory. The following shows TYPICAL locations where
the HOSTS file, SERVICES file and PROTOCOL file may be
found:

In Windows NT these files are always in SYSTEM32\DRIVERS\ETC
under the Windows directory. For instance:

C:\WINNT\SYSTEM32\DRIVERS\ETC\HOSTS
C:\WINDOWS\SYSTEM32\DRIVERS\ETC\HOSTS
C:\WINNT35\SYSTEM32\DRIVERS\ETC\HOSTS

In Windows 95 using Microsoft's TCP/IP software, the HOSTS,
SERVICES and PROTOCOL files can be found in the Windows
directory. For instance:

C:\WINDOWS\HOSTS
C:\WIN95\HOSTS

In Windows for Workgroups (also known as Windows 3.11) the
HOSTS and SERVICES files are typically found in the C:\NET
directory:

C:\NET\HOSTS

In Windows 3.1 there is no standard location. Windows 3.1
did not include networking software, customers purchased
TCP/IP software either as an extra-cost option from
Microsoft or from a third party vendor, subdirectory names
varied widely.

With any version of Windows, you can quickly find any file
by using the SEARCH or FIND features in Windows Explorer or
Windows File Manager.

NOTE: Microsoft typically includes sample files showing how
a particular HOSTS or SERVICES file might be built. These
sample files may be identified by the file extension of
.SAM, such as HOSTS.SAM or PROTOCOL.SAM. They are only
samples, these files are not used by the TCP/IP software.