I myself would not bother trying to learn
how to setup TCP/IP for a windows 3.1. My
solution is that upgrading a windows 3.1
machine to a Windows 3.11 for Workgroup
machine, and then I talk about networking:
because networking is Windows 3.11 for
workgroup mininum requirement: otherwise,
I would waste much more time trying to install protocols and configure for a windows
3.1 which is not networking friendly at all.
If it is because of not having Windows 3.11
for workgroup at hand, you should try to
"borrow" one from a friend or someone who
has it.
NETBEUI protocol is the main protocol that
should be used in small network at home.
If you buy a network card with a driver
diskette with it, there is likely that
during installation of your network driver,
the NETBEUI protocol is already installed on
your machine. During Windows 3.11 installation, when networking components are
being installed(together with the network card driver), the NETBEUI protocol and an
IPX/SPX protocol should be already installed
onto you machine. In order for the networking
to be alive between a Windows 3.11 and a Windows 95 machines, there must be a least
the following components:
1. Protocol: - The NETBEUI
2. Client : - Client for Microsoft Network
3. Services: - File and Printer Sharing
4. Adapter : - A working adapter.
If your machines (both) have at least these
components, they will be up and running. If
they do not, it is probably the BINDINGS
is not set correctly. Here how it should be
set:
1. NETBEUI should be bound to the network
card, and only to the "interior" network
card ( that is it should not be bound to
a DIAL-UP ADAPTER, or any exterior adapter
cards.)
2 Files and Printer Sharing should be
enables on the machine on which you want
to share resources that other machines.
( Files and Printer Sharing service should
not be "bound" (enabled) to any TCP/IP bindings to any adapter cards:for reason
of networking performance. This is also true
for any being "bound" of services of any
kinds to any TCP/IP bindings to adapter cards.)
3. Client for Mircrosoft Network should be
"used" (selected).
4. Identifications: Each computer must
have a unique name and all computers must
be on the some workgroup( the workgroup
names all have to be the same on all
computers unless there is a server
with domain defining instead of workgroup.
5. Computers have to be rebooted when there
any changes made to any setting or configuration of networkging configuration:
if you can not "connect " to another computer
on the network, first try to reboot the computer that has the most recent modification.
SUMMARY: NETBEUI protocol is the "transporting language" to be used (bound)
by two or more adapter cards in small
networking. Just like if there is a server
of some kind, there must be a client of
some kind. "Permission to use" (File and
printer sharing) of resources should be
granted(enabled)for the resources to be
transferable.
For INTERNET SHARING CAPABILITY:
1. TCP/IP protocol must be installed on
all machines and be bound to all adapters.
It must also be set to obtain IP address
automatically: DHCP will provide an IP
address for each machine each time they
log on. Also the File and Printer Sharing
service ( or any other services) and the
Client for Mircosoft Networking client
( or any other clients) should not be
set enabled to communicate with these
TCP/IP bindings to any adapter cards. This
is for a better networking performance
result. The server machine (one that has
the INTERNET CONNECTION SHARING software
installed), after being installed with
this INTERNET CONNECTION SHARING software
and configured will have an IP address
of 192.168.0.1.
2. Windows 98 Second Edition has the
INTERNET CONNECTION SHARING package
built in. For example, if there networking
in which Windows 98 Second Edition had
successfully configured for sharing its
internet connection with some other
windows 95 machines, The Windows 3.11 for
workgroup can merge in and sharing this
internet connection with these machines by
just setting to use LAN or PROXY server
in the INTERNET OPTION in the control
panel( instead of using its regular
modem connection.)
Hope this will help connecting a windows
3.11 machine to a windows 95 one.
