Windows 10: Problem Sharing Files Between 2 W10 Laptops

Hi all I hope this is the correct place to post this question.

So i have 2 Toshiba laptops and I have them in a workgroup so that Laptop 1 (1803) can sync files with Laptop 2 (1803) using Free File Sync.

I rebuilt Laptop 2 using Macrium the other day and now I cant seem to see Laptop 2 from 1.

I have tried to re add Laptop 2 to the workgroup and also reshared the folders that I want to share.
In doing this I have added the group Everyone and given it Read/Write permissions
Ive also checked that network sharing is on too.

What am i doing wrong

and is there a better more secure way to do this? essentially I just want to sync some files between the 2 laptops

TIA Bart

:)

 

Issue with accessing shared files on Homegroup

Original title: Homegroup Issue

<p>I have a laptop and a desktop both running W10 home.&nbsp; Homegroup on both.&nbsp; Each can see the others shared files, pics, etc..&nbsp; The laptop can access the shares on the desktop.</p><p></p><p>The problem is that when I try to access the shared
file on the laptop from the desktop I get an error message:



I have tried many solutions from other sites, but they don't related directly to W10. Many of the methods suggested seem to call for steps that cannot be done on W10.

 

W10 cant access WS2008 file shares

I have the following setup:

Server: Proliant series, with my required folders shared with 'Administrators', WS2008

Clients:
2 Laptops, W10 Home installation |
1 Desktop, W10 Pro installation

All are connected to the same router, there is only 1 router which is also our internet gateway

Previously

Whenever I wanted to retrieve or store files on the server, I would navigate to it through explorer \MY-SERVER\ and be prompted for login credentials. I provided the Administrator credentials and I could then see and interact with the file shares, as expected. This was true of all clients on the network.

Changes

Yesterday an order for a new mobo/cpu arrived for the Desktop. After installing these I flattened the boot drive and reinstalled W10 (for good house keeping)

Now

If I try to access the server (nav to \MY-SERVER) I am presented with the following message:
"Windows cannot access \MY-SERVER\

You do not have permission to access \MY-SERVER. Contact your network administrator to request access"

It is not even prompting me for login credentials. Whats curious is that if I navigate to a specific shared folder, eg \MY-SERVER\stuff, then I AM prompted to login (after a long pause), but the login dialog is captioned "Access denied", and providing the correct login credentials presents a similar Network Error message.

The server also does not appear in the list of network places on the Desktop. The other clients (2 W10 laptops) can still see and access the Server as normal.

Notes

• The desktop can reach the server through ping and Remote Desktop (I
  would just live with it and copy files through the tsclient share
  which appears during an RDP session, but I cannot stream files this
  way).
  
• The server has not stale credentials in Credential Manager
  
• All systems are in the same workgroup (WORKGROUP)
  
• Reg keys for 'restrictanonymous' are set to 0, although this surely would not affect an authenticated login anyway?
  

What am I doing wrong? Why is the W10 Desktop not able to access the shares in the same way the other W10 clients can?

 

How to file share between 2 pc's only?

Ok I've been looking all over the net and cant find a clear way to connect my pc and laptop to each other. I have a router Linksys 160N. The problem is I charge my neighbor $20 a month to use my network wireless only. They have 3 pc's on it. I have 3 pc's and 2 laptops on it. No im not having lag. The question is how in a step by step way how can I connect my new laptop and my main pc to each other over the network only. secure of course to be able to get any file from each of the 2 comptuers anytime I want.

The os im using is windows 7 home premium 64

details please i am a bit of a noob when it comes to this.

thank you