Char Jackson <none@none.invalid> wrote:
[...]

> When you're connected to the access point, run "ipconfig /all" on a
> connected PC. (I know you ran that command before, but you weren't
> connected to a network at that time, so no useful info was obtained.)
> In the ipconfig output, you should see your own IP address, plus the
> IP address of the DHCP server and the Default Gateway. (Plus DNS
> address(es) but we don't care about DNS right now.)

Thanks for clearing that up! I was quite puzzled that jetjock's
"ipconfig /all" output didn't show that information. Now I know (because
he wasn't connected to a network.

Thanks again.

[...]

In message <uep5le.20k.1@ID-201911.user.individual.net> at Sun, 24 Sep
2023 09:14:03, Frank Slootweg <this@ddress.is.invalid> writes
>Char Jackson <none@none.invalid> wrote:
>[...]
>
>> When you're connected to the access point, run "ipconfig /all" on a
>> connected PC. (I know you ran that command before, but you weren't
>> connected to a network at that time, so no useful info was obtained.)
>> In the ipconfig output, you should see your own IP address, plus the
>> IP address of the DHCP server and the Default Gateway. (Plus DNS
>> address(es) but we don't care about DNS right now.)
>
> Thanks for clearing that up! I was quite puzzled that jetjock's
>"ipconfig /all" output didn't show that information. Now I know (because
>he wasn't connected to a network.
>
> Thanks again.
>
>[...]

ipconfig /all | more
might of course help.

I was going to say
ipconfig /all | grep 192.
might help, but I've just discovered grep isn't part of the basic W7-32
system )-:! Is its function there under a different name? If not, is it
downloadable from somewhere, that could safely be put in sys32 or
whatever?
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

"Bother," said Pooh, as he fell off the bridge with his stick.

J. P. Gilliver <G6JPG@255soft.uk> wrote:
> In message <uep5le.20k.1@ID-201911.user.individual.net> at Sun, 24 Sep
> 2023 09:14:03, Frank Slootweg <this@ddress.is.invalid> writes
> >Char Jackson <none@none.invalid> wrote:
> >[...]
> >
> >> When you're connected to the access point, run "ipconfig /all" on a
> >> connected PC. (I know you ran that command before, but you weren't
> >> connected to a network at that time, so no useful info was obtained.)
> >> In the ipconfig output, you should see your own IP address, plus the
> >> IP address of the DHCP server and the Default Gateway. (Plus DNS
> >> address(es) but we don't care about DNS right now.)
> >
> > Thanks for clearing that up! I was quite puzzled that jetjock's
> >"ipconfig /all" output didn't show that information. Now I know (because
> >he wasn't connected to a network.
> >
> > Thanks again.
> >
> >[...]
>
> ipconfig /all | more
> might of course help.

Just in case this was meant for me: I was/am quite aware of what to
look for, but I was puzzled as to why the information wasn't in
jetjock's "ipconfig /all" output.

> I was going to say
> ipconfig /all | grep 192.
> might help, but I've just discovered grep isn't part of the basic W7-32
> system )-:! Is its function there under a different name? If not, is it
> downloadable from somewhere, that could safely be put in sys32 or
> whatever?

'findstr' is more or less the 'DOS' equivalent of 'grep'. Just do
'findstr /?' to get help.

Example:

C:\home\franks>ipconfig /all | findstr 192
IPv4 Address. . . . . . . . . . . : 192.168.178.14(Preferred)
Default Gateway . . . . . . . . . : 192.168.178.1
DHCP Server . . . . . . . . . . . : 192.168.178.1

C:\home\franks>

On Sun, 24 Sep 2023 12:48:36 +0100, "J. P. Gilliver" <G6JPG@255soft.uk> wrote:

>In message <uep5le.20k.1@ID-201911.user.individual.net> at Sun, 24 Sep
>2023 09:14:03, Frank Slootweg <this@ddress.is.invalid> writes
>>Char Jackson <none@none.invalid> wrote:
>>[...]
>>
>>> When you're connected to the access point, run "ipconfig /all" on a
>>> connected PC. (I know you ran that command before, but you weren't
>>> connected to a network at that time, so no useful info was obtained.)
>>> In the ipconfig output, you should see your own IP address, plus the
>>> IP address of the DHCP server and the Default Gateway. (Plus DNS
>>> address(es) but we don't care about DNS right now.)
>>
>> Thanks for clearing that up! I was quite puzzled that jetjock's
>>"ipconfig /all" output didn't show that information. Now I know (because
>>he wasn't connected to a network.
>>
>> Thanks again.
>>
>>[...]
>
> ipconfig /all | more
>might of course help.
>
>I was going to say
> ipconfig /all | grep 192.
>might help, but I've just discovered grep isn't part of the basic W7-32
>system )-:! Is its function there under a different name? If not, is it
>downloadable from somewhere, that could safely be put in sys32 or
>whatever?

In addition to what Frank said, I wouldn't filter the output this way because
there's no guarantee that the relevant IP addresses include "192." in them.
Instead, I might filter on "IPv4", but even that isn't 100%. Probably best to
not filter at all during the initial discovery phase.

On 9/24/2023 7:48 AM, J. P. Gilliver wrote:
> In message <uep5le.20k.1@ID-201911.user.individual.net> at Sun, 24 Sep
> 2023 09:14:03, Frank Slootweg <this@ddress.is.invalid> writes
>> Char Jackson <none@none.invalid> wrote:
>> [...]
>>
>>> When you're connected to the access point, run "ipconfig /all" on a
>>> connected PC. (I know you ran that command before, but you weren't
>>> connected to a network at that time, so no useful info was obtained.)
>>> In the ipconfig output, you should see your own IP address, plus the
>>> IP address of the DHCP server and the Default Gateway. (Plus DNS
>>> address(es) but we don't care about DNS right now.)
>>
>> Thanks for clearing that up! I was quite puzzled that jetjock's
>> "ipconfig /all" output didn't show that information. Now I know (because
>> he wasn't connected to a network.
>>
>> Thanks again.
>>
>> [...]
>
> ipconfig /all | more
> might of course help.
>
> I was going to say
> ipconfig /all | grep 192.
> might help, but I've just discovered grep isn't part of the basic W7-32
> system )-:! Is its function there under a different name? If not, is it
> downloadable from somewhere, that could safely be put in sys32 or
> whatever?
>

GNUWin32 packages can give you a "grep".

You can add a GNUWin32 path element to the OS %path% , to pick them up.

It requires using the installers provided on the download page,
to integrate everything nicely.

https://gnuwin32.sourceforge.net/packages.html

https://gnuwin32.sourceforge.net/packages/grep.htm

Doing stuff like this, is mostly for people with time on
their hands. (This is stuff an old Unix fart would pick up
like flypaper -- other generations, not so much.)

*******

For everything else, you can try pages like this.
I can't find the good page I used to have for this.

https://www.computerhope.com/msdos.htm

The value of items like that, is when they include examples.

https://www.computerhope.com/findstr.htm

Paul

In message <uepip7.2g4.1@ID-201911.user.individual.net> at Sun, 24 Sep
2023 12:57:54, Frank Slootweg <this@ddress.is.invalid> writes
[]
>> I was going to say
>> ipconfig /all | grep 192.
>> might help, but I've just discovered grep isn't part of the basic W7-32
>> system )-:! Is its function there under a different name? If not, is it
>> downloadable from somewhere, that could safely be put in sys32 or
>> whatever?
>
> 'findstr' is more or less the 'DOS' equivalent of 'grep'. Just do
>'findstr /?' to get help.
>
> Example:
>
>C:\home\franks>ipconfig /all | findstr 192
> IPv4 Address. . . . . . . . . . . : 192.168.178.14(Preferred)
> Default Gateway . . . . . . . . . : 192.168.178.1
> DHCP Server . . . . . . . . . . . : 192.168.178.1
>
>C:\home\franks>

