Laptops (2) connected by Crossover cable..can ping but cannot access?

Windows 10 Pro Version 1909 (OS Build 18363.752)

Hi Everyone!

I've worked on this problem for over two weeks now and applied every possible "fix" I could find.

I'm attempting to transfer things from my old laptop to my new laptop by direct connecting with Crossover cable. I realize I could use other methods to move these documents but I'm confused that some of these methods seem to have worked for some, but not for others.

My biggest fear now is that because of my intense focus on solving this problem, perhaps I've missed something really elementary...if so, I apologize in advance.

If there's anything else I've neglected, please let me know.

Many thanks,

Jerry


 Connected both laptops together with Crossover cable
o Toshiba Tecra connected to Dell XPS-15-7590

 Turned off McAfee Firewall

 Disconnected wireless WiFi

 Mapping Nework Drive also failed

 Changed advanced sharing settings on both laptops
o Private Networks:
 Turn on network discovery as well as automatic setup of devices
 Turn on file and printer sharing
o Guest or Public Networks:
 Turn on network discovery
 Turn on file and printer sharing
o All Networks:
 Turn on sharing so anyone with network access can read and write files in the Public folders
 Use 128-bit encryption to help protect file sharing connections (recommended)
 Turn off password protected sharing

 Changed Adapter Settings (Internet Protocol Version 4) on both laptops
o Change to “Static IP Address” on both laptops (192.168.1.10 & 192.168.1.20)
o Enable NetBIOS over TCP/IP found under WINS tab on both laptops

 Installed “Reliable Multicast Protocol” on both laptops

 Shared specific drive or folder with full control on Source PC

 Enabled SMB 1.0/CIFS File Sharing Support on both laptops

 Windows Credentials added to both laptops

 Changed LAN Manager authentication level on both laptops
o Select “Send LM & NTLM - use NTLMv2 session security if negotiated”

 Enabled TCP/IP NetBIOS Helper in Services on both laptops

 Delete “HardwareID” and “Store” keys in MSLicensing on both laptops

 Disabled the Master Browser on both laptops

 Lanman Workstation changed to “Enable insecure guest logins”

 Edit Hosts File to add IP Address & name on both laptops

Have you shared folder and given everyone permission have you then set NTFS permissions. You seem to be connecting to the pc not a share ie jerry-pc instead of \\jerry-pc\sharename

Another point windows doesnt like - in computer names rename pc to gerrys

try cmdline

net use s: \\gerrys\share

Hi Samuria,

Thanks for your response.

Computer "A" is named JERRY-PC
Computer "B" is named XPX-15-7590

From Computer B, I can successfully ping Computer A by typing "ping jerry-pc" (using name instead of IP Address)

However, from Computer A, I can't ping Computer B by typing "ping xps-15-7590" (using name instead of IP Address)

Also, I can see the "other" laptop on File Explorer from both laptops, but when I click on the "other" laptop name to open or expand the directory, I get the error messages shown.

I've shared the "desktop" folder on each laptop but can't expand these directories to access the shared drives within.

Thank you,

Jerry

- - - Updated - - -

Thank you Berton,

Yes, I'm aware of Laplink however I wanted to solve the mystery of why this won't work. There are literally hundreds of "solutions" in the internet but most threads simply fizzle out and I'm assuming they didn't work...lol.

I also have a QNAP Nas which I could use wirelessly from backup however I'm told the direct cable setup is faster. I may have to give up soon and use another method.

Thank you again for taking the time to respond,

Jerry

Hi Everyone!

I was able to Map the drives successfully. Now I can access each laptop from the other one.

I'm still perplexed as to why I can't connect to the other laptop under "Network" (JERRY-PC and XPS-15-7590).

Is it perhaps because I'm trying to connect to the entire drive of each laptop?

Any thoughts?

Jerry

As mentioned windows network doesn't like names with - and other none standard names

C and every hd are shared as admin shares is c$ d$ you need an admin account to access it