Direct Cable Connect Win 95 to Win 3.11 RAS

Windows 3.11 to Windows 95

Direct Cable Connect / RAS Setup Instructions

Users of Windows for Workgroups 3.11 who want to periodically transfer files to Windows 95 but not bother with loading/unloading the interlink driver can connect using this procedure. This is also a good alternative for those 95 owners with compatibility problems with the interlnk.exe system driver. These instructions guide you through the WFW RAS client installation and setup as well as configuring your windows 95 computer. Disadvantages of this method include the difficulty of setup, and it may not work if you are already connecting on a LAN using the NETBEUI protocol (see KB article #127136). Users who will not be connecting often should probably consider using interlink. This procedure is for WFW 3.11 installations with no networking installed, although, perhaps your network administrator could assist in the addition of RAS to your computer. The upside of this method is the RAS upgrade is a server and you can connect drives both ways simultaneously!

Requirements:

Serial File Transfer Cable (and)

Unused Serial Ports on both Computers

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 3.1 or DOS Instructions

Also availiable: Windows 95 to Windows 95 Instructions

First, an Important Warning to Consider

If you do not use "Dial-Up Networking" to connect to the internet, the winsock/dialer you are using could be disabled by installing Direct Cable Connection. For computers with no internet access and no network software or if you are already using the built-in winsock shown below, continue on to the setup/install procedure.

If you did not set-up the internet on the computer, not a problem, but if the above pictures are not familiar to you, consider consulting your service provider before performing this procedure. You might consider using interlink to connect your computers. If you are a bit more daring or familiar with the winsock you are using, be aware the following file will be overwritten if you install "DCC" which requires "Dial-Up Networking:

look in the windows directory and you'll see winsock.dll. If not GREAT if so it will be overwritten

You will want to review the following Microsoft KB article #139384 for more assistance in installing third party winsocks. Perhaps the instructions for the particular dialup you are using will be of assistance as well. If you can configure the winsock to use a winsock.dll in its own directory, and can redirect clients to load it, the task is complete.

Download RAS Upgrade from Microsoft

This procedure requires the RAS client upgrade from Microsoft. This improved client has the ability to answer incoming calls and is required for this procedure to work correctly. So click on the RAS panel below and save the upgrade while your reviewing this document. You might want to read more about it in KB article #111292. You must be using windows for workgroups version 3.11. Save the file in a temporary directory (or a floppy disk - ask America Online for a Free One).

(click here)

Windows for Workgroups 3.11 Setup

If you did not install networking do so now.

Click Windows Setup /Options/Add Remove Windows Components

Click on Slect Files for Accessories

Add Remote Access Service

Add Remote Access and you should also have Notepad to edit files later. You should now have RAS appearing in the Network Program Group

If you already have a network installed, you should consult your administrator before making the following changes. Click on the Remote Access Icon to add the appropriate drivers to your system.

Click Install

Click Ok to Install Microsoft Workgroup Networking

Select YES and install Microsoft Networking

pop in Disk #7 as instructed

Select Null Modem for the COM Port You will be using. It is ok to configure more than one.

Enter your information for the Network ID. If this information already exists, I suggest leaving it alone as you might deconfigure other network sessions. Be sure to note your COMPUTER NAME to access files from the windows 95 computer.

Dont Reset Yet

Click Continue. You must now install the network divers in your config.sys. Add the line "DEVICEHIGH ... IFSHLP.SYS". Be sure to enter the location where your windows is installed. Also check to see if the file exists using file manager. If it doesn't you must use the expand.exe utility to copy it off of setup disk #7 in the windows for workgroups install set.

$Add DEVICEHIGH=C:\WINDOWS\IFSHLP.SYS$

If you do not have a memory manager present, you may just enter

DEVICE=C:\{windows directory}\IFSHLP.SYS

RESTART YOUR COMPUTER NOW.

Check Network Config Error Box

If you see the above display, verify that you entered the correct path for ifshlp.sys and also that the entry "NET START" is in your autoexec.bat, and the path statement points to the windows directory so as to be able to find the NET.EXE program. If these three conditions are met, you will have to go below and check out the knowledge base articles regarding the net command because it has failed.

Run the Program you Downloaded from Microsoft to extract the new files. You can click BRWOSE to find the directory you used for downloading.

Program Manager: Click File-RUN wfwptp.exe

Install the Upgraded RAS Client (and now Server).

Run the "COPYPTP.BAT" batch file with the calling parameter of your Windows directory so it knows where to install the files. My windows is installed in the directory "WIN4WG31" since this is a dual boot computer. Yours is probably C:\WINDOWS.

Syntax: {location of files} \ COPYPTP.BAT {location of your Windows Directory}

run the file copyptp.bat generated from the self-extracting archive

Follow the upgrade instructions. The install batch file will ask for your windows directory information.

Using notepad, open the file "serial.ini" in the default windows directory.

edit the serial.ini file with notepad or something

Change the number 9600 to 19200 everywhere you see it. Windows 95 direct cable connect default baud rate is 19200 baud and this change is required. Once you have your connection operating, the baud rate may be adjusted in windows 95 by the System ICON in control panel. Click on device manager and select the modem group. Adjust the settings for the COM port you are using.

Open file manager to share some disks

Share some files for the Windows 95 Computer Click on DISK / Share As

Click Disk / Share As... Enter a name for the shared resource

You can share a directory or the entire drive depending upon what you want to access from the windows 95 computer. The example above shares the entire Drive C: with permissions for the windows 95 computer to read and write.

Network Program Group

Click On Remote Access.

Configure to receive calls. Select the SERVER PORT where the cable will be connected to the Windows 95 computer. Be sure to Allow incoming calls to this computer.

Tip: This is where you change the port if you move the cable in the future.

Click Configuration and Allow incoming calls

Click Options and Start Up in Answer Mode

Select Start Up in Answer Mode for sake of convenience. Click Answer if it is not Now Selected. The Windows 3.11 Machine is READY! (Your description field will not say Windows 95 DCC Host, this is ok)

Windows 95 Computer Set-Up

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

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 the check box next to "Dial-Up Networking" is not checked, windows will require its installation. Please read the warning at the beginning of this page regarding possible disabling of your internet dial-up connection.

Install the "Client for Microsoft Networks".

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

The NETBEUI Protocol must be present. This is the only protocol WFW RAS will allow.

from Network click Add / Protocol / Microsoft / NetBUI

Add the client for Microsoft Networks:

Click Add, Client / Microsoft / Client for Microsoft Networks

Now Determine the name of your windows 95 computer, this appears in the first box entitled "Computer Name". You may need the computer name to mount the drives on the guest computer if auto-connect fails.

network panel/id tab/ make sure to have a unique computer name

Now Share your file system.

Click the file and print sharing Option BOX

Configure the bindings for TCP/IP so no-one can access or damage your files while logged into the internet.

Disable client, file and print sharing for TCP/IP

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 you chose not to during the setup of your computer.

Do This Procedure on the windows 95 Computer

Note: Windows 95 must operate as the Guest due to a compatability issue with the 3.11 RAS initiation sequence. Though the connection must be established in this way, resources may still be shared in both directions.

Launch the "Direct Cable Connect" utility on the Guest (probably in the Accessories Group):

Click Change

select guest click NEXT>

Select the cable where you will connect click NEXT>

You may need to Install the port. If you cannot see the port you will be using, it must be corrected in the control panel system section.

Click FINISH>

Click Finish

The connecting panel on both computers should be Verifying Password

The connection between both computers is functioning properly if you see the Verifying user name and password!

Note: RAS must be running on the windows for workgroups machine. You may add the icon to the startup group so it is always ready, but be aware this will tie up the port.

Enter the Computer Name of your Windows 3.11 Box.

You are fully connected!

Enter Password for Microsoft Networking Panel

If you have acount information, enter it here. You may also be able to log into a LAN connected to the HOST. If no account exists, fabricate a user name and click OK.

No Domain Server

Ignore this message. There is really no network server to log into. Microsoft has an update to correct this in Windows 95.

If you are fortunate, you will have two connected computers. The view host will open a "My Computer" format window series and you can drag files to/from it (provided you shared some files on the windows for workgroups host using file manager).

(95 display)

You can mount the Windows for Workgroup files by doing the following:

(95 display)

If you have shared files on the windows 3.11 computer using file manager the full network name of the shared resource will appear at the bottom of the display but is just:

\\ {computer name} \ {shared name}