Windows cannot Access......<computer name>

[Peter H Williams]

I have tried several times to connect an older W10 PC with my W11 PC and fail to achieve my goal. I get same sort of error on both machines.

The File Sharing etc all seems to be correct. I can't 'see' the two PC's across the network but can't access the files

Any help appreciated

From W11

From W10

The PC Names seem to be correct

The Network names are different - but both access via the same Network / router / switch ( both plugged into switch located on my desk which then connects to the Router)

 

[Peter H Williams]

A further 3 files from W10.

I am still baffled. So many of the names are similar - one place the name is all CAPS elsewhere may not be the case etc

Both PCs have the professional version of the OS - so I thought I'd try and use remote desktop (to establish that a network can be used) which seems so simple to set up - but again failed
Still another observation my 'file sharing' server - uses the WELINE app and shows as the Linux / Icon device CD2510 can be accessed readily from both machines. The Weline app was just plug and play with no problem

 

[ChatGPT]

Your frustration is completely justified—after a full OS rebuild, sharing and Remote Desktop should be far simpler. Some plug-and-play apps or NAS devices (like your WELINE/CD2510 Linux device) just work, while Windows insists on rules, legacy baggage, and sometimes, almost comically strict or obscure configuration requirements.
Let’s address your immediate obstacles and observations:

---

1. Names, CAPITALS, and User Confusion​

• Windows is not case sensitive about computer names or usernames, but misalignment between account display names and actual user folder (profile) names can cause confusion, especially for sharing and remote desktop.
  • Renaming a user in Control Panel does not rename their C:\Users\ folder or SID. For true clarity, it’s best to create a new user with your desired name and move your files if you want everything both "visibly" and "internally" aligned—a known Windows quirk.
• Remote Desktop and file sharing care more about correct username/password and permissions than the exact computer name formatting.

---

2. Remote Desktop Not Connecting (But File Share Works for NAS)​

• If both PCs are Windows Pro, RD should “just work” once enabled, unless:
  • RD is not allowed by Windows Firewall.
  • The user you log in as does not have a password set, or is not in the allowed users list.
  • Network profile isn’t set to Private.
• Double-check:
  1. Enable Remote Desktop:
     Settings > System > Remote Desktop > “Enable Remote Desktop”
  2. Firewall Exception:
     Control Panel > Windows Defender Firewall > Allow an app… > Remote Desktop checked.
  3. Correct User:
     Edit allowed users (Settings > System > Remote Desktop > Advanced settings > Select users) to include your current user account.
  4. Password Required:
     You must have a password set to connect via RD.

If you still can't connect, check for specific error messages—they will point to missing permissions, credentials, or network profile/firewall issues.

---

3. Why Linux NAS "Just Works" and Windows Shares Don’t​

• Devices like your CD2510 often use legacy SMB1 and allow totally anonymous guest access. Modern Windows, by contrast, disables SMB1 by default (for security) and blocks unauthenticated shares unless you relax sharing and security settings.
• For quick Windows-to-Windows troubleshooting, be sure to temporarily disable password-protected sharing and assign “Everyone” permission to the test share for diagnosis. Once working, you can harden security.

---

4. Key Steps to Try—ALL in One Place​

Here’s your simplest post-reinstall checklist:

1. BOTH PCs—Private Network/Discovery/File Sharing:
   • Network set to Private.
   • Network discovery and file/printer sharing enabled.
2. SHARE—Folder permission for "Everyone" (Sharing tab), Read or Full Control.
   • Security tab: “Everyone” added with Read or Modify (test only).
3. ACCESS—Use IP address, e.g. \\192.168.1.x\YourShare
   • If prompted, give full username as:
     • COMPUTERNAME\Username or
     • MicrosoftAccountyour@email.com (if using Microsoft account).
4. FIREWALL—Temporarily turn off on both sides.
5. Remote Desktop:
   • Enable as above.
   • Make sure allowed users, password set, and firewall exception enabled.

If this still doesn’t work, please share the exact error messages (text and/or screenshot)—that pinpoints the issue directly (e.g., “user not allowed”, “network path not found”, “unable to connect”, etc.).

---

Final Reassurance​

• You are NOT alone. Even seasoned IT pros have spent hours untangling Windows peer networking—meanwhile, Linux- or app-based devices happily bypass half of this by using legacy guest protocols or simpler permissions models.
• Once you get even a single simple shared folder or RDP connection working, you can safely build back up to a more secure setup (restore strict permissions, enable password protections, etc.).

Let me know:

• The exact error when RDP fails.
• If you see any specific text when share access fails.
• If you need a sanity check on usernames, system names, or any output.

I’ll help distill this to a solution that just works—no more guesswork. And if you want, we can go step-by-step, screenshot by screenshot.
Hang in there—your perseverance will pay off!

 

[Peter H Williams]

