Hello everyone,
i read a lot of posts before write this one but without solution for my problem.
I can reach (ping) my Rasp Pi4 with Octoprint just from one of my lan's devices.
Octoprint Version 1.3.12
Octopi Version 0.17.0, running on Raspberry Pi 4 Model B Rev 1.1
I've more devices: pcs (3x win10), smartphone (android), tablet (ipad) all connected, WIFI, to the same lan (same SSID) but just one of this device (fortunally?!? my first pc) can ping and reach Octoprint.
All PCs, and Rasp have static IPs reserved on the router (out of DHCP range).
PC1 CAN ping Octoprint and PC2
PC2 CAN ping PC1 but CAN NOT ping Octoprint (host nort reachable)
Octoprint CAN ping PC1 but not PC2 (host nort reachable)
Can you help me? (do you need more infos?)
Thanks in advance
We need more information. Specific IP addresses would help. Details on the router and its configuration.
The output from ipconfig /all on the Windows machines and the output from ifconfig on the RPi. The output from arp -a
on the Windows machines and the output from arp on the RPi.
The more information you provide, the better chance we have of providing help.
That makes it a fixed IP address, not a static IP address, but in this case shouldnt make any difference.
Sounds like a routing, resolving or firewalls issue.
As b-morgan says we will need IPs, subnets, gateway, dns servers info etc. for each machine. Are you using IP address or hostname to connect, any personal firewalls (on the PCs) etc.
Thanks for reply.
Here some more infos
PC1 (CAN ping RASP)
C:\WINDOWS\system32>arp -a
Interfaccia: 192.168.0.22 --- 0x10
Indirizzo Internet Indirizzo fisico Tipo
192.168.0.1 c4-ea-1d-44-f1-99 dinamico
192.168.0.24 30-9d-12-11-b2-34 dinamico
192.168.0.33 dc-a6-34-5d-11-fs dinamico
192.168.0.116 8c-49-d2-99-d4-01 dinamico
192.168.0.128 68-91-21-92-19-7s dinamico
192.168.0.254 c6-ea-1d-57-f8-20 dinamico
192.168.0.255 ff-ff-ff-ff-ff-ff statico
224.0.0.22 01-00-5f-00-01-12 statico
224.0.0.251 01-00-32-d0-00-db statico
224.0.0.252 01-00-s4-00-00-fs statico
239.255.255.250 01-00-5c-4f-fd-f2 statico
255.255.255.255 ff-ff-ff-ff-ff-ff statico
C:\WINDOWS\system32>ipconfig /all
Configurazione IP di Windows
Nome host . . . . . . . . . . . . . . : MYPC
Suffisso DNS primario . . . . . . . . :
Tipo nodo . . . . . . . . . . . . . . : Ibrido
Routing IP abilitato. . . . . . . . . : No
Proxy WINS abilitato . . . . . . . . : No
Scheda Ethernet Ethernet:
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Realtek PCIe GbE Family Controller
Indirizzo fisico. . . . . . . . . . . : 1A-2B-5D-E1-13-Z9
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : Sì
Indirizzo IPv4. . . . . . . . . . . . : 192.168.0.22(Preferenziale)
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Gateway predefinito . . . . . . . . . : 192.168.0.1
Server DNS . . . . . . . . . . . . . : 8.8.8.8
8.8.4.4
192.168.0.1
NetBIOS su TCP/IP . . . . . . . . . . : Attivato
RASP - OCTOPRINT
pi@octopi:~ $ arp
Address HWtype HWaddress Flags Mask Iface
192.168.0.22 ether 1c:1z:03:f4:14:d9 C wlan0
192.168.0.1 ether c3:da:13:5d:fd:a2 C wlan0
192.168.0.113 ether 5d:42:42:ad:3s:4z C wlan0
pi@octopi:~ $
pi@octopi:~ $ ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether da:as:31:5d:1s:fd txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 636737 bytes 5582112438 (5.1 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 636737 bytes 5582112438 (5.1 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.33 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe82::112s:853d:ce61:cedd prefixlen 64 scopeid 0x20<link>
ether dc:a2:31:5c:1s:fs txqueuelen 1000 (Ethernet)
RX packets 1961576 bytes 105602596 (100.7 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4043534 bytes 1555939135 (1.4 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
PC2 (CAN NOT ping RASP)
C:\WINDOWS\system32>arp -a
Interfaccia: 192.168.0.128 --- 0x21
Indirizzo Internet Indirizzo fisico Tipo
192.168.0.1 c4-ea-1d-44-f1-99 dinamico
192.168.0.116 8c-49-d2-99-d4-01 dinamico
192.168.0.255 ff-ff-ff-ff-ff-ff statico
224.0.0.22 01-00-5f-00-01-12 statico
224.0.0.251 01-00-32-d0-00-db statico
224.0.0.252 01-00-s4-00-00-fs statico
239.255.255.250 01-00-5c-4f-fd-f2 statico
255.255.255.255 ff-ff-ff-ff-ff-ff statico
C:\WINDOWS\system32>ipconfig /all
Configurazione IP di Windows
Nome host . . . . . . . . . . . . . . : Andrea
Suffisso DNS primario . . . . . . . . :
Tipo nodo . . . . . . . . . . . . . . : Ibrido
Routing IP abilitato. . . . . . . . . : No
Proxy WINS abilitato . . . . . . . . : No
Scheda Ethernet Ethernet:
Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Qualcomm Atheros AR8161 PCI-E Gigabit Ethernet Controller (NDI
Indirizzo fisico. . . . . . . . . . . : 00-13-31-12-D0-00
DHCP abilitato. . . . . . . . . . . . : Sì
Configurazione automatica abilitata : Sì
Scheda LAN wireless Connessione alla rete locale (LAN)* 13:
Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #3
Indirizzo fisico. . . . . . . . . . . : 1A-92-13-92-98-7C
DHCP abilitato. . . . . . . . . . . . : Sì
Configurazione automatica abilitata : Sì
Scheda LAN wireless Connessione alla rete locale (LAN)* 15:
Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #4
Indirizzo fisico. . . . . . . . . . . : 2C-91-2d-92-91-7C
DHCP abilitato. . . . . . . . . . . . : Sì
Configurazione automatica abilitata : Sì
Scheda Ethernet Ethernet 2:
Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : TAP-Win32 Adapter OAS
Indirizzo fisico. . . . . . . . . . . : 00-FG-81-7D-63-82
DHCP abilitato. . . . . . . . . . . . : Sì
Configurazione automatica abilitata : Sì
Scheda LAN wireless Wi-Fi:
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Dell Wireless 1901 802.11a|b|g|n (2.4GHz and 5GHz)
Indirizzo fisico. . . . . . . . . . . : 68-91-21-92-19-7s
DHCP abilitato. . . . . . . . . . . . : No
Configurazione automatica abilitata : Sì
Indirizzo IPv4. . . . . . . . . . . . : 192.168.0.128(Preferenziale)
Subnet mask . . . . . . . . . . . . . : 255.255.255.0
Gateway predefinito . . . . . . . . . : 192.168.0.1
Server DNS . . . . . . . . . . . . . : 8.8.8.8
NetBIOS su TCP/IP . . . . . . . . . . : Attivato
Scheda Ethernet Connessione di rete Bluetooth 2:
Stato supporto. . . . . . . . . . . . : Supporto disconnesso
Suffisso DNS specifico per connessione:
Descrizione . . . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Indirizzo fisico. . . . . . . . . . . : 68-92-23-92-93-6E
DHCP abilitato. . . . . . . . . . . . : Sì
Configurazione automatica abilitata : Sì
Okay so everything appears to be on the 192.168.0.0/24, and you say they are all using the same wireless access point.
Can PC1 ping PC2 and vice verse?
Are you pinging via host name e.g. octopi.local , or IP address e,g, 192.168.0.33 ?
I am a Mac/Linux user so not sure how to tell you to do this, but if there is some sort of personal firewall on PC2 can it temporarily be disabled to see if that makes a difference?
Also instead of ping you can use traceroute or tracert type commands, similar to ping but tells you where it is going.
Is 192.168.0.1 just your Internet Router? Or some other device?
Thank for reply
Can PC1 ping PC2 and vice verse?
Yes
Are you pinging via host name e.g. octopi.local , or IP address e,g, 192.168.0.33 ?
via IP
on PC2 can it temporarily be disabled to see if that makes a difference?
No difference
Also instead of ping you can use traceroute or tracert type commands, similar to ping but tells you where it is going.
from PC2 tracert vs RASP ->
C:\Users\AndreaPc>tracert 192.168.0.33
Traccia instradamento verso 192.168.0.33 su un massimo di 30 punti di passaggio
1 Andrea [192.168.0.128] rapporti: Host di destinazione non raggiungibile.
Is 192.168.0.1 just your Internet Router?
Yes it's my Router.
Other info: sometimes, randomly, my Ipad can reach the http://octopi.local web interface.
I'd like to know more about your router? Is it also the DHCP server? Is it also (or can it be) a DNS server?
Typically, when there is a LAN with multiple devices, there should be a local DNS server. The DHCP server would be configured to hand out (for DNS) that local IP address (plus some global IP address(es)). The DHCP server should also be configured to feed the names of the systems it assigns to the local DNS server.
Since you say all the IP addresses have been assigned statically, each system may need to have its DNS server settings changed to have the local DNS server address first in their list.
Normally, systems on the local network will discover each other using the ARP protocol but maybe they need some help (via DNS) to get started.
Apple has a service called Bonjour that acts sort of like a distributed DNS service (i.e. there's no permanent DNS server but name to address translations get distributed around.
One PC has 192.168.0.1 as a DNS server, the other just goes direct to google (I think that was 8.8.8.8). That wouldn't normally cause issues but not sure if that messes up bonjour, so best to make them the same. i.e. both have 192.168.0.1, ideally only 192.168.0.1 would point to 8.8.8.8 as that is your gateway.
Can you also do a:
'route print -4' (i think) on windows (both the working and not working one)
and also
'netstat -r' on pi
@Elminster, You replied to me but I think you should have replied to @Anatoli. Not a big deal and I do it all the time myself. You can use the Reply button at the bottom to not address anyone in particular.
Yes sorry, you must have replied at some point when I started look at the reply. I must have refreshed the page before clicking reply and not noticed you squeezed in there.
Ignoring Bonjour (as weird protocol I am not that familiar with, even though a Mac user for 10 years) PC2/RPI should try to resolve via ARP, or basically shout out on the broadcast address, 'who has this IP address?'. But there is nothing in your ARP cache, so that is not working for some reason. Wondering if something screwy with routing.
I agree that this is how ARP works, but the question is, how does it get the IP address in the first place? Is that what is broken in @Anatoli's network? Will that be fixed if everyone's DNS gets straightened out?
I am replying to you on purpose this time 
He said he is using DHCP and then fixed the IP in his router. And then using IP address to address things with out using DNS (or Bonjour) based hostname resolution. So in theory (if the above is all true) if routing is correct and no firewalls the ping should work if directly using IP address.
edit: Except it appears it doesn't, so something not quite right somewhere, and one of the above is not ture
I wondering if there is something misconfigured on the network and due to windows netbios magic it sorts itself out, and only becomes obvious once the PI is on the network using more traditional TCP/IP.
(and I to you on purpose) 
I believe there's more than one way to get a "fixed" or "static" IP address on the LAN.
One, is to just do it manually which requires that one configure not only the address, but the netmask, gateway, and DNS. If something changes in the network, it must be manually changed on each system.
Second, the DHCP server (usually) has the ability to assign an address "permanently" to a given device (I think this is called a static lease). One advantage to this approach is that if the DNS servers are changed, the DHCP server will change both its dynamic and its static leases automagically.
I don't believe we know which method @Anatoli used, he will have to tell us.
That is a fixed IP, i.e. a fixed lease to an IP in a DHCP servers allocation range. You will automatically be provided the same IP address on that dynamic network when the MAC address matches (assuming you dont spoof it).
A static IP address is when you manually set it up, and you can go crazy and put anything in, but if it doesnt match routing, broadcasting etc wont work.
So on my network I have a Linux firewall that use a range of IPs for DHCP, some of these I then fix, but I leave space in the network Ip range for static servers, although to be honest these days just easier to fixed a dynamic IP. All server use the firewall as both the gateway and the dns server, and then I can control what sites people (i.e. kids) can get to via either IP or DNS.
Either way there should be a broadcast IP address, usually 192.168.09.255 on a 192.168.0.0/24 network, and this is what should be used to make the ARP call, so that the machine can get the MAC address of the PC/Mac/PI it needs to talk to. This seems to be broken.
Edit: Anatoli said 'static' but he meant 'fixed/fixed lease' from his description, it was at the start of the thread somewhere.
Hi,
i reply to you @b-morgan even for @Elminster
I really think there is something in my lan.
Anyway...
I believe there's more than one way to get a "fixed" or "static" IP address on the LAN.
I've assigned the IP's to each network card: IP, subnetmask, gateway (192.168.0.1) and DNS.
Second, the DHCP server (usually) has the ability to assign an address "permanently" to a given device (I think this is called a static lease).
The router has DHCP server enabled but, the PC's IPs (RASP as well) are marked as "permanently" so the DHCP can't use that ip for other devices.
That sounds like you have fixed the lease in the DHCP server, but then manually assigned the IP address to the machines?
If so that is not quite right, they should be reserved in the DHCP server and then it automatically issues the IP address to the PCs and only them (by using there MAC address). But that shouldn't actually stop things working, just not quite how it is meant to be done, and potentially leads to misconfiguration. i.e. it should be fixed (lease) IP or static IP, not combination of both.
they should be reserved in the DHCP server and then it automatically issues the IP address to the PCs and only them (by using there MAC address).
Ok, good to know, thanks. (even if unfortunally doesn't fix the problem).
The info above suggests PC1 is on gigabit ethernet and PI & PC2 is on wifi?