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 1 of 11 [1] 2 3 … 11 Next page →
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-04-27 11:58 +0200 |
| Subject | Can't connect to laptop |
| Message-ID | <m76dejFfqtkU1@mid.individual.net> |
Hi all, My wife has a W11 Pro laptop. It is visable in the network but I can't open it. Her network detection is on, just as file and printer sharing. It is on a private network. When I try to open it from my pc, I get the message "Windows cannot access" the name of her laptop. Error code 0x80070035. This code says how to Enable NetBIOS over TCP / IP. I did and restarted the laptop. I still can't open it from my pc. All other pc's I can open, so this is a problem with her laptop. What else can I do to open it and access the folders and files? Thanks in advance for your help. With regards, Fokke Nauta
[toc] | [next] | [standalone]
| From | VanguardLH <V@nguard.LH> |
|---|---|
| Date | 2025-04-27 05:50 -0500 |
| Message-ID | <19dpvj20hqpzx$.dlg@v.nguard.lh> |
| In reply to | #18727 |
Fokke Nauta <fnauta@solfon.nl> wrote: > My wife has a W11 Pro laptop. It is visable in the network but I can't > open it. Her network detection is on, just as file and printer sharing. > It is on a private network. > When I try to open it from my pc, I get the message "Windows cannot > access" the name of her laptop. Error code 0x80070035. > This code says how to Enable NetBIOS over TCP / IP. I did and restarted > the laptop. > I still can't open it from my pc. All other pc's I can open, so this is > a problem with her laptop. > What else can I do to open it and access the folders and files? > Thanks in advance for your help. Is your wife's computer assigned to the same workgroup as the remote host to which she tries to connect? https://www.pcworld.com/article/2191054/windows-11-how-to-set-up-a-network.html That mentions the step where you decide in which workgroup your host is assigned. Hosts in the same workgroup can work with each other. For example, you might have SOHO hosts for work-use only that you don't want your wife, kids, or anyone else on your intranet to access. The default workgroup name is "WORKGROUP" (I don't think it needs to be uppercase). The PCworld article fails to mention just how you get directly into the System Properties config tool without having to walk through some setup wizard. Run: sysdm.cpl Under the General tab, click Change (your computer name). The next dialog lets you specify the workgroup name. Your wife needs to use the same workgroup name as your other intranet hosts to which she wants to connect. In Control Panel (control.exe), select "Network and Sharing Center", is your wife's computer in a private or public network. Intranet sharing requires using a private network. Public is, well, when you're on a public network, and don't want anyone accessing your host. https://support.microsoft.com/en-us/windows/essential-network-settings-and-tasks-in-windows-f21a9bbc-c582-55cd-35e0-73431160a1b9 which says: - Public network (Recommended). Use this for networks you connect to at home, work, or in a public place. You should use this in most cases. Your PC will be hidden from other devices on the network. Therefore, you can’t use your PC for file and printer sharing. - Private network. Your PC is discoverable to other devices on the network, and you can use your PC for file and printer sharing. You should know and trust the people and devices on the network. I can't tell from: https://learn.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3?tabs=server if SMBv2 and SMBv3 are enabled by default in Windows 11. I've seen other posters mentioning having to enable SMB to get home networking to function, but I'm not sure if that is between Windows hosts using auto-discovery, or between Windows hosts to Mac, Linux, or NAS hosts. Another problem I've seen discussed is that you need to have a login that permits access. Do the following: - Open the run dialog (Win+R). - Run: control /name Microsoft.CredentialManager - Select Windows credentials. - Click Add Windows credential. - Enter your remote path with your Windows credentials. This is where I'm unsure about what to enter here. https://support.microsoft.com/en-us/windows/credential-manager-in-windows-1b5c916a-6a16-889f-8581-fc16e8165ac0 That was incomplete, and unhelpful in knowing on which host you define Windows credentials for the other host. My guess is that you run this on the host where you want to connect to your remote host. Supply the IP address of your remote host, and the login credentials for a Windows account defined on the remote host. Using the IP address of the remote host should work. You might be able to specify the hostname assigned to the remote host. https://buffaloamericas.com/knowledge-base/adding-windows-credentials-of-your-nas-on-windows-10-or-windows-server-2019 That has you use the Credentials Manager on your Windows host to add credentials for the NAS device (remote host). https://www.1kosmos.com/identity-management/windows-credential-manager/ pretty much says the same: define the credentials on your host for the remote host to which you want to connect. I'm also guessing that you need to specify the login credentials for an admin-level account. Do you have an admin account in Windows 11? No, not the Administrator account, but a user account you created that is in the Administrators security group. You can see to which security group a Windows account is assigned by running: net users <acctname> where <acctname> is the Windows account you want to check its info. At the bottom is the list of local [security] groups to which that account is associated. To get a list of accounts, and to which security group they are assigned, run: wmic useraccount list brief To see which accounts (users) are in a specific security group, run: net localgroup administrators That will list who is in the Administrators security group. If you run: net localgroup you can see which security groups are in your instance of Windows (to know which to specify to find out which users are under a specific security group).
[toc] | [prev] | [next] | [standalone]
| From | knuttle <keith_nuttle@yahoo.com> |
|---|---|
| Date | 2025-04-27 07:11 -0400 |
| Message-ID | <vul3dn$l3ap$1@dont-email.me> |
| In reply to | #18729 |
On 04/27/2025 6:50 AM, VanguardLH wrote: > Fokke Nauta <fnauta@solfon.nl> wrote: > >> My wife has a W11 Pro laptop. It is visable in the network but I can't >> open it. Her network detection is on, just as file and printer sharing. >> It is on a private network. >> When I try to open it from my pc, I get the message "Windows cannot >> access" the name of her laptop. Error code 0x80070035. >> This code says how to Enable NetBIOS over TCP / IP. I did and restarted >> the laptop. >> I still can't open it from my pc. All other pc's I can open, so this is >> a problem with her laptop. >> What else can I do to open it and access the folders and files? >> Thanks in advance for your help. > > Is your wife's computer assigned to the same workgroup as the remote > host to which she tries to connect? > > https://www.pcworld.com/article/2191054/windows-11-how-to-set-up-a-network.html > > That mentions the step where you decide in which workgroup your host is > assigned. Hosts in the same workgroup can work with each other. For > example, you might have SOHO hosts for work-use only that you don't want > your wife, kids, or anyone else on your intranet to access. The default > workgroup name is "WORKGROUP" (I don't think it needs to be uppercase). > > The PCworld article fails to mention just how you get directly into the > System Properties config tool without having to walk through some setup > wizard. Run: > > sysdm.cpl > > Under the General tab, click Change (your computer name). The next > dialog lets you specify the workgroup name. Your wife needs to use the > same workgroup name as your other intranet hosts to which she wants to > connect. > > In Control Panel (control.exe), select "Network and Sharing Center", is > your wife's computer in a private or public network. Intranet sharing > requires using a private network. Public is, well, when you're on a > public network, and don't want anyone accessing your host. > > https://support.microsoft.com/en-us/windows/essential-network-settings-and-tasks-in-windows-f21a9bbc-c582-55cd-35e0-73431160a1b9 > which says: > - Public network (Recommended). Use this for networks you connect to at > home, work, or in a public place. You should use this in most cases. > Your PC will be hidden from other devices on the network. Therefore, > you can’t use your PC for file and printer sharing. > - Private network. Your PC is discoverable to other devices on the > network, and you can use your PC for file and printer sharing. You > should know and trust the people and devices on the network. > > > I can't tell from: > > https://learn.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3?tabs=server > > if SMBv2 and SMBv3 are enabled by default in Windows 11. I've seen > other posters mentioning having to enable SMB to get home networking to > function, but I'm not sure if that is between Windows hosts using > auto-discovery, or between Windows hosts to Mac, Linux, or NAS hosts. > > Another problem I've seen discussed is that you need to have a login > that permits access. Do the following: > > - Open the run dialog (Win+R). > - Run: control /name Microsoft.CredentialManager > - Select Windows credentials. > - Click Add Windows credential. > - Enter your remote path with your Windows credentials. > > This is where I'm unsure about what to enter here. > > https://support.microsoft.com/en-us/windows/credential-manager-in-windows-1b5c916a-6a16-889f-8581-fc16e8165ac0 > > That was incomplete, and unhelpful in knowing on which host you define > Windows credentials for the other host. > > My guess is that you run this on the host where you want to connect to > your remote host. Supply the IP address of your remote host, and the > login credentials for a Windows account defined on the remote host. > Using the IP address of the remote host should work. You might be able > to specify the hostname assigned to the remote host. > > https://buffaloamericas.com/knowledge-base/adding-windows-credentials-of-your-nas-on-windows-10-or-windows-server-2019 > > That has you use the Credentials Manager on your Windows host to add > credentials for the NAS device (remote host). > > https://www.1kosmos.com/identity-management/windows-credential-manager/ > > pretty much says the same: define the credentials on your host for the > remote host to which you want to connect. I'm also guessing that you > need to specify the login credentials for an admin-level account. Do > you have an admin account in Windows 11? No, not the Administrator > account, but a user account you created that is in the Administrators > security group. You can see to which security group a Windows account > is assigned by running: > > net users <acctname> > > where <acctname> is the Windows account you want to check its info. At > the bottom is the list of local [security] groups to which that account > is associated. To get a list of accounts, and to which security group > they are assigned, run: > > wmic useraccount list brief > > To see which accounts (users) are in a specific security group, run: > > net localgroup administrators > > That will list who is in the Administrators security group. If you run: > > net localgroup > > you can see which security groups are in your instance of Windows (to > know which to specify to find out which users are under a specific > security group). This information was found after a struggle of over a week, and hours of online research while setting up my new computer to be able to connect to my LAN's resources From a recent experience with the same symptoms I suspect there are two possible reasons, assuming you owned the folder you were sharing. 1. Make sure that the groups mentioned in the Share tab of the folder Properties contains EVERYONE as a user with the appropriate rights. 2. In recent HP and probably other brands, the local area LANs are consider insecure, and by default the computer is prevented from connecting to them. These lines when run as one string in the Terminal Admin, set the parameters to allow the connection and use of LAN folders. reg add HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ /f /v RequireSecuritySignature /t REG_DWORD /d 0 reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation /f /v AllowInsecureGuestAuth /t REG_DWORD /d 1 reg add HKLM\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\LanmanWorkstation /f /v AllowInsecureGuestAuth /t REG_DWORD /d 1
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-04-27 13:33 +0200 |
| Message-ID | <m76j0tFghrbU2@mid.individual.net> |
| In reply to | #18730 |
On 27/04/2025 13:11, knuttle wrote: > On 04/27/2025 6:50 AM, VanguardLH wrote: >> Fokke Nauta <fnauta@solfon.nl> wrote: >> >>> My wife has a W11 Pro laptop. It is visable in the network but I can't >>> open it. Her network detection is on, just as file and printer sharing. >>> It is on a private network. >>> When I try to open it from my pc, I get the message "Windows cannot >>> access" the name of her laptop. Error code 0x80070035. >>> This code says how to Enable NetBIOS over TCP / IP. I did and restarted >>> the laptop. >>> I still can't open it from my pc. All other pc's I can open, so this is >>> a problem with her laptop. >>> What else can I do to open it and access the folders and files? >>> Thanks in advance for your help. >> >> Is your wife's computer assigned to the same workgroup as the remote >> host to which she tries to connect? >> >> https://www.pcworld.com/article/2191054/windows-11-how-to-set-up-a-network.html >> >> That mentions the step where you decide in which workgroup your host is >> assigned. Hosts in the same workgroup can work with each other. For >> example, you might have SOHO hosts for work-use only that you don't want >> your wife, kids, or anyone else on your intranet to access. The default >> workgroup name is "WORKGROUP" (I don't think it needs to be uppercase). >> >> The PCworld article fails to mention just how you get directly into the >> System Properties config tool without having to walk through some setup >> wizard. Run: >> >> sysdm.cpl >> >> Under the General tab, click Change (your computer name). The next >> dialog lets you specify the workgroup name. Your wife needs to use the >> same workgroup name as your other intranet hosts to which she wants to >> connect. >> >> In Control Panel (control.exe), select "Network and Sharing Center", is >> your wife's computer in a private or public network. Intranet sharing >> requires using a private network. Public is, well, when you're on a >> public network, and don't want anyone accessing your host. >> >> https://support.microsoft.com/en-us/windows/essential-network-settings-and-tasks-in-windows-f21a9bbc-c582-55cd-35e0-73431160a1b9 >> which says: >> - Public network (Recommended). Use this for networks you connect to at >> home, work, or in a public place. You should use this in most cases. >> Your PC will be hidden from other devices on the network. Therefore, >> you can’t use your PC for file and printer sharing. >> - Private network. Your PC is discoverable to other devices on the >> network, and you can use your PC for file and printer sharing. You >> should know and trust the people and devices on the network. >> >> >> I can't tell from: >> >> https://learn.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3?tabs=server >> >> if SMBv2 and SMBv3 are enabled by default in Windows 11. I've seen >> other posters mentioning having to enable SMB to get home networking to >> function, but I'm not sure if that is between Windows hosts using >> auto-discovery, or between Windows hosts to Mac, Linux, or NAS hosts. >> >> Another problem I've seen discussed is that you need to have a login >> that permits access. Do the following: >> >> - Open the run dialog (Win+R). >> - Run: control /name Microsoft.CredentialManager >> - Select Windows credentials. >> - Click Add Windows credential. >> - Enter your remote path with your Windows credentials. >> >> This is where I'm unsure about what to enter here. >> >> https://support.microsoft.com/en-us/windows/credential-manager-in-windows-1b5c916a-6a16-889f-8581-fc16e8165ac0 >> >> That was incomplete, and unhelpful in knowing on which host you define >> Windows credentials for the other host. >> >> My guess is that you run this on the host where you want to connect to >> your remote host. Supply the IP address of your remote host, and the >> login credentials for a Windows account defined on the remote host. >> Using the IP address of the remote host should work. You might be able >> to specify the hostname assigned to the remote host. >> >> https://buffaloamericas.com/knowledge-base/adding-windows-credentials-of-your-nas-on-windows-10-or-windows-server-2019 >> >> That has you use the Credentials Manager on your Windows host to add >> credentials for the NAS device (remote host). >> >> https://www.1kosmos.com/identity-management/windows-credential-manager/ >> >> pretty much says the same: define the credentials on your host for the >> remote host to which you want to connect. I'm also guessing that you >> need to specify the login credentials for an admin-level account. Do >> you have an admin account in Windows 11? No, not the Administrator >> account, but a user account you created that is in the Administrators >> security group. You can see to which security group a Windows account >> is assigned by running: >> >> net users <acctname> >> >> where <acctname> is the Windows account you want to check its info. At >> the bottom is the list of local [security] groups to which that account >> is associated. To get a list of accounts, and to which security group >> they are assigned, run: >> >> wmic useraccount list brief >> >> To see which accounts (users) are in a specific security group, run: >> >> net localgroup administrators >> >> That will list who is in the Administrators security group. If you run: >> >> net localgroup >> >> you can see which security groups are in your instance of Windows (to >> know which to specify to find out which users are under a specific >> security group). > > This information was found after a struggle of over a week, and hours of > online research while setting up my new computer to be able to connect > to my LAN's resources > > From a recent experience with the same symptoms I suspect there are two > possible reasons, assuming you owned the folder you were sharing. No. The shared folders are on the laptop, which I don't own. > > 1. Make sure that the groups mentioned in the Share tab of the folder > Properties contains EVERYONE as a user with the appropriate rights. Ofcourse it's EVERYONE.. > > 2. In recent HP and probably other brands, the local area LANs are > consider insecure, and by default the computer is prevented from > connecting to them. It's an HP laptop indeed. But I have a same HP laptop, which doesn't have this problem. > These lines when run as one string in the Terminal Admin, set the > parameters to allow the connection and use of LAN folders. > > reg add > HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ /f > /v RequireSecuritySignature /t REG_DWORD /d 0 > > reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation /f /v > AllowInsecureGuestAuth /t REG_DWORD /d 1 > > reg add > HKLM\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\LanmanWorkstation > /f /v AllowInsecureGuestAuth /t REG_DWORD /d 1 > > > > >
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-04-27 19:31 +0200 |
| Message-ID | <m777v9Fji1tU4@mid.individual.net> |
| In reply to | #18730 |
On 27/04/2025 13:11, knuttle wrote: > On 04/27/2025 6:50 AM, VanguardLH wrote: >> Fokke Nauta <fnauta@solfon.nl> wrote: >> >>> My wife has a W11 Pro laptop. It is visable in the network but I can't >>> open it. Her network detection is on, just as file and printer sharing. >>> It is on a private network. >>> When I try to open it from my pc, I get the message "Windows cannot >>> access" the name of her laptop. Error code 0x80070035. >>> This code says how to Enable NetBIOS over TCP / IP. I did and restarted >>> the laptop. >>> I still can't open it from my pc. All other pc's I can open, so this is >>> a problem with her laptop. >>> What else can I do to open it and access the folders and files? >>> Thanks in advance for your help. >> >> Is your wife's computer assigned to the same workgroup as the remote >> host to which she tries to connect? >> >> https://www.pcworld.com/article/2191054/windows-11-how-to-set-up-a-network.html >> >> That mentions the step where you decide in which workgroup your host is >> assigned. Hosts in the same workgroup can work with each other. For >> example, you might have SOHO hosts for work-use only that you don't want >> your wife, kids, or anyone else on your intranet to access. The default >> workgroup name is "WORKGROUP" (I don't think it needs to be uppercase). >> >> The PCworld article fails to mention just how you get directly into the >> System Properties config tool without having to walk through some setup >> wizard. Run: >> >> sysdm.cpl >> >> Under the General tab, click Change (your computer name). The next >> dialog lets you specify the workgroup name. Your wife needs to use the >> same workgroup name as your other intranet hosts to which she wants to >> connect. >> >> In Control Panel (control.exe), select "Network and Sharing Center", is >> your wife's computer in a private or public network. Intranet sharing >> requires using a private network. Public is, well, when you're on a >> public network, and don't want anyone accessing your host. >> >> https://support.microsoft.com/en-us/windows/essential-network-settings-and-tasks-in-windows-f21a9bbc-c582-55cd-35e0-73431160a1b9 >> which says: >> - Public network (Recommended). Use this for networks you connect to at >> home, work, or in a public place. You should use this in most cases. >> Your PC will be hidden from other devices on the network. Therefore, >> you can’t use your PC for file and printer sharing. >> - Private network. Your PC is discoverable to other devices on the >> network, and you can use your PC for file and printer sharing. You >> should know and trust the people and devices on the network. >> >> >> I can't tell from: >> >> https://learn.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3?tabs=server >> >> if SMBv2 and SMBv3 are enabled by default in Windows 11. I've seen >> other posters mentioning having to enable SMB to get home networking to >> function, but I'm not sure if that is between Windows hosts using >> auto-discovery, or between Windows hosts to Mac, Linux, or NAS hosts. >> >> Another problem I've seen discussed is that you need to have a login >> that permits access. Do the following: >> >> - Open the run dialog (Win+R). >> - Run: control /name Microsoft.CredentialManager >> - Select Windows credentials. >> - Click Add Windows credential. >> - Enter your remote path with your Windows credentials. >> >> This is where I'm unsure about what to enter here. >> >> https://support.microsoft.com/en-us/windows/credential-manager-in-windows-1b5c916a-6a16-889f-8581-fc16e8165ac0 >> >> That was incomplete, and unhelpful in knowing on which host you define >> Windows credentials for the other host. >> >> My guess is that you run this on the host where you want to connect to >> your remote host. Supply the IP address of your remote host, and the >> login credentials for a Windows account defined on the remote host. >> Using the IP address of the remote host should work. You might be able >> to specify the hostname assigned to the remote host. >> >> https://buffaloamericas.com/knowledge-base/adding-windows-credentials-of-your-nas-on-windows-10-or-windows-server-2019 >> >> That has you use the Credentials Manager on your Windows host to add >> credentials for the NAS device (remote host). >> >> https://www.1kosmos.com/identity-management/windows-credential-manager/ >> >> pretty much says the same: define the credentials on your host for the >> remote host to which you want to connect. I'm also guessing that you >> need to specify the login credentials for an admin-level account. Do >> you have an admin account in Windows 11? No, not the Administrator >> account, but a user account you created that is in the Administrators >> security group. You can see to which security group a Windows account >> is assigned by running: >> >> net users <acctname> >> >> where <acctname> is the Windows account you want to check its info. At >> the bottom is the list of local [security] groups to which that account >> is associated. To get a list of accounts, and to which security group >> they are assigned, run: >> >> wmic useraccount list brief >> >> To see which accounts (users) are in a specific security group, run: >> >> net localgroup administrators >> >> That will list who is in the Administrators security group. If you run: >> >> net localgroup >> >> you can see which security groups are in your instance of Windows (to >> know which to specify to find out which users are under a specific >> security group). > > This information was found after a struggle of over a week, and hours of > online research while setting up my new computer to be able to connect > to my LAN's resources > > From a recent experience with the same symptoms I suspect there are two > possible reasons, assuming you owned the folder you were sharing. > > > 1. Make sure that the groups mentioned in the Share tab of the folder > Properties contains EVERYONE as a user with the appropriate rights. > > > 2. In recent HP and probably other brands, the local area LANs are > consider insecure, and by default the computer is prevented from > connecting to them. > > These lines when run as one string in the Terminal Admin, set the > parameters to allow the connection and use of LAN folders. > > reg add > HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters\ /f > /v RequireSecuritySignature /t REG_DWORD /d 0 > > reg add HKLM\SOFTWARE\Policies\Microsoft\Windows\LanmanWorkstation /f /v > AllowInsecureGuestAuth /t REG_DWORD /d 1 > > reg add > HKLM\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\LanmanWorkstation > /f /v AllowInsecureGuestAuth /t REG_DWORD /d 1 Sorry, But I wasn't able to add this to the registry on the laptop. Fokke
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-04-27 13:30 +0200 |
| Message-ID | <m76iqkFghrbU1@mid.individual.net> |
| In reply to | #18729 |
On 27/04/2025 12:50, VanguardLH wrote: > Fokke Nauta <fnauta@solfon.nl> wrote: > >> My wife has a W11 Pro laptop. It is visable in the network but I can't >> open it. Her network detection is on, just as file and printer sharing. >> It is on a private network. >> When I try to open it from my pc, I get the message "Windows cannot >> access" the name of her laptop. Error code 0x80070035. >> This code says how to Enable NetBIOS over TCP / IP. I did and restarted >> the laptop. >> I still can't open it from my pc. All other pc's I can open, so this is >> a problem with her laptop. >> What else can I do to open it and access the folders and files? >> Thanks in advance for your help. > > Is your wife's computer assigned to the same workgroup as the remote > host to which she tries to connect? Yes. > https://www.pcworld.com/article/2191054/windows-11-how-to-set-up-a-network.html > > That mentions the step where you decide in which workgroup your host is > assigned. Hosts in the same workgroup can work with each other. For > example, you might have SOHO hosts for work-use only that you don't want > your wife, kids, or anyone else on your intranet to access. The default > workgroup name is "WORKGROUP" (I don't think it needs to be uppercase). > > The PCworld article fails to mention just how you get directly into the > System Properties config tool without having to walk through some setup > wizard. Run: > > sysdm.cpl > > Under the General tab, click Change (your computer name). The next > dialog lets you specify the workgroup name. Your wife needs to use the > same workgroup name as your other intranet hosts to which she wants to > connect. All pc's and laptops use WORKGROUP. > In Control Panel (control.exe), select "Network and Sharing Center", is > your wife's computer in a private or public network. Intranet sharing > requires using a private network. Public is, well, when you're on a > public network, and don't want anyone accessing your host. It's private. > https://support.microsoft.com/en-us/windows/essential-network-settings-and-tasks-in-windows-f21a9bbc-c582-55cd-35e0-73431160a1b9 > which says: > - Public network (Recommended). Use this for networks you connect to at > home, work, or in a public place. You should use this in most cases. > Your PC will be hidden from other devices on the network. Therefore, > you can’t use your PC for file and printer sharing. > - Private network. Your PC is discoverable to other devices on the > network, and you can use your PC for file and printer sharing. You > should know and trust the people and devices on the network. > > > I can't tell from: > > https://learn.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3?tabs=server > > if SMBv2 and SMBv3 are enabled by default in Windows 11. I've seen > other posters mentioning having to enable SMB to get home networking to > function, but I'm not sure if that is between Windows hosts using > auto-discovery, or between Windows hosts to Mac, Linux, or NAS hosts. > > Another problem I've seen discussed is that you need to have a login > that permits access. Do the following: Shared folders are open for every one. In our local network that is safe. > - Open the run dialog (Win+R). > - Run: control /name Microsoft.CredentialManager > - Select Windows credentials. > - Click Add Windows credential. > - Enter your remote path with your Windows credentials. > > This is where I'm unsure about what to enter here. > > https://support.microsoft.com/en-us/windows/credential-manager-in-windows-1b5c916a-6a16-889f-8581-fc16e8165ac0 > > That was incomplete, and unhelpful in knowing on which host you define > Windows credentials for the other host. > > My guess is that you run this on the host where you want to connect to > your remote host. Supply the IP address of your remote host, and the > login credentials for a Windows account defined on the remote host. > Using the IP address of the remote host should work. You might be able > to specify the hostname assigned to the remote host. Login credentials are not needed yet, as the laptop is completely unaccessible. > https://buffaloamericas.com/knowledge-base/adding-windows-credentials-of-your-nas-on-windows-10-or-windows-server-2019 > > That has you use the Credentials Manager on your Windows host to add > credentials for the NAS device (remote host). We don't have a NAS dvice. > https://www.1kosmos.com/identity-management/windows-credential-manager/ > > pretty much says the same: define the credentials on your host for the > remote host to which you want to connect. I'm also guessing that you > need to specify the login credentials for an admin-level account. Do > you have an admin account in Windows 11? No, not the Administrator > account, but a user account you created that is in the Administrators > security group. You can see to which security group a Windows account > is assigned by running: > > net users <acctname> > > where <acctname> is the Windows account you want to check its info. At > the bottom is the list of local [security] groups to which that account > is associated. To get a list of accounts, and to which security group > they are assigned, run: > > wmic useraccount list brief > > To see which accounts (users) are in a specific security group, run: > > net localgroup administrators > > That will list who is in the Administrators security group. If you run: > > net localgroup > > you can see which security groups are in your instance of Windows (to > know which to specify to find out which users are under a specific > security group).
[toc] | [prev] | [next] | [standalone]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2025-04-27 09:32 -0400 |
| Message-ID | <vulblt$tbgd$1@dont-email.me> |
| In reply to | #18731 |
On Sun, 4/27/2025 7:30 AM, Fokke Nauta wrote: > On 27/04/2025 12:50, VanguardLH wrote: >> Fokke Nauta <fnauta@solfon.nl> wrote: >> >>> My wife has a W11 Pro laptop. It is visable in the network but I can't >>> open it. Her network detection is on, just as file and printer sharing. >>> It is on a private network. >>> When I try to open it from my pc, I get the message "Windows cannot >>> access" the name of her laptop. Error code 0x80070035. >>> This code says how to Enable NetBIOS over TCP / IP. I did and restarted >>> the laptop. >>> I still can't open it from my pc. All other pc's I can open, so this is >>> a problem with her laptop. >>> What else can I do to open it and access the folders and files? >>> Thanks in advance for your help. >> >> Is your wife's computer assigned to the same workgroup as the remote >> host to which she tries to connect? > > Yes. > >> https://www.pcworld.com/article/2191054/windows-11-how-to-set-up-a-network.html >> >> That mentions the step where you decide in which workgroup your host is >> assigned. Hosts in the same workgroup can work with each other. For >> example, you might have SOHO hosts for work-use only that you don't want >> your wife, kids, or anyone else on your intranet to access. The default >> workgroup name is "WORKGROUP" (I don't think it needs to be uppercase). >> >> The PCworld article fails to mention just how you get directly into the >> System Properties config tool without having to walk through some setup >> wizard. Run: >> >> sysdm.cpl >> >> Under the General tab, click Change (your computer name). The next >> dialog lets you specify the workgroup name. Your wife needs to use the >> same workgroup name as your other intranet hosts to which she wants to >> connect. > > All pc's and laptops use WORKGROUP. > >> In Control Panel (control.exe), select "Network and Sharing Center", is >> your wife's computer in a private or public network. Intranet sharing >> requires using a private network. Public is, well, when you're on a >> public network, and don't want anyone accessing your host. > > It's private. > >> https://support.microsoft.com/en-us/windows/essential-network-settings-and-tasks-in-windows-f21a9bbc-c582-55cd-35e0-73431160a1b9 >> which says: >> - Public network (Recommended). Use this for networks you connect to at >> home, work, or in a public place. You should use this in most cases. >> Your PC will be hidden from other devices on the network. Therefore, >> you can’t use your PC for file and printer sharing. >> - Private network. Your PC is discoverable to other devices on the >> network, and you can use your PC for file and printer sharing. You >> should know and trust the people and devices on the network. >> >> >> I can't tell from: >> >> https://learn.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3?tabs=server >> >> if SMBv2 and SMBv3 are enabled by default in Windows 11. I've seen >> other posters mentioning having to enable SMB to get home networking to >> function, but I'm not sure if that is between Windows hosts using >> auto-discovery, or between Windows hosts to Mac, Linux, or NAS hosts. >> >> Another problem I've seen discussed is that you need to have a login >> that permits access. Do the following: > > Shared folders are open for every one. In our local network that is safe. > >> - Open the run dialog (Win+R). >> - Run: control /name Microsoft.CredentialManager >> - Select Windows credentials. >> - Click Add Windows credential. >> - Enter your remote path with your Windows credentials. >> >> This is where I'm unsure about what to enter here. >> >> https://support.microsoft.com/en-us/windows/credential-manager-in-windows-1b5c916a-6a16-889f-8581-fc16e8165ac0 >> >> That was incomplete, and unhelpful in knowing on which host you define >> Windows credentials for the other host. >> >> My guess is that you run this on the host where you want to connect to >> your remote host. Supply the IP address of your remote host, and the >> login credentials for a Windows account defined on the remote host. >> Using the IP address of the remote host should work. You might be able >> to specify the hostname assigned to the remote host. > > Login credentials are not needed yet, as the laptop is completely unaccessible. > >> https://buffaloamericas.com/knowledge-base/adding-windows-credentials-of-your-nas-on-windows-10-or-windows-server-2019 >> >> That has you use the Credentials Manager on your Windows host to add >> credentials for the NAS device (remote host). > > We don't have a NAS dvice. > >> https://www.1kosmos.com/identity-management/windows-credential-manager/ >> >> pretty much says the same: define the credentials on your host for the >> remote host to which you want to connect. I'm also guessing that you >> need to specify the login credentials for an admin-level account. Do >> you have an admin account in Windows 11? No, not the Administrator >> account, but a user account you created that is in the Administrators >> security group. You can see to which security group a Windows account >> is assigned by running: >> >> net users <acctname> >> >> where <acctname> is the Windows account you want to check its info. At >> the bottom is the list of local [security] groups to which that account >> is associated. To get a list of accounts, and to which security group >> they are assigned, run: >> >> wmic useraccount list brief >> >> To see which accounts (users) are in a specific security group, run: >> >> net localgroup administrators >> >> That will list who is in the Administrators security group. If you run: >> >> net localgroup >> >> you can see which security groups are in your instance of Windows (to >> know which to specify to find out which users are under a specific >> security group). > It's not in the graphical menu, these troubleshooters do not always work that well, but give this a try. msdt.exe /id NetworkDiagnosticsFileShare Paul
[toc] | [prev] | [next] | [standalone]
| From | VanguardLH <V@nguard.LH> |
|---|---|
| Date | 2025-04-27 10:19 -0500 |
| Message-ID | <q31vb63ng1cn.dlg@v.nguard.lh> |
| In reply to | #18734 |
Paul <nospam@needed.invalid> wrote: > It's not in the graphical menu, https://support.microsoft.com/en-us/windows/fix-wi-fi-connection-issues-in-windows-9424a1f7-6a3b-65a6-4d78-7f07eee84d2c#id0ebh=windows_10 Select Windows 10, and it shows the Start menu navigation to run the network troubleshooter. Select Windows 11, and it says to run some "Get Help" app. Two different means of loading msdt.exe. Geesh, I wonder how much dumber they could make using their troubleshooter. I know: they'll make you use Copilot. > these troubleshooters do not always work that well, but give this a try. > > msdt.exe /id NetworkDiagnosticsFileShare Most times the troubleshooter doesn't help, but occasionally it does. I was going to suggest that, but you beat me to it. He might want to run msdt on his and her computers.
[toc] | [prev] | [next] | [standalone]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2025-04-27 11:25 -0400 |
| Message-ID | <vuli8e$139a3$1@dont-email.me> |
| In reply to | #18736 |
On Sun, 4/27/2025 11:19 AM, VanguardLH wrote: > Paul <nospam@needed.invalid> wrote: > >> It's not in the graphical menu, > > https://support.microsoft.com/en-us/windows/fix-wi-fi-connection-issues-in-windows-9424a1f7-6a3b-65a6-4d78-7f07eee84d2c#id0ebh=windows_10 > > Select Windows 10, and it shows the Start menu navigation to run the > network troubleshooter. > > Select Windows 11, and it says to run some "Get Help" app. > > Two different means of loading msdt.exe. Geesh, I wonder how much > dumber they could make using their troubleshooter. I know: they'll make > you use Copilot. > >> these troubleshooters do not always work that well, but give this a try. >> >> msdt.exe /id NetworkDiagnosticsFileShare > > Most times the troubleshooter doesn't help, but occasionally it does. I > was going to suggest that, but you beat me to it. He might want to run > msdt on his and her computers. > There are two troubleshooters that I know of. There is a "general network troubleshooter", which happens to emit the two commands to "reset networking". That usually helps with a particular file sharing bug. Whereas the above command line invocation, is supposed to be file sharing specific. And it might not be in the Troubleshooters list. They have messed with that Throubleshooters list so many times, I can't really be sure what *any* users see in the screen any more. And, the dumbasses have done this to *every* OS, there are troubleshooters at first, and they gradually remove them. Using the command line, is to remove the uncertainty of the graphical presentation. Paul
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-04-27 19:12 +0200 |
| Message-ID | <m776siFji1tU2@mid.individual.net> |
| In reply to | #18734 |
On 27/04/2025 15:32, Paul wrote: > On Sun, 4/27/2025 7:30 AM, Fokke Nauta wrote: >> On 27/04/2025 12:50, VanguardLH wrote: >>> Fokke Nauta <fnauta@solfon.nl> wrote: >>> >>>> My wife has a W11 Pro laptop. It is visable in the network but I can't >>>> open it. Her network detection is on, just as file and printer sharing. >>>> It is on a private network. >>>> When I try to open it from my pc, I get the message "Windows cannot >>>> access" the name of her laptop. Error code 0x80070035. >>>> This code says how to Enable NetBIOS over TCP / IP. I did and restarted >>>> the laptop. >>>> I still can't open it from my pc. All other pc's I can open, so this is >>>> a problem with her laptop. >>>> What else can I do to open it and access the folders and files? >>>> Thanks in advance for your help. >>> >>> Is your wife's computer assigned to the same workgroup as the remote >>> host to which she tries to connect? >> >> Yes. >> >>> https://www.pcworld.com/article/2191054/windows-11-how-to-set-up-a-network.html >>> >>> That mentions the step where you decide in which workgroup your host is >>> assigned. Hosts in the same workgroup can work with each other. For >>> example, you might have SOHO hosts for work-use only that you don't want >>> your wife, kids, or anyone else on your intranet to access. The default >>> workgroup name is "WORKGROUP" (I don't think it needs to be uppercase). >>> >>> The PCworld article fails to mention just how you get directly into the >>> System Properties config tool without having to walk through some setup >>> wizard. Run: >>> >>> sysdm.cpl >>> >>> Under the General tab, click Change (your computer name). The next >>> dialog lets you specify the workgroup name. Your wife needs to use the >>> same workgroup name as your other intranet hosts to which she wants to >>> connect. >> >> All pc's and laptops use WORKGROUP. >> >>> In Control Panel (control.exe), select "Network and Sharing Center", is >>> your wife's computer in a private or public network. Intranet sharing >>> requires using a private network. Public is, well, when you're on a >>> public network, and don't want anyone accessing your host. >> >> It's private. >> >>> https://support.microsoft.com/en-us/windows/essential-network-settings-and-tasks-in-windows-f21a9bbc-c582-55cd-35e0-73431160a1b9 >>> which says: >>> - Public network (Recommended). Use this for networks you connect to at >>> home, work, or in a public place. You should use this in most cases. >>> Your PC will be hidden from other devices on the network. Therefore, >>> you can’t use your PC for file and printer sharing. >>> - Private network. Your PC is discoverable to other devices on the >>> network, and you can use your PC for file and printer sharing. You >>> should know and trust the people and devices on the network. >>> >>> >>> I can't tell from: >>> >>> https://learn.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3?tabs=server >>> >>> if SMBv2 and SMBv3 are enabled by default in Windows 11. I've seen >>> other posters mentioning having to enable SMB to get home networking to >>> function, but I'm not sure if that is between Windows hosts using >>> auto-discovery, or between Windows hosts to Mac, Linux, or NAS hosts. >>> >>> Another problem I've seen discussed is that you need to have a login >>> that permits access. Do the following: >> >> Shared folders are open for every one. In our local network that is safe. >> >>> - Open the run dialog (Win+R). >>> - Run: control /name Microsoft.CredentialManager >>> - Select Windows credentials. >>> - Click Add Windows credential. >>> - Enter your remote path with your Windows credentials. >>> >>> This is where I'm unsure about what to enter here. >>> >>> https://support.microsoft.com/en-us/windows/credential-manager-in-windows-1b5c916a-6a16-889f-8581-fc16e8165ac0 >>> >>> That was incomplete, and unhelpful in knowing on which host you define >>> Windows credentials for the other host. >>> >>> My guess is that you run this on the host where you want to connect to >>> your remote host. Supply the IP address of your remote host, and the >>> login credentials for a Windows account defined on the remote host. >>> Using the IP address of the remote host should work. You might be able >>> to specify the hostname assigned to the remote host. >> >> Login credentials are not needed yet, as the laptop is completely unaccessible. >> >>> https://buffaloamericas.com/knowledge-base/adding-windows-credentials-of-your-nas-on-windows-10-or-windows-server-2019 >>> >>> That has you use the Credentials Manager on your Windows host to add >>> credentials for the NAS device (remote host). >> >> We don't have a NAS dvice. >> >>> https://www.1kosmos.com/identity-management/windows-credential-manager/ >>> >>> pretty much says the same: define the credentials on your host for the >>> remote host to which you want to connect. I'm also guessing that you >>> need to specify the login credentials for an admin-level account. Do >>> you have an admin account in Windows 11? No, not the Administrator >>> account, but a user account you created that is in the Administrators >>> security group. You can see to which security group a Windows account >>> is assigned by running: >>> >>> net users <acctname> >>> >>> where <acctname> is the Windows account you want to check its info. At >>> the bottom is the list of local [security] groups to which that account >>> is associated. To get a list of accounts, and to which security group >>> they are assigned, run: >>> >>> wmic useraccount list brief >>> >>> To see which accounts (users) are in a specific security group, run: >>> >>> net localgroup administrators >>> >>> That will list who is in the Administrators security group. If you run: >>> >>> net localgroup >>> >>> you can see which security groups are in your instance of Windows (to >>> know which to specify to find out which users are under a specific >>> security group). >> > > It's not in the graphical menu, these troubleshooters do not always > work that well, but give this a try. > > msdt.exe /id NetworkDiagnosticsFileShare From my pc: Troubleshoother couldn't identify the problem. From my wife's laptop: Troubleshooters are being moved and this utility is being retired. Microsoft Support Diagnostic Tool (MSDT) and MSDT Troubleshooters are being deprecated. > Paul With regards, Fokke
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2025-04-27 17:53 +0000 |
| Message-ID | <vum20c.10lg.1@ID-201911.user.individual.net> |
| In reply to | #18742 |
Fokke Nauta <fnauta@solfon.nl> wrote: > On 27/04/2025 15:32, Paul wrote: [Endless needless quotes snipped. No, you're not the only one.] > > It's not in the graphical menu, these troubleshooters do not always > > work that well, but give this a try. > > > > msdt.exe /id NetworkDiagnosticsFileShare > > From my pc: Troubleshoother couldn't identify the problem. > From my wife's laptop: Troubleshooters are being moved and this utility > is being retired. > Microsoft Support Diagnostic Tool (MSDT) and MSDT Troubleshooters are > being deprecated. That doesn't seem quite right. You say your wife's laptop has Windows 11, but on my Windows 11 (24H2) laptop, this 'Shared Folders' troubleshooting tool still *does* still exist and 'works' [1]. Which Windows 11 version (2YH2) does your wife's laptop have? [1] 'Succeeds' for share '\\bogus' and (correctly) fails for share 'bogus'.
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-04-28 11:53 +0200 |
| Message-ID | <m791gjFskpsU1@mid.individual.net> |
| In reply to | #18747 |
On 27/04/2025 19:53, Frank Slootweg wrote: > Fokke Nauta <fnauta@solfon.nl> wrote: >> On 27/04/2025 15:32, Paul wrote: > > [Endless needless quotes snipped. No, you're not the only one.] > >>> It's not in the graphical menu, these troubleshooters do not always >>> work that well, but give this a try. >>> >>> msdt.exe /id NetworkDiagnosticsFileShare >> >> From my pc: Troubleshoother couldn't identify the problem. >> From my wife's laptop: Troubleshooters are being moved and this utility >> is being retired. >> Microsoft Support Diagnostic Tool (MSDT) and MSDT Troubleshooters are >> being deprecated. > > That doesn't seem quite right. You say your wife's laptop has Windows > 11, but on my Windows 11 (24H2) laptop, this 'Shared Folders' > troubleshooting tool still *does* still exist and 'works' [1]. > > Which Windows 11 version (2YH2) does your wife's laptop have? 24H2 > [1] 'Succeeds' for share '\\bogus' and (correctly) fails for share > 'bogus'.
[toc] | [prev] | [next] | [standalone]
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2025-04-27 14:42 -0400 |
| Message-ID | <vultqr$1dhja$1@dont-email.me> |
| In reply to | #18742 |
On Sun, 4/27/2025 1:12 PM, Fokke Nauta wrote:
> On 27/04/2025 15:32, Paul wrote:
>> msdt.exe /id NetworkDiagnosticsFileShare
>
> From my pc: Troubleshoother couldn't identify the problem.
> From my wife's laptop: Troubleshooters are being moved and this utility is being retired.
> Microsoft Support Diagnostic Tool (MSDT) and MSDT Troubleshooters are being deprecated.
This seems to have happened on another HP box. No msdt.exe .
https://answers.microsoft.com/en-us/windows/forum/all/error-cwindowssystem32msdtexe/53f8db72-a66b-4c3e-9d22-d2d900d22d1c
If you use Start : Run : control.exe and then look for the Troubleshooting control panel,
that is supposed to have them. That's how you would normally go about accessing it.
C:\Windows\diagnostics\index
NetworkDiagnostics_2_FileShare.xml
It looks like it is part of Networking.
Yet running the network troubleshooter, doesn't
offer that in the first screen.
Paul
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-04-28 12:12 +0200 |
| Message-ID | <m792k8FskpsU2@mid.individual.net> |
| In reply to | #18748 |
On 27/04/2025 20:42, Paul wrote: > On Sun, 4/27/2025 1:12 PM, Fokke Nauta wrote: >> On 27/04/2025 15:32, Paul wrote: > >>> msdt.exe /id NetworkDiagnosticsFileShare >> >> From my pc: Troubleshoother couldn't identify the problem. >> From my wife's laptop: Troubleshooters are being moved and this utility is being retired. >> Microsoft Support Diagnostic Tool (MSDT) and MSDT Troubleshooters are being deprecated. > > This seems to have happened on another HP box. No msdt.exe . > > https://answers.microsoft.com/en-us/windows/forum/all/error-cwindowssystem32msdtexe/53f8db72-a66b-4c3e-9d22-d2d900d22d1c > > If you use Start : Run : control.exe and then look for the Troubleshooting control panel, > that is supposed to have them. That's how you would normally go about accessing it. > > C:\Windows\diagnostics\index > > NetworkDiagnostics_2_FileShare.xml I did. I see a list of comments and results, and the message "This XML file does not appear to have any style information associated with it. The document tree is shown below" > It looks like it is part of Networking. > Yet running the network troubleshooter, doesn't > offer that in the first screen. > > Paul Fokke
[toc] | [prev] | [next] | [standalone]
| From | VanguardLH <V@nguard.LH> |
|---|---|
| Date | 2025-04-27 21:20 -0500 |
| Message-ID | <3q9r7zon7e6x.dlg@v.nguard.lh> |
| In reply to | #18742 |
Fokke Nauta <fnauta@solfon.nl> wrote: > From my pc: Troubleshoother couldn't identify the problem. > From my wife's laptop: Troubleshooters are being moved and this utility > is being retired. > Microsoft Support Diagnostic Tool (MSDT) and MSDT Troubleshooters are > being deprecated. wmic.exe is deprecated, too. You're supposed to switch to PowerShell to use commands to the WMI API. However, wmic.exe still works until it has been removed which means eventually in some future version of Windows it will not be included. msdt.exe gave some error, and refused to load?
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-04-28 12:26 +0200 |
| Message-ID | <m793ehFskpsU3@mid.individual.net> |
| In reply to | #18750 |
On 28/04/2025 04:20, VanguardLH wrote: > Fokke Nauta <fnauta@solfon.nl> wrote: > >> From my pc: Troubleshoother couldn't identify the problem. >> From my wife's laptop: Troubleshooters are being moved and this utility >> is being retired. >> Microsoft Support Diagnostic Tool (MSDT) and MSDT Troubleshooters are >> being deprecated. > > wmic.exe is deprecated, too. You're supposed to switch to PowerShell to > use commands to the WMI API. However, wmic.exe still works until it has > been removed which means eventually in some future version of Windows it > will not be included. > > msdt.exe gave some error, and refused to load? It did load but I need a key that I got from a support assistance. Thais is bullshit, ofcourse. It also said "Troubleshooters have been moved and this utility will be deprecated." Fokke
[toc] | [prev] | [next] | [standalone]
| From | VanguardLH <V@nguard.LH> |
|---|---|
| Date | 2025-04-28 07:58 -0500 |
| Message-ID | <nc5boq0no2r2$.dlg@v.nguard.lh> |
| In reply to | #18755 |
Fokke Nauta <fnauta@solfon.nl> wrote: > VanguardLH wrote: > >> Fokke Nauta <fnauta@solfon.nl> wrote: >> >>> From my pc: Troubleshoother couldn't identify the problem. >>> From my wife's laptop: Troubleshooters are being moved and this utility >>> is being retired. >>> Microsoft Support Diagnostic Tool (MSDT) and MSDT Troubleshooters are >>> being deprecated. >> >> msdt.exe gave some error, and refused to load? > > It did load but I need a key that I got from a support assistance. Thais > is bullshit, ofcourse. > It also said "Troubleshooters have been moved and this utility will be > deprecated." Yeah, that is when invoked with no command-line parameters. I got that, too, on Windows 10. Invoke it with the command line that includes the "/id NetworkDiagnosticsFileShare" argument that Paul mentioned. For Windows 10, I can get at the troubleshooter using the Start menu for navigation. When I loaded it that way, and saw msdt.exe show up in Task Manager, I used SysInternals' Process Explorer to see if there were arguments in the command line, but it didn't show any. In the MS article I mentioned before in a reply to Paul, and for Windows 11, you use the Get Help app to dig out the troubleshooter. If you didn't disable Copilot, maybe that can start the troubleshooter. https://support.microsoft.com/en-us/topic/getting-started-with-copilot-on-windows-1159c61f-86c3-4755-bf83-7fbff7e0982d Not sure what you'd ask it, but maybe "network troubleshoot" would work. Your reply to Paul looked like you did run the troubleshooter, not that it refused to load or start. Yet what you said made it appear your computer had a different version of Windows than your wife. On your computer, the troubleshooter ran, but didn't find a problem. On your wife's, a message appeared about deprecation, but that was unclear if it just showed the message, and refused to run. In any case, sometimes the troubleshooters find a problem, but more often they don't. They're not very intelligent, and they don't check much, plus they aren't trying to connect to anywhere to actually testing networking. From another reply from you, there are more than just your computer and your wife's on your intranet. "All other pc's I can open" which probably meant you have other computers to which yours can connect. How about the "other pc's": can they connect to your wife's computer?
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-04-28 15:31 +0200 |
| Message-ID | <m79e9rF3qlU1@mid.individual.net> |
| In reply to | #18761 |
On 28/04/2025 14:58, VanguardLH wrote: > Fokke Nauta <fnauta@solfon.nl> wrote: > >> VanguardLH wrote: >> >>> Fokke Nauta <fnauta@solfon.nl> wrote: >>> >>>> From my pc: Troubleshoother couldn't identify the problem. >>>> From my wife's laptop: Troubleshooters are being moved and this utility >>>> is being retired. >>>> Microsoft Support Diagnostic Tool (MSDT) and MSDT Troubleshooters are >>>> being deprecated. >>> >>> msdt.exe gave some error, and refused to load? >> >> It did load but I need a key that I got from a support assistance. Thais >> is bullshit, ofcourse. >> It also said "Troubleshooters have been moved and this utility will be >> deprecated." > > Yeah, that is when invoked with no command-line parameters. I got that, > too, on Windows 10. Invoke it with the command line that includes the > "/id NetworkDiagnosticsFileShare" argument that Paul mentioned. > > For Windows 10, I can get at the troubleshooter using the Start menu for > navigation. When I loaded it that way, and saw msdt.exe show up in Task > Manager, I used SysInternals' Process Explorer to see if there were > arguments in the command line, but it didn't show any. > > In the MS article I mentioned before in a reply to Paul, and for Windows > 11, you use the Get Help app to dig out the troubleshooter. If you > didn't disable Copilot, maybe that can start the troubleshooter. > > https://support.microsoft.com/en-us/topic/getting-started-with-copilot-on-windows-1159c61f-86c3-4755-bf83-7fbff7e0982d > > Not sure what you'd ask it, but maybe "network troubleshoot" would work. I'll have a look at copilot. It's new for me. > Your reply to Paul looked like you did run the troubleshooter, not that > it refused to load or start. Yet what you said made it appear your > computer had a different version of Windows than your wife. Yes. My pc has W10 Pro, my wife's laptop has W11 Pro. On your > computer, the troubleshooter ran, but didn't find a problem. On your > wife's, a message appeared about deprecation, but that was unclear if it > just showed the message, and refused to run. > > In any case, sometimes the troubleshooters find a problem, but more > often they don't. They're not very intelligent, and they don't check > much, plus they aren't trying to connect to anywhere to actually testing > networking. > > From another reply from you, there are more than just your computer and > your wife's on your intranet. "All other pc's I can open" which > probably meant you have other computers to which yours can connect. Correct. How > about the "other pc's": can they connect to your wife's computer? No, they can't either. Fokke
[toc] | [prev] | [next] | [standalone]
| From | VanguardLH <V@nguard.LH> |
|---|---|
| Date | 2025-04-27 11:24 -0500 |
| Message-ID | <12ms3gulh2znv$.dlg@v.nguard.lh> |
| In reply to | #18731 |
Fokke Nauta <fnauta@solfon.nl> wrote: > On 27/04/2025 12:50, VanguardLH wrote: >> Fokke Nauta <fnauta@solfon.nl> wrote: >> >>> My wife has a W11 Pro laptop. It is visable in the network but I can't >>> open it. Her network detection is on, just as file and printer sharing. >>> It is on a private network. >>> When I try to open it from my pc, I get the message "Windows cannot >>> access" the name of her laptop. Error code 0x80070035. >>> This code says how to Enable NetBIOS over TCP / IP. I did and restarted >>> the laptop. >>> I still can't open it from my pc. All other pc's I can open, so this is >>> a problem with her laptop. >>> What else can I do to open it and access the folders and files? >>> Thanks in advance for your help. >> >> Is your wife's computer assigned to the same workgroup as the remote >> host to which she tries to connect? > > Yes. > >> https://www.pcworld.com/article/2191054/windows-11-how-to-set-up-a-network.html >> >> That mentions the step where you decide in which workgroup your host is >> assigned. Hosts in the same workgroup can work with each other. For >> example, you might have SOHO hosts for work-use only that you don't want >> your wife, kids, or anyone else on your intranet to access. The default >> workgroup name is "WORKGROUP" (I don't think it needs to be uppercase). >> >> The PCworld article fails to mention just how you get directly into the >> System Properties config tool without having to walk through some setup >> wizard. Run: >> >> sysdm.cpl >> >> Under the General tab, click Change (your computer name). The next >> dialog lets you specify the workgroup name. Your wife needs to use the >> same workgroup name as your other intranet hosts to which she wants to >> connect. > > All pc's and laptops use WORKGROUP. > >> In Control Panel (control.exe), select "Network and Sharing Center", is >> your wife's computer in a private or public network. Intranet sharing >> requires using a private network. Public is, well, when you're on a >> public network, and don't want anyone accessing your host. > > It's private. > >> https://support.microsoft.com/en-us/windows/essential-network-settings-and-tasks-in-windows-f21a9bbc-c582-55cd-35e0-73431160a1b9 >> which says: >> - Public network (Recommended). Use this for networks you connect to at >> home, work, or in a public place. You should use this in most cases. >> Your PC will be hidden from other devices on the network. Therefore, >> you can’t use your PC for file and printer sharing. >> - Private network. Your PC is discoverable to other devices on the >> network, and you can use your PC for file and printer sharing. You >> should know and trust the people and devices on the network. >> >> I can't tell from: >> >> https://learn.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3?tabs=server >> >> if SMBv2 and SMBv3 are enabled by default in Windows 11. I've seen >> other posters mentioning having to enable SMB to get home networking to >> function, but I'm not sure if that is between Windows hosts using >> auto-discovery, or between Windows hosts to Mac, Linux, or NAS hosts. >> >> Another problem I've seen discussed is that you need to have a login >> that permits access. Do the following: > > Shared folders are open for every one. In our local network that is safe. > >> - Open the run dialog (Win+R). >> - Run: control /name Microsoft.CredentialManager >> - Select Windows credentials. >> - Click Add Windows credential. >> - Enter your remote path with your Windows credentials. >> >> This is where I'm unsure about what to enter here. >> >> https://support.microsoft.com/en-us/windows/credential-manager-in-windows-1b5c916a-6a16-889f-8581-fc16e8165ac0 >> >> That was incomplete, and unhelpful in knowing on which host you define >> Windows credentials for the other host. >> >> My guess is that you run this on the host where you want to connect to >> your remote host. Supply the IP address of your remote host, and the >> login credentials for a Windows account defined on the remote host. >> Using the IP address of the remote host should work. You might be able >> to specify the hostname assigned to the remote host. > > Login credentials are not needed yet, as the laptop is completely > unaccessible. > >> https://buffaloamericas.com/knowledge-base/adding-windows-credentials-of-your-nas-on-windows-10-or-windows-server-2019 >> >> That has you use the Credentials Manager on your Windows host to add >> credentials for the NAS device (remote host). > > We don't have a NAS dvice. > >> https://www.1kosmos.com/identity-management/windows-credential-manager/ >> >> pretty much says the same: define the credentials on your host for the >> remote host to which you want to connect. I'm also guessing that you >> need to specify the login credentials for an admin-level account. Do >> you have an admin account in Windows 11? No, not the Administrator >> account, but a user account you created that is in the Administrators >> security group. You can see to which security group a Windows account >> is assigned by running: >> >> net users <acctname> >> >> where <acctname> is the Windows account you want to check its info. At >> the bottom is the list of local [security] groups to which that account >> is associated. To get a list of accounts, and to which security group >> they are assigned, run: >> >> wmic useraccount list brief >> >> To see which accounts (users) are in a specific security group, run: >> >> net localgroup administrators >> >> That will list who is in the Administrators security group. If you run: >> >> net localgroup >> >> you can see which security groups are in your instance of Windows (to >> know which to specify to find out which users are under a specific >> security group). You said your wife is using Windows 11, but didn't mention what you are using on your computer when trying to connect to her computer. you (what?) ---> her (Windows 11) How about the other direction: can she on Windows 11 access your computer? How do connect to the router: Ethernet or wifi? What connection type for the other hosts which you can access? And her? Can both you and her get to the Internet? How about to the router's internal web server? Mine is http://10.0.0.1, but yours could have a different LAN-side IP address. In File Explorer, are you entering just the hostname of her computer, or a shared folder on her computer? That is, are you entering: \\<hercomputername> or \\<hercomputername>\c$ or \\<hercomputer>\c$\<somefolder> or \\<hercomputername>\<sharedfoldername> C$, D$, and so on are hidden shares of drives (root folders), so you can access any folder by its name under the root folder of a drive on the remote host (as long as you have permissions under whatever account you use) instead of by the folder's sharename. In File Explorer on her computer (where you are trying to access shared folders), right-click on the folder you want to share, select "Give access to" and "Advanced sharing" in the context menu. Is the Share button enabled? If not, click the Advanced Sharing button to check "Share this folder" is selected, and, if so, what sharename you gave to that folder. Does she have any shares? On her computer, run: compmgmt.msc to see if anything is listed under Shared Folders -> Shares. Is network discovery enabled on both hosts? In Windows 10: Settings -> Network & Internet -> Status -> Network and Sharing Center -> Change advanced sharing settings. Might be a different navpath in Windows 11. You said both hosts are configured to use a Private network profile (required for file/folder sharing). Is "Turn on network discovery" enabled, and its "Turn on automatic setup of network connected devices"? Can you map a drive letter to her computer? File Explorer -> Computer tab -> Map a drive. Run ncpa.cpl, and right-click on the connectoid you/she is using to connect to your intranet to look at Properties? What protocols are selected? Under Windows 10, the ones I have enabled are: Client fro Microsoft Networks File and Printer Sharing for Microsoft Networks Npcap Packet Driver (NPF) Npcap Packet Driver (NPCAP) QoS Packet Scheduler Internet Protocol Version 4 (TCP/IPv4) Microsoft LLDP Protocol Driver Internet Protocol Version 6 (TCP/IPv6) Link-Layer Topology Discovery Responder Link-Layer Topology Discovery Mapper I/O Driver The Npcap entries might be due to me using streaming capture software that installs Npcap (https://en.wikipedia.org/wiki/Pcap#Npcap).
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-04-27 18:59 +0200 |
| Message-ID | <m7764eFji1tU1@mid.individual.net> |
| In reply to | #18739 |
On 27/04/2025 18:24, VanguardLH wrote: > Fokke Nauta <fnauta@solfon.nl> wrote: > >> On 27/04/2025 12:50, VanguardLH wrote: >>> Fokke Nauta <fnauta@solfon.nl> wrote: >>> >>>> My wife has a W11 Pro laptop. It is visable in the network but I can't >>>> open it. Her network detection is on, just as file and printer sharing. >>>> It is on a private network. >>>> When I try to open it from my pc, I get the message "Windows cannot >>>> access" the name of her laptop. Error code 0x80070035. >>>> This code says how to Enable NetBIOS over TCP / IP. I did and restarted >>>> the laptop. >>>> I still can't open it from my pc. All other pc's I can open, so this is >>>> a problem with her laptop. >>>> What else can I do to open it and access the folders and files? >>>> Thanks in advance for your help. >>> (cut) > You said your wife is using Windows 11, but didn't mention what you are > using on your computer when trying to connect to her computer. W10 Pro > you (what?) ---> her (Windows 11) > > How about the other direction: can she on Windows 11 access your > computer? Yes, no problem. > How do connect to the router: Ethernet or wifi? What connection type > for the other hosts which you can access? And her? All pc's by ethernet. Both laptops (my wife's and mine) by wifi. > Can both you and her get to the Internet? Yes. How about to the router's > internal web server? Mine is http://10.0.0.1, but yours could have a > different LAN-side IP address. Yes. 192.168.1.1 > In File Explorer, are you entering just the hostname of her computer, or > a shared folder on her computer? That is, are you entering: > > \\<hercomputername> > > or > > \\<hercomputername>\c$ > > or > > \\<hercomputer>\c$\<somefolder> > > or > > \\<hercomputername>\<sharedfoldername> No. I double click on her name of her laptop and can't open it. It says Windows cannot acces her computer name. I can't acces her folders. > > C$, D$, and so on are hidden shares of drives (root folders), so you can > access any folder by its name under the root folder of a drive on the > remote host (as long as you have permissions under whatever account you > use) instead of by the folder's sharename. > > In File Explorer on her computer (where you are trying to access shared > folders), right-click on the folder you want to share, select "Give > access to" and "Advanced sharing" in the context menu. Is the Share > button enabled? If not, click the Advanced Sharing button to check > "Share this folder" is selected, and, if so, what sharename you gave to > that folder. > > Does she have any shares? On her computer, run: Yes, ofcourse she has shared folders. > compmgmt.msc > > to see if anything is listed under Shared Folders -> Shares. > > Is network discovery enabled on both hosts? Yes. > In Windows 10: Settings -> > Network & Internet -> Status -> Network and Sharing Center -> Change > advanced sharing settings. Might be a different navpath in Windows 11. > You said both hosts are configured to use a Private network profile > (required for file/folder sharing). Is "Turn on network discovery" > enabled, and its "Turn on automatic setup of network connected devices"? > > Can you map a drive letter to her computer? File Explorer -> Computer > tab -> Map a drive. No. Can't acces her laptop. > Run ncpa.cpl, and right-click on the connectoid you/she is using to > connect to your intranet to look at Properties? What protocols are > selected? Under Windows 10, the ones I have enabled are: > > Client fro Microsoft Networks > File and Printer Sharing for Microsoft Networks > Npcap Packet Driver (NPF) > Npcap Packet Driver (NPCAP) > QoS Packet Scheduler > Internet Protocol Version 4 (TCP/IPv4) > Microsoft LLDP Protocol Driver > Internet Protocol Version 6 (TCP/IPv6) > Link-Layer Topology Discovery Responder > Link-Layer Topology Discovery Mapper I/O Driver > > The Npcap entries might be due to me using streaming capture software > that installs Npcap (https://en.wikipedia.org/wiki/Pcap#Npcap). From my pc I can see all other folders on our pc's and my laptop. Fokke
[toc] | [prev] | [next] | [standalone]
Page 1 of 11 [1] 2 3 … 11 Next page →
Back to top | Article view | alt.comp.os.windows-11
csiph-web