We have visitors for a few days so my time is limited !
Just don't understand why this is so incredibly difficult.
I just can't help feel I am doing the same thing time after time and hoping for a different result
I thought Remote Desktop would be straight forward and maybe give a clue to the problem - but not so.
I have tried connections from both computers. Details attached
Is there perhaps an app or third party software that may help.

Almost 60 years in IT and hate to be defeated like this

 

[ChatGPT]

Absolutely understood—sometimes taking a step back (or spending time with visitors!) is the best plan when tech throws up roadblocks. As someone with decades of IT experience, you know perseverance counts, but so does recognizing when Windows networking is being utterly absurd.
You’re right, Remote Desktop and plain old file sharing should be simple.
Windows networking sometimes “remembers” weird states, stubborn firewalls, or hidden settings that even experts can spend hours wrangling.

---

Answers to Your Questions​

1. Why Is This So Difficult?​

• Windows’ home/pro peer-to-peer networking has legacy protocols (NetBIOS/SMB), security layers, and evolving defaults that sometimes work against simplicity—especially after updates, mismatched names, or fresh installs.
• Tools like your plug-and-play network storage "just work" because they default to open guest access, often using SMB1 (which Windows disables for security).

2. Remote Desktop as a Clue​

• If RDP won’t work either, even with correct credentials and firewalls off, it can point to deep network isolation, stuck network profiles, or even policies.
• If RDP and file sharing both fail, it’s usually a network configuration, firewall, or “profile” issue, not just file sharing alone.

3. Am I Missing a Tool or App That Just Works?​

Yes!
If you simply want to reliably share files without battling Windows SMB/folder sharing quirks—here are battle-tested alternatives:

A. Free Third-Party Apps for File Transfer​

• TeamViewer (with built-in file sharing/remote access; works even if RDP breaks)
• AnyDesk (lightweight remote + file transfer)
• Syncthing (secure, real-time, networked folder syncing, no Windows sharing required, easy setup)
• WinSCP (if you enable SFTP on one PC, e.g., via installing OpenSSH server)

B. Classic Network File Managers​

• Total Commander with LAN plugin, or Double Commander, allows browsing SMB shares with more helpful error messages.
• FileZilla Server lets you set up a dead-simple FTP, accessible from any client—even SMB-broken ones.

C. USB Stick​

• Not glamorous, but always works. Sometimes, worth it for sanity's sake.

D. Resilio Sync (formerly BitTorrent Sync)​

• Great for peer-to-peer, encrypted folder syncing between PCs—even with network oddities.

---

Your Next Step​

• Take a break. Let the absurd complexity of Windows networking wait!
• When you return, if you want, upload the error details/screenshots from RDP and sharing attempts—exact error texts are gold.
• Or, if you want true plug-and-play, grab Syncthing on both PCs, set a shared folder, and marvel as it “just works” over your LAN (and Internet if needed).

---

Final Thought​

You can absolutely “win” at this by switching tools if Windows won’t play ball.
Decades of experience don’t inoculate anyone from Microsoft’s networking madness—some battles are best won by choosing your weapons. You haven’t been defeated; you’ve just hit the limit of what’s reasonable to expect from legacy file sharing.
If you want to dive deeper after your visitors leave, just say the word—I’ll help you comb every log, script, or screenshot if needed. Or help you get Syncthing up in minutes and move on with your life!
Enjoy your company and take heart—you haven’t lost, you’ve just witnessed an enduring IT mystery at its finest.

 

[Peter H Williams]

By way of explanation.

I have this old W10 PC with 500 gb.
I could use this to run some long running tests from time to time (Forex Trading software - MetaTrader)
I also figured I could use 'Storage Spaces in Windows' to provide some easy to use file space via the Network. I'd need 2 additional drives (sata SSD).
However I need to establish reliable network access and ability to run backup schedules etc before I start with additional drives.
The Orico CD2510 is pretty useless for what I want - looking to return and refund

I'll look at the options suggested and give Windows Network File Sharing a miss for the time being.

 

[ChatGPT]

That’s a very rational and strategic approach. Your plan makes excellent sense:

• Repurposing your W10 machine for long-running tasks and backup/storage duties is a great way to extract value from older hardware.
• You’re right to want reliable network access before investing in new drives or configuring Storage Spaces. Being able to automate backups, run jobs, and easily move files are table stakes.

---

Quick Thoughts On Your Plan​

1. Storage Spaces for Network File Server​

• Storage Spaces is a solid, flexible option for pooling drives. For sharing over the network, you’d still be interacting with Windows File Sharing (SMB)—so, yes, reliable SMB/config is critical before committing.

2. “Easy-Use File Space”—Alternatives​

• Given the headaches with SMB, solutions like Syncthing, TeamViewer/AnyDesk’s file transfer, or even a simple third-party FTP/SFTP server can be less hassle.
• Syncthing is especially robust for automatic, cross-device file sync and versioned backup—even over flaky LAN conditions, and works seamlessly regardless of what Windows thinks of its network names.

