I do not, call the hotline and have engineering work it or decline it with a reason for it.
Downgraded I should have said I guess about the firmware. I will try working with these tips you have given me and reply after I finish. Thanks!
Servers don't matter, Domains do, and VersaLink can't be altbooted. If it sees some PC's and not others, then something is different, and a Fiery or printer is close to never registered on a domain, so it makes sense those can be seen while PC's can't, also, subnetting can do it.
In the lab, we have about 200 devices, the test equipment shows up (Macs, PC's and Fiery/Freeflow rips) but none of our work laptops do, because they are on the Xerox domain, and the printers are not, all they see at the top level is WORKGROUP.
If it worked before and doesn't now, and you wiped the device back to general release firmware and it didn't make it work again, then the change is on the LAN side. Switch from STATIC to DHCP to see if it will register into their DNS (Router or domain controller), if that works, you have the answer, they need to register the device in DNS
The Fiery is external. The office is not in a server environment. There is a mix of Windows 7 and Windows 10 machines out there. The firmware was on the latest release and I even tried alt-booting it as far back as the date of manufacture of the motherboard thinking that perhaps there was a firmware update that broke the function. (In the past the feature worked fine but then it quit at some point. I have a customer that is trying to use the feature but is having the same issue. However, I was at an account today (a county account) and the feature worked fine there.)
Is it a bustled or Win7 based Fiery and all the other PC's are Win10? Because of that is the case, it probably needs a firmware update, or it is only able to see things in a Workgroup because the unfound devices are on a Domain and the printer isn't.