Recent content by mikejp

Whoa! I'm not sure how you interpreted that. That was NOT what I said. I said "I need someone who understands network access who can take me through the steps to track down the 'blockage'."

psey - many thanks for that. As you can probably see I have done all of that apart from adding credentials since I do not need to access other machines. I am now stuck with a W11 network path that cannot be accessed and I just do not understand what is stopping the access. As far as I know all...

OAT reckons I could map a drive I cannot access on the network. Hoping there is someone who undertstand W11 who can tell me how to do that.

Which 'path' is that? See OP Are you pointing to a share? Yes Have you mapped a drive? No. I don't think that is possible if the share cannot be accessed?:

Thanks, OAT. A summary, then I can now 'see' the errant laptop on the network but its 'path' cannot be found. There are 2 IPs associated, one an ethernet one and one a wireless one, the wireless being on a fixed IP in my router, the ethernet being on a DHCP assigned IP. I can ping both...

A quick question?!! I recall right from W95 days that it was recommended to deselect the IP6 box in the adapter properties. Is that still necessary?

A little progress. I had included the Lanman Workstation in Gp Pol as a dependency following 'advice' on anther thread here, bur removing that dependency has allowed Network D to remain active, so the W11 laptop now shows in the network BUT still cannot be 'found'

Thanks - running.

I think Ihave checked all the dependencies, but services.msc does not hold HTTP Service?

That is set but service is not running and will not allow me to 'start' it. 'Error 1075 ; The dependency service does not exist or has been marked for delete'

Before I go any further I have discovered that each restart and or network reset turns off Network Discovery which I assume is the problem (private network). Is there a reg or gppol setting that controls the default?

Correction: "but not the given network name 'MIKELAP' (not found)" I was trying to ping \\MIKELAP. Ping MIKELAP worked. Where is the thing hiding? ipconfig shows an IP of .117 whereas in my router I have a fixed ip for the laptop of .201. Can this be causing the issue?

In desperation I successfully connected with the Win11 machine via Anydesk which I know is not much help, but at least it proves the damned thing is working on the internet and at least I can access its files! Still no joy via Networking - just cannot reach the machine. I can ping the IP...

All done, thanks, glas, and 'success' with the script, but so far sadly no improvement.

System details added. I have seen elsewhere that 24H2 can cause issues with networking. Sadly none of the tutorials (if that is what you mean by 'search'?) actually helped. What is stumping me is that the laptop was fully visible and accessible when running W10 but my W10 desktop cannot resolve...