[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now


Direct cable connection problems?

Posted on 1999-01-18
Medium Priority
Last Modified: 2013-12-28
Scenario: Notebook PC (system "A") running Win98, desktop PC (system "B") running Win95.  "B" is connected to the office LAN, using another PC running NT as the server.  (if that matters?)  I want to transfer some files from "A" to "B" using Direct Cable Connect.  Have the parallel cable; ("Direct Cable Connection PC to PC File Transfer Cable" from Belkin), both computers have the IPX/SPC protocol enabled, both computers have the same workgroup name in the Identity tab under Networks.

Firing up "A" as host and "B" as guest, "A" apparently sees "B" try to login, since the DCC display changes from "Is the other computer running?" to "verifying…".  "B" asks for the host computer name, and I enter it; the same name as shown in the Identity tab under Networks on "A".  "B" then hesitates for awhile, then comes back with "can't find host computer".

What is the problem?  Is there a trick to this that I'm not seeing?
Question by:jarnold
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3

Expert Comment

ID: 1652159
The other computer must have files/directories shared in order for that to work.

That is, File and Print Sharing must be on, and at least one directory must be shared.  Also, the computer name is case sensitive.

When it says, can't find other computer, you are still connected over an IPX network, however, since nothing is shared, that message comes up.
LVL 25

Accepted Solution

dew_associates earned 150 total points
ID: 1652160
JArnold, there are a few reasons for this problem, but this is the most prevalent. Also, make sure you have the appropriate network components installed.

First, the error your receiving:

This errors can occur if the Vredir.vxd file is missing or damaged.
Remove or rename the Vredir.vxd file (if it exists) in the Windows\System folder, and then extract a new copy of the Vredir.vxd file from your original Windows disks or CD-ROM to the Windows\System folder.

Once you have replaced the file, reboot your system and try it again. Direct cable will not work if your only using the Netbui component.

As to underlying issues:

This problem can also occur when you use the default protocols installed by Windows 95 and Windows 98. By default, Windows 95 installs the NetBEUI protocol and the IPX/SPX protocol. However, Windows 98 installs only Transport Control Protocol/Internet Protocol (TCP/IP). Since Direct Cable Connection requires that the same protocol be installed on both computers, you are unable to connect.
To connect and share resources between two computers running Windows 95 or Windows 98 using Direct Cable Connection, you should have the following components installed:
 - Client for Microsoft Networks
 - File and Printer Sharing for Microsoft Networks
 - The same protocol installed on both computers
You can add these components like this:
Client for Microsoft Networks
1. Click Start, point to Setting, click Control Panel, and then double - click Networks.
2. On the Configuration tab, click Add.
3. Click Client, and then click Add.
4. In the Manufacturers box, click Microsoft. In the Network Clients box, click Client For Microsoft Networks, click OK, and then click OK again.
5. Restart your computer when you are prompted to do so.
File and Printer Sharing
1. Click Start, point to Setting, click Control Panel, and then double-click Networks.
2. Click Add, click Service, and then click Add.
3. In the Manufacturers box, click Microsoft. In the Network Services box, click "File and printer sharing for Microsoft Networks," and then click OK.
4. Click OK.
5. Restart your computer when you are prompted to do so.
1. Click Start, point to Setting, click Control Panel, and then double-click Networks.
2. Click Add, click Protocol, and then click Add.
3. In the Manufacturers box, click Microsoft. In the Network Services box, click a protocol. Be sure that at least one protocol is installed on both computers.
4. Click OK, and then click OK again.
5. Restart your computer when you are prompted to do so.

Let me know how you make out!

Author Comment

ID: 1652161
Thanks for the detailed response.  I will be trying your suggestions, as time permits, today and tomorrow, will post again if still having problems.
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!


Author Comment

ID: 1652162
Dennis, have been working on this per your suggestions, the Win95 computer still claims that it can't find the host computer system.  Check:
* both computer have folders with sharing enabled.
* both computers have Client for Microsoft Networks installed.
* both computers have File and Printer sharing for Microsoft Networks
* both computers have the same protocols available; ie, TCP/IP, IPX/SPX
* the VREDIR.VXD file replaced from original CDs on respective computers.
* Netbeui not installed on either machine.
* Was concious of machine name case sensitivity.
* Both machines in the same workgroup (case the same for both).

Trying it both ways yielded the same result; ie, if the Win98 machine was host, Win95 guest, you can see the Win98 display change after you type in the computer name, but it eventually comes back with "can't find host computer".  Ditto when I tried it vice versa.

Other areas to be checked?

LVL 25

Expert Comment

ID: 1652163
Okay, click Start, Find Computer and ask it to find each of the computer names that you installed and let me know what happens.

I have a feeling there may be a registry error. Leave the other network components in place and add Netbui to two machines, the one Win98 machine and one Win95 machine.

Author Comment

ID: 1652164
Ok, we're finally cookin'.  Using Find Computer, neither computer found the other. (?)  I then went in and added Netbui to the protocol on both machines, rebooted both, and then it worked like a champ.  Go figure.  I thought DCC used IPX/SPX?  Anyway, thanks for the suggestions and followup, it now works.
LVL 25

Expert Comment

ID: 1652165
It's a common problem. Netbuis is a base protocol and M$ assumes (you know what that means) that you know this.

Featured Post

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Ever visit a website where you spotted a really cool looking Font, yet couldn't figure out which font family it belonged to, or how to get a copy of it for your own use? This article explains the process of doing exactly that, as well as showing how…
Know the reasons and solutions to move/import EDB to New Exchange Server. Also, find out how to recover an Exchange .edb file and to restore the file back.
As developers, we are not limited to the functions provided by the VBA language. In addition, we can call the functions that are part of the Windows operating system. These functions are part of the Windows API (Application Programming Interface). U…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

656 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question