Networking NOT

Win 7 PC looks at the LAN and says it cannot see other PCs.

Win 10 PC on same LAN sees and can transfer files to that Win 7 PC that
is blind.

Are there any apps that can diagnose these damn networking problems?

I mean diagnose NOT some unintelligible packet presenter.

In article , says...

Win 7 PC looks at the LAN and says it cannot see other PCs.

Win 10 PC on same LAN sees and can transfer files to that Win 7 PC that
is blind.

Are there any apps that can diagnose these damn networking problems?

I mean diagnose NOT some unintelligible packet presenter.

Yes it's called "Educate Yourself". Sorry but unless willing to spend
money for someone else who knows what they're doing to physically look
at system, that's the way it is.

OTUser wrote:
Win 7 PC looks at the LAN and says it cannot see other PCs.

Win 10 PC on same LAN sees and can transfer files to that Win 7 PC that
is blind.

Are there any apps that can diagnose these damn networking problems?

I mean diagnose NOT some unintelligible packet presenter.

The actual network diagnostics aren't that good.

They hardly ever recognize a problem.

Your problem is a file sharing problem. If your browser
works, you don't have a networking problem, right ?
But file sharing is a bunch of other stuff. Encryption
and authentication.

*******

File sharing is called SMB (that's one name
for it). On Linux, they made a name of Samba from that.

This picture shows getting some info on Win10, about
the connections coming in. Unfortunately, I haven't
found anything that lists *failed* file sharing attempts.
Having such a tool would help a lot.

https://s15.postimg.org/ow77tu1jv/smb.gif

"get-smbconnection" is a Powershell command. Every OS
will have a different version of Powershell, and so
not all the commands are available everywhere. But
that one, shows the connections that have been made
and what version of SMB was used. SMB comes in several
versions, and Win10 has occasionally had a slight bug
in that stuff.

At one time, it would only use SMB3 and wouldn't fall back.
I've also had account problems, manifested by later versions
of Win10 tightening up permissions. The idea of "guest"
login has gone out the window. You might have to
log in with a common user account that all the
OSes have got. This is especially difficult if you
are using a Microsoft Account (MSA). Win7 might not be
using an MSA, while Win10 could be. But you should
be getting symptoms that tell you that. I had a bitch of
a time with the Win10 Insider edition keeping this
stuff running, and I got lucky on a guess one day as
to what they had broken. At first I couldn't figure it
out, why it wasn't working.)

While you could use HomeGroup, that's yet another set of
pieces of software, with its own problems. Yes, HomeGroup
setups get busted too, so there is no such thing
as "absolutely reliable" software. But if you haven't
tried HomeGroup before, you could give that a whirl.

I was working on a networking problem earlier today,
and I only worked on it long enough until "ping" worked.
Because I knew I didn't know enough to get the rest of
it working :-) And I'm still trying to find a tutorial that
isn't a half-baked Command Line session. I don't mind
Command Prompt sessions, if it really looks like it's
going to work.

So if Win10 was the "first OS that is easy-peasy",
it's a "giant fail" at it. It's no easier when
push comes to shove, than any of the OSes before it.
Just look at how busted Bluetooth is, for inspiration.
(It took me six tries, a number of reboots, a change
in order of booting, to do it. And I can't be sure
I've got the right ingredients yet.)

When file sharing works, you should feel honored,
then knock on wood that it doesn't go to hell on you :-)
Because there will be days when stuff like this happens.

Paul

Oops, sorry, different PC different user name.
No spanking 'cause I already kicked myself.

OK so I got my local LAN connection back.
I do not understand any of this and just tried all possible buttons and
links in the Network Sharing area.

I found that something changed my network from Private to Public.
Who did that ????

I then found that the LAN was disabled.
Who did that ???

I did a driver update there during this mess but the problem existed
before that. Realtek PCIe GBE Family Controller.

Also 802.11ac Wireless LAN Card. A WIFI USB to WiFi AC antenna thingy
that has always worked and given me super fast access to my WiFi side of
my home network.

Not me. I would not know how or why so I would not touch default
settings. I did ask me a long time ago and I did say Private but that
is all.

The LAN was working.
I installed a big bunch of Windows updates and that was probably what
screwed up my system.


Did I learn anything ? DO NOT DO UPDATES when every thing seems to be
working.

Thanks to all who participated.

OTUser wrote:

Did I learn anything ? DO NOT DO UPDATES when every thing seems to be
working.

Thanks to all who participated.

Correct.

And you figured out the root cause.

When you re-install the driver, the network
is "discovered" again. The settings need to be
discovered or set too. Like whether it's public
or private, whether file sharing is to be enabled
or not. It starts out by default with file
sharing disabled. And it prompts you when you
go to use file sharing (visit another machine)
to turn file sharing back on. That's
your first hint "you upset it". And you
know it lost the setting (somehow).

*******

There is only one scenario for frequent driver updates:

* You play 3D games. Maybe you have a
Steam account or something.
* You play a new game every week. Each new
game absolutely insists on the latest driver,
or the game doesn't render properly.

For the rest of the drivers, you update them when
they're "broken". I can have drivers from 2002
here that still work properly in the year 2016.
And they don't need to be coddled to continue working.

There's nothing wrong with updating a network driver...
as long as you remember what the side effects are :-)

Paul