Direct Cable Connect Win 95 to Win NT 3.51

Spider Note: Connect NT 3.51 using a serial cable. Illustrated guide to set-up and operation. DCC

Windows 95 to Windows NT 3.51

Direct Cable Connect Setup Instructions

As you may have discovered, dos level programs such as interlnk.exe do not operate in the windows NT dos shell. This is due to a change in the file handles provided to dos applications. Other applications suffer similar porting problems due to changes in the port drivers provided by windows NT. The two operating systems may still be connected using a serial file transfer cable by following these setup directions.

Requirements:

File Transfer Serial Cable

Availiable Serial Port on the Windows 95 Machine

Availiable Serial Port on the Windows NT Machine

Disclaimer: In using this information you agree not to sue me because you or I or both are stupid. The Images and trademarks shown in this doc are copyright(c)Microsoft people.

Also availiable: Windows 95 to Windows 95 Instructions

Also availiable: Windows 95 to Windows NT Version 4.0

Set-Up the Windows 95 Machine

Click START / Settings / Control Panel

Click Add/Remove Programs and verify you have Direct Cable Connection Installed.

Note: Click the "Windows Setup" tab, Double Click on the "Communications" Telephone

If the check mark is not apparent next to "Direct Cable Connection:", click in the box then select OK. Windows will install the direct cable client when you click OK at the main Add/Remove Programs Properties window.

Warning: If windows 95 also selects the installation of "Dial-Up Networking", you may want to review this information regarding the possible deletion of old winsock.dll Internet connections.

Install NetBEUI Protocol and IPX-SPX-compatable protocol. Also install the "Client for Microsoft Networks".

Click on the network ICON in control panel, Select Configuration Panel

Now Determine the name of your windows 95 computer, this appears in the first box entitled "Computer Name". You will need this information to mount the drives on the windows NT machine:

Get the computer name from the Network Computer Name: box

Now Share your file system. You will want to configure TCP/IP later to not share your information over the internet. This is done by adjusting the bindings. You must name the drive to mount it in NT, remember the name it is used later.

Click the file and print sharing Option BOX

We are Done With the Control Panel.

Run "Windows Explorer" and share some information so that we can test our new link.

This is done by highlighting the drive, clicking file and properties.

A picture of the properties display in file manager .. oh yeah nt explorer

RESTART YOUR COMPUTER if any software or changes have been made.

Attach a cable between the two computers. You may want to use hyperterminal on both computers set at 19200baud to determine if the cable is ok. If you can type on both windows and see it on the other screen, youre ready to connect. Note the port names used on both computers this will be required configure the link.

Launch the "Direct Cable Connect" utility in windows 95

Select the cable where you will connect click NEXT>

Dont bother with the password, click NEXT>

Status: Waiting for remote computer ...

The windows 95 computer should be ready to connect to the NT machine. Leave the program running as we will soon be connecting...

Set-Up the Windows NT 3.51 Machine

Install the Remote Access service if not already present in the Control Panel/ Network Display:

Control Panel/Network

You also must have the NetBUI and IPX/SPX Protocols Installed:

Control Panel / Network Settings

Make Sure that the bindings show the protocols for RAS:

Check Network Bindings

Add the "Null Modem 19200" In Remote Access Setup

Click on the Modems Icon

Install Service Pack 5 to Correct RAS Malfunction. If RAS was just added the service pack will also require re-installation if already present. Files not required in the current system are not installed from the service pack.

RESTART YOUR COMPUTER if any software or changes have been made.

Start the Remote Access (RAS) application

Click the AddButton: Call It something appropriate so you can remember what it will do later.

Make Sure Baud Rate is 19200

Disable TCP/IP it wont connect, check LCP extensions, IPX & NetBUI

Select NetBUI and IPX... & LPC ext

Take Default Security Settings

Click OK and Youre Ready to Connect

Establishing the Connection

Start Remote Access (RAS)

(windows NT Program Manager Display)

Click DIAL

(windows NT display)

Again your windows 95 computer must be in the following mode:

You know the DCC Waiting panel (windows 95 display)

Do not enter a password, and just enter anything as the User Name:

Note: If you enabled passwords on the Direct Cable Client for windows 95 enter the appropriate information here.

(windows NT display)

Click OK. Now you should see if you click Status:

Connected Looking Stuff .. youll know (windows NT display)

(windows 95 display)

Using Files on the Windows 95 computer

Run the Windows NT File Manager

Click Disk, Connect Network Drive:

Enter the following in Path \\ your computer name \ shared name

Note: "Computer Name"is shown in the control panel, network selection, Click on Identification and it is the first line entitled "Computer Name". You should have noted it from the windows 95 machine setup. Shared name can be found under windows 95 explorer / Properties for the drive you wish to mount.

The windows 95 files and directories now appear as a network drive in the file manager. You may copy files as normally done on local drives. If the setup does not allow writing from file shares, you may not be able to write to the remote computer. Use the file manager in windows 95 to change the sharing "properties" if write access is required. Be aware that you should disable TCP/IP bindings to the share or someone may get you over the internet next time you log in.

Related Sites

FAQ for this document (Hypertext)

Instructions for connecting two Windows 95 Computers

Drop A Line if I forgot something, or it was unclear, Frank J. Kime Jr.