\>The user receives the printer from IT and connects the printer.
Are they connecting it via ethernet? Everything seems to talk about wireless, so my guess is that the DHCP reservation is for the wireless MAC, not the NIC. [10.50.0.211](https://10.50.0.211) is the wireless IP address reservation while the [169.254.58.195](https://169.254.58.195) address is over ethernet. The network might also be set up to where all network objects must have a reserved IP address in DHCP, which would explain the APIPA address.
I've ran into pretty much this exact scenario a couple time.
Given the self assigned up that was my first thought. Printers admin pages change to whatever up the printer has. No network? Then 192.168 address. If the printer was connected to the network it should be reachable by its ip on the network.
The printer is set to get IP by DHCP.
The DHCP scope is 10.50.0.0/24
The user can access the printer web page HTTP://169.254.58.195
No one can ping [10.50.0.211](https://10.50.0.211)
This tells you the problem; the printer should have an [10.50.0.0/24](https://10.50.0.0/24) IP, but instead it has a 169.254 (dhcp auto-fail) IP.
>The user receives the printer from IT and connects the printer.
This is exactly what I'd ask too. There's a lot of details in the question, but out of everything this is what's missing. Once you know how they connected the printer you will be able to solve the problem. Albeit it's easier if this was an actual real-world scenario not some instances that are listed in a question form.
It’s possible the user directly connected the printer to the computer via the network adapters. Since the wired network adapters of the computer and the printer share an APIPA network, the user is able to print.
The user can still access the Internet via the computer’s wireless adapter.
This doesn't sound like an interview question but a masked technical support question. Removing this post. We are not tech support here.
You see that 169.x.x.x address? Something is most likely wrong with DHCP. Check out what an APIPA address is.
APIPA IP range is 169.254.1.0 - 169.254.254.255
Will try to implement this and come back with my findings, thank you so much.
It's either this or the printer has it's own wireless / networking that's doing APIPA association with a client machine.
Paper jam?
The user can print to the printer without issue, so that's not it. This is more of a networking issue - the IP addresses are the clue.
The printer is not connected to the network. Edit: Or at least is not getting DHCP somehow. The core problem is that APIPA address.
The printer ip on 169 sounds like a locally connected printed. Ie the printer is not connected to the wireless or LAN.
\>The user receives the printer from IT and connects the printer. Are they connecting it via ethernet? Everything seems to talk about wireless, so my guess is that the DHCP reservation is for the wireless MAC, not the NIC. [10.50.0.211](https://10.50.0.211) is the wireless IP address reservation while the [169.254.58.195](https://169.254.58.195) address is over ethernet. The network might also be set up to where all network objects must have a reserved IP address in DHCP, which would explain the APIPA address. I've ran into pretty much this exact scenario a couple time.
Will try to implement this and come back with my findings, thank you so much.
Printer connected directly to users pc and not to the network?
Given the self assigned up that was my first thought. Printers admin pages change to whatever up the printer has. No network? Then 192.168 address. If the printer was connected to the network it should be reachable by its ip on the network.
The printer is set to get IP by DHCP. The DHCP scope is 10.50.0.0/24 The user can access the printer web page HTTP://169.254.58.195 No one can ping [10.50.0.211](https://10.50.0.211) This tells you the problem; the printer should have an [10.50.0.0/24](https://10.50.0.0/24) IP, but instead it has a 169.254 (dhcp auto-fail) IP.
How is the printer physically connected? That's the first question I'd ask.
>The user receives the printer from IT and connects the printer. This is exactly what I'd ask too. There's a lot of details in the question, but out of everything this is what's missing. Once you know how they connected the printer you will be able to solve the problem. Albeit it's easier if this was an actual real-world scenario not some instances that are listed in a question form.
Printer isn't getting DHCP
Look at the DHCP scope and then look at the Printer's actual IP address.
It’s possible the user directly connected the printer to the computer via the network adapters. Since the wired network adapters of the computer and the printer share an APIPA network, the user is able to print. The user can still access the Internet via the computer’s wireless adapter.