u/Platebuster

The Latest firmware for this device (Released I think maybe back in May?) 05.51.OP16Q4 I think basically killed the wifi on this expensive printer. This printer worked in this location on the same wifi for 100s of prints no problem. I did a firmware update one day and came back to it only being able to finish one print in 30 min. The eventual work around was to run a ridculously long ethernet cable to it and it began working as intended again. I reached out to support, and of course they were less than helpful. The basic troubleshooting techinques and no help with firmware, how to revert, or anything.

Anyone else have this issue also?

I have a Vlan , we will call VLAN 3

VLAN 3 DHCP is two windows domain controllers with failover.

the DNS servers are umbrella forwarders that forward to the domain controllers for dns.

Gateway is defined on Cisco core switch as layer 3 interface with HSRP/VRRP or whatever it’s called and with ip helper commands defining the dhcp servers.

Symptom: Some devices only on VLAN 3 receive the correct gateway and the dhcp server that responded is one of my domain controllers, yet they either don’t receive the correct dns servers. I had one say the gateway of another vlan was its dns server. I have roughly 30-40 client vlans setup the same way and this is the only one.

I will say this particular vlan was setup as 192.168.1.x (I herrited)

At this same physical location, not all devices are having issues and I’m having no issues with the voice vlan on the same switches at the site.

There are no known changes that occurred other than rebuilding the umbrella forwarders do to us changing from VMware to hyper V (locally hosted).

ADDED:

DHCP is not handing out what’s defined in the scope for that subnet

Any ideas what could be causing this. I’m almost to the point of re-ip and different vlan or switch change out because I’m lost as to why it’s happening. I haven’t found evidence of a rouge dhcp server yet either.

SOLVED:

it ended up being a Grandstream ATA device. HT15 . Why idk but once I removed it and factory reset, that resolved it. It had been setup for a long time with no issues , so not sure what caused it to behave this way.