Connect Windows 7 to Mac El Capitan

I have a couple earlier threads relating to my efforts to get my Windows
computers to connect to my iMac.

I had a good portion of it working, and then one day, nothing worked.
The Windows systems would not connect with each other.

What is really interesting is, the iMac simply worked, I could connect
to all of them, and transfer files.

After a bunch of web searching, I found an MS Win10 site that told me
how to reset items back to "new" from the command prompt. netsh and
ipconfig

After that, back in business, almost.

W10 and W8.1 work fine with the iMac. Windows 7 Ultimate, Starter, and
Vista Ultimate do not.

The iMac shows up under Network twice, but can't connect to it, for all
3 systems. The iMac connects to them just fine.

Error code: 0x80070035 The network path was not found

Any ideas on how to fix this?


--
Ken
Mac OS X 10.11.6
Firefox 53.0.2 (64 bit)
Thunderbird 52.0
"My brain is like lightning, a quick flash
and it's gone!"

Ken Springer wrote:
I have a couple earlier threads relating to my efforts to get my Windows
computers to connect to my iMac.

I had a good portion of it working, and then one day, nothing worked.
The Windows systems would not connect with each other.

What is really interesting is, the iMac simply worked, I could connect
to all of them, and transfer files.

After a bunch of web searching, I found an MS Win10 site that told me
how to reset items back to "new" from the command prompt. netsh and
ipconfig

After that, back in business, almost.

W10 and W8.1 work fine with the iMac. Windows 7 Ultimate, Starter, and
Vista Ultimate do not.

The iMac shows up under Network twice, but can't connect to it, for all
3 systems. The iMac connects to them just fine.

Error code: 0x80070035 The network path was not found

Any ideas on how to fix this?

Your 0x80070035 is here.

https://social.technet.microsoft.com...tpronetworking

*******

Three versions (SMBV1, SMBV2, SMBV3) plus dialects.
WinXP has SMBV1. The rest could share SMB2. Win10 might
have SMBV3. Each version has slight differences in feature
set (not important enough for me to look up).

Link encryption includes 40 bit and 128 bit. WinXP might be
40 bit. I don't think this is particularly a gating item.
While (maybe) you could force a machine to use only 128 bit,
then the WinXP machine would presumably be locked out on
a negotiation failure.

NetBIOS is used for discovery.

Normally, the OS will pester you to enable sharing and printing,
and network discovery might be part of that.

WannaCrypt caused the release of a number of patches.
Without the patches in place, disabling SMBV1 was considered
a (clumsy) option. That would disconnect WinXP. I don't think
the patches necessarily harm anything, but the patch for WinXP
did cause my WinXP machine to be isolated. Uninstalling the WinXP patch
would make it work again. And this is an issue with that OS install,
as other WinXP users don't see this problem.

AV products and their firewalls, have been known to upset file sharing.

Wireshark has a "dissector" for file sharing protocol, and
can display information in the negotiation packets. But it
leaves you with a rather large bitfield to sort through,
and I don't consider that to be a "big help". When my networking
broke, the symptoms were "receiving machine says 'need more info'"
when I was expecting the sending machine to be the laggard. And
then I couldn't find any articles which could hint at what
the "more info" was.

On the Mac, I experienced a lack of "pacing" in the protocol.
The Mac would put up a username/password box, but by that time,
the Windows machine had given up and dropped the connection.
If you did enter a username/password and send it, the other
machine wouldn't do anything, because it didn't seem to be
expecting it. I would not count on the Apple implementation
to always work. That might have been MacOSX 10.2 or 10.3.

Paul

On 9/2/17 6:25 PM, Paul wrote:
Ken Springer wrote:
I have a couple earlier threads relating to my efforts to get my Windows
computers to connect to my iMac.

I had a good portion of it working, and then one day, nothing worked.
The Windows systems would not connect with each other.

What is really interesting is, the iMac simply worked, I could connect
to all of them, and transfer files.

After a bunch of web searching, I found an MS Win10 site that told me
how to reset items back to "new" from the command prompt. netsh and
ipconfig

After that, back in business, almost.

W10 and W8.1 work fine with the iMac. Windows 7 Ultimate, Starter, and
Vista Ultimate do not.

The iMac shows up under Network twice, but can't connect to it, for all
3 systems. The iMac connects to them just fine.

Error code: 0x80070035 The network path was not found

Any ideas on how to fix this?

Your 0x80070035 is here.

https://social.technet.microsoft.com...tpronetworking

I found that before posting. But after reading the first two
paragraphs, and looking at the date (2010), concluded the info wasn't
much good to me.

Now that you've mentioned the post, I've tried everything in it, and
some other possibilities I've found, all to no avail. I can't even find
a dialogue for NetBios, TCP/IP. or WINS.

