Linea Recta wrote:
"Paul" schreef in bericht
...
Linea Recta wrote:
After 3 ms updates & reboot laptop I cant connect anymore to my
shared files on my pc.
panic.
Laptop is connected to router by wifi and has internet access.
PC is connected to router by cable and has internet access.

When I click on the other computer under network, I get an error:
could not be found.
From other computer: same result.
I have util wifi-guard and it does find the other pc.
Why cant I go in there with windows file explorer normally?

Restoring image from before the updates: problem solved.

What to do?
Do I skip the latest updates?


regards,


Try connecting using the IP address.

In file explorer, in the path bar

\\192.168.1.2\sharename

and it should prompt for an account if one
is needed. For this to work, you can go to Command Prompt
on the other (serving) machine and get the IP address

ipconfig

Go back to the other machine, with known IP address in
hand, and make the connection.

You might have to resort to logging in first like this
if that doesn't work on the first try.

\\192.168.1.2

*******

The purpose of using an IP address, is to bypass a broken
NetBIOS nameserving function. Windows 7 may have two
"Function Discovery ..." services, which are a different
way of doing nameserving, and those are used for HomeGroup.
I don't know which one is related to NetBIOS.

HTH,
Paul



Thanks for replying.
Tried your suggestions. No solution though.
On one occasion I got a "problem solver", but after a while "this
problem could not be solved".

I dont understand, how can an ms update mess up my settings.

I;m no network expert and stay away as far as possible to prevent
complications. But now this was done for me automatically.

In network centre I see double lines between
THISCOMPUTER==============ROUTER=================I NTERNET

Does that give any clue?

There's a button for network map. What does it show ?
Network map is possible on Windows 7, via probing with
SSDP support. It's possible in the picture below, the WinXP
machine is "discounted" because no SSDP is running on it
and only NetBIOS detected it.

I checked the "ipconfig" on my three machines and they're
all on the same subnet (I neglected to add the IP values here).

https://i.postimg.cc/C1K7YSpN/win7-details.gif

One thing you can try, is lets assume the current machine
is 192.168.1.1, and I know the IP addresses of some other
machines, I can "ping" them and see if the "wires" are connected
to the other LAN members. You say you have Internet access, but
that's a proof that the WAN connection is there. The ping
helps verify the LAN is there.

ping 192.168.1.2
ping 192.168.1.3

Another tool is this one. I think if you accidentally
have nodes on different workgroups, it still lists them.
The /24 refers to the size of the netmask, and the remaining
8 bits scans 256 addresses. If you changed the /24 to
/16, it would consider the subnet to cover 192.168.x.x
and 65536 addresses. That's why the /24 is on the end of that
specification.

http://www.unixwiz.net/tools/nbtscan.html

http://www.unixwiz.net/tools/nbtscan-1.0.35.exe

nbtscan 192.168.1.0/24

You can run that program from any of the machines
on the subnet, check for "partitions" or whatever.

Paul