Window 11 - Can't connect to RPI 3 & Octoprint

General
1

I just replaced my Dell laptop running Window 10 with a Lenovo Running Windows 11
I can not access octoprint. I have octoprint (no plugins) running on RPi 3b, with an Ender3 Pro, I had no issues with it under windows 10.
I can't ping the pi from the laptop. In fact, I set up 4 RPi's running at the same time and I couldn't ping any of them from the laptop.
Yet, I can ping all the RPi's from each other, I can't ping the laptop from any of the Pi's I setup.
Putty won't connect to the Pi's from the laptop either. Yet, Iinstalled Putty on my Pi 400 and it works on the other Pi's but not the new PC

I have tried all types of adjustments the laptop that I have found on the internet but nothing is working.
I did reflash the SD card this a fresh version of octoprint using the RPI imager.
I turned off windows defender, still can't connect

What gives with Windows 11?????

2

Sounds like local Firewall or AV is blocking these activities on your new W11 laptop. If your OP are running on ports like 5000 you may need to tell your Windows 11 laptop that it is ok to make out going requests on those ports. It could also be AV software firewall blocking these requests. Although, those most of the time will give you a pop up that something was blocked.

1 Like
3

I rechecked the firewall settings,
I set TCP in's and out's to port 5000,
I turned off windows defender entirely,
Still can not communicate with any Pi,
I can't ping anything that comes up in the list (using arp -a in command prompt as admin),
I can not ping any Pi,
The Pi's can ping each other, but not the PC,
I receive "request timed out" or "destination host not reachable" messages
I deleted MacAfee after I finished the setup on this new laptop
Any ideas of what could be the issue?
Have others had issues with Windows 11?

4

When you attempt to ping your Pi's, are you using a name or an IP address?

On your laptop open a command prompt and type ipconfig /all. Post the output here (use the </> icon above to surround the text). Post the output of any other commands you run on the Laptop.

On one of your Pi systems. Type ifconfig and post that result.

Have others had issues with Windows 11?

I have three systems including a Laptop running Windows 11 without issues.

5

Network Discovery not on or the Network type set to Public maybe?

Don't know if it's relevant, but I recently got stung with a Win 11 upgrade.
Simply connecting to shared Printers on other PC's failed.
Fix: Printer Error 0x00000bc4 or 0x00000709 in Windows 11 22H2 » Winhelponline

That said, my only Win11 here is 11 Pro on a Surface Pro & it's my daily goto for monitoring Octo & my other couple of Pi's.

Didn't need to apply the above GP change on it, but it is configured as on a Private Network with Network Discovery enable.

6

Windows IP Configuration

Wireless LAN adapter Local Area Connection* 1:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Local Area Connection* 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . : lan
IPv6 Address. . . . . . . . . . . : 2607:fb90:9a23:879:d466:2cf6:0:7f1
IPv6 Address. . . . . . . . . . . : 2607:fb90:9a23:879:db05:188b:3108:32c7
Temporary IPv6 Address. . . . . . : 2607:fb90:9a23:879:d421:926c:b625:1a3a
Link-local IPv6 Address . . . . . : fe80::4f2c:f945:789:a75d%4
IPv4 Address. . . . . . . . . . . : 192.168.12.131
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::de8d:8aff:fe85:5599%4
192.168.12.1

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Windows IP Configuration

Wireless LAN adapter Local Area Connection* 1:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Local Area Connection* 2:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

Wireless LAN adapter Wi-Fi:

Connection-specific DNS Suffix . : lan
IPv6 Address. . . . . . . . . . . : 2607:fb90:9a23:879:d466:2cf6:0:7f1
IPv6 Address. . . . . . . . . . . : 2607:fb90:9a23:879:db05:188b:3108:32c7
Temporary IPv6 Address. . . . . . : 2607:fb90:9a23:879:d421:926c:b625:1a3a
Link-local IPv6 Address . . . . . : fe80::4f2c:f945:789:a75d%4
IPv4 Address. . . . . . . . . . . : 192.168.12.131
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::de8d:8aff:fe85:5599%4
192.168.12.1

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :

7

IMG_7534
IMG_75341920×1440 268 KB

Here is a picture of the pi 400 config results

8

I'm confused because what you posted for the laptop network configuration doesn't appear to be the output of ipconfig /all or it doesn't match the format of that command on my Windows 11 systems (see below).

In particular, I was looking for the DNS server being used at both ends. On Windows, I believe nslookup with the name of one of the Pi's as a parameter and on the Pi, cat /etc/resolv.conf should give us this information. Also route print on the Windows system and just route on the Pi.

You also didn't answer my question about ping... are you using the name or the IP address?

For two systems on your LAN to communicate by name, they need to share a DNS server and a gateway. To communicate with IP addresses, a DNS server isn't needed.

The DNS server should be populated by the DHCP server. In typical home networks, the gateway, DHCP server, and DNS server are all the same system, usually the router. Since you can ping the Pi's from each other I'm guessing this is all working for them, but the laptop running Windows 11 doesn't appear to be playing nice. I suspect it is a DNS issue.


Windows IP Configuration

   Host Name . . . . . . . . . . . . : Brad-Morgan6
   Primary Dns Suffix  . . . . . . . : 
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : morgan.local

Ethernet adapter Ethernet:

   Connection-specific DNS Suffix  . : morgan.local
   Description . . . . . . . . . . . : Intel(R) Ethernet Connection (7) I219-V
   Physical Address. . . . . . . . . : 24-4B-FE-58-95-59
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::32c0:41d1:e83a:79fc%4(Preferred) 
   IPv4 Address. . . . . . . . . . . : 192.168.0.148(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Wednesday, March 15, 2023 9:44:08 AM
   Lease Expires . . . . . . . . . . : Monday, March 20, 2023 6:42:59 AM
   Default Gateway . . . . . . . . . : 192.168.0.1
   DHCP Server . . . . . . . . . . . : 192.168.0.1
   DHCPv6 IAID . . . . . . . . . . . : 103042046
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-26-B1-CA-69-24-4B-FE-58-95-59
   DNS Servers . . . . . . . . . . . : 192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter vEthernet (Default Switch):

   Connection-specific DNS Suffix  . : 
   Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter
   Physical Address. . . . . . . . . : 00-15-5D-14-B5-97
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::4fc8:effe:71ed:a46%18(Preferred) 
   IPv4 Address. . . . . . . . . . . : 172.18.176.1(Preferred) 
   Subnet Mask . . . . . . . . . . . : 255.255.240.0
   Default Gateway . . . . . . . . . : 
   DHCPv6 IAID . . . . . . . . . . . : 301995357
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-26-B1-CA-69-24-4B-FE-58-95-59
   NetBIOS over Tcpip. . . . . . . . : Enabled
9

First thing that stands out to me is IP6.

Don't know how many client network issues I've resolved by Disabling IP6.
It's quite a few & my default configs are to always turn it off.

Don't think it's really needed on the local side & nothing is gained internally.

Have seen where even local software won't work as it can't connect to localhost as it is first resolved to IP6 which some software does not bind to.

10

Problem solved!
Apparently, in W11, by default, windows defender has the "make my pc discoverable" toggled off. So, my new pc was not being seen by other stuff on my network. I switched it on and BINGO I can see my Ender3 Pro again!
Keep that in mind when setting up a W11 machine.

Thanks for all the help!!!!!!!!!

11

You were correct!
By default Network Discovery is off
I turned it on and Bingo!
Thx

1 Like