Thanks for that information; findstr seems to work for me (gives the
same result, other than the end dot are 184, 254, 254, 254 [the last
being an extra line that starts "DNS Servers"]). Now, just to try to
remember the name "findstr"! (Maybe I can make a "grep.bat" containing
something like "findstr %0". [I did think of just renaming findstr, but
thought that's probably not a good idea.])
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

You'll need to have this fish in your ear. (First series, fit the first.)

On Sun, 24 Sep 2023 12:48:36 +0100, "J. P. Gilliver"
<G6JPG@255soft.uk> wrote:

>In message <uep5le.20k.1@ID-201911.user.individual.net> at Sun, 24 Sep
>2023 09:14:03, Frank Slootweg <this@ddress.is.invalid> writes
>>Char Jackson <none@none.invalid> wrote:
>>[...]
>>
>>> When you're connected to the access point, run "ipconfig /all" on a
>>> connected PC. (I know you ran that command before, but you weren't
>>> connected to a network at that time, so no useful info was obtained.)
>>> In the ipconfig output, you should see your own IP address, plus the
>>> IP address of the DHCP server and the Default Gateway. (Plus DNS
>>> address(es) but we don't care about DNS right now.)
>>
>> Thanks for clearing that up! I was quite puzzled that jetjock's
>>"ipconfig /all" output didn't show that information. Now I know (because
>>he wasn't connected to a network.
>>
>> Thanks again.
>>
>>[...]
>
> ipconfig /all | more
>might of course help.
>
>I was going to say
> ipconfig /all | grep 192.
>might help, but I've just discovered grep isn't part of the basic W7-32
>system )-:! Is its function there under a different name? If not, is it
>downloadable from somewhere, that could safely be put in sys32 or
>whatever?

Ok. I tried ipconfig /all | more and this time I got this:(edited)

Windows IP Configuration

Wireless LAN adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC
7265
Physical Address. . . . . . . . . : 5C-E4-2A-16-03-A0
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
fe80::4d13:d630:dca5:b4d3%15(Preferred)
IPv4 Address. . . . . . . . . . . : 172.17.46.34(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Tuesday, September 19, 2023
10:38:57 AM
Lease Expires . . . . . . . . . . : Monday, September 25, 2023
8:51:38 AM
Default Gateway . . . . . . . . . : 172.17.46.1
DHCP Server . . . . . . . . . . . : 172.17.46.2
DHCPv6 IAID . . . . . . . . . . . : 475849770
DHCPv6 Client DUID. . . . . . . . :
00-01-00-01-22-BE-CD-9F-10-C3-7B-6B-9A-E1
DNS Servers . . . . . . . . . . . : 1.1.1.1
1.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

So I tried IPv4 address and both the default gateway and DHCP Server.
Still would not connect. The first address said there was an error
connecting. The later two both timed out.

>>>>>>>>>>jetjock<<<<<<<<<<

On Sat, 23 Sep 2023 19:31:39 -0500, Char Jackson <none@none.invalid>
wrote:

>On Sat, 23 Sep 2023 13:28:28 -0500, jetjock <jetjock@unkown.com> wrote:
>
>>I think I confused the issue by referring to my setup as "community
>>WiFi". Since we don't have an IT person for our community I am not
>>able to get comprehensive knowledge from anyone, but here is our
>>system as I understand it.
>>
>>Somewhere on the property is a transmitter that provides WiFi signals.
>>There are two distinct versions, depending on whether you live in an
>>apartment in the main building, all of whom share a signal with a
>>common password, or a cottage as I do. Each cottage has a distinct
>>password. In my cottage there is a modem and an Rukus access point
>
>Possibly one of the models on this page:
>https://www.ruckusnetworks.com/products/wireless-access-points/

I had already checked there. My box appears to be a 300 or 350. I
tried calling support but they would not help me without a serial
number which I can't get to. :-(
>
>
>>which is mounted on the ceiling in the middle of the cottage. Since we
>>have 10 ft. ceilings (and I don't have an ladder since we moved), I
>>can't reach it to get a model, serial # or IP address off it. I have
>>tried every address I can think of (see reply to J.P. Gilliver), but I
>>can't get into it. My WiFi analyzer shows hidden networks, so maybe
>>they have blocked access to keep fools like me out! :-)
>
>No, but it's a nice thought. :)
>
>When you're connected to the access point, run "ipconfig /all" on a connected
>PC. (I know you ran that command before, but you weren't connected to a network
>at that time, so no useful info was obtained.) In the ipconfig output, you
>should see your own IP address, plus the IP address of the DHCP server and the
>Default Gateway. (Plus DNS address(es) but we don't care about DNS right now.)

I'm a little confused here. I assumed that my computer is always
connected to the "Network". It says I am connected to the "Wireless
Connection" with "Internet access". Anyway, I tried J.P. Gilliver's
suggestion and ran ipconfig / all | more. See my reply to him for what
happened.
>
>All 3 of those addresses will be on the same subnet, with the latter two most
>likely being the same address. They don't have to be the same, but they usually
>are. The gateway address should be the router that serves your cottage, and
>possibly other cottages. The ceiling-mounted access point very likely has an IP
>address that's also in that same subnet. Obviously, you don't need to know it in
>order to use the access point (because you use an access point at layer 2 of the
>OSI model and IP addresses live above that at layer 3, but who cares, right?)
>
>Because I'm weird that way, when I'm connected to that WiFi system I'd run a
>utility called an IP scanner. When it finishes, it provides a list of every IP
>address that it found on your subnet, plus some basic info about each of those
>IP addresses. The access point will probably show up in that list, as will the
>router.
>
>I haven't said anything about the modem because, technically, the modem is not
>on your LAN. It's almost certainly on the WAN side of the router that serves
>your cottage, even if it's in the same plastic case as the router. You still
>might be able to access it, though, just for the sake of info. If it was a
>standard cable modem, it would likely be at http://168.192.100.1

Connection timed out

> but I'm
>guessing it's not a standard cable modem. If you can get the make/model, you
>might find a default address for it. It won't be an address that's on your LAN
>subnet, since it's on the far side of the router.
>
>>I just redid my libraries to reduce some clutter, and also "Optimized
>>for TV" all my TV shows. I saw where some were optimized for mobile
>>and some were not yet optimized. surprised they played at all. Doesn't
>>address the problem of playing my phone videos, but one thing at a
>>time. I'll see tonight how the TV shows work.
>
>I've never optimized anything. Maybe I should, but everything plays just fine.

Optimization is now driving me crazy! I put season two of a show into
the _Plex TV folder and optimize it. I get a new folder named
"Optimized for TV". Great. Now I add season 3 to the _Plex TV folder
and optimize it. When I look in the "Optimized for TV" folder, season
3 is there but season 2 is now gone! AARRGGG!!

Only problem with not optimizing is Plex tries to transcode on the fly
while watching, and is mostly unsuccessful doing so.

>>>>>>>>>>jetjock<<<<<<<<<<

On Sun, 24 Sep 2023 19:23:08 +0100, "J. P. Gilliver" <G6JPG@255soft.uk> wrote:

>In message <uepip7.2g4.1@ID-201911.user.individual.net> at Sun, 24 Sep
>2023 12:57:54, Frank Slootweg <this@ddress.is.invalid> writes
>[]
>>> I was going to say
>>> ipconfig /all | grep 192.
>>> might help, but I've just discovered grep isn't part of the basic W7-32
>>> system )-:! Is its function there under a different name? If not, is it
>>> downloadable from somewhere, that could safely be put in sys32 or
>>> whatever?
>>
>> 'findstr' is more or less the 'DOS' equivalent of 'grep'. Just do
>>'findstr /?' to get help.
>>
>> Example:
>>
>>C:\home\franks>ipconfig /all | findstr 192
>> IPv4 Address. . . . . . . . . . . : 192.168.178.14(Preferred)
>> Default Gateway . . . . . . . . . : 192.168.178.1
>> DHCP Server . . . . . . . . . . . : 192.168.178.1
>>
>>C:\home\franks>
>
>Thanks for that information; findstr seems to work for me (gives the
>same result, other than the end dot are 184, 254, 254, 254 [the last
>being an extra line that starts "DNS Servers"]). Now, just to try to
>remember the name "findstr"! (Maybe I can make a "grep.bat" containing
>something like "findstr %0". [I did think of just renaming findstr, but
>thought that's probably not a good idea.])

Keep an eye on the find command, as well. It seems to be a simplified
alternative to findstr. I use find when I just need a quick and simple search.
It saves me typing 3 keystrokes.

On Sun, 24 Sep 2023 14:12:25 -0500, jetjock <jetjock@unkown.com> wrote:

>On Sat, 23 Sep 2023 19:31:39 -0500, Char Jackson <none@none.invalid>
>wrote:
>
>>On Sat, 23 Sep 2023 13:28:28 -0500, jetjock <jetjock@unkown.com> wrote:
>>
>>>I think I confused the issue by referring to my setup as "community
>>>WiFi". Since we don't have an IT person for our community I am not
>>>able to get comprehensive knowledge from anyone, but here is our
>>>system as I understand it.
>>>
>>>Somewhere on the property is a transmitter that provides WiFi signals.
>>>There are two distinct versions, depending on whether you live in an
>>>apartment in the main building, all of whom share a signal with a
>>>common password, or a cottage as I do. Each cottage has a distinct
>>>password. In my cottage there is a modem and an Rukus access point
>>
>>Possibly one of the models on this page:
>>https://www.ruckusnetworks.com/products/wireless-access-points/
>
>I had already checked there. My box appears to be a 300 or 350. I
>tried calling support but they would not help me without a serial
>number which I can't get to. :-(

There probably isn't much you can or should do within the access point, so I'd
probably forget it and move on. If you're determined and curious, an IP scanner
should show you its IP address, and I'd expect it to have a web server running
on port 80.

Now that you know your IP address subnet, to scan for live IP's you'd scan the
range 172.17.46.0/24, or your scanner might expect a starting and ending
address, so you'd use 172.17.46.1 to 172.17.46.254.

>>>which is mounted on the ceiling in the middle of the cottage. Since we
>>>have 10 ft. ceilings (and I don't have an ladder since we moved), I
>>>can't reach it to get a model, serial # or IP address off it. I have
>>>tried every address I can think of (see reply to J.P. Gilliver), but I
>>>can't get into it. My WiFi analyzer shows hidden networks, so maybe
>>>they have blocked access to keep fools like me out! :-)
>>
>>No, but it's a nice thought. :)
>>
>>When you're connected to the access point, run "ipconfig /all" on a connected
>>PC. (I know you ran that command before, but you weren't connected to a network
>>at that time, so no useful info was obtained.) In the ipconfig output, you
>>should see your own IP address, plus the IP address of the DHCP server and the
>>Default Gateway. (Plus DNS address(es) but we don't care about DNS right now.)
>
>I'm a little confused here. I assumed that my computer is always
>connected to the "Network". It says I am connected to the "Wireless
>Connection" with "Internet access". Anyway, I tried J.P. Gilliver's
>suggestion and ran ipconfig / all | more. See my reply to him for what
>happened.

It may have been connected, but the output that you provided didn't include an
entry for the "Wireless Connection" connectoid. Maybe it was just a copy/paste
issue but we got to see everything on the second attempt.

>>>I just redid my libraries to reduce some clutter, and also "Optimized
>>>for TV" all my TV shows. I saw where some were optimized for mobile
>>>and some were not yet optimized. surprised they played at all. Doesn't
>>>address the problem of playing my phone videos, but one thing at a
>>>time. I'll see tonight how the TV shows work.
>>
>>I've never optimized anything. Maybe I should, but everything plays just fine.
>
>Optimization is now driving me crazy! I put season two of a show into
>the _Plex TV folder and optimize it. I get a new folder named
>"Optimized for TV". Great. Now I add season 3 to the _Plex TV folder
>and optimize it. When I look in the "Optimized for TV" folder, season
>3 is there but season 2 is now gone! AARRGGG!!

Are the optimized versions supposed to replace the unoptimized versions, or
should both versions remain available? I don't know what 'normal' is.

>Only problem with not optimizing is Plex tries to transcode on the fly
>while watching, and is mostly unsuccessful doing so.

What does it mean to be unsuccessful? Is the Plex server not up to the task of
doing realtime transcoding, or is it something else?

I'm sorry, but I can't offer any solid advice since it's something I've never
had to do.

On Sun, 24 Sep 2023 13:56:49 -0500, jetjock <jetjock@unkown.com> wrote:

>Ok. I tried ipconfig /all | more and this time I got this:(edited)
>
>
>Windows IP Configuration
>
>
>Wireless LAN adapter Wireless Network Connection:
>
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC
>7265
> Physical Address. . . . . . . . . : 5C-E4-2A-16-03-A0
> DHCP Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> Link-local IPv6 Address . . . . . :
>fe80::4d13:d630:dca5:b4d3%15(Preferred)
> IPv4 Address. . . . . . . . . . . : 172.17.46.34(Preferred)
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Lease Obtained. . . . . . . . . . : Tuesday, September 19, 2023
>10:38:57 AM
> Lease Expires . . . . . . . . . . : Monday, September 25, 2023
>8:51:38 AM
> Default Gateway . . . . . . . . . : 172.17.46.1
> DHCP Server . . . . . . . . . . . : 172.17.46.2
> DHCPv6 IAID . . . . . . . . . . . : 475849770
> DHCPv6 Client DUID. . . . . . . . :
>00-01-00-01-22-BE-CD-9F-10-C3-7B-6B-9A-E1
> DNS Servers . . . . . . . . . . . : 1.1.1.1
> 1.0.0.1
> NetBIOS over Tcpip. . . . . . . . : Enabled

So we see that your current IP address is 172.17.46.34/24 and that your default
gateway is at 172.17.46.1.

I would expect a web server to be running on port 80 at the gateway address, but
the folks running things could have disabled it.

>So I tried IPv4 address and both the default gateway and DHCP Server.
>Still would not connect. The first address said there was an error
>connecting. The later two both timed out.

46.34 is your own address, so no need to try to connect there, and 46.2 is the
DHCP server, so no need to try to connect there, as well. That just leaves the
gateway address, 46.1, which your community admins might have disabled, as I
mentioned above.

I don't think any of this is helping you, is it? :)

In message <1a02hi5h424orev4vl96filtrbu9bs61kp@4ax.com> at Sun, 24 Sep
2023 22:52:42, Char Jackson <none@none.invalid> writes
[]
>>Thanks for that information; findstr seems to work for me (gives the
>>same result, other than the end dot are 184, 254, 254, 254 [the last
>>being an extra line that starts "DNS Servers"]). Now, just to try to
>>remember the name "findstr"! (Maybe I can make a "grep.bat" containing
>>something like "findstr %0". [I did think of just renaming findstr, but
>>thought that's probably not a good idea.])
>
>Keep an eye on the find command, as well. It seems to be a simplified
>alternative to findstr. I use find when I just need a quick and simple search.
>It saves me typing 3 keystrokes.
>
Thanks; another command noted!
--
J. P. Gilliver. UMRA: 1960/<1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf

Look out for #1. Don't step in #2 either.

Char Jackson <none@none.invalid> wrote:
> On Sun, 24 Sep 2023 19:23:08 +0100, "J. P. Gilliver" <G6JPG@255soft.uk> wrote:
>
> >In message <uepip7.2g4.1@ID-201911.user.individual.net> at Sun, 24 Sep
> >2023 12:57:54, Frank Slootweg <this@ddress.is.invalid> writes
> >[]
> >>> I was going to say
> >>> ipconfig /all | grep 192.
> >>> might help, but I've just discovered grep isn't part of the basic W7-32
> >>> system )-:! Is its function there under a different name? If not, is it
> >>> downloadable from somewhere, that could safely be put in sys32 or
> >>> whatever?
> >>
> >> 'findstr' is more or less the 'DOS' equivalent of 'grep'. Just do
> >>'findstr /?' to get help.
> >>
> >> Example:
> >>
> >>C:\home\franks>ipconfig /all | findstr 192
> >> IPv4 Address. . . . . . . . . . . : 192.168.178.14(Preferred)
> >> Default Gateway . . . . . . . . . : 192.168.178.1
> >> DHCP Server . . . . . . . . . . . : 192.168.178.1
> >>
> >>C:\home\franks>
> >
> >Thanks for that information; findstr seems to work for me (gives the
> >same result, other than the end dot are 184, 254, 254, 254 [the last
> >being an extra line that starts "DNS Servers"]). Now, just to try to
> >remember the name "findstr"! (Maybe I can make a "grep.bat" containing
> >something like "findstr %0". [I did think of just renaming findstr, but
> >thought that's probably not a good idea.])
>
> Keep an eye on the find command, as well. It seems to be a simplified
> alternative to findstr. I use find when I just need a quick and simple search.
> It saves me typing 3 keystrokes.

Yes, I seemed to remember the 'DOS' 'find' command, but as for me the
Unix 'find' command appears earlier in my PATH, 'find /?' didn't work,
so I pointed to the 'DOS' 'findstr' comman instead.

Just now, I used 'C:\Windows\System32\find /?' and see - as you noted
- that the 'DOS' 'find' command can indeed be used for simple grep-like
searches.

Thanks for refreshing my memory.

On 9/25/2023 12:51 AM, Char Jackson wrote:

> If you're determined and curious, an IP scanner
> should show you its IP address, and I'd expect it to have a web server running
> on port 80.

Devices don't have to respond to an IP scan.

You should not become distraught if such a scan
offers no response :-)

"White boxes" are mystery meat. Expect mysteries.

Some devices have anti-hammer protection. The GRC
scanner at one time, did not work properly against
my device (gave it a "stealth rating"), because
I found a couple log entries indicating
"some anti-hammer thing detected". Today that
is likely fixed, on the GRC end. At the time, it
was scanning port numbers sequentially. My device wasn't
actually stealthy. There was something needing a fix.
My device stopped responding for a period of time,
as the scan was running, which invalidates the test results.

Paul

On Mon, 25 Sep 2023 00:04:36 -0500, Char Jackson <none@none.invalid>
wrote:

>On Sun, 24 Sep 2023 13:56:49 -0500, jetjock <jetjock@unkown.com> wrote:
>
>>Ok. I tried ipconfig /all | more and this time I got this:(edited)
>>
>>
>>Windows IP Configuration
>>
>>
>>Wireless LAN adapter Wireless Network Connection:
>>
>> Connection-specific DNS Suffix . :
>> Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC
>>7265
>> Physical Address. . . . . . . . . : 5C-E4-2A-16-03-A0
>> DHCP Enabled. . . . . . . . . . . : Yes
>> Autoconfiguration Enabled . . . . : Yes
>> Link-local IPv6 Address . . . . . :
>>fe80::4d13:d630:dca5:b4d3%15(Preferred)
>> IPv4 Address. . . . . . . . . . . : 172.17.46.34(Preferred)
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Lease Obtained. . . . . . . . . . : Tuesday, September 19, 2023
>>10:38:57 AM
>> Lease Expires . . . . . . . . . . : Monday, September 25, 2023
>>8:51:38 AM
>> Default Gateway . . . . . . . . . : 172.17.46.1
>> DHCP Server . . . . . . . . . . . : 172.17.46.2
>> DHCPv6 IAID . . . . . . . . . . . : 475849770
>> DHCPv6 Client DUID. . . . . . . . :
>>00-01-00-01-22-BE-CD-9F-10-C3-7B-6B-9A-E1
>> DNS Servers . . . . . . . . . . . : 1.1.1.1
>> 1.0.0.1
>> NetBIOS over Tcpip. . . . . . . . : Enabled
>
>So we see that your current IP address is 172.17.46.34/24 and that your default
>gateway is at 172.17.46.1.
>
>I would expect a web server to be running on port 80 at the gateway address, but
>the folks running things could have disabled it.
>
>>So I tried IPv4 address and both the default gateway and DHCP Server.
>>Still would not connect. The first address said there was an error
>>connecting. The later two both timed out.
>
>46.34 is your own address, so no need to try to connect there, and 46.2 is the
>DHCP server, so no need to try to connect there, as well. That just leaves the
>gateway address, 46.1, which your community admins might have disabled, as I
>mentioned above.
>
>I don't think any of this is helping you, is it? :)

Yes and no! :-) I'm not sure how ipconfig found the 172 address, but
something Paul said about GRC triggered an old memory of "Shields Up".
I ran a scan with that and discovered that my IP was actually
 208.185.183.xxx. I tried putting that in the browser, but it timed
out also. The good news is that my modem (Nokia, by the way) was in
"Stealth" mode at all ports! :-)

I think we've beat this poor ol' horse to death. Time to give it a
dignified burial.

>>>>>>>>>>jetjock<<<<<<<<<<

On Mon, 25 Sep 2023 10:47:29 -0500, jetjock <jetjock@unkown.com> wrote:

>On Mon, 25 Sep 2023 00:04:36 -0500, Char Jackson <none@none.invalid>
>wrote:
>
>>On Sun, 24 Sep 2023 13:56:49 -0500, jetjock <jetjock@unkown.com> wrote:
>>
>>>Ok. I tried ipconfig /all | more and this time I got this:(edited)
>>>
>>>
>>>Windows IP Configuration
>>>
>>>
>>>Wireless LAN adapter Wireless Network Connection:
>>>
>>> Connection-specific DNS Suffix . :
>>> Description . . . . . . . . . . . : Intel(R) Dual Band Wireless-AC
>>>7265
>>> Physical Address. . . . . . . . . : 5C-E4-2A-16-03-A0
>>> DHCP Enabled. . . . . . . . . . . : Yes
>>> Autoconfiguration Enabled . . . . : Yes
>>> Link-local IPv6 Address . . . . . :
>>>fe80::4d13:d630:dca5:b4d3%15(Preferred)
>>> IPv4 Address. . . . . . . . . . . : 172.17.46.34(Preferred)
>>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>>> Lease Obtained. . . . . . . . . . : Tuesday, September 19, 2023
>>>10:38:57 AM
>>> Lease Expires . . . . . . . . . . : Monday, September 25, 2023
>>>8:51:38 AM
>>> Default Gateway . . . . . . . . . : 172.17.46.1
>>> DHCP Server . . . . . . . . . . . : 172.17.46.2
>>> DHCPv6 IAID . . . . . . . . . . . : 475849770
>>> DHCPv6 Client DUID. . . . . . . . :
>>>00-01-00-01-22-BE-CD-9F-10-C3-7B-6B-9A-E1
>>> DNS Servers . . . . . . . . . . . : 1.1.1.1
>>> 1.0.0.1
>>> NetBIOS over Tcpip. . . . . . . . : Enabled
>>
>>So we see that your current IP address is 172.17.46.34/24 and that your default
>>gateway is at 172.17.46.1.
>>
>>I would expect a web server to be running on port 80 at the gateway address, but
>>the folks running things could have disabled it.
>>
>>>So I tried IPv4 address and both the default gateway and DHCP Server.
>>>Still would not connect. The first address said there was an error
>>>connecting. The later two both timed out.
>>
>>46.34 is your own address, so no need to try to connect there, and 46.2 is the
>>DHCP server, so no need to try to connect there, as well. That just leaves the
>>gateway address, 46.1, which your community admins might have disabled, as I
>>mentioned above.
>>
>>I don't think any of this is helping you, is it? :)
>
>Yes and no! :-) I'm not sure how ipconfig found the 172 address, but

The ipconfig command simply gathers a list of your physical and virtual network
adapters, then it prints the current status of each of them.

>something Paul said about GRC triggered an old memory of "Shields Up".
>I ran a scan with that and discovered that my IP was actually
> 208.185.183.xxx.

That's your WAN IP, the IP address that everything outside of your LAN sees you
as. This discussion is supposed to be about your LAN, so your WAN IP isn't
relevant or important.

>I tried putting that in the browser, but it timed out also.

I hope so.

>The good news is that my modem (Nokia, by the way) was in
>"Stealth" mode at all ports! :-)

Did you happen to see a model number?

>I think we've beat this poor ol' horse to death. Time to give it a
>dignified burial.

How is Plex doing these days?

On Mon, 25 Sep 2023 09:00:34 -0400, Paul <nospam@needed.invalid> wrote:

>On 9/25/2023 12:51 AM, Char Jackson wrote:
>
>> If you're determined and curious, an IP scanner
>> should show you its IP address, and I'd expect it to have a web server running
>> on port 80.
>
>Devices don't have to respond to an IP scan.

True, but almost all do.

>You should not become distraught if such a scan
>offers no response :-)
>
>"White boxes" are mystery meat. Expect mysteries.
>
>Some devices have anti-hammer protection. The GRC
>scanner at one time, did not work properly against
>my device (gave it a "stealth rating"), because
>I found a couple log entries indicating
>"some anti-hammer thing detected". Today that
>is likely fixed, on the GRC end. At the time, it
>was scanning port numbers sequentially. My device wasn't
>actually stealthy. There was something needing a fix.
>My device stopped responding for a period of time,
>as the scan was running, which invalidates the test results.

That's a port scan, versus the IP scan that I was talking about. Two very
different things.

On 9/25/2023 3:05 PM, Char Jackson wrote:
> On Mon, 25 Sep 2023 09:00:34 -0400, Paul <nospam@needed.invalid> wrote:
>
>> On 9/25/2023 12:51 AM, Char Jackson wrote:
>>
>>> If you're determined and curious, an IP scanner
>>> should show you its IP address, and I'd expect it to have a web server running
>>> on port 80.
>>
>> Devices don't have to respond to an IP scan.
>
> True, but almost all do.
>
>> You should not become distraught if such a scan
>> offers no response :-)
>>
>> "White boxes" are mystery meat. Expect mysteries.
>>
>> Some devices have anti-hammer protection. The GRC
>> scanner at one time, did not work properly against
>> my device (gave it a "stealth rating"), because
>> I found a couple log entries indicating
>> "some anti-hammer thing detected". Today that
>> is likely fixed, on the GRC end. At the time, it
>> was scanning port numbers sequentially. My device wasn't
>> actually stealthy. There was something needing a fix.
>> My device stopped responding for a period of time,
>> as the scan was running, which invalidates the test results.
>
> That's a port scan, versus the IP scan that I was talking about. Two very
> different things.
>

The point of that paragraph, is to indicate the mystery meat
nature of these things.

Even the simplest of things, doesn't work out and is a
learning experience.

There can be a number of issues created, by parts or all of this
being switched off.

https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol

Paul

On Mon, 25 Sep 2023 15:14:23 -0400, Paul <nospam@needed.invalid> wrote:

>On 9/25/2023 3:05 PM, Char Jackson wrote:
>> On Mon, 25 Sep 2023 09:00:34 -0400, Paul <nospam@needed.invalid> wrote:
>>
>>> On 9/25/2023 12:51 AM, Char Jackson wrote:
>>>
>>>> If you're determined and curious, an IP scanner
>>>> should show you its IP address, and I'd expect it to have a web server running
>>>> on port 80.
>>>
>>> Devices don't have to respond to an IP scan.
>>
>> True, but almost all do.
>>
>>> You should not become distraught if such a scan
>>> offers no response :-)
>>>
>>> "White boxes" are mystery meat. Expect mysteries.
>>>
>>> Some devices have anti-hammer protection. The GRC
>>> scanner at one time, did not work properly against
>>> my device (gave it a "stealth rating"), because
>>> I found a couple log entries indicating
>>> "some anti-hammer thing detected". Today that
>>> is likely fixed, on the GRC end. At the time, it
>>> was scanning port numbers sequentially. My device wasn't
>>> actually stealthy. There was something needing a fix.
>>> My device stopped responding for a period of time,
>>> as the scan was running, which invalidates the test results.
>>
>> That's a port scan, versus the IP scan that I was talking about. Two very
>> different things.
>>
>
>The point of that paragraph, is to indicate the mystery meat
>nature of these things.
>
>Even the simplest of things, doesn't work out and is a
>learning experience.
>
>There can be a number of issues created, by parts or all of this
>being switched off.
>
>https://en.wikipedia.org/wiki/Internet_Control_Message_Protocol

I don't know if I've ever felt that way. There are things we don't know in the
current situation, but it's only because we aren't there. If we were able to
walk in and look around, I don't think any significant mysteries would remain.