Gary -- quick update. In the end Microsoft Tech Support completed a full reinstall of Windows 10 and so far things are looking stable.
Thanks for your help.
Murray
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We have 2 new Lenovo Thinkpad T490s laptops. Built identically with Windows 10 Pro Version 21H1.
PC 1 : accesses all networked PC's correctly - see image below : OAK-THINKPAD-T
PC2 : only accesses the local networked PC - see image below : OAK-THINKPAD-T2
The only major difference between the 2 PC's is that PC2 - OAK-THINKPAD-T2 has MS Teams running and this could be causing an issue. We are unable to access & open Mapped network drives even though they display.
This is major business issue that needs urgent attention from Microsoft.
Please advise.
Murray
Gary -- quick update. In the end Microsoft Tech Support completed a full reinstall of Windows 10 and so far things are looking stable.
Thanks for your help.
Murray
Hello @Murray Croft ,
The first thing that I would check/compare is the "Advanced sharing settings" on each PC. The choice of profile is often set when the PC first connects to the network, so could easily differ between the two devices.
Gary
Thanks Gary.
Can confirm both are identical.
Murray
Gary -- thanks for the articles. I have started to work through them -- have to say pretty complex stuff.
I am at a total loss as to why we are having this network issue. Have drives mapped OK but only seeing the local machine plus a Surface Pro tablet on the network. Our 2nd Thinkpad (which BTW is seeing everything) plus local networked PC's missing. All on the same Workgroup. Beginning to question whether we should move everything to a Domain.
We currently have a total of 6 Windows PC's active on our network including 2 servers with Fixed IP.
Cheers
Murray
Hello Murray,
There are two statements in your messages that seem, to me, to be in conflict:
What is the situation with the drives?
If you want to pursue the "trace, analyse, fix" approach, then the elements of the "trace" step are as follows.
A trace can be started in a command window, running as administrator, with pktmon start --capture --comp nics --pkt-size 0 --flags 0x10 --provider Microsoft-Windows-WFP --keywords 0x7FFFFFFFFFFFFFFF --level 255 --file-name why.etl
. The command pktmon stop
stops the trace.
For the missing PC problem, click on the "refresh" symbol in File Explorer (for the Network item) while the trace is running:
If there is a problem with the network file shares, try to access them while the trace is running.
Gary