Direct-Cable Connection between Win95 and NT4
One of the best proves, that Direct-Cable
connection (DCC) and Dialup-Networking (DUN) are closely related,
is the possibility to establish a connection between Windows95
Direct-Cable Connection (DCC) and Windows NT4 Dialup-Networking
(DUN)/ Remote Access Server(RAS) ( which is
(unluckily) limited to serial communications, NOT
allowing the higher throughput of a connection via parallel
of the "Direct Cable" modem
||In the Modem applet of the
NT Control-panel, select to
add a new modem (if no
modem was previously defined,
it will start this dialog directly)
Put a Check-mark into:
"Don't detect my Modem,...."
||Select now manually from
the category ("Manufacturer"):
"Standard Modem Types"
"Dial-Up Networking Serial
Cable between 2 PC's"
||Select the serial port
to be used for the
||Once this "modem" is installed,
check its properties and make
sure, that it is configured for the
MAXIMUM speed of 115000.
If you have already a network installed, just add RAS to it (skip
the next section).
If you have no network installed:
start the network-icon in the Control-Panel and agree to install
||select to install only the
"Remote access to a network"
(unless you install at the same
time also a network board)
||When you are prompted for a
Network adapter, do NOT
"Start a Search", but defined
to "Select from a List"
||Select from the list the
"MS Loopback Adapter":
for proper operation, NT RAS
requires, that a Network card
if no REAL network card is
installed, then you need to
install this network card
if there is a REAL network card
already installed, then there is
no need to install this emulator.
||Once the network-card (a REAL
one or the emulator) is selected,
continue to the next screen and
select your protocol.
For use of the Direct Cable
Connection, keep it simple
and select ONLY NetBEUI
(the use of IPX/SPX and/or
TCP/IP would require much
more setup work and is NOT
suggested to use for inexperienced
||The verification, that
"Remote Access Service"
is selected for installation.
||You are prompted for the NT
CD-ROM: make sure, that
you point it to the proper
directory : to the \I386
directory on your CD-ROM .
||The Network card emulator
"MS Loopback Adapter"
to be configured:
just leave it on the default
"802.3" and continue.
||The Network Setup activates
the RAS Setup, which first
prompts you to confirm,
that the modem
"Dialup-Network serial cable"
should be added as RAS device.
Accept this and select OK
If you had RAS already previously installed, continue here,
make sure, that the
"Dialup-Networking Serial cable"
is defined as RAS device:
||Configure the port:
Since I like to use it in BOTH
directions, I select here:
"Dial out and Receive Calls"
||Define the Network
in this setup, using NetBEUI as
protocol for both Dialing Out
and for working as Server
(to receive Calls).
||RAS Setup is done.
The reminder, that you
need to define in User Manager,
whether a user is allowed to
connect via RAS.
||You can verify the bindings
(click on the '+' to expand the
display), it should only show
||Define your workgroup-name:
Both systems MUST be in the
Workgroup, but MUST
||Network/RAS setup is done !
You are reminded TWICE, that
you have to restart your system.
as a DCC-Host:
You need to startup RAS for acting as a host (unless configured
using from the "Administrative Tools"
menu the "Remote Access Admin"
(you need to have NT administrator rights to do this job ! ):
||Start up RAS.
(it takes a few seconds)
||NT is ready to act as
DCC host !
Making the Connection from the Windows95/98/ME
||On starting the DCC Client on Windows95,
you are prompted with a User Logon
you are connecting to an NT system and
have therefore now to comply to the
NT security scheme.
enter a username and password, which
is defined in the User-database of NT.
||The DCC client cannot find folder on the Host
and asks you now to define the Host-Name:
enter the Computername of the NT-system.
||You are connected:
The DCC Client connection allows to
"View the Host", but
Network Neighborhood is
(since we have a network board, real or
emulation, installed in the NT system, a
network is running with an acting
Browse-Master, providing the
Network Neighborhood with the
||Since we connect only via a
we can only expect a throughput of
approx. 10 Kbytes/sec.
||On the NT-system, you can check the
incoming connection using the
"Dialup Networking Monitor"
||If the DCC Client has "File-and-Print
Sharing" installed, it will be shown
in the Network Neighborhood,
allowing to access the data of the
Win95 DCC-Client from the
from NT Dialup Networking to a Windows95/98/ME DCC-Host:
start up on the Windows 95/98/ME system DCC to act as Host, then:
||Define in NT "Dialup Networking"
a new connection, using the
"Dialup-Networking Serial cable"
(no phone number is required).
||select the proper protocol
(should Be NetBEUI)
deactivate the Checkmark on:
"Enable PPP LCP extentions"
||since there is no user-security
on the Windows 95 system, you can
define ANY username.
However, watch out for the password:
If the DCC Host was configure
to allow connections WITHOUT
a password, do NOT define any
If the DCC Host requires a password
for a connection, define it here !
||You are connected,
as you can verify using the
"Dialup Networking Monitor".
The Network Neighborhood
is available to access the data.
Connection between NT4 systems
Although it is not called Direct-Cable-Connection, it is possible
2 NT4-systems directly via a serial cable (NT4
does NOT support a direct
cable connection using a parallel cable ! ).
The setup-steps are identical with the DCC connection with a
- Definition of the
"Direct Cable" modem
- define one NT4-system
- define one NT4-system