Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > alt.comp.os.windows-11 > #18727 > unrolled thread
| Started by | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| First post | 2025-04-27 11:58 +0200 |
| Last post | 2025-05-16 14:46 +0200 |
| Articles | 20 on this page of 217 — 17 participants |
Back to article view | Back to alt.comp.os.windows-11
Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-27 11:58 +0200
Re: Can't connect to laptop VanguardLH <V@nguard.LH> - 2025-04-27 05:50 -0500
Re: Can't connect to laptop knuttle <keith_nuttle@yahoo.com> - 2025-04-27 07:11 -0400
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-27 13:33 +0200
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-27 19:31 +0200
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-27 13:30 +0200
Re: Can't connect to laptop Paul <nospam@needed.invalid> - 2025-04-27 09:32 -0400
Re: Can't connect to laptop VanguardLH <V@nguard.LH> - 2025-04-27 10:19 -0500
Re: Can't connect to laptop Paul <nospam@needed.invalid> - 2025-04-27 11:25 -0400
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-27 19:12 +0200
Re: Can't connect to laptop Frank Slootweg <this@ddress.is.invalid> - 2025-04-27 17:53 +0000
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-28 11:53 +0200
Re: Can't connect to laptop Paul <nospam@needed.invalid> - 2025-04-27 14:42 -0400
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-28 12:12 +0200
Re: Can't connect to laptop VanguardLH <V@nguard.LH> - 2025-04-27 21:20 -0500
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-28 12:26 +0200
Re: Can't connect to laptop VanguardLH <V@nguard.LH> - 2025-04-28 07:58 -0500
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-28 15:31 +0200
Re: Can't connect to laptop VanguardLH <V@nguard.LH> - 2025-04-27 11:24 -0500
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-27 18:59 +0200
Re: Can't connect to laptop knuttle <keith_nuttle@yahoo.com> - 2025-04-27 13:03 -0400
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-27 19:19 +0200
Re: Can't connect to laptop VanguardLH <V@nguard.LH> - 2025-04-27 21:54 -0500
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-28 12:37 +0200
Re: Can't connect to laptop MikeS <mikes@is.invalid> - 2025-04-28 13:35 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-28 15:33 +0200
Re: Can't connect to laptop VanguardLH <V@nguard.LH> - 2025-04-28 08:37 -0500
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-28 16:09 +0200
Re: Can't connect to laptop VanguardLH <V@nguard.LH> - 2025-04-28 09:53 -0500
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-01 11:40 +0200
Re: Can't connect to laptop Frank Slootweg <this@ddress.is.invalid> - 2025-05-01 13:05 +0000
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-02 11:44 +0200
Re: Can't connect to laptop Jack <invalid@invalid.invalid> - 2025-05-02 16:30 +0000
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-02 18:53 +0200
Re: Can't connect to laptop Frank Slootweg <this@ddress.is.invalid> - 2025-04-27 17:31 +0000
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-28 12:42 +0200
Re: Can't connect to laptop knuttle <keith_nuttle@yahoo.com> - 2025-04-28 08:06 -0400
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-28 15:35 +0200
Re: Can't connect to laptop VanguardLH <V@nguard.LH> - 2025-04-28 09:35 -0500
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-29 09:40 +0200
Re: Can't connect to laptop VanguardLH <V@nguard.LH> - 2025-04-29 04:12 -0500
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-01 11:46 +0200
Re: Can't connect to laptop Graham J <nobody@nowhere.co.uk> - 2025-04-27 18:46 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-28 13:02 +0200
Re: Can't connect to laptop Graham J <nobody@nowhere.co.uk> - 2025-04-28 14:15 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-28 15:39 +0200
Re: Can't connect to laptop Char Jackson <none@none.invalid> - 2025-04-28 19:31 -0500
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-29 09:29 +0200
Re: Can't connect to laptop Graham J <nobody@nowhere.co.uk> - 2025-04-29 08:52 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-01 11:47 +0200
Re: Can't connect to laptop Graham J <nobody@nowhere.co.uk> - 2025-05-01 12:19 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-01 15:05 +0200
Re: Can't connect to laptop knuttle <keith_nuttle@yahoo.com> - 2025-05-01 16:59 -0400
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-02 11:47 +0200
Re: Can't connect to laptop Char Jackson <none@none.invalid> - 2025-04-29 10:06 -0500
Re: Can't connect to laptop Sam E <no.email@here.invalid> - 2025-04-29 17:00 +0000
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-01 11:48 +0200
Re: Can't connect to laptop Paul <nospam@needed.invalid> - 2025-04-28 12:26 -0400
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-29 09:47 +0200
Re: Can't connect to laptop Paul <nospam@needed.invalid> - 2025-04-29 09:39 -0400
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-01 11:59 +0200
Re: Can't connect to laptop Jack <Jack@invalid.invalid> - 2025-04-28 03:46 +0000
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-28 15:43 +0200
Re: Can't connect to laptop Jack <invalid@invalid.invalid> - 2025-04-28 16:52 +0000
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-29 09:51 +0200
Re: Can't connect to laptop Jack <invalid@invalid.invalid> - 2025-04-29 20:07 +0000
Re: Can't connect to laptop knuttle <keith_nuttle@yahoo.com> - 2025-04-29 17:25 -0400
Re: Can't connect to laptop Paul <nospam@needed.invalid> - 2025-04-29 18:50 -0400
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-01 12:04 +0200
Re: Can't connect to laptop Jack <invalid@invalid.invalid> - 2025-05-02 16:35 +0000
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-01 12:01 +0200
Re: Can't connect to laptop Paul <nospam@needed.invalid> - 2025-05-01 19:00 -0400
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-02 11:48 +0200
Re: Can't connect to laptop "...winston" <winstonmvp@gmail.com> - 2025-05-02 10:59 -0400
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-02 18:56 +0200
Re: Can't connect to laptop "...winston" <winstonmvp@gmail.com> - 2025-05-04 11:48 -0400
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-05 09:19 +0200
Re: Can't connect to laptop VanguardLH <V@nguard.LH> - 2025-04-28 08:43 -0500
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-28 16:11 +0200
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-28 16:34 +0200
Re: Can't connect to laptop knuttle <keith_nuttle@yahoo.com> - 2025-04-28 13:44 -0400
Re: Can't connect to laptop VanguardLH <V@nguard.LH> - 2025-04-28 15:35 -0500
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-29 10:08 +0200
Re: Can't connect to laptop VanguardLH <V@nguard.LH> - 2025-04-29 04:24 -0500
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-01 12:08 +0200
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-04-29 09:52 +0200
Re: Can't connect to laptop Java Jive <java@evij.com.invalid> - 2025-04-29 10:49 +0100
Re: Can't connect to laptop Frank Slootweg <this@ddress.is.invalid> - 2025-04-29 15:44 +0000
Re: Can't connect to laptop Java Jive <java@evij.com.invalid> - 2025-04-29 17:22 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-01 12:25 +0200
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-01 12:24 +0200
Re: Can't connect to laptop Frank Slootweg <this@ddress.is.invalid> - 2025-05-01 13:05 +0000
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-02 11:50 +0200
Re: Can't connect to laptop VanguardLH <V@nguard.LH> - 2025-05-02 06:27 -0500
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-02 14:22 +0200
Re: Can't connect to laptop VanguardLH <V@nguard.LH> - 2025-05-02 08:31 -0500
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-02 19:01 +0200
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-01 12:21 +0200
Re: Can't connect to laptop Java Jive <java@evij.com.invalid> - 2025-05-01 17:38 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-02 11:59 +0200
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-02 14:42 +0200
Re: Can't connect to laptop Java Jive <java@evij.com.invalid> - 2025-05-02 14:52 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-02 19:06 +0200
Re: Can't connect to laptop Java Jive <java@evij.com.invalid> - 2025-05-02 18:41 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-02 20:15 +0200
Re: Can't connect to laptop Java Jive <java@evij.com.invalid> - 2025-05-02 21:49 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-05 12:00 +0200
Re: Can't connect to laptop Java Jive <java@evij.com.invalid> - 2025-05-05 11:40 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-07 10:57 +0200
Re: Can't connect to laptop Andy Burns <usenet@andyburns.uk> - 2025-05-07 10:14 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-07 15:11 +0200
Re: Can't connect to laptop Java Jive <java@evij.com.invalid> - 2025-05-07 13:22 +0100
Re: Can't connect to laptop Graham J <nobody@nowhere.co.uk> - 2025-05-07 13:45 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-07 15:28 +0200
Re: Can't connect to laptop Graham J <nobody@nowhere.co.uk> - 2025-05-07 17:47 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-07 21:34 +0200
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-07 15:23 +0200
Re: Can't connect to laptop Andy Burns <usenet@andyburns.uk> - 2025-05-07 14:59 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-07 18:36 +0200
Re: Can't connect to laptop Java Jive <java@evij.com.invalid> - 2025-05-07 15:00 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-07 18:38 +0200
Re: Can't connect to laptop Paul <nospam@needed.invalid> - 2025-05-08 15:13 -0400
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-09 13:50 +0200
Re: Can't connect to laptop Paul <nospam@needed.invalid> - 2025-05-09 08:41 -0400
Re: Can't connect to laptop Frank Slootweg <this@ddress.is.invalid> - 2025-05-09 13:50 +0000
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-09 18:30 +0200
Re: Can't connect to laptop Paul <nospam@needed.invalid> - 2025-05-09 14:01 -0400
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-12 14:03 +0200
Re: Can't connect to laptop Simon Jenkins <user@invalid.invalid> - 2025-05-13 00:13 +0000
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-14 17:07 +0200
Re: Can't connect to laptop Frank Slootweg <this@ddress.is.invalid> - 2025-05-09 19:00 +0000
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-12 14:07 +0200
Re: Can't connect to laptop Frank Slootweg <this@ddress.is.invalid> - 2025-05-12 15:02 +0000
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-12 20:55 +0200
Re: Can't connect to laptop Paul <nospam@needed.invalid> - 2025-05-12 16:43 -0400
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-16 14:42 +0200
Re: Can't connect to laptop Frank Slootweg <this@ddress.is.invalid> - 2025-05-13 10:24 +0000
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-16 14:43 +0200
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-09 18:37 +0200
Re: Can't connect to laptop Paul <nospam@needed.invalid> - 2025-05-09 14:09 -0400
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-12 14:15 +0200
Re: Can't connect to laptop dillinger <dillinger@invalid.not> - 2025-05-09 20:26 +0200
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-12 14:20 +0200
Re: Can't connect to laptop Frank Slootweg <this@ddress.is.invalid> - 2025-05-12 15:08 +0000
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-12 20:57 +0200
Re: Can't connect to laptop Frank Slootweg <this@ddress.is.invalid> - 2025-05-13 11:01 +0000
Re: Can't connect to laptop Paul <nospam@needed.invalid> - 2025-05-13 15:10 -0400
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-14 18:40 +0200
Re: Can't connect to laptop Graham J <nobody@nowhere.co.uk> - 2025-05-14 22:16 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-16 14:52 +0200
Re: Can't connect to laptop John <Man@the.keyboard> - 2025-05-17 21:58 +0100
Re: Can't connect to laptop Paul <nospam@needed.invalid> - 2025-05-17 17:32 -0400
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-14 18:36 +0200
Re: Can't connect to laptop Frank Slootweg <this@ddress.is.invalid> - 2025-05-15 15:39 +0000
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-16 14:53 +0200
Re: Can't connect to laptop dillinger <dillinger@invalid.not> - 2025-05-20 05:52 +0200
Re: Can't connect to laptop dillinger <dillinger@invalid.not> - 2025-05-20 07:31 +0200
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-20 10:49 +0200
Re: Can't connect to laptop Paul <nospam@needed.invalid> - 2025-05-07 09:56 -0400
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-07 18:40 +0200
Re: Can't connect to laptop Paul <nospam@needed.invalid> - 2025-05-07 16:58 -0400
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-09 13:56 +0200
Re: Can't connect to laptop Graham J <nobody@nowhere.co.uk> - 2025-05-02 15:01 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-02 19:12 +0200
Re: Can't connect to laptop Andy Burns <usenet@andyburns.uk> - 2025-05-02 23:12 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-05 12:01 +0200
Re: Can't connect to laptop Andy Burns <usenet@andyburns.uk> - 2025-05-05 11:13 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-05 13:36 +0200
Re: Can't connect to laptop Frank Slootweg <this@ddress.is.invalid> - 2025-05-05 12:59 +0000
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-07 10:59 +0200
Re: Can't connect to laptop Graham J <nobody@nowhere.co.uk> - 2025-05-05 14:14 +0100
Re: Can't connect to laptop Andy Burns <usenet@andyburns.uk> - 2025-05-05 15:10 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-07 11:01 +0200
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-07 11:00 +0200
Re: Can't connect to laptop Andy Burns <usenet@andyburns.uk> - 2025-05-05 15:08 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-07 11:02 +0200
Re: Can't connect to laptop Java Jive <java@evij.com.invalid> - 2025-05-05 11:44 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-05 13:38 +0200
Re: Can't connect to laptop "...winston" <winstonmvp@gmail.com> - 2025-05-05 11:49 -0400
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-07 11:03 +0200
Re: Can't connect to laptop VanguardLH <V@nguard.LH> - 2025-05-01 13:16 -0500
Re: Can't connect to laptop Java Jive <java@evij.com.invalid> - 2025-05-01 22:34 +0100
Re: Can't connect to laptop VanguardLH <V@nguard.LH> - 2025-05-01 18:42 -0500
Re: Can't connect to laptop Java Jive <java@evij.com.invalid> - 2025-05-02 02:55 +0100
Re: Can't connect to laptop VanguardLH <V@nguard.LH> - 2025-05-01 22:23 -0500
Re: Can't connect to laptop Java Jive <java@evij.com.invalid> - 2025-05-02 11:17 +0100
Re: Can't connect to laptop VanguardLH <V@nguard.LH> - 2025-05-02 06:05 -0500
Re: Can't connect to laptop Java Jive <java@evij.com.invalid> - 2025-05-02 13:28 +0100
Re: Can't connect to laptop Java Jive <java@evij.com.invalid> - 2025-05-02 13:46 +0100
Re: Can't connect to laptop VanguardLH <V@nguard.LH> - 2025-05-02 08:46 -0500
Re: Can't connect to laptop Java Jive <java@evij.com.invalid> - 2025-05-02 14:58 +0100
Re: Can't connect to laptop VanguardLH <V@nguard.LH> - 2025-05-02 10:30 -0500
Re: Can't connect to laptop Java Jive <java@evij.com.invalid> - 2025-05-02 18:14 +0100
Re: Can't connect to laptop VanguardLH <V@nguard.LH> - 2025-05-02 10:34 -0500
Re: Can't connect to laptop Java Jive <java@evij.com.invalid> - 2025-05-02 18:37 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-02 19:15 +0200
Re: Can't connect to laptop VanguardLH <V@nguard.LH> - 2025-05-03 01:34 -0500
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-05 12:10 +0200
Re: Can't connect to laptop Java Jive <java@evij.com.invalid> - 2025-05-05 12:11 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-05 13:42 +0200
Re: Can't connect to laptop VanguardLH <V@nguard.LH> - 2025-05-01 22:25 -0500
Re: Can't connect to laptop Java Jive <java@evij.com.invalid> - 2025-05-02 11:24 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-02 12:02 +0200
Re: Can't connect to laptop Frank Slootweg <this@ddress.is.invalid> - 2025-05-05 14:42 +0000
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-07 11:06 +0200
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-07 15:41 +0200
Re: Can't connect to laptop Graham J <nobody@nowhere.co.uk> - 2025-05-07 17:41 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-09 14:14 +0200
Re: Can't connect to laptop Paul <nospam@needed.invalid> - 2025-05-09 15:05 -0400
Re: Can't connect to laptop Java Jive <java@evij.com.invalid> - 2025-05-10 00:33 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-12 14:25 +0200
Re: Can't connect to laptop Graham J <nobody@nowhere.co.uk> - 2025-05-12 14:29 +0100
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-12 20:59 +0200
Re: Can't connect to laptop Paul <nospam@needed.invalid> - 2025-05-12 16:51 -0400
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-14 18:44 +0200
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-14 18:42 +0200
Re: Can't connect to laptop Fokke Nauta <fnauta@solfon.nl> - 2025-05-16 14:46 +0200
Page 7 of 11 — ← Prev page 1 … 5 6 [7] 8 9 … 11 Next page →
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-05-07 18:38 +0200 |
| Message-ID | <m81gjlFq6t7U2@mid.individual.net> |
| In reply to | #19149 |
On 07/05/2025 16:00, Java Jive wrote: > On 2025-05-07 14:23, Fokke Nauta wrote: >> I checked my W10 pc and the other 2 W10 pc's, but there is no text. >> Only the values of the column width. > > So then click 'Ok'! What now do you see in the right-hand pane of > Explorer! After OK, the little window is gone. Nothing in Explorer. > > You should see something like this: > <https://www.macfh.co.uk/Temp/ExplorerColumns.png> > No, nothing. Nothing like that. Fokke
[toc] | [prev] | [next] | [standalone]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2025-05-08 15:13 -0400 |
| Message-ID | <vvivph$22jq7$1@dont-email.me> |
| In reply to | #19154 |
On Wed, 5/7/2025 12:38 PM, Fokke Nauta wrote:
> On 07/05/2025 16:00, Java Jive wrote:
>> On 2025-05-07 14:23, Fokke Nauta wrote:
>>> I checked my W10 pc and the other 2 W10 pc's, but there is no text. Only the values of the column width.
>>
>> So then click 'Ok'! What now do you see in the right-hand pane of Explorer!
>
> After OK, the little window is gone. Nothing in Explorer.
>>
>> You should see something like this:
>> <https://www.macfh.co.uk/Temp/ExplorerColumns.png>
>>
>
> No, nothing. Nothing like that.
>
> Fokke
Start : Run : services.msc
Check "Function Discovery Provider Host"
Mine is Running, but the status in services.msc is
not displayed properly. You can check the status
of it using the tiny dialog shown on the right.
[Picture]
https://i.postimg.cc/0QDDCk27/Function-Discovery-Provider-Host-W11.gif
Paul
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-05-09 13:50 +0200 |
| Message-ID | <m868gsFipppU1@mid.individual.net> |
| In reply to | #19184 |
On 08/05/2025 21:13, Paul wrote: > On Wed, 5/7/2025 12:38 PM, Fokke Nauta wrote: >> On 07/05/2025 16:00, Java Jive wrote: >>> On 2025-05-07 14:23, Fokke Nauta wrote: >>>> I checked my W10 pc and the other 2 W10 pc's, but there is no text. Only the values of the column width. >>> >>> So then click 'Ok'! What now do you see in the right-hand pane of Explorer! >> >> After OK, the little window is gone. Nothing in Explorer. >>> >>> You should see something like this: >>> <https://www.macfh.co.uk/Temp/ExplorerColumns.png> >>> >> >> No, nothing. Nothing like that. >> >> Fokke > > Start : Run : services.msc > > Check "Function Discovery Provider Host" > > Mine is Running, but the status in services.msc is > not displayed properly. You can check the status > of it using the tiny dialog shown on the right. > > [Picture] > > https://i.postimg.cc/0QDDCk27/Function-Discovery-Provider-Host-W11.gif > > Paul Checked it on my W10 pc. It's running, startup type is manual. Fokke
[toc] | [prev] | [next] | [standalone]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2025-05-09 08:41 -0400 |
| Message-ID | <vvkt5m$2q38r$1@dont-email.me> |
| In reply to | #19194 |
On Fri, 5/9/2025 7:50 AM, Fokke Nauta wrote:
> On 08/05/2025 21:13, Paul wrote:
>> On Wed, 5/7/2025 12:38 PM, Fokke Nauta wrote:
>>> On 07/05/2025 16:00, Java Jive wrote:
>>>> On 2025-05-07 14:23, Fokke Nauta wrote:
>>>>> I checked my W10 pc and the other 2 W10 pc's, but there is no text. Only the values of the column width.
>>>>
>>>> So then click 'Ok'! What now do you see in the right-hand pane of Explorer!
>>>
>>> After OK, the little window is gone. Nothing in Explorer.
>>>>
>>>> You should see something like this:
>>>> <https://www.macfh.co.uk/Temp/ExplorerColumns.png>
>>>>
>>>
>>> No, nothing. Nothing like that.
>>>
>>> Fokke
>>
>> Start : Run : services.msc
>>
>> Check "Function Discovery Provider Host"
>>
>> Mine is Running, but the status in services.msc is
>> not displayed properly. You can check the status
>> of it using the tiny dialog shown on the right.
>>
>> [Picture]
>>
>> https://i.postimg.cc/0QDDCk27/Function-Discovery-Provider-Host-W11.gif
>>
>> Paul
>
> Checked it on my W10 pc. It's running, startup type is manual.
>
> Fokke
Yet your discovery screen does not render in File Explorer.
Mine works here, even if the account is a Limited User.
[Picture]
https://i.postimg.cc/pTctmN38/discovery-limited-user.gif
Paul
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2025-05-09 13:50 +0000 |
| Message-ID | <vvl876.tmg.1@ID-201911.user.individual.net> |
| In reply to | #19197 |
Paul <nospam@needed.invalid> wrote: > On Fri, 5/9/2025 7:50 AM, Fokke Nauta wrote: > > On 08/05/2025 21:13, Paul wrote: [...] > >> Start : Run : services.msc > >> > >> Check "Function Discovery Provider Host" > >> > >> Mine is Running, but the status in services.msc is > >> not displayed properly. You can check the status > >> of it using the tiny dialog shown on the right. > >> > >> [Picture] > >> > >> https://i.postimg.cc/0QDDCk27/Function-Discovery-Provider-Host-W11.gif > >> > >> Paul > > > > Checked it on my W10 pc. It's running, startup type is manual. > > > > Fokke > > Yet your discovery screen does not render in File Explorer. > > Mine works here, even if the account is a Limited User. > > [Picture] > > https://i.postimg.cc/pTctmN38/discovery-limited-user.gif FWIW, also on my systems (Windows 11 and 10) network discovery is flaky, while 'Function Discovery Provider Host' is (manual and) running. For example on my Windows 11 system, I only see my own system (with WSD), but not my wife's Windows 10 system. And if I do a 'Refresh "Network" (F5)', it doesn't even show my own system anymore. BUT, *Network Shares* work just fine. That's why I think there is (and was) too much emphasis on Fokke's network discovery 'problem' and too little on why \\<computer>\<share> apparently *silently* [1] fails when he tries to access a share on his wife's Windows 11 laptop. [1] I find that very hard to believe, but Fokke is adamant that that's the case.
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-05-09 18:30 +0200 |
| Message-ID | <m86osvFlb4eU1@mid.individual.net> |
| In reply to | #19198 |
On 09/05/2025 15:50, Frank Slootweg wrote: > Paul <nospam@needed.invalid> wrote: >> On Fri, 5/9/2025 7:50 AM, Fokke Nauta wrote: >>> On 08/05/2025 21:13, Paul wrote: > [...] >>>> Start : Run : services.msc >>>> >>>> Check "Function Discovery Provider Host" >>>> >>>> Mine is Running, but the status in services.msc is >>>> not displayed properly. You can check the status >>>> of it using the tiny dialog shown on the right. >>>> >>>> [Picture] >>>> >>>> https://i.postimg.cc/0QDDCk27/Function-Discovery-Provider-Host-W11.gif >>>> >>>> Paul >>> >>> Checked it on my W10 pc. It's running, startup type is manual. >>> >>> Fokke >> >> Yet your discovery screen does not render in File Explorer. >> >> Mine works here, even if the account is a Limited User. >> >> [Picture] >> >> https://i.postimg.cc/pTctmN38/discovery-limited-user.gif > > FWIW, also on my systems (Windows 11 and 10) network discovery is > flaky, while 'Function Discovery Provider Host' is (manual and) running. > > For example on my Windows 11 system, I only see my own system (with > WSD), but not my wife's Windows 10 system. And if I do a 'Refresh > "Network" (F5)', it doesn't even show my own system anymore. > > BUT, *Network Shares* work just fine. That's why I think there is (and > was) too much emphasis on Fokke's network discovery 'problem' and too > little on why \\<computer>\<share> apparently *silently* [1] fails when > he tries to access a share on his wife's Windows 11 laptop. > > [1] I find that very hard to believe, but Fokke is adamant that that's > the case. What would you think that is the case, then? Fokke
[toc] | [prev] | [next] | [standalone]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2025-05-09 14:01 -0400 |
| Message-ID | <vvlft7$2uube$1@dont-email.me> |
| In reply to | #19199 |
On Fri, 5/9/2025 12:30 PM, Fokke Nauta wrote: > On 09/05/2025 15:50, Frank Slootweg wrote: >> Paul <nospam@needed.invalid> wrote: >>> On Fri, 5/9/2025 7:50 AM, Fokke Nauta wrote: >>>> On 08/05/2025 21:13, Paul wrote: >> [...] >>>>> Start : Run : services.msc >>>>> >>>>> Check "Function Discovery Provider Host" >>>>> >>>>> Mine is Running, but the status in services.msc is >>>>> not displayed properly. You can check the status >>>>> of it using the tiny dialog shown on the right. >>>>> >>>>> [Picture] >>>>> >>>>> https://i.postimg.cc/0QDDCk27/Function-Discovery-Provider-Host-W11.gif >>>>> >>>>> Paul >>>> >>>> Checked it on my W10 pc. It's running, startup type is manual. >>>> >>>> Fokke >>> >>> Yet your discovery screen does not render in File Explorer. >>> >>> Mine works here, even if the account is a Limited User. >>> >>> [Picture] >>> >>> https://i.postimg.cc/pTctmN38/discovery-limited-user.gif >> >> FWIW, also on my systems (Windows 11 and 10) network discovery is >> flaky, while 'Function Discovery Provider Host' is (manual and) running. >> >> For example on my Windows 11 system, I only see my own system (with >> WSD), but not my wife's Windows 10 system. And if I do a 'Refresh >> "Network" (F5)', it doesn't even show my own system anymore. >> >> BUT, *Network Shares* work just fine. That's why I think there is (and >> was) too much emphasis on Fokke's network discovery 'problem' and too >> little on why \\<computer>\<share> apparently *silently* [1] fails when >> he tries to access a share on his wife's Windows 11 laptop. >> >> [1] I find that very hard to believe, but Fokke is adamant that that's >> the case. > > What would you think that is the case, then? > > Fokke I gave a suggestion, to debug at the network level and see the error code that is being sent back. As a group, we can give a summary of the "visible" levers in the scheme. It will always be possible for us to miss something. There are seven services that have to be enabled for file sharing to work. In a better era, I might have said to do a Repair Install, to reset the services to their defaults and so on. But these days, with the problems the OS has (my crashes are back), I don't feel confident in that, to even suggest it. A Repair Install is done by running "Setup.exe" on the DVD you used to install the current version of the OS. Use "winver" to determine which version of OS that is (22H2 likely 19045 on a Win10). It is even possible that a recent Patch Tuesday update has broken it. The following examples would be for the repair of the Win10 on my daily driver (this) machine. Example: 1) I locate the version of Windows used for all Win10 Repair. S:\DVD\Win10_22H2_English_x64v1.iso 2) I right-click that and select Mount. If running Imgburn, the Mount option is removed and replaced by Imgburn, so you need to "Open with Explorer" and then File Explorer will mount it. 3) From the new drive letter (which is the mounted DVD), locate Setup.exe and run it. It would likely help if the user belongs to the Administrator group, but I suppose an elevation dialog for the Administrators Group account would appear if it does not want to run. 4) After the install, certain advertising settings will be reset to their normal irritating levels. You will need to correct the advertising settings. Other settings will mostly be kept. Your files and programs will be preserved. Paul
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-05-12 14:03 +0200 |
| Message-ID | <m8e6csFqrbdU1@mid.individual.net> |
| In reply to | #19202 |
On 09/05/2025 20:01, Paul wrote: > On Fri, 5/9/2025 12:30 PM, Fokke Nauta wrote: >> On 09/05/2025 15:50, Frank Slootweg wrote: >>> Paul <nospam@needed.invalid> wrote: >>>> On Fri, 5/9/2025 7:50 AM, Fokke Nauta wrote: >>>>> On 08/05/2025 21:13, Paul wrote: >>> [...] >>>>>> Start : Run : services.msc >>>>>> >>>>>> Check "Function Discovery Provider Host" >>>>>> >>>>>> Mine is Running, but the status in services.msc is >>>>>> not displayed properly. You can check the status >>>>>> of it using the tiny dialog shown on the right. >>>>>> >>>>>> [Picture] >>>>>> >>>>>> https://i.postimg.cc/0QDDCk27/Function-Discovery-Provider-Host-W11.gif >>>>>> >>>>>> Paul >>>>> >>>>> Checked it on my W10 pc. It's running, startup type is manual. >>>>> >>>>> Fokke >>>> >>>> Yet your discovery screen does not render in File Explorer. >>>> >>>> Mine works here, even if the account is a Limited User. >>>> >>>> [Picture] >>>> >>>> https://i.postimg.cc/pTctmN38/discovery-limited-user.gif >>> >>> FWIW, also on my systems (Windows 11 and 10) network discovery is >>> flaky, while 'Function Discovery Provider Host' is (manual and) running. >>> >>> For example on my Windows 11 system, I only see my own system (with >>> WSD), but not my wife's Windows 10 system. And if I do a 'Refresh >>> "Network" (F5)', it doesn't even show my own system anymore. >>> >>> BUT, *Network Shares* work just fine. That's why I think there is (and >>> was) too much emphasis on Fokke's network discovery 'problem' and too >>> little on why \\<computer>\<share> apparently *silently* [1] fails when >>> he tries to access a share on his wife's Windows 11 laptop. >>> >>> [1] I find that very hard to believe, but Fokke is adamant that that's >>> the case. >> >> What would you think that is the case, then? >> >> Fokke > > I gave a suggestion, to debug at the network level and see the error > code that is being sent back. > > As a group, we can give a summary of the "visible" levers in > the scheme. It will always be possible for us to miss something. > There are seven services that have to be enabled for file sharing > to work. > > In a better era, I might have said to do a Repair Install, to > reset the services to their defaults and so on. But these days, > with the problems the OS has (my crashes are back), I don't feel > confident in that, to even suggest it. A Repair Install is > done by running "Setup.exe" on the DVD you used to install the > current version of the OS. Use "winver" to determine which > version of OS that is (22H2 likely 19045 on a Win10). It is even > possible that a recent Patch Tuesday update has broken it. The > following examples would be for the repair of the Win10 on > my daily driver (this) machine. > > Example: > > 1) I locate the version of Windows used for all Win10 Repair. > > S:\DVD\Win10_22H2_English_x64v1.iso > > 2) I right-click that and select Mount. If running Imgburn, the Mount > option is removed and replaced by Imgburn, so you need to "Open with Explorer" > and then File Explorer will mount it. > > 3) From the new drive letter (which is the mounted DVD), locate Setup.exe and > run it. It would likely help if the user belongs to the Administrator group, > but I suppose an elevation dialog for the Administrators Group account would > appear if it does not want to run. > > 4) After the install, certain advertising settings will be reset to their > normal irritating levels. You will need to correct the advertising settings. > Other settings will mostly be kept. Your files and programs will be preserved. > > Paul > Thanks, Paul. But I'm not going to do a repair install. Fokke
[toc] | [prev] | [next] | [standalone]
| From | Simon Jenkins <user@invalid.invalid> |
|---|---|
| Date | 2025-05-13 00:13 +0000 |
| Message-ID | <vvu33l$1j934$1@paganini.bofh.team> |
| In reply to | #19225 |
On 12/05/2025 13:03, Fokke Nauta wrote: > On 09/05/2025 20:01, Paul wrote: >> On Fri, 5/9/2025 12:30 PM, Fokke Nauta wrote: >>> On 09/05/2025 15:50, Frank Slootweg wrote: >>>> Paul <nospam@needed.invalid> wrote: >>>>> On Fri, 5/9/2025 7:50 AM, Fokke Nauta wrote: >>>>>> On 08/05/2025 21:13, Paul wrote: >>>> [...] >>>>>>> Start : Run : services.msc >>>>>>> >>>>>>> Check "Function Discovery Provider Host" >>>>>>> >>>>>>> Mine is Running, but the status in services.msc is >>>>>>> not displayed properly. You can check the status >>>>>>> of it using the tiny dialog shown on the right. >>>>>>> >>>>>>> [Picture] >>>>>>> >>>>>>> https://i.postimg.cc/0QDDCk27/Function-Discovery-Provider-Host-W11.gif >>>>>>> >>>>>>> Paul >>>>>> >>>>>> Checked it on my W10 pc. It's running, startup type is manual. >>>>>> >>>>>> Fokke >>>>> >>>>> Yet your discovery screen does not render in File Explorer. >>>>> >>>>> Mine works here, even if the account is a Limited User. >>>>> >>>>> [Picture] >>>>> >>>>> https://i.postimg.cc/pTctmN38/discovery-limited-user.gif >>>> >>>> FWIW, also on my systems (Windows 11 and 10) network discovery is >>>> flaky, while 'Function Discovery Provider Host' is (manual and) >>>> running. >>>> >>>> For example on my Windows 11 system, I only see my own system (with >>>> WSD), but not my wife's Windows 10 system. And if I do a 'Refresh >>>> "Network" (F5)', it doesn't even show my own system anymore. >>>> >>>> BUT, *Network Shares* work just fine. That's why I think there >>>> is (and >>>> was) too much emphasis on Fokke's network discovery 'problem' and too >>>> little on why \\<computer>\<share> apparently *silently* [1] fails when >>>> he tries to access a share on his wife's Windows 11 laptop. >>>> >>>> [1] I find that very hard to believe, but Fokke is adamant that that's >>>> the case. >>> >>> What would you think that is the case, then? >>> >>> Fokke >> >> I gave a suggestion, to debug at the network level and see the error >> code that is being sent back. >> >> As a group, we can give a summary of the "visible" levers in >> the scheme. It will always be possible for us to miss something. >> There are seven services that have to be enabled for file sharing >> to work. >> >> In a better era, I might have said to do a Repair Install, to >> reset the services to their defaults and so on. But these days, >> with the problems the OS has (my crashes are back), I don't feel >> confident in that, to even suggest it. A Repair Install is >> done by running "Setup.exe" on the DVD you used to install the >> current version of the OS. Use "winver" to determine which >> version of OS that is (22H2 likely 19045 on a Win10). It is even >> possible that a recent Patch Tuesday update has broken it. The >> following examples would be for the repair of the Win10 on >> my daily driver (this) machine. >> >> Example: >> >> 1) I locate the version of Windows used for all Win10 Repair. >> >> S:\DVD\Win10_22H2_English_x64v1.iso >> >> 2) I right-click that and select Mount. If running Imgburn, the Mount >> option is removed and replaced by Imgburn, so you need to "Open >> with Explorer" >> and then File Explorer will mount it. >> >> 3) From the new drive letter (which is the mounted DVD), locate >> Setup.exe and >> run it. It would likely help if the user belongs to the >> Administrator group, >> but I suppose an elevation dialog for the Administrators Group >> account would >> appear if it does not want to run. >> >> 4) After the install, certain advertising settings will be reset to their >> normal irritating levels. You will need to correct the advertising >> settings. >> Other settings will mostly be kept. Your files and programs will >> be preserved. >> >> Paul >> > Thanks, Paul. > But I'm not going to do a repair install. > > Fokke > Well if you are not going to do anything people ask you to do then why are you continuing with this thread? This thread has created more than 100 posts and nothing has solved your problem and you do not want to do anything to solve it. Just cut it off and move on. Don't expect the problem to be resolved without doing anything. Windows is a very secure operating system and access to other people's machine is a complete NO NO without the express permission of the owner.
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-05-14 17:07 +0200 |
| Message-ID | <m8jpufFnocgU1@mid.individual.net> |
| In reply to | #19238 |
On 13/05/2025 02:13, Simon Jenkins wrote: > On 12/05/2025 13:03, Fokke Nauta wrote: >> On 09/05/2025 20:01, Paul wrote: >>> On Fri, 5/9/2025 12:30 PM, Fokke Nauta wrote: >>>> On 09/05/2025 15:50, Frank Slootweg wrote: >>>>> Paul <nospam@needed.invalid> wrote: >>>>>> On Fri, 5/9/2025 7:50 AM, Fokke Nauta wrote: >>>>>>> On 08/05/2025 21:13, Paul wrote: >>>>> [...] <cut> > > > Well if you are not going to do anything people ask you to do then why > are you continuing with this thread? This thread has created more than > 100 posts and nothing has solved your problem and you do not want to do > anything to solve it. > > Just cut it off and move on. Don't expect the problem to be resolved > without doing anything. Windows is a very secure operating system and > access to other people's machine is a complete NO NO without the express > permission of the owner. > > Fuck off and get lost.
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2025-05-09 19:00 +0000 |
| Message-ID | <vvlqcf.1a0s.1@ID-201911.user.individual.net> |
| In reply to | #19199 |
Fokke Nauta <fnauta@solfon.nl> wrote: > On 09/05/2025 15:50, Frank Slootweg wrote: > > Paul <nospam@needed.invalid> wrote: > >> On Fri, 5/9/2025 7:50 AM, Fokke Nauta wrote: > >>> On 08/05/2025 21:13, Paul wrote: > > [...] > >>>> Start : Run : services.msc > >>>> > >>>> Check "Function Discovery Provider Host" > >>>> > >>>> Mine is Running, but the status in services.msc is > >>>> not displayed properly. You can check the status > >>>> of it using the tiny dialog shown on the right. > >>>> > >>>> [Picture] > >>>> > >>>> https://i.postimg.cc/0QDDCk27/Function-Discovery-Provider-Host-W11.gif > >>>> > >>>> Paul > >>> > >>> Checked it on my W10 pc. It's running, startup type is manual. > >>> > >>> Fokke > >> > >> Yet your discovery screen does not render in File Explorer. > >> > >> Mine works here, even if the account is a Limited User. > >> > >> [Picture] > >> > >> https://i.postimg.cc/pTctmN38/discovery-limited-user.gif > > > > FWIW, also on my systems (Windows 11 and 10) network discovery is > > flaky, while 'Function Discovery Provider Host' is (manual and) running. > > > > For example on my Windows 11 system, I only see my own system (with > > WSD), but not my wife's Windows 10 system. And if I do a 'Refresh > > "Network" (F5)', it doesn't even show my own system anymore. > > > > BUT, *Network Shares* work just fine. That's why I think there is (and > > was) too much emphasis on Fokke's network discovery 'problem' and too > > little on why \\<computer>\<share> apparently *silently* [1] fails when > > he tries to access a share on his wife's Windows 11 laptop. > > > > [1] I find that very hard to believe, but Fokke is adamant that that's > > the case. > > What would you think that is the case, then? No idea, really. Whatever *I* do, I get a request for username/ password of the remote computer or an error if I specify an incorrect computer name or share name. I never get a silent failure, i.e. no response at all. Coming to think of it, perhaps it's not a silent failure. Yes, it's silent, but is it a failure? Perhaps the request (to access the share) is just hanging forever for some strange reason. That is no response, but strictly speaking not a failure.
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-05-12 14:07 +0200 |
| Message-ID | <m8e6kjFqrbdU2@mid.individual.net> |
| In reply to | #19205 |
On 09/05/2025 21:00, Frank Slootweg wrote: > Fokke Nauta <fnauta@solfon.nl> wrote: >> On 09/05/2025 15:50, Frank Slootweg wrote: >>> Paul <nospam@needed.invalid> wrote: >>>> On Fri, 5/9/2025 7:50 AM, Fokke Nauta wrote: >>>>> On 08/05/2025 21:13, Paul wrote: >>> [...] >>>>>> Start : Run : services.msc >>>>>> >>>>>> Check "Function Discovery Provider Host" >>>>>> >>>>>> Mine is Running, but the status in services.msc is >>>>>> not displayed properly. You can check the status >>>>>> of it using the tiny dialog shown on the right. >>>>>> >>>>>> [Picture] >>>>>> >>>>>> https://i.postimg.cc/0QDDCk27/Function-Discovery-Provider-Host-W11.gif >>>>>> >>>>>> Paul >>>>> >>>>> Checked it on my W10 pc. It's running, startup type is manual. >>>>> >>>>> Fokke >>>> >>>> Yet your discovery screen does not render in File Explorer. >>>> >>>> Mine works here, even if the account is a Limited User. >>>> >>>> [Picture] >>>> >>>> https://i.postimg.cc/pTctmN38/discovery-limited-user.gif >>> >>> FWIW, also on my systems (Windows 11 and 10) network discovery is >>> flaky, while 'Function Discovery Provider Host' is (manual and) running. >>> >>> For example on my Windows 11 system, I only see my own system (with >>> WSD), but not my wife's Windows 10 system. And if I do a 'Refresh >>> "Network" (F5)', it doesn't even show my own system anymore. >>> >>> BUT, *Network Shares* work just fine. That's why I think there is (and >>> was) too much emphasis on Fokke's network discovery 'problem' and too >>> little on why \\<computer>\<share> apparently *silently* [1] fails when >>> he tries to access a share on his wife's Windows 11 laptop. >>> >>> [1] I find that very hard to believe, but Fokke is adamant that that's >>> the case. >> >> What would you think that is the case, then? > > No idea, really. Whatever *I* do, I get a request for username/ > password of the remote computer or an error if I specify an incorrect > computer name or share name. I never get a silent failure, i.e. no > response at all. Well, trying to open my wifs'laptop on my pc, I get the error message Windows cannot access \\Computer name. > > Coming to think of it, perhaps it's not a silent failure. Yes, it's > silent, but is it a failure? Perhaps the request (to access the share) > is just hanging forever for some strange reason. That is no response, > but strictly speaking not a failure. Fokke
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2025-05-12 15:02 +0000 |
| Message-ID | <vvt9j5.14hs.1@ID-201911.user.individual.net> |
| In reply to | #19226 |
Fokke Nauta <fnauta@solfon.nl> wrote: > On 09/05/2025 21:00, Frank Slootweg wrote: > > Fokke Nauta <fnauta@solfon.nl> wrote: > >> On 09/05/2025 15:50, Frank Slootweg wrote: [...] > >>> FWIW, also on my systems (Windows 11 and 10) network discovery is > >>> flaky, while 'Function Discovery Provider Host' is (manual and) running. > >>> > >>> For example on my Windows 11 system, I only see my own system (with > >>> WSD), but not my wife's Windows 10 system. And if I do a 'Refresh > >>> "Network" (F5)', it doesn't even show my own system anymore. > >>> > >>> BUT, *Network Shares* work just fine. That's why I think there is (and > >>> was) too much emphasis on Fokke's network discovery 'problem' and too > >>> little on why \\<computer>\<share> apparently *silently* [1] fails when > >>> he tries to access a share on his wife's Windows 11 laptop. > >>> > >>> [1] I find that very hard to believe, but Fokke is adamant that that's > >>> the case. > >> > >> What would you think that is the case, then? > > > > No idea, really. Whatever *I* do, I get a request for username/ > > password of the remote computer or an error if I specify an incorrect > > computer name or share name. I never get a silent failure, i.e. no > > response at all. > > Well, trying to open my wifs'laptop on my pc, I get the error message > Windows cannot access \\Computer name. Which 'Error code:' (click on 'See details') do you get? 0x80070035 as in your OP or a different one? And please in every response, indicate which Windows version you are using, because IIRC you yourself have more than one system with different Windows versions (10 and 11) You of course know what you have and use, but we don't keep a list of that, at least I don't and after 150+ responses it's hard/impossible to tell what is which. > > Coming to think of it, perhaps it's not a silent failure. Yes, it's > > silent, but is it a failure? Perhaps the request (to access the share) > > is just hanging forever for some strange reason. That is no response, > > but strictly speaking not a failure.
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-05-12 20:55 +0200 |
| Message-ID | <m8euh7Fufg7U1@mid.individual.net> |
| In reply to | #19231 |
On 12/05/2025 17:02, Frank Slootweg wrote: > Fokke Nauta <fnauta@solfon.nl> wrote: >> On 09/05/2025 21:00, Frank Slootweg wrote: >>> Fokke Nauta <fnauta@solfon.nl> wrote: >>>> On 09/05/2025 15:50, Frank Slootweg wrote: > [...] >>>>> FWIW, also on my systems (Windows 11 and 10) network discovery is >>>>> flaky, while 'Function Discovery Provider Host' is (manual and) running. >>>>> >>>>> For example on my Windows 11 system, I only see my own system (with >>>>> WSD), but not my wife's Windows 10 system. And if I do a 'Refresh >>>>> "Network" (F5)', it doesn't even show my own system anymore. >>>>> >>>>> BUT, *Network Shares* work just fine. That's why I think there is (and >>>>> was) too much emphasis on Fokke's network discovery 'problem' and too >>>>> little on why \\<computer>\<share> apparently *silently* [1] fails when >>>>> he tries to access a share on his wife's Windows 11 laptop. >>>>> >>>>> [1] I find that very hard to believe, but Fokke is adamant that that's >>>>> the case. >>>> >>>> What would you think that is the case, then? >>> >>> No idea, really. Whatever *I* do, I get a request for username/ >>> password of the remote computer or an error if I specify an incorrect >>> computer name or share name. I never get a silent failure, i.e. no >>> response at all. >> >> Well, trying to open my wifs'laptop on my pc, I get the error message >> Windows cannot access \\Computer name. > > Which 'Error code:' (click on 'See details') do you get? 0x80070035 as > in your OP or a different one? Yes, 0x80070035. > > And please in every response, indicate which Windows version you are > using, because IIRC you yourself have more than one system with > different Windows versions (10 and 11) You of course know what you have > and use, but we don't keep a list of that, at least I don't and after > 150+ responses it's hard/impossible to tell what is which. W10 Pro. > >>> Coming to think of it, perhaps it's not a silent failure. Yes, it's >>> silent, but is it a failure? Perhaps the request (to access the share) >>> is just hanging forever for some strange reason. That is no response, >>> but strictly speaking not a failure. Fokke
[toc] | [prev] | [next] | [standalone]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2025-05-12 16:43 -0400 |
| Message-ID | <vvtmh6$19st4$1@dont-email.me> |
| In reply to | #19233 |
On Mon, 5/12/2025 2:55 PM, Fokke Nauta wrote:
> On 12/05/2025 17:02, Frank Slootweg wrote:
>> Fokke Nauta <fnauta@solfon.nl> wrote:
>>> On 09/05/2025 21:00, Frank Slootweg wrote:
>>>> Fokke Nauta <fnauta@solfon.nl> wrote:
>>>>> On 09/05/2025 15:50, Frank Slootweg wrote:
>> [...]
>>>>>> FWIW, also on my systems (Windows 11 and 10) network discovery is
>>>>>> flaky, while 'Function Discovery Provider Host' is (manual and) running.
>>>>>>
>>>>>> For example on my Windows 11 system, I only see my own system (with
>>>>>> WSD), but not my wife's Windows 10 system. And if I do a 'Refresh
>>>>>> "Network" (F5)', it doesn't even show my own system anymore.
>>>>>>
>>>>>> BUT, *Network Shares* work just fine. That's why I think there is (and
>>>>>> was) too much emphasis on Fokke's network discovery 'problem' and too
>>>>>> little on why \\<computer>\<share> apparently *silently* [1] fails when
>>>>>> he tries to access a share on his wife's Windows 11 laptop.
>>>>>>
>>>>>> [1] I find that very hard to believe, but Fokke is adamant that that's
>>>>>> the case.
>>>>>
>>>>> What would you think that is the case, then?
>>>>
>>>> No idea, really. Whatever *I* do, I get a request for username/
>>>> password of the remote computer or an error if I specify an incorrect
>>>> computer name or share name. I never get a silent failure, i.e. no
>>>> response at all.
>>>
>>> Well, trying to open my wifs'laptop on my pc, I get the error message
>>> Windows cannot access \\Computer name.
>>
>> Which 'Error code:' (click on 'See details') do you get? 0x80070035 as
>> in your OP or a different one?
>
> Yes, 0x80070035.
>>
>> And please in every response, indicate which Windows version you are
>> using, because IIRC you yourself have more than one system with
>> different Windows versions (10 and 11) You of course know what you have
>> and use, but we don't keep a list of that, at least I don't and after
>> 150+ responses it's hard/impossible to tell what is which.
>
> W10 Pro.
>>
>>>> Coming to think of it, perhaps it's not a silent failure. Yes, it's
>>>> silent, but is it a failure? Perhaps the request (to access the share)
>>>> is just hanging forever for some strange reason. That is no response,
>>>> but strictly speaking not a failure.
>
> Fokke
>
PS> .\err_6.4.5.exe 0x80070035
# No results found for hex 0x80070035 / decimal -2147024843
# as an HRESULT: Severity: FAILURE (1), FACILITY_WIN32 (0x7), Code 0x35
# for hex 0x35 / decimal 53
ERROR_BAD_NETPATH winerror.h <===== Error does not help much
# The network path was not found.
# 1 matches found for "0x80070035"
PS>
AI Overview
-----------
Error code 0x80070035, which often appears with the message "The network path was not found",
indicates a problem accessing a network location, drive, or computer.
And of course, you already tried the IP address version
explorer \\wallace\shared <=== Symbolic, works if BrowseMaster is running
explorer \\192.168.1.3\shared <=== Numeric. One less issue to deal with. <=== I am pretty sure you have tried the IP address
Report the error number this returns.
Paul
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-05-16 14:42 +0200 |
| Message-ID | <m8oq5aFim2tU1@mid.individual.net> |
| In reply to | #19236 |
On 12/05/2025 22:43, Paul wrote: > On Mon, 5/12/2025 2:55 PM, Fokke Nauta wrote: >> On 12/05/2025 17:02, Frank Slootweg wrote: >>> Fokke Nauta <fnauta@solfon.nl> wrote: >>>> On 09/05/2025 21:00, Frank Slootweg wrote: >>>>> Fokke Nauta <fnauta@solfon.nl> wrote: >>>>>> On 09/05/2025 15:50, Frank Slootweg wrote: >>> [...] >>>>>>> FWIW, also on my systems (Windows 11 and 10) network discovery is >>>>>>> flaky, while 'Function Discovery Provider Host' is (manual and) running. >>>>>>> >>>>>>> For example on my Windows 11 system, I only see my own system (with >>>>>>> WSD), but not my wife's Windows 10 system. And if I do a 'Refresh >>>>>>> "Network" (F5)', it doesn't even show my own system anymore. >>>>>>> >>>>>>> BUT, *Network Shares* work just fine. That's why I think there is (and >>>>>>> was) too much emphasis on Fokke's network discovery 'problem' and too >>>>>>> little on why \\<computer>\<share> apparently *silently* [1] fails when >>>>>>> he tries to access a share on his wife's Windows 11 laptop. >>>>>>> >>>>>>> [1] I find that very hard to believe, but Fokke is adamant that that's >>>>>>> the case. >>>>>> >>>>>> What would you think that is the case, then? >>>>> >>>>> No idea, really. Whatever *I* do, I get a request for username/ >>>>> password of the remote computer or an error if I specify an incorrect >>>>> computer name or share name. I never get a silent failure, i.e. no >>>>> response at all. >>>> >>>> Well, trying to open my wifs'laptop on my pc, I get the error message >>>> Windows cannot access \\Computer name. >>> >>> Which 'Error code:' (click on 'See details') do you get? 0x80070035 as >>> in your OP or a different one? >> >> Yes, 0x80070035. >>> >>> And please in every response, indicate which Windows version you are >>> using, because IIRC you yourself have more than one system with >>> different Windows versions (10 and 11) You of course know what you have >>> and use, but we don't keep a list of that, at least I don't and after >>> 150+ responses it's hard/impossible to tell what is which. >> >> W10 Pro. >>> >>>>> Coming to think of it, perhaps it's not a silent failure. Yes, it's >>>>> silent, but is it a failure? Perhaps the request (to access the share) >>>>> is just hanging forever for some strange reason. That is no response, >>>>> but strictly speaking not a failure. >> >> Fokke >> > > PS> .\err_6.4.5.exe 0x80070035 > > # No results found for hex 0x80070035 / decimal -2147024843 > # as an HRESULT: Severity: FAILURE (1), FACILITY_WIN32 (0x7), Code 0x35 > # for hex 0x35 / decimal 53 > ERROR_BAD_NETPATH winerror.h <===== Error does not help much > # The network path was not found. > # 1 matches found for "0x80070035" > PS> > > AI Overview > ----------- > > Error code 0x80070035, which often appears with the message "The network path was not found", > indicates a problem accessing a network location, drive, or computer. > > And of course, you already tried the IP address version > > explorer \\wallace\shared <=== Symbolic, works if BrowseMaster is running Paul, I can't believe it. Using \\HP-SONJA\Documents, I cen see the share. When clicking in the Network field on HP-SONJA, I now can see all the shares! How is it possible! Problem solved! > explorer \\192.168.1.3\shared <=== Numeric. One less issue to deal with. <=== I am pretty sure you have tried the IP address No, no need to anymore, and I don't know her IP address. She is working on her laptop so I can't use ipconfig now. > Report the error number this returns. > > Paul Fokke >
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2025-05-13 10:24 +0000 |
| Message-ID | <vvvdls.m38.1@ID-201911.user.individual.net> |
| In reply to | #19233 |
Fokke Nauta <fnauta@solfon.nl> wrote: > On 12/05/2025 17:02, Frank Slootweg wrote: > > Fokke Nauta <fnauta@solfon.nl> wrote: [...] > >> Well, trying to open my wifs'laptop on my pc, I get the error message > >> Windows cannot access \\Computer name. > > > > Which 'Error code:' (click on 'See details') do you get? 0x80070035 as > > in your OP or a different one? > > Yes, 0x80070035. > > > > And please in every response, indicate which Windows version you are > > using, because IIRC you yourself have more than one system with > > different Windows versions (10 and 11) You of course know what you have > > and use, but we don't keep a list of that, at least I don't and after > > 150+ responses it's hard/impossible to tell what is which. > > W10 Pro. [...] As we're still not making any progress after 200 responses, I advise to also (not only) go back and do some Google searches. I searched on "Windows share error 0x80070035" and of course found many reports, but also some troubleshooting cookbooks which might be of use. *Example* (i.e. by far *not* the only one): 'How to Fix Error 0x80070035 on Windows ands Say Goodbye to Networking Nightmares' <https://geekflare.com/dev/fix-error-0x80070035-windows/>
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-05-16 14:43 +0200 |
| Message-ID | <m8oq80Fim2tU2@mid.individual.net> |
| In reply to | #19239 |
On 13/05/2025 12:24, Frank Slootweg wrote: > Fokke Nauta <fnauta@solfon.nl> wrote: >> On 12/05/2025 17:02, Frank Slootweg wrote: >>> Fokke Nauta <fnauta@solfon.nl> wrote: > [...] >>>> Well, trying to open my wifs'laptop on my pc, I get the error message >>>> Windows cannot access \\Computer name. >>> >>> Which 'Error code:' (click on 'See details') do you get? 0x80070035 as >>> in your OP or a different one? >> >> Yes, 0x80070035. >>> >>> And please in every response, indicate which Windows version you are >>> using, because IIRC you yourself have more than one system with >>> different Windows versions (10 and 11) You of course know what you have >>> and use, but we don't keep a list of that, at least I don't and after >>> 150+ responses it's hard/impossible to tell what is which. >> >> W10 Pro. > [...] > > As we're still not making any progress after 200 responses, I advise > to also (not only) go back and do some Google searches. I searched on > "Windows share error 0x80070035" and of course found many reports, but > also some troubleshooting cookbooks which might be of use. > > *Example* (i.e. by far *not* the only one): > > 'How to Fix Error 0x80070035 on Windows ands > Say Goodbye to Networking Nightmares' > <https://geekflare.com/dev/fix-error-0x80070035-windows/> Hi Frank, The problem is solved! See my respose to Paul. Completely unsuspectable. Fokke
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-05-09 18:37 +0200 |
| Message-ID | <m86pabFlb4eU2@mid.individual.net> |
| In reply to | #19197 |
On 09/05/2025 14:41, Paul wrote: > On Fri, 5/9/2025 7:50 AM, Fokke Nauta wrote: >> On 08/05/2025 21:13, Paul wrote: >>> On Wed, 5/7/2025 12:38 PM, Fokke Nauta wrote: >>>> On 07/05/2025 16:00, Java Jive wrote: >>>>> On 2025-05-07 14:23, Fokke Nauta wrote: >>>>>> I checked my W10 pc and the other 2 W10 pc's, but there is no text. Only the values of the column width. >>>>> >>>>> So then click 'Ok'! What now do you see in the right-hand pane of Explorer! >>>> >>>> After OK, the little window is gone. Nothing in Explorer. >>>>> >>>>> You should see something like this: >>>>> <https://www.macfh.co.uk/Temp/ExplorerColumns.png> >>>>> >>>> >>>> No, nothing. Nothing like that. >>>> >>>> Fokke >>> >>> Start : Run : services.msc >>> >>> Check "Function Discovery Provider Host" >>> >>> Mine is Running, but the status in services.msc is >>> not displayed properly. You can check the status >>> of it using the tiny dialog shown on the right. >>> >>> [Picture] >>> >>> https://i.postimg.cc/0QDDCk27/Function-Discovery-Provider-Host-W11.gif >>> >>> Paul >> >> Checked it on my W10 pc. It's running, startup type is manual. >> >> Fokke > > Yet your discovery screen does not render in File Explorer. > > Mine works here, even if the account is a Limited User. > > [Picture] > > https://i.postimg.cc/pTctmN38/discovery-limited-user.gif > > Paul I double clicked on WSD, but there is no Powershell. Only the message that you can't contact the pc. What's the use of Powershell? Fokke
[toc] | [prev] | [next] | [standalone]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2025-05-09 14:09 -0400 |
| Message-ID | <vvlgd3$2v2hd$1@dont-email.me> |
| In reply to | #19200 |
On Fri, 5/9/2025 12:37 PM, Fokke Nauta wrote:
> On 09/05/2025 14:41, Paul wrote:
>> On Fri, 5/9/2025 7:50 AM, Fokke Nauta wrote:
>>> On 08/05/2025 21:13, Paul wrote:
>>>> On Wed, 5/7/2025 12:38 PM, Fokke Nauta wrote:
>>>>> On 07/05/2025 16:00, Java Jive wrote:
>>>>>> On 2025-05-07 14:23, Fokke Nauta wrote:
>>>>>>> I checked my W10 pc and the other 2 W10 pc's, but there is no text. Only the values of the column width.
>>>>>>
>>>>>> So then click 'Ok'! What now do you see in the right-hand pane of Explorer!
>>>>>
>>>>> After OK, the little window is gone. Nothing in Explorer.
>>>>>>
>>>>>> You should see something like this:
>>>>>> <https://www.macfh.co.uk/Temp/ExplorerColumns.png>
>>>>>>
>>>>>
>>>>> No, nothing. Nothing like that.
>>>>>
>>>>> Fokke
>>>>
>>>> Start : Run : services.msc
>>>>
>>>> Check "Function Discovery Provider Host"
>>>>
>>>> Mine is Running, but the status in services.msc is
>>>> not displayed properly. You can check the status
>>>> of it using the tiny dialog shown on the right.
>>>>
>>>> [Picture]
>>>>
>>>> https://i.postimg.cc/0QDDCk27/Function-Discovery-Provider-Host-W11.gif
>>>>
>>>> Paul
>>>
>>> Checked it on my W10 pc. It's running, startup type is manual.
>>>
>>> Fokke
>>
>> Yet your discovery screen does not render in File Explorer.
>>
>> Mine works here, even if the account is a Limited User.
>>
>> [Picture]
>>
>> https://i.postimg.cc/pTctmN38/discovery-limited-user.gif
>>
>> Paul
>
> I double clicked on WSD, but there is no Powershell. Only the message that you can't contact the pc.
> What's the use of Powershell?
>
> Fokke
OK, so then that dialog *is* working for you.
You claim to be seeing the word WSD, and you have a status.
That means Function Discovery is working.
Something else is blocking the success of the transaction.
We need to gather evidence, to see what that is.
If I was there, I would be collecting "network status" from a packet
tracer, as I showed in a picture.
Network Monitor 3.4 (I used the x64 version for my Win11 x64 tests, client side machine)
https://www.microsoft.com/en-ca/download/details.aspx?id=4865
[Picture] W11 Trisket calls W11 Wallace Server, success, Directory List fetched
https://i.postimg.cc/bNQqGT10/Network-Monitor-Demo-NM34-W11-W11-SMB.gif
The alternative to that, is to do a Repair Install.
Paul
[toc] | [prev] | [next] | [standalone]
Page 7 of 11 — ← Prev page 1 … 5 6 [7] 8 9 … 11 Next page →
Back to top | Article view | alt.comp.os.windows-11
csiph-web