Problem using direct parallel pc to pc connection

[Saur0n]

Im using a direct connection cable to connect my laptop to my desktop pc, ive set the laptop to be the host and the desktop pc to be the guest (the stuff that needs moving is on the laptop). The desktop pc connects fine at 4mb/s, but now im stuck, how can i copy some files to the desktop pc?

Any help would be appreciated thanks.

 

[rjkrash]

Did you use the connection wizard to det this whole thing up? The two rules for success are:
1. Never tell them everything you know.

 

[rjkrash]

If you did use the connection wizard on both computers make sure the same users are allowed to access on both machines.

right click on Network Neighborhood > Properties

in Network connections right click on the connection > properties and go to the user's tab and check who can do what. The two rules for success are:
1. Never tell them everything you know.

 

[rjkrash]

I just thought of something else...

Maybe you can only go one way at a time like incooming or outgoing. I reall don't know how this wrks!!! The two rules for success are:
1. Never tell them everything you know.

 

[rjkrash]

I sur cn typ cn't I... LOL The two rules for success are:
1. Never tell them everything you know.

 

[Saur0n]

Yep, i used a connection wizard. In network connections under network tasks i used create a new connection>setup an advanced connection>connect directly to another computer then set the laptop as the host and the desktop pc as the guest.

 

[rjkrash]

I'm outta ideas... I keep this thread marked maybe dilettante will com back with some fresh ideas The two rules for success are:
1. Never tell them everything you know.

 

[Saur0n]

"in Network connections right click on the connection > properties and go to the user's tab and check who can do what. "

in the users part i have the top box checked, it says "administrator" and ive checked the box near the bottom that says "Always allow directly connected devices such as palmtop computers to connect without providing a password"

BTW, the network connection i made on this laptop to make it the host is called "incoming connections" under "incoming". When the desktop pc is connected to this laptop, in the network connections, it says connected unauthenticated user or something :/

 

[Saur0n]

Ok, Thanks for giving it a go rj

 

[dilettante]

Greetings SaurOn, rjkrash, and any others we're all entertaining...

Sorry, I had duties that took me away from the computer for awhile. Then I came back and read the latest posts here, and went offline to thrash with my own DCC failure before attempting to offer any crumbs of advice here.

Here is my own situation:

|XPPro desktop| <-- TCP/IP --> |95 laptop|
|  DCC Host   | <- Parallel -> |DCC Guest|

So I had this working just fine - no need for IPX/SPX, no NetBEUI, no other creeping crud.

The XP Pro machine has a LAN adapater and across its LAN is a cable router to the Internet.

XP is set up as Host, and here are my Incoming Connections properties:

-General Tab-

Incoming Connections:
Generic Soft56K: unchecked
Direct Parallel (LPT1): checked
VPN: unchecked
Show Icon in notification area: checked

-Users Tab-

Users allowed to connect:
Administrator: unchecked
MyAdminUser: checked
MyPowerUser: checked
Guest: unchecked
all others: unchecked
Require all users to secure: unchecked
Always allow directly connected: checked

-Networking Tab-

IP Properties:
Allow callers to access my LAN: checked
Specify TCP/IP Addresses: checked
From: 192.168.123.1
To: 192.168.123.10
Allow calling computer to specfy: unchecked
Client for MS Net Properties:
RPC Service Tab:
Name Svc Provider: Windows Locator


I have several shares on each machine, the Win95 shares secured by a simple password. The XPPro shares available to "Everyone" at present. Note: yes I do use a "hardware" firewall ;-)

Ok.

So from the XP machine I can ping the 95 laptop by computer name as well as IP address. CAn ping XP from the laptop.

When I run WinPopup over there the XP machine can do NET SENDs which I can see at the 95 laptop. Sending to XP from the laptop through WinPopup works (by XP user name as well as computer name).

I can browse the shares on the 95 laptop from XP, though the laptop machine doesn't appear in my workgroup under My Network Places|Entire Network|Microsoft Windows Network as one would expect. I must first browse to the machine manually: Start|Run and enter \\machine to pop up WinExplorer open to my laptop -OR- open a WinExplorer window and enter \\machinename in the address bar.