3. Automated Backups​

• Whether using built-in Windows Backup, third-party (e.g., Macrium Reflect, EaseUS ToDo, AOMEI), or scripting (PowerShell + Robocopy), reliable, visible network shares are important for targeting your files.
• If you use Syncthing or FTP, many backup tools can target those folders just as easily as standard shares.

4. MetaTrader Headless/Remote​

• MetaTrader and similar software can run fine over RDP, VNC, or even in a self-hosted virtual machine if your backup processes require separation or resilience.
• If you can’t get RDP working, TeamViewer or AnyDesk can fill the gap with minimal setup.

---

About Orico CD2510​

• Your instincts are right—these “simple” NAS-like enclosures sound good, but if they lack robust user management, backup scheduling, or protocol support, they can quickly become more trouble than they’re worth for even lightly advanced use-cases.

---

Closing Advice​

• Give yourself a break from battling SMB for now.
• Try Syncthing or similar for file operations—it works even across very differently configured systems without fuss.
• When you’re ready to set up Storage Spaces and need targeted advice (on best RAID/backup strategies, drive choices, or network sharing tweaks), just ask.

---

Useful Reading:
Storage Spaces in Windows - Microsoft Docs

---

If you ever want to give SMB one last try, or need help translating a Syncthing/FTP setup into “backup friendly” automation, I’ll be here with step-by-step instructions—no more stabs in the dark.
Good luck, and enjoy peace of mind with your next solution!

 

[Peter H Williams]

A brief update - by way of interest.

My old W10 PC is not in regular use but I am just reluctant to 'dump' it. Can use for some testing of FOREX / Metatrader applications.
I managed to use a software product called D-Lan - which enables both PC's to communicate with each other.
Microsoft 'refused' to upgrade my W10 PC to W11 ...but... I cam across a Youtube video clearly showing how the upgrade can be done legitimately approx 20 minute video see youtube here

I had already done a 'clean' installation of W10 so now have a 'clean-ish' version of W11 - I'll say great.
The real surprise is that my newer PC with W11 can now access the Old upgraded W10 to W11 PC via the network - fantastic. However I still get the same error messages the other way round.

As stated before not a major do list and now have 1TB additional space on my newer W11 PC, have 250gb available via a USB SSD and of vcourse the like s of D-Lan, Google drive (and email)

 

[ChatGPT]

Thank you for sharing such a clear summary and update—this is actually a textbook case of perseverance paying off, as well as proof that “third-party” network tools can often succeed where Windows native sharing stumbles!

---

Key Points from Your Update​

1. D-LAN Success​

• D-LAN is a smart peer-to-peer LAN file sharing tool, and it reliably bypasses all the usual Windows SMB/network neighborhood headaches. For local file transfers, it’s fast and nearly foolproof.

2. Windows 10-to-11 Upgrade​

• Your upgrade from W10 to W11 via alternative method is valid, and as you noted, results in an even more "clean" install that often clears stubborn registry or policy glitches blocking sharing.

3. Network Access Now Working (in One Direction)​

• The fact that your “old” PC, now running W11, is accessible from the newer W11 PC—but not vice versa—is classic in Windows peer networking:
  • Newer, clean installs often have fewer legacy restrictions, and firewall profiles are updated.
  • Sometimes share visibility only works one way due to local firewall rules, account permissions, or Windows still using "private" vs. "public" network profiles unevenly.

4. Expanded Storage and Cloud Options​

• With your 1TB local, 250GB SSD, and integration of D-LAN and Google Drive, you’re now in a strong data management position—everything you need for testing, backups, or even cloud syncing/remote file retrieval.

---

What’s Left (If You Ever Want to Fix the Final Piece)​

If you want your upgraded W11 (formerly W10 machine) to access shares on your "main" W11 PC:

• Double-check that the necessary folders are shared on the "main" PC, with “Everyone” or appropriate user permissions.
• Verify that the “main” PC is on a Private network profile, with discovery enabled.
• Make sure no third-party security tools are blocking inbound connections.

But as you've already discovered, D-LAN and similar tools make this almost irrelevant in practice for file moving and backup purposes.

---

Final Notes​

Your approach is now essentially “platform agnostic”:

• D-LAN (or similar) makes file transfer truly cross-PC and set-and-forget.
• Cloud sync covers critical redundancy and remote sharing.
• USB SSD covers you for fast, large local copies or "grab and go" scenarios.

---

In short: Mission accomplished.
You’ve turned stubborn hardware into a flexible, productive, and easy-to-maintain data environment. If you ever want to polish off Windows native sharing for the intellectual challenge, just reach out—otherwise, you have a robust, no-hassle solution in place!
If you ever need help with:

• Storage Spaces setup and best practices,
• Automating file syncs or backup routines,
• Or maximizing your new “clean” Windows setup,

just let me know. Enjoy your newly unlocked storage and streamlined file moves!