*******

Three versions (SMBV1, SMBV2, SMBV3) plus dialects.
WinXP has SMBV1. The rest could share SMB2. Win10 might
have SMBV3. Each version has slight differences in feature
set (not important enough for me to look up).

No clue what you are talking about. LOL

Link encryption includes 40 bit and 128 bit. WinXP might be
40 bit. I don't think this is particularly a gating item.
While (maybe) you could force a machine to use only 128 bit,
then the WinXP machine would presumably be locked out on
a negotiation failure.

NetBIOS is used for discovery.

Discovery and File and Printer sharing is turned on, one of the first
things I did when starting this networking project. Also Password
Protected file sharing is off. The same settings are on W8.1 and W10.

Normally, the OS will pester you to enable sharing and printing,
and network discovery might be part of that.

WannaCrypt caused the release of a number of patches.
Without the patches in place, disabling SMBV1 was considered
a (clumsy) option. That would disconnect WinXP. I don't think
the patches necessarily harm anything, but the patch for WinXP
did cause my WinXP machine to be isolated. Uninstalling the WinXP patch
would make it work again. And this is an issue with that OS install,
as other WinXP users don't see this problem.

AV products and their firewalls, have been known to upset file sharing.

Wireshark has a "dissector" for file sharing protocol, and
can display information in the negotiation packets. But it
leaves you with a rather large bitfield to sort through,
and I don't consider that to be a "big help". When my networking
broke, the symptoms were "receiving machine says 'need more info'"
when I was expecting the sending machine to be the laggard. And
then I couldn't find any articles which could hint at what
the "more info" was.

On the Mac, I experienced a lack of "pacing" in the protocol.
The Mac would put up a username/password box, but by that time,
the Windows machine had given up and dropped the connection.
If you did enter a username/password and send it, the other
machine wouldn't do anything, because it didn't seem to be
expecting it. I would not count on the Apple implementation
to always work. That might have been MacOSX 10.2 or 10.3.

I don't even get the option of entering a username or password for the Mac.

One web suggestion was to create an entry in the Credentials Manager.
Also did not work.

Perhaps you should consider a used Mac! LOL El Capitan is 10.11, and
the current OS is MacOS Sierra, 10.12, with another new one due this
fall, I believe. I'm sure there's a lot of changes. G

--
Ken
Mac OS X 10.11.6
Firefox 53.0.2 (64 bit)
Thunderbird 52.0
"My brain is like lightning, a quick flash
and it's gone!"

Ken Springer wrote:


I don't even get the option of entering a username or password for the Mac.

Then that is a good thing (tm).

One web suggestion was to create an entry in the Credentials Manager.
Also did not work.

Oh, well.


Perhaps you should consider a used Mac! LOL El Capitan is 10.11, and
the current OS is MacOS Sierra, 10.12, with another new one due this
fall, I believe. I'm sure there's a lot of changes. G


My machine was bought for a specific reason, namely it was the
last box that would run most of my Mac stuff. It's a crossover box,
and has MacOS as a VM (like WinXP Mode), as well as MacOSX.
All on PowerPC. It's a Mac from before the switch to Intel.
I even had Connectix Virtual PC on it, running Win2K at the time.
It was used mainly for desktop publishing jobs (writing specs),
some of which would be 500 pages long. If I needed to work at home,
that's what I used.

Paul

On 9/3/17 12:44 AM, Paul wrote:
Ken Springer wrote:


I don't even get the option of entering a username or password for the Mac.

Then that is a good thing (tm).

One web suggestion was to create an entry in the Credentials Manager.
Also did not work.

Oh, well.


Perhaps you should consider a used Mac! LOL El Capitan is 10.11, and
the current OS is MacOS Sierra, 10.12, with another new one due this
fall, I believe. I'm sure there's a lot of changes. G


My machine was bought for a specific reason, namely it was the
last box that would run most of my Mac stuff. It's a crossover box,
and has MacOS as a VM (like WinXP Mode), as well as MacOSX.
All on PowerPC. It's a Mac from before the switch to Intel.
I even had Connectix Virtual PC on it, running Win2K at the time.
It was used mainly for desktop publishing jobs (writing specs),
some of which would be 500 pages long. If I needed to work at home,
that's what I used.

As soon as I saw that Apple was now going to replace OS X with MacOS, I
did get a chuckle. Maybe they are "going back to their roots". LOL

I forgot to mention, I can ping the Mac just fine from the command window.


--
Ken
Mac OS X 10.11.6
Firefox 53.0.2 (64 bit)
Thunderbird 52.0
"My brain is like lightning, a quick flash
and it's gone!"