//flex table opened by JP

Click to See Complete Forum and Search --> : Direct Cable Connection... direct parallel connection won't work?


Etruscan
08-08-2001, 12:04 AM
I am trying to connect two computers with 10' of cable by the parallel ports. I don't have any network cards other than modems in either computer. As the cheapest way to share a file between two computers, I thought I would use the Windows program: Direct Cable Connection.

I have gone through the trouble shooting procedure that Windows provides in the program. Here is how it went. Maybe someone can spot an error.

1. I have the computers properly configured one host (the one that has the file I want to share) and the other guest (the one I want to download to)

2. Sharing is enabled on both computers.

3. The file I want to share is marked for sharing through My Computer ... sharing with a hand icon and password configured.

4. IPX/SPX protocol is loaded on both computers in the network options.

5. The boxes are checked in 'dialup adapter' binding the IPX/SPX protocol to the adapter.

6. ECP (extended capabilities port) is enabled in both BIOS.

Finally, the last in Windows check list: do you have the right cable? This what I am beginning to seriously doubt.

Windows says, for a parallel connection, you must have:

a) Standard or Basic 4-bit cable, Laplink or Interlink.

b) ECP cable (extended capabilities port)

c) UCM cable (universal connection module)


I don't know what kind of cable I have. It looks like the printer cable only it doesn't have the the kind terminal that will fit in the parallel port of printer (the push in terminal in a standard parallel port on the back of a printer). Instead it has two male connectors on either end the same as the computer end of the printer cable. Thus, one is able to connect the parallel ports of the two computers.

I checked the pins with a meter to see if all the pins were wired before I hooked it up. Each pin is continuous with its opposite number on the other end the cable and isolated from ground. In other words, 25 pins wired straight through from end to end with no cross overs, grounds or commons. I don't know if it is shielded, probably not. So, it just connects the parallel ports exactly matching each pin on the opposite port and providing continuity.

Is that enough? Or do the cable types listed above have devices wired inside the connector that you can't see? Oddly enough, the bag it was in had SERIAL stamped on it. Nevertheless, it should work, right? It is connecting the ports up. That should be all that's needed. However, it doesn't work. Help!

One last bit of business. I tryed logging on with Windows Log On activated, then Client for Microsoft Networks, and finally booted up with Client for Netware Networks active. None of these changes helped.

Rhino302
08-08-2001, 12:29 AM
I would bet that you need a cross-over or null modem cable. I've only done this with a serial cable, and I think it had to have some wires crossed, just like an ethernet would.

[This message has been edited by Rhino302 (edited 08-08-2001).]

Etruscan
08-08-2001, 12:39 AM
Yeah, Rhino302, this is Serial cable. That's what is says on the bag, but I want to make a connection to the parallel port. I could connect to the serial port if had some adapters. This cable only fits the parallel port. I don't really think there should be crossovers. There could be hidden devices in the cables that Windows specifies though.

Want is null modem cable? RS-232 that windows specifies for connecting to the serial port?

Azza
08-08-2001, 04:52 AM
I think Rhino is right!! You are basically doing a peer to peer connection except with a parallel cable.
Your connection would probably work if you went through a parallel hub!!
Speak to an electrician if you know one, they are usually more experienced with the cable side of things!!
Good luck.

TOAD6147
08-08-2001, 05:02 AM
Here's an excerpt from a source I've always used for networking problems:
"This cable by the way, is a special cable for "Windows 9x Direct Cable Connection." I found mine at CompUSA for about $15. Mail order is probably even cheaper."
The full tutorial is here: http://www.homepcnetwork.com/cable.htm

manwhore
08-08-2001, 06:18 AM
First of the cable you need definitely needs to be crossed over and not 25 pins straight

This is effectively what you have now

PC1 Transmit Pin ------- Transmit Pin PC2
PC1 Recieve Pin ------- Recieve Pin PC2

This means that if PC1 transmits data it uses the channel that PC2 wants to send on and not its recieve chanel.

Needs to be like this

PC1 Transmit Pin ------- Recieve Pin PC2
PC1 Recieve Pin ------- Transmit Pin PC2

or
PC1 Transmit Pin ---\/ -- Transmit Pin PC2
PC1 Recieve Pin ---/\-- Recieve Pin PC2

So that when PC1 transmits dat PC2 recieves it correctly.

If the cable if 25 pins wired straight then get another cabel beofre you change any settings on the computer.

Not sure exactly which pins are crossed over
check this site http://www.loop-back.com/null-mod.html which has some info you could rewire it or get another cable

andy

muchmark
08-08-2001, 07:03 AM
Hi,
Here is the wiring diagram for making a Parallel Laplink cable:http://www.cablingdirectory.com/pinouts/parallelserial/ParallelLaplinkPinout.htm

Etruscan
08-08-2001, 11:12 AM
Thanks muchmark, the pin out for the cable shows that indeed there are crossovers between the two male connectors of the cable. No wonder it won't work. I have everything else right, so it has to be the cable. I'll recheck with a meter, but I'm sure the pins are just wired straight through.

Thanks for the link Manwhore, now I know how to wire a null modem connection.

If anyone out there has the the pinout for an ECP cable,(extented capabilities port) I would appreciate it. Muchmark gave me a link with a Laplink cable pinout. This is a "basic 4 bit" hook up. The ECP, which used the same connectors and cable, is faster. I suppose it uses more of the wires in the cable (there quite a few spares in a Laplink cable) and is more that likely an 8 bit connection.

I think what I'll have to do, rather than return the cable($5.50), is cut it in half and splice the wires to the right pinout configuration. If I had the ECP config., I would end up with a faster cable. Thanks to all so far. http://www.sysopt.com/forum/smile.gif

[This message has been edited by Etruscan (edited 08-08-2001).]

Etruscan
08-08-2001, 11:39 PM
I got it hooked up and working. I cut the cable and respliced it to a LapLink Standard 4 bit congfiguration. The speed is tolerable: 6.5 MB in two minutes for a file transfer.

I spent about 1/2 an hour in a web search for information about ECP configuration and only found one diagram which wasn't clear enough to use as a wiring diagram. The net site that has the wiring configurations for IEEE 1284 (ECP cable) was shut down. The information I did find said the cable contained shielded twisted pairs. I couldn't make one from the cable I have, which is just a shielded 25 conductor cable. I had to cut it to find out what it was. Thanks again everyone. http://www.sysopt.com/forum/smile.gif





[This message has been edited by Etruscan (edited 08-08-2001).]

Rhino302
08-09-2001, 12:33 AM
Hopefully it works for good for you. Whenever I trasnfered large files (over 50 megs) it would always lock up a PC halfway through.

NDC
08-09-2001, 03:59 AM
Moved to Networking and Internet