After this it seems to persist - I think there is a 48 to 96 hour caching of this information in Windows.

The laptop can see the XP desktop in much the same manner, except there is an odd DCC feature/button called "View Host" which brings up an Explorer window that can only see the XP desktop's "printer" and "SharedDocs" (the latter a share generated during XP installation?). This window never contains my own shares. As said, for the 95 laptop to see XP shares I created, I must use the "manual browse to share" technique again (Start|Run \\machine).

Let's see... the DCC Guest laptop can see all my normal LAN resources, it can Telnet to my XP Pro machine's Telnet server by machine name (i.e. don't have to use IP address), can surf the Web, run Messenger programs.

Basically, I almost have a connection just like a real LAN connection.

 

[dilettante]

Dropping the "other shoe."

As I said in a much earlier post (yesterday) - this was all working a few days ago, then it got strange.

The XP Desktop could still do everything it ever had: ping the 95 desktop, see its shares, etc

But, the 95 laptop became suddenly "crippled."

It could no longer see shares on the XP dekstop Host machine - at all. The DCC "View Host" button DIDN'T EVEN APPEAR on the DCC Status dialog anymore!

The laptop could still get to Internet resources - and by name! Surfing to

http://www.yahoo.com

was trivial. MSN Messenger still came up by itself and announced 37 more pieces of spam in my HoTMaiL account.

I could Telnet to the XP desktop - but only by IP address, no longer by name. I could Telnet to Internet sites by name, but not to other Telnet servers on my own LAN!

NET SEND / WinPopup was completely crippled. NET VIEW timed out, returning nothing on both ends.

What could have changed?

I tweaked and diddled the laptop Network settings.

Went through the desktop Incoming Connections settings 100 times.

I downloaded MSDUN 1.4 for 95 and went through a rather nasty install.

Nothing.

Then I uninstalled DUN 1.4 (Add/Remove Programs), and removed ALL networking components: clients, adapters, protocols (shutting down and popping out the laptop's PCMCIA NIC).

Rebooted the laptop for the 1000th time.

Reinstalled DUN 1.4

Rebooted.

Touched nothing and fired up DCC and...

HALELUYAH! HALELUYAH! Sang the chorus.

For the 1st time in two days DCC was back in business.

Next I went into the laptop's Network settings and pruned a bunch of junk the DU 1.4 reinstall added, such as a Netware client, a few bags of stale stuff like NetBEUI, etc.

Rebooted again (god, wasn't networking a PAIN before Win2K?)

Whew! I didn't break anything this time.

Next, I popped in my PC-Card NIC and let Win95 install its drivers, then go through a nasty Network rebuild again. This time the installer was looking for stuff in a directory where the MSDUN CAB file lives, but it wouldn't take the files from the CAB at all, it wanted the pre-extracted files. What fun!

Well, this machine is slow enough that I'd been able to see what happened earlier as the filenames flew by on some of my previous 10,000 networking rebuilds. I just bashed "skip file" about 30 times. It was only trying to copy a bunch of stuff like Telnet.exe, arp.exe and so on that it had just copies not 10 minutes before!

Whew!

Reboot.

Uh. Uh... DCC is broken again! Arrrghh!

Hey - wait a minute. I was reading something in a knowledge base article, or maybe a readme file... hmmm. Something about a second network connection causing Windows to give up knowledge of the first one due to limitations... Now where WAS that???

 

[dilettante]

So...

Now I've had DCC functioning fully once more, and then I broke it again. *sigh*

I found a note in the DUN 1.4 release notes about default gateway woes with two network connections, but not about NetBIOS issues with two connections.

Where am I now?

Gee, when I had DCC working last week I had a 56K modem card in the slot instead of the NIC. I wonder...?

So I shut down and remove the NIC, restart DCC, AND EVERYTHING IS WORKING ONCE AGAIN!

Put the NIC back in, Win95 powers it up, but DCC continues to work!

Shut down the machine (leaving the NIC installed), power it back up, try starting DCC - and DCC is back in "crippled mode" once more.

Power down the card leaving it in the slot, restart DCC, and now I'm fully back in business!


So I have to conclude that there is a problem with DCC Guest machines that have a preexisting network interface active. Could this be related to your situation, SaurOn? Maybe my Incoming Connections settings give you an idea?

Gee, the laptop NIC didn't even have a cable attached.

Now I'll have to reverse roles (Guest/Host) and see what trouble I can get in!


I hope this is getting somebody somewhere - I'm about out of hair to pull out. ;-)

 

[rjkrash]

Quote from Q227148

... This issue can occur if you use the DCC protocol to send and receive, and the mIRC is using the IP address of the the network adapter that connects to the Internet. The computer is unable to establish a secure connection to itself. ...

Not exactly the same but a clue to what may be going on.
The two rules for success are:
1. Never tell them everything you know.

 

[rjkrash]

have you guys looked at this article?

http://support.microsoft.com/support/kb/articles/Q310/1/52.ASP

The two rules for success are:
1. Never tell them everything you know.

 

[dilettante]

Good thought, but yep, been there, done that.

I have TCP/IP as the only protocol on both ends.

Working fine now - as long as the NIC is shut off or taken out of the laptop.

 

[rjkrash]

dilettante

When you have DCC running and the NIC in the Laptop what are the IP addresses of the two "devices"? run "ipconfig /all"

Where do they get their IP addrsess from. Are the addresses both in the same Network?

(-: The two rules for success are:
1. Never tell them everything you know.

 

[dilettante]

rjkrash -

As a matter of fact, they are!

Remember, the NIC isn't plugged into the LAN at all. I mean, if'n I have a NIC, why use DCC?

I'm just using this laptop to test DCC for other possible uses.

But anyway... do you suspect this is the problem? The NIC's address is "leftover" from the last time it was LAN-connected. It got it from the DHCP server on the LAN.

Funny how these settings hang over even after "completely removing" networking, etc.

- dilettante (Bob R)

 

[rjkrash]

I suspect it is the issue. your comment -

So I have to conclude that there is a problem with DCC Guest machines that have a preexisting network interface active.

leads me to believe that TCP/IP is the culprit here. I'm off to do some more research re this... later... The two rules for success are:
1. Never tell them everything you know.

 

[dilettante]

Hmm...

Well, keep in mind that TCP/IP works FINE while in this situation. I can surf the Web, ping everything I can get a name for (DNS) or IP address for (everything), etc. etc.

What I CAN'T get to work is NetBIOS names and resources.
I think this is a problem farther "up the tree" than TCP/IP.

And the problem seems to be a "NetBIOS Client" problem on the laptop (guest). The host machine can see the guest's resources just fine!

And of course, without the NIC everything works, both ways.

 

[rjkrash]

I think that in effect you have a multihomed system when both DCC and NIC are present and thus may have to enable TCP/IP routing on one or both devices.

TCP/IP routing allows packets to be forwarded on a computer connected to a multihomed system.

To include TCP/IP routing in your configuration, you must enable Internet Protocol (IP) forwarding for the TCP/IP component.

To enable or disable IP routing

Right-click the TCP/IP component, and then click Properties.
Click the Routing tab.
To enable forwarding, select the IP Forwarding check box.

Or, to disable forwarding, clear the IP Forwarding check box. The two rules for success are:
1. Never tell them everything you know.

 

[rjkrash]

re your comment:

And the problem seems to be a "NetBIOS Client" problem on the laptop (guest). The host machine can see the guest's resources just fine!

You have turned off NetBios on the Laptop right? This thread is so long now i can't find your refence to what you turned on and off (-:. but any hew, have you looke at the LMHOSTS file on the laptop? Is the pc computername listed there? There may be a name service/ browser issue.
The two rules for success are:
1. Never tell them everything you know.