You did not say that...
So, login via SSH. Enter ``sudo raspi-config in 2 network options - N1 Hostname you can find it.
or in SSH type in hostname -s
Okay let me rephrase the issue. I already know my hostname; I just cannot connect to the server with it. The console says I can either use the hostname.local, or the pi's IP address, but only the IP address works.
Per the install instructions:
(it is located at
octopi.localif your computer supports bonjour or the IP address assigned by your router)
You will need to check your computer has bonjour/zeroconf installed, so it can resolve the hostname. The link above should tell you how to do that.
The hostname worked when I was connected to ethernet though. Is that a different situation?
Okay so I was able to extract the bonjour installer from an itunes installer, so I now have it, but the hostname still doesn't work
The way that bonjour/avahi/zeroconf/mdns (same thing, several names) works is via multicasts on the local network. If your wired and wireless network aren't bridged or your network settings deny forwarding of multicast packages, stuff won't work. In that case, either see if your router maybe supports name resolution for connected clients by hostname (e.g. via something like the .lan tld), or use the IP address.
This working relies on your network and the client you are trying to connect from. It usually works in home LANs, but not always, and it is impossible to predict - too many variables.
Well I'm not exactly working with a home network, or one that I have any true access working with; I was hoping I'd be able to get things working on my own. I'm working with a college wifi, and if things are that large scale I don't think I can get it working at all.
In that case use the IP address. Frankly I'm surprised that in this setup you can even reach it by IP address, usually larger scale networks like that do client isolation to reduce the risk of attacks on the network, meaning you wouldn't even be able to reach it via IP.
Well I suppose that's a win then. It won't be an issue as long as I never turn the pi off, so the IP doesn't change. Normally when I'm done printing for a while I will turn it off, but now it will probably be better keeping it on.
The default network configuration on the RPi is to use DHCP to request an IP address from a DHCP server. The RPi will submit its hostname as part of this request. If so configured, the DHCP server will inform a DNS server of both the name and the address and it will supply the DNS server IP address to the RPi along with the assigned IP address. If your desktop computer and the RPi are using the same DHCP server and using the suggested DNS server, then connecting via the RPi hostname should work. Use the ifconfig and/or ipconfig commands to verify.
Using ifconfig on the pi and ipconfig on the laptop? And if so, what specific things should I be looking for?
Yes (if the laptop is running Windows). Actually, use ipconfig /all on Windows. This will give you IP, Mask, DHCP, and DNS server info. For the RPi, ifconfig, cat /etc/resolv.conf, and grep -i dhcp /var/log/syslog will give you similar info.
The laptop and the RPi should be in the same subnet (which they should be as you can connect via IP address) and should use the same DNS and DHCP servers.
If you want, post the output here (use </> around it) and I'll also look at it (and probably figure out I missed other useful output).
Output from Windows "ipconfig /all"
Windows IP Configuration
Host Name . . . . . . . . . . . . : JonsLaptop
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : arizona.edu
Ethernet adapter Ethernet:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : arizona.edu
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 98-28-A6-1C-45-1A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Local Area Connection* 1:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #3
Physical Address. . . . . . . . . : 3C-6A-A7-A3-14-B7
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Local Area Connection* 12:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #4
Physical Address. . . . . . . . . : 3E-6A-A7-A3-14-B6
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . : arizona.edu
Description . . . . . . . . . . . : Intel(R) Wireless-AC 9560 160MHz
Physical Address. . . . . . . . . : 3C-6A-A7-A3-14-B6
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::6972:cc3a:37e7:5b80%21(Preferred)
IPv4 Address. . . . . . . . . . . : 10.134.152.242(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.192.0
Lease Obtained. . . . . . . . . . : Thursday, November 12, 2020 3:09:51 PM
Lease Expires . . . . . . . . . . : Friday, November 13, 2020 6:42:34 PM
Default Gateway . . . . . . . . . : 10.134.128.1
DHCP Server . . . . . . . . . . . : 10.133.127.254
DHCPv6 IAID . . . . . . . . . . . : 272394919
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-23-18-67-D5-98-28-A6-1C-45-1A
DNS Servers . . . . . . . . . . . : 128.196.11.234
128.196.11.235
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Bluetooth Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 3C-6A-A7-A3-14-BA
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Output from Raspberry pi "ifconfig", "cat /etc/resolv.conf", and "grep -i dhcp /var/log/syslog"
pi@JkanePrinter:~ $ ifconfig
enxb827ebacd345: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether b8:27:eb:ac:d3:45 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 62 bytes 16840 (16.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 62 bytes 16840 (16.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.132.128.114 netmask 255.255.192.0 broadcast 10.132.191.255
inet6 fe80::22a7:6491:fe81:ce74 prefixlen 64 scopeid 0x20<link>
ether b8:27:eb:f9:86:10 txqueuelen 1000 (Ethernet)
RX packets 1081 bytes 143279 (139.9 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1209 bytes 236607 (231.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
pi@JkanePrinter:~ $
pi@JkanePrinter:~ $ cat /etc/resolv.conf
# Generated by resolvconf
domain arizona.edu
nameserver 128.196.11.234
nameserver 128.196.11.233
pi@JkanePrinter:~ $
pi@JkanePrinter:~ $ grep -i dhcp /var/log/syslog
Nov 12 00:49:32 JkanePrinter systemd[1]: Starting dhcpcd on all interfaces...
Nov 12 00:49:32 JkanePrinter dhcpcd[338]: dev: loaded udev
Nov 12 00:49:32 JkanePrinter dhcpcd[338]: forked to background, child pid 389
Nov 12 00:49:32 JkanePrinter systemd[1]: Started dhcpcd on all interfaces.
Nov 12 00:49:32 JkanePrinter dhcpcd-run-hooks[430]: wlan0: starting wpa_supplicant
Nov 12 00:49:33 JkanePrinter dhcpcd[389]: wlan0: connected to Access Point `'
Nov 12 00:49:33 JkanePrinter dhcpcd[389]: enxb827ebacd345: waiting for carrier
Nov 12 00:49:33 JkanePrinter dhcpcd[389]: wlan0: waiting for carrier
Nov 12 00:49:33 JkanePrinter dhcpcd[389]: wlan0: carrier acquired
Nov 12 00:49:33 JkanePrinter dhcpcd[389]: DUID 00:01:00:01:25:1e:c1:c0:b8:27:eb:f9:86:10
Nov 12 00:49:33 JkanePrinter dhcpcd[389]: wlan0: IAID eb:f9:86:10
Nov 12 00:49:33 JkanePrinter dhcpcd[389]: wlan0: adding address fe80::3bc7:44d9:af8a:2074
Nov 12 00:49:33 JkanePrinter dhcpcd[389]: wlan0: carrier lost
Nov 12 00:49:33 JkanePrinter dhcpcd[389]: wlan0: deleting address fe80::3bc7:44d9:af8a:2074
Nov 12 00:49:35 JkanePrinter dhcpcd[389]: wlan0: carrier acquired
Nov 12 00:49:35 JkanePrinter dhcpcd[389]: wlan0: connected to Access Point `UAWiFi'
Nov 12 00:49:35 JkanePrinter dhcpcd[389]: wlan0: IAID eb:f9:86:10
Nov 12 00:49:35 JkanePrinter dhcpcd[389]: wlan0: adding address fe80::22a7:6491:fe81:ce74
Nov 12 00:49:36 JkanePrinter dhcpcd[389]: wlan0: rebinding lease of 10.132.136.213
Nov 12 00:49:36 JkanePrinter dhcpcd[389]: wlan0: probing address 10.132.136.213/18
Nov 12 00:49:36 JkanePrinter dhcpcd[389]: wlan0: soliciting an IPv6 router
Nov 12 00:49:41 JkanePrinter dhcpcd[389]: wlan0: leased 10.132.136.213 for 567 seconds
Nov 12 00:49:41 JkanePrinter dhcpcd[389]: wlan0: adding route to 10.132.128.0/18
Nov 12 00:49:41 JkanePrinter dhcpcd[389]: wlan0: adding default route via 10.132.128.1
Nov 12 00:49:49 JkanePrinter dhcpcd[389]: wlan0: no IPv6 Routers available
Nov 12 00:59:52 JkanePrinter systemd[1]: Starting dhcpcd on all interfaces...
Nov 12 00:59:52 JkanePrinter dhcpcd[312]: dev: loaded udev
Nov 12 00:59:52 JkanePrinter dhcpcd[312]: forked to background, child pid 385
Nov 12 00:59:52 JkanePrinter systemd[1]: Started dhcpcd on all interfaces.
Nov 12 00:59:52 JkanePrinter dhcpcd-run-hooks[435]: wlan0: starting wpa_supplicant
Nov 12 00:59:53 JkanePrinter dhcpcd[385]: wlan0: connected to Access Point `'
Nov 12 00:59:53 JkanePrinter dhcpcd[385]: enxb827ebacd345: waiting for carrier
Nov 12 00:59:53 JkanePrinter dhcpcd[385]: wlan0: waiting for carrier
Nov 12 00:59:53 JkanePrinter dhcpcd[385]: wlan0: carrier acquired
Nov 12 00:59:53 JkanePrinter dhcpcd[385]: DUID 00:01:00:01:25:1e:c1:c0:b8:27:eb:f9:86:10
Nov 12 00:59:53 JkanePrinter dhcpcd[385]: wlan0: IAID eb:f9:86:10
Nov 12 00:59:53 JkanePrinter dhcpcd[385]: wlan0: adding address fe80::3bc7:44d9:af8a:2074
Nov 12 00:59:53 JkanePrinter dhcpcd[385]: wlan0: carrier lost
Nov 12 00:59:53 JkanePrinter dhcpcd[385]: wlan0: deleting address fe80::3bc7:44d9:af8a:2074
Nov 12 00:59:56 JkanePrinter dhcpcd[385]: wlan0: carrier acquired
Nov 12 00:59:56 JkanePrinter dhcpcd[385]: wlan0: connected to Access Point `UAWiFi'
Nov 12 00:59:56 JkanePrinter dhcpcd[385]: wlan0: IAID eb:f9:86:10
Nov 12 00:59:56 JkanePrinter dhcpcd[385]: wlan0: adding address fe80::22a7:6491:fe81:ce74
Nov 12 00:59:56 JkanePrinter dhcpcd[385]: wlan0: soliciting an IPv6 router
Nov 12 00:59:57 JkanePrinter dhcpcd[385]: wlan0: rebinding lease of 10.132.136.213
Nov 12 00:59:57 JkanePrinter dhcpcd[385]: wlan0: probing address 10.132.136.213/18
Nov 12 01:00:01 JkanePrinter dhcpcd[385]: wlan0: leased 10.132.136.213 for 559 seconds
Nov 12 01:00:01 JkanePrinter dhcpcd[385]: wlan0: adding route to 10.132.128.0/18
Nov 12 01:00:01 JkanePrinter dhcpcd[385]: wlan0: adding default route via 10.132.128.1
Nov 12 01:00:09 JkanePrinter dhcpcd[385]: wlan0: no IPv6 Routers available
Nov 12 01:55:44 JkanePrinter systemd[1]: Starting dhcpcd on all interfaces...
Nov 12 01:55:44 JkanePrinter dhcpcd[326]: dev: loaded udev
Nov 12 01:55:44 JkanePrinter dhcpcd[326]: forked to background, child pid 398
Nov 12 01:55:44 JkanePrinter systemd[1]: Started dhcpcd on all interfaces.
Nov 12 01:55:44 JkanePrinter dhcpcd-run-hooks[438]: wlan0: starting wpa_supplicant
Nov 12 01:55:45 JkanePrinter dhcpcd[398]: wlan0: connected to Access Point `'
Nov 12 01:55:45 JkanePrinter dhcpcd[398]: enxb827ebacd345: waiting for carrier
Nov 12 01:55:45 JkanePrinter dhcpcd[398]: wlan0: waiting for carrier
Nov 12 01:55:45 JkanePrinter dhcpcd[398]: wlan0: carrier acquired
Nov 12 01:55:45 JkanePrinter dhcpcd[398]: DUID 00:01:00:01:25:1e:c1:c0:b8:27:eb:f9:86:10
Nov 12 01:55:45 JkanePrinter dhcpcd[398]: wlan0: IAID eb:f9:86:10
Nov 12 01:55:45 JkanePrinter dhcpcd[398]: wlan0: adding address fe80::3bc7:44d9:af8a:2074
Nov 12 01:55:45 JkanePrinter dhcpcd[398]: wlan0: carrier lost
Nov 12 01:55:45 JkanePrinter dhcpcd[398]: wlan0: deleting address fe80::3bc7:44d9:af8a:2074
Nov 12 01:55:48 JkanePrinter dhcpcd[398]: wlan0: carrier acquired
Nov 12 01:55:48 JkanePrinter dhcpcd[398]: wlan0: connected to Access Point `UAWiFi'
Nov 12 01:55:48 JkanePrinter dhcpcd[398]: wlan0: IAID eb:f9:86:10
Nov 12 01:55:48 JkanePrinter dhcpcd[398]: wlan0: adding address fe80::22a7:6491:fe81:ce74
Nov 12 01:55:49 JkanePrinter dhcpcd[398]: wlan0: soliciting an IPv6 router
Nov 12 01:55:49 JkanePrinter dhcpcd[398]: wlan0: rebinding lease of 10.132.136.213
Nov 12 01:55:53 JkanePrinter dhcpcd[398]: wlan0: probing address 10.132.136.213/18
Nov 12 01:55:58 JkanePrinter dhcpcd[398]: wlan0: leased 10.132.136.213 for 600 seconds
Nov 12 01:55:58 JkanePrinter dhcpcd[398]: wlan0: adding route to 10.132.128.0/18
Nov 12 01:55:58 JkanePrinter dhcpcd[398]: wlan0: adding default route via 10.132.128.1
Nov 12 01:56:02 JkanePrinter dhcpcd[398]: wlan0: no IPv6 Routers available
Nov 12 15:07:19 JkanePrinter systemd[1]: Starting dhcpcd on all interfaces...
Nov 12 15:07:19 JkanePrinter dhcpcd[341]: dev: loaded udev
Nov 12 15:07:19 JkanePrinter dhcpcd[341]: forked to background, child pid 396
Nov 12 15:07:19 JkanePrinter systemd[1]: Started dhcpcd on all interfaces.
Nov 12 15:07:19 JkanePrinter dhcpcd-run-hooks[442]: wlan0: starting wpa_supplicant
Nov 12 15:07:20 JkanePrinter dhcpcd[396]: wlan0: connected to Access Point `'
Nov 12 15:07:20 JkanePrinter dhcpcd[396]: enxb827ebacd345: waiting for carrier
Nov 12 15:07:20 JkanePrinter dhcpcd[396]: wlan0: waiting for carrier
Nov 12 15:07:20 JkanePrinter dhcpcd[396]: wlan0: carrier acquired
Nov 12 15:07:20 JkanePrinter dhcpcd[396]: DUID 00:01:00:01:25:1e:c1:c0:b8:27:eb:f9:86:10
Nov 12 15:07:20 JkanePrinter dhcpcd[396]: wlan0: IAID eb:f9:86:10
Nov 12 15:07:20 JkanePrinter dhcpcd[396]: wlan0: adding address fe80::3bc7:44d9:af8a:2074
Nov 12 15:07:20 JkanePrinter dhcpcd[396]: wlan0: carrier lost
Nov 12 15:07:20 JkanePrinter dhcpcd[396]: wlan0: deleting address fe80::3bc7:44d9:af8a:2074
Nov 12 15:07:23 JkanePrinter dhcpcd[396]: wlan0: carrier acquired
Nov 12 15:07:23 JkanePrinter dhcpcd[396]: wlan0: connected to Access Point `UAWiFi'
Nov 12 15:07:23 JkanePrinter dhcpcd[396]: wlan0: IAID eb:f9:86:10
Nov 12 15:07:23 JkanePrinter dhcpcd[396]: wlan0: adding address fe80::22a7:6491:fe81:ce74
Nov 12 15:07:23 JkanePrinter dhcpcd[396]: wlan0: soliciting an IPv6 router
Nov 12 15:07:23 JkanePrinter dhcpcd[396]: wlan0: rebinding lease of 10.132.136.213
Nov 12 15:07:23 JkanePrinter dhcpcd[396]: wlan0: probing address 10.132.136.213/18
Nov 12 15:07:29 JkanePrinter dhcpcd[396]: wlan0: leased 10.132.136.213 for 492 seconds
Nov 12 15:07:29 JkanePrinter dhcpcd[396]: wlan0: adding route to 10.132.128.0/18
Nov 12 15:07:29 JkanePrinter dhcpcd[396]: wlan0: adding default route via 10.132.128.1
Nov 12 15:07:36 JkanePrinter dhcpcd[396]: wlan0: no IPv6 Routers available
Nov 12 15:16:08 JkanePrinter systemd[1]: Starting dhcpcd on all interfaces...
Nov 12 15:16:08 JkanePrinter dhcpcd[298]: dev: loaded udev
Nov 12 15:16:08 JkanePrinter dhcpcd[298]: forked to background, child pid 328
Nov 12 15:16:08 JkanePrinter systemd[1]: Started dhcpcd on all interfaces.
Nov 12 15:16:08 JkanePrinter dhcpcd-run-hooks[415]: wlan0: starting wpa_supplicant
Nov 12 15:16:09 JkanePrinter dhcpcd[328]: wlan0: connected to Access Point `'
Nov 12 15:16:09 JkanePrinter dhcpcd[328]: enxb827ebacd345: waiting for carrier
Nov 12 15:16:09 JkanePrinter dhcpcd[328]: wlan0: waiting for carrier
Nov 12 15:16:09 JkanePrinter dhcpcd[328]: wlan0: carrier acquired
Nov 12 15:16:09 JkanePrinter dhcpcd[328]: DUID 00:01:00:01:25:1e:c1:c0:b8:27:eb:f9:86:10
Nov 12 15:16:09 JkanePrinter dhcpcd[328]: wlan0: IAID eb:f9:86:10
Nov 12 15:16:09 JkanePrinter dhcpcd[328]: wlan0: adding address fe80::3bc7:44d9:af8a:2074
Nov 12 15:16:09 JkanePrinter dhcpcd[328]: wlan0: carrier lost
Nov 12 15:16:09 JkanePrinter dhcpcd[328]: wlan0: deleting address fe80::3bc7:44d9:af8a:2074
Nov 12 15:16:22 JkanePrinter dhcpcd[328]: wlan0: carrier acquired
Nov 12 15:16:22 JkanePrinter dhcpcd[328]: wlan0: connected to Access Point `UAWiFi'
Nov 12 15:16:22 JkanePrinter dhcpcd[328]: wlan0: IAID eb:f9:86:10
Nov 12 15:16:22 JkanePrinter dhcpcd[328]: wlan0: adding address fe80::22a7:6491:fe81:ce74
Nov 12 15:16:22 JkanePrinter dhcpcd[328]: wlan0: rebinding lease of 10.132.136.213
Nov 12 15:16:22 JkanePrinter dhcpcd[328]: wlan0: probing address 10.132.136.213/18
Nov 12 15:16:23 JkanePrinter dhcpcd[328]: wlan0: soliciting an IPv6 router
Nov 12 15:16:27 JkanePrinter dhcpcd[328]: wlan0: leased 10.132.136.213 for 600 seconds
Nov 12 15:16:27 JkanePrinter dhcpcd[328]: wlan0: adding route to 10.132.128.0/18
Nov 12 15:16:27 JkanePrinter dhcpcd[328]: wlan0: adding default route via 10.132.128.1
Nov 12 15:16:36 JkanePrinter dhcpcd[328]: wlan0: no IPv6 Routers available
Nov 12 15:16:52 JkanePrinter dhcpcd[328]: wlan0: carrier lost
Nov 12 15:16:52 JkanePrinter dhcpcd[328]: wlan0: deleting address fe80::22a7:6491:fe81:ce74
Nov 12 15:16:52 JkanePrinter dhcpcd[328]: wlan0: deleting route to 10.132.128.0/18
Nov 12 15:16:52 JkanePrinter dhcpcd[328]: wlan0: deleting default route via 10.132.128.1
Nov 12 15:17:00 JkanePrinter dhcpcd[328]: wlan0: carrier acquired
Nov 12 15:17:00 JkanePrinter dhcpcd[328]: wlan0: IAID eb:f9:86:10
Nov 12 15:17:00 JkanePrinter dhcpcd[328]: wlan0: adding address fe80::22a7:6491:fe81:ce74
Nov 12 15:17:00 JkanePrinter dhcpcd[328]: wlan0: soliciting an IPv6 router
Nov 12 15:17:00 JkanePrinter dhcpcd[328]: wlan0: rebinding lease of 10.132.136.213
Nov 12 15:17:00 JkanePrinter dhcpcd[328]: wlan0: probing address 10.132.136.213/18
Nov 12 15:17:05 JkanePrinter dhcpcd[328]: wlan0: leased 10.132.136.213 for 562 seconds
Nov 12 15:17:05 JkanePrinter dhcpcd[328]: wlan0: adding route to 10.132.128.0/18
Nov 12 15:17:05 JkanePrinter dhcpcd[328]: wlan0: adding default route via 10.132.128.1
Nov 12 15:17:13 JkanePrinter dhcpcd[328]: wlan0: no IPv6 Routers available
Nov 12 15:21:37 JkanePrinter dhcpcd[328]: wlan0: carrier lost
Nov 12 15:21:37 JkanePrinter dhcpcd[328]: wlan0: deleting address fe80::22a7:6491:fe81:ce74
Nov 12 15:21:37 JkanePrinter dhcpcd[328]: wlan0: deleting route to 10.132.128.0/18
Nov 12 15:21:37 JkanePrinter dhcpcd[328]: wlan0: deleting default route via 10.132.128.1
Nov 12 15:21:37 JkanePrinter dhcpcd[328]: wlan0: carrier acquired
Nov 12 15:21:37 JkanePrinter dhcpcd[328]: wlan0: IAID eb:f9:86:10
Nov 12 15:21:37 JkanePrinter dhcpcd[328]: wlan0: adding address fe80::22a7:6491:fe81:ce74
Nov 12 15:21:37 JkanePrinter dhcpcd[328]: wlan0: soliciting an IPv6 router
Nov 12 15:21:38 JkanePrinter dhcpcd[328]: wlan0: rebinding lease of 10.132.136.213
Nov 12 15:21:38 JkanePrinter dhcpcd[328]: wlan0: probing address 10.132.136.213/18
Nov 12 15:21:43 JkanePrinter dhcpcd[328]: wlan0: leased 10.132.136.213 for 600 seconds
Nov 12 15:21:43 JkanePrinter dhcpcd[328]: wlan0: adding route to 10.132.128.0/18
Nov 12 15:21:43 JkanePrinter dhcpcd[328]: wlan0: adding default route via 10.132.128.1
Nov 12 15:21:50 JkanePrinter dhcpcd[328]: wlan0: no IPv6 Routers available
Nov 12 15:46:06 JkanePrinter systemd[1]: Starting dhcpcd on all interfaces...
Nov 12 15:46:06 JkanePrinter dhcpcd[309]: dev: loaded udev
Nov 12 15:46:06 JkanePrinter dhcpcd[309]: forked to background, child pid 380
Nov 12 15:46:06 JkanePrinter systemd[1]: Started dhcpcd on all interfaces.
Binary file /var/log/syslog matches
pi@JkanePrinter:~ $
Sorry if it's a lot to look through; I tried all three commands for the RPi you gave me
The RPi is at 10.132.128.114 netmask 255.255.192.0 gateway 10.134.128.1
The laptop is at 10.134.152.242 netmask 255.255.192.0 via 10.132.128.1
They are in different subnets. They do appear to share a DNS server however it is in another subnet. We don't know if the DHCP servers are configured to update the DNS servers.
RPi nameservers 128.196.11.234 128.196.11.233 DNS Suffix arizona.edu
laptop nameservers 128.196.11.234 128.196.11.235 DNS Suffix arizona.edu
On the laptop try nslookup RPiname and nslookup RPiname.arizona.edu
On the RPi try host laptopname and host laptopname.arizona.edu
(Note: don't add .local to the names)
Just for completeness, try looking up yourself (i.e. nslookup laptopname, host RPi name etc.
Are both the laptop and the RPi using the same wireless band (i.e. 2.4 or 5)? You didn't say what model RPi you have.
Sorry; it's a Raspberry Pi 3 B+
Commands on Laptop
C:\Users\jonth>nslookup JkanePrinter
Server: DNS4.Arizona.EDU
Address: 128.196.11.234
*** DNS4.Arizona.EDU can't find JkanePrinter: Non-existent domain
C:\Users\jonth>nslookup JkanePrinter.arizona.edu
Server: DNS4.Arizona.EDU
Address: 128.196.11.234
*** DNS4.Arizona.EDU can't find JkanePrinter.arizona.edu: Non-existent domain
C:\Users\jonth>nslookup JonsLaptop
Server: DNS4.Arizona.EDU
Address: 128.196.11.234
*** DNS4.Arizona.EDU can't find JonsLaptop: Non-existent domain
C:\Users\jonth>nslookup JonsLaptop.arizona.edu
Server: DNS4.Arizona.EDU
Address: 128.196.11.234
*** DNS4.Arizona.EDU can't find JonsLaptop.arizona.edu: Non-existent domain
Commands on RPi
pi@JkanePrinter:~ $ host JonsLaptop
Host JonsLaptop not found: 3(NXDOMAIN)
pi@JkanePrinter:~ $ host JonsLaptop.arizona.edu
Host JonsLaptop.arizona.edu not found: 3(NXDOMAIN)
pi@JkanePrinter:~ $ host JkanePrinter
Host JkanePrinter not found: 3(NXDOMAIN)
pi@JkanePrinter:~ $ host JkanePrinter.arizona.edu
Host JkanePrinter.arizona.edu not found: 3(NXDOMAIN)
And there we have it. Can't connect by name, can connect by IP address.
On wired Ethernet, I believe systems on the same segment exchange names and addresses as part of the protocol so connecting by name bypasses DNS and therefore works!
BTW, as long as your RPi is mostly on, it will keep the same IP address. It will only change addresses if it is off for longer than the DHCP lease time (or off when the lease expires?).
So after all this, it's the wifi I'm on that won't allow the hostname to connect. Well it looks like I will stick to the IP address then. Thanks for all of the help.
Seems like you said you are in college network and are being assigned internet addressable IP's. First off I would get myself a home router (Linksys, Asus, Netgear, etc). Separate your stuff from the college network adding a layer of security. This way the router will get the addressable IP and your internal machines will get non-addressable IP's (192.168.X.X, 10.X.X.X). Then you have control over what IP your internal machine has INSIDE your, assuming dorm room, then you can name them, assign an ip, etc. Depending on the router you can then assign static IPs to certain devices so you can get to them by IP or name, this can be further helped by using the C:\Windows\System32\drivers\etc\hosts file. (Kind of like a local DNS style address book for your internal network).
This is how most home networks are set up. College networks being what they are, are full of "curious" students roaming the network looking for things to get into. So you would benefit fromt he extra separation. Of course this is based on whether or not it is NOT against TOS for your particular college.
Start by following OutsourcedGuru's reply in this post:
Then on your main PC goto C:\Windows\System32\drivers\etc\hosts and assign names to IP's.
Just my $1.50 on the subject.
1 Like
I would definitely try that, but yes, I am not allowed a separate router in my room unfortunately.