Direct Cable Connection: XP Pro - 2000 Pro

I am a beginner to intermediate user with Networking falling closer to beginner.

I am having a problem that somebody with some experience can help me with.

First let me describe the two systems I'm using:

Computer A: Dell Desktop P4, XP Pro
Computer B: Toshiba Notebook P3, 2K Pro

I need to transfer some files from Computer B to Computer A.

I am trying to establish a Direct Cable Connection using the parallel port with Computer A as GUEST and Computer B as HOST.

I was able to establish a 4Mbps 'unauthenticated user' connection between A and B, but I am not able to access either machine via this connection. Both computers have an icon in the system bar showing that some of communication is present.

According to all the info I have read, I should be able to see Computer B on Computer A under "My Network Places" and selecting "View workgroup computers ".

Both computers have same Workgroup name and I log in to both computers using same Username/Password.

I found a similar problem that somebody sent in some time ago. I pasted it below my name for reference. I am new all BBS's so I didn't know how to reference it any other way.

I have done this type of transfer before between Windows ME and Windows 98 and it seemed to work flawlessly! Isn't XP supposed to make things easier?

Any help would be appreciated!

Frank
----------------------------------------------------------------------------------
Win2K direct cable connection problems
Hi all, I know this is a fairly common topic but I have tried everything I can find with no luck.

I have an old Thinkpad and a new desktop PC, both now running Windows 2000 Professional.

Using a laplink parallel cable I have been able to establish a 4Mbps 'unauthenticated user' connection, but I am not able to access either machine via this connection.

I have selected the c drives and individual folders to share, I have tried disabling TCP/IP in favour of NetBEUI, I have tried mapping drives in My Computer but all to no avail (I can't browse for the other machine either way).

Neither of the 'entire network' or 'computers near me' folders show the other machine, and a network search returns no results.

The 'sent' and 'received' figures match perfectly so there is definitely some form of communication, which I assume means that my laplink cable is OK.

The only thing I haven't tried is messing about with IP addresses - I don't know how to do this or what numbers to use so I'm trusting Windows to have set suitable addresses automatically at this stage. The main PC has internet access, I don't want to ***** that up. I don't need (or want) internet access for the laptop (I don't want to have to load a firewall onto the laptop, I just want to download safe files from the PC, work on them, and then upload to the PC later).

If anyone is able to help me out I'd be grateful - I don't know what I'm doing wrong!!!

 

Sounds like you are almost there but just missing a small piece of some sort.

Assuming you are using the same null-modem parallel cable you had luck with in the past, you certainly should be connecting.

The simplest way to connect at this point is to have NetBeui running on both machines. Easy enough with 2K. With XP you have to hunt around a little for it since the protocol is unsupported beginnning with XP. But still works fine. Take a look Here for instructions.

The only problem is, while NetBeui is by far the simplest to set up, it lacks any diagnostic tools so if it doesn't work, you'll need to have TCP/IP installed as well so we can troubleshoot. With it, set the subnet mask to 255.255.255.0 and the IP addresses to 192.168.0.10 and 192.168.0.11.

And make sure the firewall that comes with XP is not active and no firewall on 2K if you use TCP/IP. NetBeui will work fine with a typical firewall - it doesn't even notice the thing.

 

One step closer

Thanks for the response.

First, after installing NetBEUI on both machines, each machine is seeing it's own shared folders, not the others, on both computers A and B, under My Network Places.

Also, you mention to change IP addresses.
Can you clarify. Some of it is new to me.

Thanks again,

Frank

 

Frank - the only reason for suggesting TCP/IP was if diagnostics were needed. They still may not be.

XP, 2000, NT all demand to know "who" wants to connect before allowing it. They figures out who based on comparing the logon with user accounts they knows. For your system, that will mean having a copy of each logon stored locally as a user on both PCs.

Easiest is to simply use the same username/password to log on to both PCs. Other options are to enable the guest account (disabled /w XP-Pro by default at install time as a security measure) or to add both user accounts to each PC. For that you will need to be using an account other than administrator to log on.

In this instance the passwords have to match as well as the username and the password is case sensitive.

 

Thanks, I'll check that the next time.

One more thing, I noticed that when I installed NetBEUI on XP as per your reply, I added it to network card, but it does not appear for direct connection under Network Connections. On 2K, it appears for both connections.

Could that be a problem?

 

It surely could be. Any protocol to be used by a connection needs to be "bound" to the connection.

Also, with DCC (direct cable connection), it's a good idea to only have a single protocol active on that connection. You don't have that much resource with DCC and don't need to lose any to additional overhead you can do without. So, TCP/IP or NetBeui for the DCC. With the ethernet (network cards) if they are wired, it won't make any difference. Wireless is a different story and should be run as lean as possible just like DCC.

 

Okay, if that could be a problem then I have a question.

How do I bound it to DCC?

When I right-click and go to properties for DCC, that protocol does not appear for DCC. Even after installing it as per instructions from Microsoft.

Where do I put the two drivers that I installed previously so the DCC properties will see them.

Thanks, your replies are appreciated.