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 9 of 11 — ← Prev page 1 … 7 8 [9] 10 11 Next page →
| From | Paul <nospam@needed.invalid> |
|---|---|
| Date | 2025-05-07 16:58 -0400 |
| Message-ID | <vvghhd$186hg$2@dont-email.me> |
| In reply to | #19155 |
On Wed, 5/7/2025 12:40 PM, Fokke Nauta wrote: > On 07/05/2025 15:56, Paul wrote: >> On Wed, 5/7/2025 4:57 AM, Fokke Nauta wrote: >>> On 05/05/2025 12:40, Java Jive wrote: >>>> On 2025-05-05 11:00, Fokke Nauta wrote: >>>>> On 02/05/2025 22:49, Java Jive wrote: >>>>>> On 2025-05-02 19:15, Fokke Nauta wrote: >>>>>>> On 02/05/2025 19:41, Java Jive wrote: >>>>>>>> On 2025-05-02 18:06, Fokke Nauta wrote: >>>>>>>>> >>>>>>>>> On 02/05/2025 15:52, Java Jive wrote: >>>>>>>>>> >>>>>>>>>> On 2025-05-02 13:42, Fokke Nauta wrote: >>>>>>>>>>> >>>>>>>>>>> On 02/05/2025 11:59, Fokke Nauta wrote: >>>>>>>>>>>> >>>>>>>>>>>> On 01/05/2025 18:38, Java Jive wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> Also, on a non-problem PC, select Network in Explorer, in the right-hand windows pane ... >>>>>>>>>>>>> >>>>>>>>>>>>> <rt-click> in a blank area >>>>>>>>>>>>> Group by >>>>>>>>>>>>> More ... >>>>>>>>>>>>> Select 'Discovery Method' and give it a width of, say, 64 >>>>>>>>>>>>> Click OK >>>>>>>>>>>>> >>>>>>>>>>>>> Does the problem PC show the same discovery method as the other non-problem PCs? >>>>>>>>>>>> >>>>>>>>>>>> I'll check this out as well. >>>>>>>>>>>>> >>>>>>>>>>>>> I think it would be worth repeating this on the problem PC, even though I'm not sure how interesting the result would be, given that it can't see much, if anything. >>>>>>>>>> >>>>>>>>>> Did you get around to trying this? As other possibilities fall by the wayside, this one assumes greater importance. >>>>>>>> >>>>>>>> Still no answer to this? >>>>>>>> >>>>>>> >>>>>>> Yes, I did. >>>>>>> Didn't make any difference. >>>>>> >>>>>> I wasn't expecting it to make a difference, I was hoping it might show useful information which you would then relay on to us. What method is discovering ... >>>>>> The non-problem PCs; >>>>>> The problem PC? >>>>>> >>>>> What do you mean by that? >>>> >>>> Follow the instructions still quoted above to display the column for the discovery method used to find each PC listed in Network, and then tell us what method is listed in that column for both a non-problem PC and the problem PC. What are they in each case, and, in particular, are they different? >>>> >>> >>> Yes, they are different. On my wife's laptop I enabled 64, on my own pc it's 80, and on the server pc it is 240. I didn't check the 3rd pc and my laptop. >>> >>> Fokke >> >> Here is a picture of what Java is doing. >> >> [Picture] >> >> https://i.postimg.cc/J4YqmpSD/Network-Discovery-Method.gif >> >> Paul > > How would I get that? > > Fokke That is the Network item (click it) on the left hand side of File Explorer. Then, go to the View tab, and change the View so you get Details. The columns showing in Details can be edited, as shown by the drop-down menu on the right of the picture. Paul
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-05-09 13:56 +0200 |
| Message-ID | <m868s0FipppU2@mid.individual.net> |
| In reply to | #19161 |
On 07/05/2025 22:58, Paul wrote: > On Wed, 5/7/2025 12:40 PM, Fokke Nauta wrote: >> On 07/05/2025 15:56, Paul wrote: >>> On Wed, 5/7/2025 4:57 AM, Fokke Nauta wrote: >>>> On 05/05/2025 12:40, Java Jive wrote: >>>>> On 2025-05-05 11:00, Fokke Nauta wrote: >>>>>> On 02/05/2025 22:49, Java Jive wrote: >>>>>>> On 2025-05-02 19:15, Fokke Nauta wrote: >>>>>>>> On 02/05/2025 19:41, Java Jive wrote: >>>>>>>>> On 2025-05-02 18:06, Fokke Nauta wrote: >>>>>>>>>> >>>>>>>>>> On 02/05/2025 15:52, Java Jive wrote: >>>>>>>>>>> >>>>>>>>>>> On 2025-05-02 13:42, Fokke Nauta wrote: >>>>>>>>>>>> >>>>>>>>>>>> On 02/05/2025 11:59, Fokke Nauta wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> On 01/05/2025 18:38, Java Jive wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> Also, on a non-problem PC, select Network in Explorer, in the right-hand windows pane ... >>>>>>>>>>>>>> >>>>>>>>>>>>>> <rt-click> in a blank area >>>>>>>>>>>>>> Group by >>>>>>>>>>>>>> More ... >>>>>>>>>>>>>> Select 'Discovery Method' and give it a width of, say, 64 >>>>>>>>>>>>>> Click OK >>>>>>>>>>>>>> >>>>>>>>>>>>>> Does the problem PC show the same discovery method as the other non-problem PCs? >>>>>>>>>>>>> >>>>>>>>>>>>> I'll check this out as well. >>>>>>>>>>>>>> >>>>>>>>>>>>>> I think it would be worth repeating this on the problem PC, even though I'm not sure how interesting the result would be, given that it can't see much, if anything. >>>>>>>>>>> >>>>>>>>>>> Did you get around to trying this? As other possibilities fall by the wayside, this one assumes greater importance. >>>>>>>>> >>>>>>>>> Still no answer to this? >>>>>>>>> >>>>>>>> >>>>>>>> Yes, I did. >>>>>>>> Didn't make any difference. >>>>>>> >>>>>>> I wasn't expecting it to make a difference, I was hoping it might show useful information which you would then relay on to us. What method is discovering ... >>>>>>> The non-problem PCs; >>>>>>> The problem PC? >>>>>>> >>>>>> What do you mean by that? >>>>> >>>>> Follow the instructions still quoted above to display the column for the discovery method used to find each PC listed in Network, and then tell us what method is listed in that column for both a non-problem PC and the problem PC. What are they in each case, and, in particular, are they different? >>>>> >>>> >>>> Yes, they are different. On my wife's laptop I enabled 64, on my own pc it's 80, and on the server pc it is 240. I didn't check the 3rd pc and my laptop. >>>> >>>> Fokke >>> >>> Here is a picture of what Java is doing. >>> >>> [Picture] >>> >>> https://i.postimg.cc/J4YqmpSD/Network-Discovery-Method.gif >>> >>> Paul >> >> How would I get that? >> >> Fokke > > That is the Network item (click it) on the left hand side of File Explorer. Did it. > > Then, go to the View tab, and change the View so you get Details. The View was already in Details. > > The columns showing in Details can be edited, as shown by the drop-down menu on the right of the picture. > > Paul There is no column named Details. There is one with Name, Discovery Method, and Network location. A column named Details is not available. Fokke
[toc] | [prev] | [next] | [standalone]
| From | Graham J <nobody@nowhere.co.uk> |
|---|---|
| Date | 2025-05-02 15:01 +0100 |
| Message-ID | <vv2j97$18j2k$1@dont-email.me> |
| In reply to | #18964 |
Fokke Nauta wrote: [snip] > To my pc (192.168.1.141) it didn't work. Request timed out. > To the server (192.168.1.140) it worked well. To clarify: From Problem_W11_Laptop: ping 192.168.1.140 works From Problem_W11_Laptop: ping 192.168.1.141 fails This is unexpected. It suggests a firewall or other misconfiguration on the machine 192.168.1.141. While this will not be the cause of the non visibility of Problem_W11_Laptop from other machines you should find out the cause of the failure and correct it. Then apply the knowledge gained to all the other machines. I think the default setting for all Windows firewalls is to allow ping from the LAN. Clearly if you have any non-Microsoft firewalls disable them for the present. I think you have 5 machines. Please check that every one of them can ping all the others, and summarise any failures for us. Thus, from A: Ping B, Ping C, Ping D, Ping E. From B: Ping C, Ping D, Ping E, Ping A. ... etc. You've explained that the router does not provide WiFi so you have an AP. You've also mentioned switches: how many? How are they connected? Can you connect all the computers via Ethernet cable directly to the router, for testing? This would eliminate any problems with the switches or AP. I understand that some laptops don't have Ethernet sockets so you might have to leave these using WiFi. But make sure the AP connects directly to the router, not via a switch. Also, to avoid confusing us and yourself, when working with a computer do so by sitting at it, rather than connecting via VNC. That way we can eliminate misunderstandings. -- Graham J
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-05-02 19:12 +0200 |
| Message-ID | <m7kconFn1a4U5@mid.individual.net> |
| In reply to | #18972 |
On 02/05/2025 16:01, Graham J wrote: > Fokke Nauta wrote: > > [snip] > > >> To my pc (192.168.1.141) it didn't work. Request timed out. >> To the server (192.168.1.140) it worked well. > > To clarify: > > From Problem_W11_Laptop: ping 192.168.1.140 works > > From Problem_W11_Laptop: ping 192.168.1.141 fails > This is unexpected. It suggests a firewall or other misconfiguration on > the machine 192.168.1.141. While this will not be the cause of the non > visibility of Problem_W11_Laptop from other machines you should find out > the cause of the failure and correct it. Then apply the knowledge > gained to all the other machines. I think the default setting for all > Windows firewalls is to allow ping from the LAN. Clearly if you have > any non-Microsoft firewalls disable them for the present. However, from the problem laptop she can see all shares on the other pc's. No problem. > > I think you have 5 machines. Yes. > Please check that every one of them can > ping all the others, and summarise any failures for us. > > Thus, from A: Ping B, Ping C, Ping D, Ping E. > > From B: Ping C, Ping D, Ping E, Ping A. > > ... etc. No problem. > > You've explained that the router does not provide WiFi so you have an > AP. You've also mentioned switches: how many? 2 > How are they connected? By cable from the router. > > Can you connect all the computers via Ethernet cable directly to the > router, for testing? No. > This would eliminate any problems with the > switches or AP. I understand that some laptops don't have Ethernet > sockets so you might have to leave these using WiFi. The laptops use the wifi from the AP. > But make sure the > AP connects directly to the router, not via a switch. No, it's connected via a switch and it works well. > > Also, to avoid confusing us and yourself, when working with a computer > do so by sitting at it, rather than connecting via VNC. That way we can > eliminate misunderstandings. Working via VNC works well. Fokke > >
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2025-05-02 23:12 +0100 |
| Message-ID | <m7kuapFos58U2@mid.individual.net> |
| In reply to | #18972 |
Graham J wrote: > Can you connect all the computers via Ethernet cable directly to the > router, for testing? Though let the O/P be aware that changing from wifi to wired ethernet will change the machine's IP address for pinging.
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-05-05 12:01 +0200 |
| Message-ID | <m7rgjuFrbb7U2@mid.individual.net> |
| In reply to | #18999 |
On 03/05/2025 00:12, Andy Burns wrote: > Graham J wrote: > >> Can you connect all the computers via Ethernet cable directly to the >> router, for testing? > > Though let the O/P be aware that changing from wifi to wired ethernet > will change the machine's IP address for pinging. > No. Every machine gets it's IP address from the router, depending on their MAC address. Fokke
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2025-05-05 11:13 +0100 |
| Message-ID | <m7rh9iFqqcbU4@mid.individual.net> |
| In reply to | #19052 |
Fokke Nauta wrote: > Andy Burns wrote: > >> Though let the O/P be aware that changing from wifi to wired ethernet >> will change the machine's IP address for pinging. > > No. Every machine gets it's IP address from the router, depending on > their MAC address. And it'll have a different MAC address for the WiFi NIC compared to the Ethernet NIC Or are you saying your router allows you to allocate the same IP to multiple MAC addresses (which would be unusual)?
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-05-05 13:36 +0200 |
| Message-ID | <m7rm51Fs88vU1@mid.individual.net> |
| In reply to | #19054 |
On 05/05/2025 12:13, Andy Burns wrote: > Fokke Nauta wrote: > >> Andy Burns wrote: >> >>> Though let the O/P be aware that changing from wifi to wired ethernet >>> will change the machine's IP address for pinging. >> >> No. Every machine gets it's IP address from the router, depending on >> their MAC address. > And it'll have a different MAC address for the WiFi NIC compared to the > Ethernet NIC What's a NIC? > > Or are you saying your router allows you to allocate the same IP to > multiple MAC addresses (which would be unusual)? Ofcourse not. Each machine gets a different IP address from the router, based on ther MAC address. Fokke
[toc] | [prev] | [next] | [standalone]
| From | Frank Slootweg <this@ddress.is.invalid> |
|---|---|
| Date | 2025-05-05 12:59 +0000 |
| Message-ID | <vvajnt.15ro.1@ID-201911.user.individual.net> |
| In reply to | #19061 |
Fokke Nauta <fnauta@solfon.nl> wrote: > On 05/05/2025 12:13, Andy Burns wrote: > > Fokke Nauta wrote: > > > >> Andy Burns wrote: > >> > >>> Though let the O/P be aware that changing from wifi to wired ethernet > >>> will change the machine's IP address for pinging. > >> > >> No. Every machine gets it's IP address from the router, depending on > >> their MAC address. > > And it'll have a different MAC address for the WiFi NIC compared to the > > Ethernet NIC > > What's a NIC? For questions like this, I advise to first use the 'define:' search term in Google (i.e. in this case 'define:NIC') or/and search in Wikipedia. In most cases, that gives the answer. > > Or are you saying your router allows you to allocate the same IP to > > multiple MAC addresses (which would be unusual)? > > Ofcourse not. Each machine gets a different IP address from the router, > based on ther MAC address. Don't be a wise-guy! Andy's *point* is that for a Wi-Fi or Ethernet connection on the same computer, the MAC address will be different, so unless you change the MAC->IP allocation, the IP address will be different or no IP address will be assigned.
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-05-07 10:59 +0200 |
| Message-ID | <m80lnbFm0ceU2@mid.individual.net> |
| In reply to | #19066 |
On 05/05/2025 14:59, Frank Slootweg wrote: > Fokke Nauta <fnauta@solfon.nl> wrote: >> On 05/05/2025 12:13, Andy Burns wrote: >>> Fokke Nauta wrote: >>> >>>> Andy Burns wrote: >>>> >>>>> Though let the O/P be aware that changing from wifi to wired ethernet >>>>> will change the machine's IP address for pinging. >>>> >>>> No. Every machine gets it's IP address from the router, depending on >>>> their MAC address. >>> And it'll have a different MAC address for the WiFi NIC compared to the >>> Ethernet NIC >> >> What's a NIC? > > For questions like this, I advise to first use the 'define:' search > term in Google (i.e. in this case 'define:NIC') or/and search in > Wikipedia. In most cases, that gives the answer. > >>> Or are you saying your router allows you to allocate the same IP to >>> multiple MAC addresses (which would be unusual)? >> >> Ofcourse not. Each machine gets a different IP address from the router, >> based on ther MAC address. > > Don't be a wise-guy! Andy's *point* is that for a Wi-Fi or Ethernet > connection on the same computer, the MAC address will be different, That's right. > so > unless you change the MAC->IP allocation, the IP address will be > different or no IP address will be assigned. It's not possible to connect her laptop by cable. Fokke
[toc] | [prev] | [next] | [standalone]
| From | Graham J <nobody@nowhere.co.uk> |
|---|---|
| Date | 2025-05-05 14:14 +0100 |
| Message-ID | <vvadiv$i1hv$1@dont-email.me> |
| In reply to | #19061 |
Fokke Nauta wrote: > On 05/05/2025 12:13, Andy Burns wrote: >> Fokke Nauta wrote: >> >>> Andy Burns wrote: >>> >>>> Though let the O/P be aware that changing from wifi to wired >>>> ethernet will change the machine's IP address for pinging. >>> >>> No. Every machine gets it's IP address from the router, depending on >>> their MAC address. >> And it'll have a different MAC address for the WiFi NIC compared to >> the Ethernet NIC > > What's a NIC? I suspect that Fokke's native language is not English. So for all he writes pretty good English, he may not be familiar with common abbreviations and acronyms - particularly those that apply in the computer and networking world. So we should probably be gentle with him ... -- Graham J
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2025-05-05 15:10 +0100 |
| Message-ID | <m7rv6vFtbasU3@mid.individual.net> |
| In reply to | #19069 |
Graham J wrote: > I suspect that Fokke's native language is not English. Yeah, we know that much, he normally manages very well in English.
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-05-07 11:01 +0200 |
| Message-ID | <m80lreFm0ceU4@mid.individual.net> |
| In reply to | #19073 |
On 05/05/2025 16:10, Andy Burns wrote: > Graham J wrote: > >> I suspect that Fokke's native language is not English. > > Yeah, we know that much, he normally manages very well in English. I used to live there for 5 years. Had a nice job in Milton Keynes. Fokke
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-05-07 11:00 +0200 |
| Message-ID | <m80lprFm0ceU3@mid.individual.net> |
| In reply to | #19069 |
On 05/05/2025 15:14, Graham J wrote: > Fokke Nauta wrote: >> On 05/05/2025 12:13, Andy Burns wrote: >>> Fokke Nauta wrote: >>> >>>> Andy Burns wrote: >>>> >>>>> Though let the O/P be aware that changing from wifi to wired >>>>> ethernet will change the machine's IP address for pinging. >>>> >>>> No. Every machine gets it's IP address from the router, depending on >>>> their MAC address. >>> And it'll have a different MAC address for the WiFi NIC compared to >>> the Ethernet NIC >> >> What's a NIC? > > I suspect that Fokke's native language is not English. That's correct. It's Dutch. > > So for all he writes pretty good English, he may not be familiar with > common abbreviations and acronyms - particularly those that apply in the > computer and networking world. > > So we should probably be gentle with him ... That's nice! Fokke >
[toc] | [prev] | [next] | [standalone]
| From | Andy Burns <usenet@andyburns.uk> |
|---|---|
| Date | 2025-05-05 15:08 +0100 |
| Message-ID | <m7rv3cFtbasU2@mid.individual.net> |
| In reply to | #19061 |
Fokke Nauta wrote: > What's a NIC? Network interface card.
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-05-07 11:02 +0200 |
| Message-ID | <m80lsfFm0ceU5@mid.individual.net> |
| In reply to | #19072 |
On 05/05/2025 16:08, Andy Burns wrote: > Fokke Nauta wrote: > >> What's a NIC? > > Network interface card. Thanks. Fokke
[toc] | [prev] | [next] | [standalone]
| From | Java Jive <java@evij.com.invalid> |
|---|---|
| Date | 2025-05-05 11:44 +0100 |
| Message-ID | <vva4rb$9ih8$2@dont-email.me> |
| In reply to | #19052 |
On 2025-05-05 11:01, Fokke Nauta wrote: > On 03/05/2025 00:12, Andy Burns wrote: >> Graham J wrote: >> >>> Can you connect all the computers via Ethernet cable directly to the >>> router, for testing? >> >> Though let the O/P be aware that changing from wifi to wired ethernet >> will change the machine's IP address for pinging. >> > > No. Every machine gets it's IP address from the router, depending on > their MAC address. In your normal set up, yes, but if, say for testing purposes, you connect a PC by cable instead of by WiFi, or vice versa, then the MAC address of the WiFi netcard will be different from that of the cable netcard, so there will no longer be any guarantee that it will still have the IP address you expect it to have when connected by whatever method is usual for that particular PC. -- Fake news kills! I may be contacted via the contact address given on my website: www.macfh.co.uk
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-05-05 13:38 +0200 |
| Message-ID | <m7rm9vFs88vU2@mid.individual.net> |
| In reply to | #19058 |
On 05/05/2025 12:44, Java Jive wrote: > On 2025-05-05 11:01, Fokke Nauta wrote: >> On 03/05/2025 00:12, Andy Burns wrote: >>> Graham J wrote: >>> >>>> Can you connect all the computers via Ethernet cable directly to the >>>> router, for testing? >>> >>> Though let the O/P be aware that changing from wifi to wired ethernet >>> will change the machine's IP address for pinging. >>> >> >> No. Every machine gets it's IP address from the router, depending on >> their MAC address. > > In your normal set up, yes, but if, say for testing purposes, you > connect a PC by cable instead of by WiFi, or vice versa, All pc's are connected by cable. Both laptops are connected by wifi from the AP. I'm not going to change that. > then the MAC > address of the WiFi netcard will be different from that of the cable > netcard, so there will no longer be any guarantee that it will still > have the IP address you expect it to have when connected by whatever > method is usual for that particular PC. > Fokke
[toc] | [prev] | [next] | [standalone]
| From | "...winston" <winstonmvp@gmail.com> |
|---|---|
| Date | 2025-05-05 11:49 -0400 |
| Message-ID | <vvamn3$q9t1$1@dont-email.me> |
| In reply to | #19062 |
Fokke Nauta wrote: > On 05/05/2025 12:44, Java Jive wrote: >> On 2025-05-05 11:01, Fokke Nauta wrote: >>> On 03/05/2025 00:12, Andy Burns wrote: >>>> Graham J wrote: >>>> >>>>> Can you connect all the computers via Ethernet cable directly to >>>>> the router, for testing? >>>> >>>> Though let the O/P be aware that changing from wifi to wired >>>> ethernet will change the machine's IP address for pinging. >>>> >>> >>> No. Every machine gets it's IP address from the router, depending on >>> their MAC address. >> >> In your normal set up, yes, but if, say for testing purposes, you >> connect a PC by cable instead of by WiFi, or vice versa, > > All pc's are connected by cable. Both laptops are connected by wifi from > the AP. I'm not going to change that. > >> then the MAC address of the WiFi netcard will be different from that >> of the cable netcard, so there will no longer be any guarantee that it >> will still have the IP address you expect it to have when connected by >> whatever method is usual for that particular PC. >> > > Fokke Does your earlier statement(router assigns ip address for each devices mac address) indicate? => in your router you: a. set a range of ip addresses that can be dispensed b. the range of dispensable ip addresses is equal or greater than the number of devices that can be assigned an ip address c. each device is always assigned the exact same(i.e. fixed) ip address d. router is configured/eanbled for mac address filtering where only allowed devices' mac address receive an ip address -- ...w¡ñ§±¤ñ
[toc] | [prev] | [next] | [standalone]
| From | Fokke Nauta <fnauta@solfon.nl> |
|---|---|
| Date | 2025-05-07 11:03 +0200 |
| Message-ID | <m80lv7Fm0ceU6@mid.individual.net> |
| In reply to | #19075 |
On 05/05/2025 17:49, ...winston wrote: > Fokke Nauta wrote: >> On 05/05/2025 12:44, Java Jive wrote: >>> On 2025-05-05 11:01, Fokke Nauta wrote: >>>> On 03/05/2025 00:12, Andy Burns wrote: >>>>> Graham J wrote: >>>>> >>>>>> Can you connect all the computers via Ethernet cable directly to >>>>>> the router, for testing? >>>>> >>>>> Though let the O/P be aware that changing from wifi to wired >>>>> ethernet will change the machine's IP address for pinging. >>>>> >>>> >>>> No. Every machine gets it's IP address from the router, depending on >>>> their MAC address. >>> >>> In your normal set up, yes, but if, say for testing purposes, you >>> connect a PC by cable instead of by WiFi, or vice versa, >> >> All pc's are connected by cable. Both laptops are connected by wifi >> from the AP. I'm not going to change that. >> >>> then the MAC address of the WiFi netcard will be different from that >>> of the cable netcard, so there will no longer be any guarantee that >>> it will still have the IP address you expect it to have when >>> connected by whatever method is usual for that particular PC. >>> >> >> Fokke > > Does your earlier statement(router assigns ip address for each devices > mac address) indicate? > => in your router you: > a. set a range of ip addresses that can be dispensed > b. the range of dispensable ip addresses is equal or greater than the > number of devices that can be assigned an ip address > c. each device is always assigned the exact same(i.e. fixed) ip address Indeed, depending on their MAC. > d. router is configured/eanbled for mac address filtering where only > allowed devices' mac address receive an ip address > Fokke
[toc] | [prev] | [next] | [standalone]
Page 9 of 11 — ← Prev page 1 … 7 8 [9] 10 11 Next page →
Back to top | Article view | alt.comp.os.windows-11
csiph-web