XPost: sci.electronics.repair, alt.home.repair   
   From: patchmoney@gmx.com   
      
   On 28 Mar 2023 at 7:09:59 PM, Scott Lurndal  wrote:   
      
   > Run a port scanner (e.g. nmap) on the entire 192.168.0.0/16 subnet.   
   > Then try the 10.0.0.0/24 subnet if you don't get a hit on 192.168.0.0/16   
      
   I don't know if the RB411 is on the 192.168.88.xxx or 192.168.1.xxx subnet.   
   Do I need to put the Windows PC on the same subnet as the RB411 might be?   
      
   Anyway, I googled for nmap and somehow I ended up with Zenmap on my desktop.   
   https://nmap.org/book/zenmap.html   
      
   The default zenmap scan is apparently this command.   
   Target: 192.168.1.1/24   
   Command: nmap -T4 -A -v 192.168.1.1/24   
      
   Target: 192.168.88.1/24   
   Command: nmap -T4 -A -v 192.168.88.1/24   
      
   The first nmap command it ran from the Zenmap GUI without the RB411 was   
   Nmap scan report for 192.168.1.0 [host down]   
   Nmap scan report for 192.168.1.2 [host down]   
   Nmap scan report for 192.168.1.3 [host down]   
   ...   
   Discovered open port 443/tcp on 192.168.1.100   
   Discovered open port 443/tcp on 192.168.1.101   
   Discovered open port 443/tcp on 192.168.1.102   
      
   There were pages of results, so I'm weeding through them first while   
   I'm on my home LAN before I connect the PC directly to the RB411 router.   
      
   It's a pain not knowing what subnet to put the PC on so I pulled   
   the Ethernet out of the home router and plugged it into the RB411   
   instead. Then I changed the PC IP address to these two one by one.   
   Win+r cmd {control+shift+enter}   
   netsh interface ipv4 show config   
   netsh interface ipv4 show config "Ethernet"   
   netsh interface ipv4 set address name="Ethernet" static 192.168.1.2   
   255.255.255.0 192.168.1.1   
   ping 192.168.1.1 -t (which fails)   
   Then I ran the zenmap GUI with a Target: 192.168.1.1 192.168.1.255   
   Command: nmap -T4 -A -v 192.168.1.1/24   
   setup_target: failed to determine route to 192.168.1.0   
   setup_target: failed to determine route to 192.168.1.1   
   setup_target: failed to determine route to 192.168.1.2   
   ...   
      
   Then I tried the 88 subnet.   
   Win+r cmd {control+shift+enter}   
   netsh interface ipv4 show config   
   netsh interface ipv4 show config "Ethernet"   
   netsh interface ipv4 set address name="Ethernet" static 192.168.88.2   
   255.255.255.0 192.168.88.1   
   ping 192.168.88.1 -t (which fails)   
   Then I ran the zenmap GUI with a Target: 192.168.88.1 192.168.88.255   
   Command: nmap -T4 -A -v 192.168.88.1/24   
   setup_target: failed to determine route to 192.168.88.0   
   setup_target: failed to determine route to 192.168.88.1   
   get_srcaddr: can't connect socket: A socket operation was attempted to an   
   unreachable host.   
   setup_target: failed to determine route to 192.168.88.3   
   setup_target: failed to determine route to 192.168.88.4   
   setup_target: failed to determine route to 192.168.88.5   
   ...   
      
   I'm not sure what I'm doing, but it seems I get different results   
   if I put the PC on 192.168.1.xxx versus 192.168.88.xxx and then   
   I run that zenmap port scan - but I don't yet know what to make   
   of the results since nothing came back as a really good hit.   
      
   My googling found also "ipscan" and "portscanner" which I may try.   
   https://angryip.org/download/#windows   
   https://www.eusing.com/ipscan/free_ip_scanner.htm   
   https://www.advanced-ip-scanner.com/download/   
      
   The problem is that the search is filled with shills so I don't know   
   which is the right freeware respected ipscanner or port scanner download.   
      
   Given the syntax is not in the least intuitive (it takes experimentation),   
   does anyone have a recommendation as to which scanner to concentrate on?   
   --   
   Cheers, Rob   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)