Connect Win 7 PCs to Win 10 PC

I have a WIn 7 PC and my wife a Win 10 laptop PC.

ATM I can see my PC from her PC and actually open it and view, create, edit etc files. I have streamed media as well.

But while I can see her PC on mine, if I try to open it, I am not allowed to: my PC says
"Windows cannot access \\XXX-PC. Check the spelling of the name, or there might be a problem with your network. Click diagnose"

Error code 0x80070035
The network path was not found

The name is generated by the network onto my PC, and is the correct spelling of my wife's PC's name.

Diagnosis results in
"Make sure that the device or resource (XXX-PC) allows incoming connections for file and printer sharing"

I have definitely set File and Printer Sharing to ON. I am not aware of any incoming switch.

I have disabled the Windows firewall on her PC. She has Comodo Security installed, vanilla, as have I.

We are definitely on the same server, as she can use my PC and I can actually see her PC, just cannot access it. At this stage I have not even been asked for any passwords etc.

I am successfully connected to another PC on the network. That other PC (also a Win 7 machine) Has the same trouble as my machine: it can "see" but not access my wife's machine

Can anyone help? ATM the situation is exactly the opposite of what I want, because the whole idea is that I can back up her machine over the network.

Any help appreciated.


Discussion is locked

Reply to: Connect Win 7 PCs to Win 10 PC
PLEASE NOTE: Do not post advertisements, offensive materials, profanity, or personal attacks. Please remember to be considerate of other members. If you are new to the CNET Forums, please read our CNET Forums FAQ. All submitted content is subject to our Terms of Use.
Reporting: Connect Win 7 PCs to Win 10 PC
This post has been flagged and will be reviewed by our staff. Thank you for helping us maintain CNET's great community.
Sorry, there was a problem flagging this post. Please try again now or at a later time.
If you believe this post is offensive or violates the CNET Forums' Usage policies, you can report it below (this will not automatically remove the post). Once reported, our moderators will be notified and the post will be reviewed.
- Collapse -
This area is all about permissions and accounts.

So when we share we must authenticate as a valid user. This confounds some so please think about it.

When you connect to the other PC you are logged into yours with a name and password. This name and password (the account) must exist on the machine serving up the share or "I don't know you."

- Collapse -
Thanks, but...

That does not sound right to me.

I would have thought that the login to the remote PC was not necessarily the same as the login to my own PC. Should there not be a separate login that is required of me when I try to access the remote PC? They are two separate things, surely. On m y wife's machine I need to create an account that can have any user name and password, as long as I know what they are and am asked to enter them when I try to contact that machine.

Anyhoo, I have set up a User and password on her machine, that matches the one I log on with onto my own PC, just to see if it helps, and still my wife's machine has "no path", although I can see it as a PC on my machine. I have never been asked to log in to her machine at any time when trying to net with it. It has never got that far.

The third machine and my machine work fine in both directions.

- Collapse -
Give it time.

Nope. Network access to shares is done by user authentication unless you turn on the guest account. I'd rather work this with you rather than you tell me you don't think so. If you say so I have to leave you as you are and not work the most common problem I run into on Windows Shares.

So my test is simple. I log into the first PC as Bob and password dynomite. OK I walk to the machine that is serving up the share and I get to the login screen to log on as Bob with the password dynomite. If I can't I found one reason the share is access denied.

If you made the share before this account (be sure it's an admin too) then unshare and reshare using the Bob account.

- Collapse -
There plenty of tutorials on this.

What we get into next is firewalls and security suites after we cover the basics.

- Collapse -
Message title

I have read tutes by the score, and have set up networks OK, as with my third machine.

Just for the record, Windows Firewall is off in all machines. I have Comodo security on all machines,mas far as I know default settings in all cases.

- Collapse -
Comodo's firewall.

I did run into that blocking even when disabled a while back.

If tutorials are failing then something is blocking or you may be discounting tutes and my advice. I'm just an old hand at networking since I wrote router code in the 90's. But I know folk get upset at working through the list. I have yet to use any other method because one time it's the accounts, then next the need to unshare, share and reboot and the next a firewall in some router.

Work the tutes, ask for help and I see the awful HomeGroup is laid waste below.

- Collapse -

I turned off the Comodo Firewall on my wife's PC and ...immediate success.

But of course I want her to have the FW. I started reading about ways to allow local networking and there was a lot of back and forth about the danger of allowing this and that.

Anyone help here, please? Comodo is installed and FW'd on both my and the loungeroom PCs as well and they are fine.



- Collapse -
Back to Comodo.
- Collapse -
I posted on their forum

Comodo is aggressive: many of the reported problems are for stopping too much, but I have used it for years. IMO its problems outweigh its solid protection..NOTHING has got through....and I lived through times when it was worse/rougher than now. They seem to learn from feedback. What more can you ask?

The Comodo forums have been excellent as well.

I have posted on their forums, to see what I get.

- Collapse -
Message title

OK. I am not trying not to work with you. I thought you said that the login to the server had to be exactly the same as my login to my own PC direct. That is not the case with my machine and the third, successful, machine. Anyway, as I said, setting it up like that made no difference. So I did try it anyway.

I log into my own PC as OldNick, my-password. I can also log in to the remote server machine, sitting in front of it and direct log in, as OldNick with my-password. But I still cannot remotely connect to the server machine, my wife's. The reason I am now using OldNick is that I tried deleting user Nick from my wife's machine and reinstating it, but her machine insisted that I use a new name. That's all I needed.

I un-shared everything and re-shared it. No better.


- Collapse -
Message Title

Just OOI. I have just realised that the third machine can see my PC, but does not see my wife's machine at all. As far as it is concerned, my wife's machine does not exist.

- Collapse -
Is this all done in Home Group?

That's nothing but problems. On my home LAN I abandoned Home Group on any windows computers and instead set those up with standard networking, which is in another area since W7 till now. Now even my linux computers can interact with windows computers too.

CNET Forums

Forum Info