Live data from Hacker News

Microsoft to kill off third-party printer drivers in Windows

theregister.com

31–40 of 135 posts

Re: Microsoft to kill off third-party printer drivers in Windows

#31

Earlier quoted context omitted.

ZeroConf actually works pretty well as long as everything is in the same range.

Is that on a Mac? Windows doesn't seem to support it.

It's called "Bonjour" on Windows and Mac. Windows doesn't have support out of the box, but you can get it. https://learn.adafruit.com/bonjour-zeroconf-networking-for-w...

Edit: until build 1703 in 2017. Huh!

Re: Microsoft to kill off third-party printer drivers in Windows

#32

Printing at home is so horrible. I have a printer connected to my Wifi router. It changes IP every time I reboot. When it changes IP, Windows can't find it. I can give the printer a static IP but how many people know to do this? Wifi has been around for more than 2 decades. Isn't that enough time to figure out a solution?

I can't speak to printers (much less yours specifically) but most home routers (or more generally servers that act as both DHCP and DNS servers) will create DNS records in a locally-administered zone for each DHCP client according to the request. This same zone is then given as the DNS suffix as a DHCP option to the same set of clients. I would think that your printer does something similar, so if you add the printer by hostname (which you can probably locate by looking at DHCP leases in your router's web-based admin panel) instead of IP it should always "just work".

Re: Microsoft to kill off third-party printer drivers in Windows

#33

Earlier quoted context omitted.

ZeroConf actually works pretty well as long as everything is in the same range.

Is that on a Mac? Windows doesn't seem to support it.

Did you change your router settings? It should all heal up with a simple broadcast packet.

It could be your router defaults to blocking broadcast packets related to wireless devices. (Either in or out)

Re: Microsoft to kill off third-party printer drivers in Windows

#34

Earlier quoted context omitted.

You missed the point. I wasn't asking for help on how to assign a static IP address. My point was that ordinary people shouldn't have to know what an IP address is, let alone what a static IP address is, in this day and age.

That's wishful thinking, imo. If you want to have a network, someone needs to know a bit of networking. Or you need someone you can call who does. Don't get mad at the printer for what your router is doing to its IP address. This day and age isn't as advanced as you'd like it to be, or you need a new router that does what you expect.

Thankfully people at Apple thought this can be easier. They came up with Bonjour... Bonjour is apparently also known as ZeroConf [1].

Microsoft is behind the times.

[1] https://en.wikipedia.org/wiki/Zero-configuration_networking

Re: Microsoft to kill off third-party printer drivers in Windows

#35

Earlier quoted context omitted.

You missed the point. I wasn't asking for help on how to assign a static IP address. My point was that ordinary people shouldn't have to know what an IP address is, let alone what a static IP address is, in this day and age.

That's wishful thinking, imo. If you want to have a network, someone needs to know a bit of networking. Or you need someone you can call who does. Don't get mad at the printer for what your router is doing to its IP address. This day and age isn't as advanced as you'd like it to be, or you need a new router that does what you expect.

Part of the commoditization process for consumer products is that they are made to be user friendly for non-experts. Most other networked devices have already done this. Nobody needs to know how to configure /var/lib/dhcpd/dhcpd.leases to use an iPad on the router that Xfinity provides.

Re: Microsoft to kill off third-party printer drivers in Windows

#36

Earlier quoted context omitted.

Did you turn off the HP "DIRECT" wifi AP that screams at the top of its lungs and hogs valuable wifi spectrum? I live in a fairly low density townhouse, and 3 of my neighbors' printers are visible..

It's not broadcasting that, so either I did turn it off (and then forgot), or it was off by default. That's funny though. Can you connect to them and print them a message asking them to turn it off?

Thats a good idea! I just printed a google search "how to disable wifi direct"

Re: Microsoft to kill off third-party printer drivers in Windows

#37
> Mopria is part of the Windows' teams justification for removing support. Founded in 2013 by Canon, HP, Samsung and Xerox, the Mopria Alliance's mission is to provide universal standards for printing and scanning. Epson, Lexmark, Adobe and Microsoft have also joined the gang since then.

What about Brother?

Re: Microsoft to kill off third-party printer drivers in Windows

#38

Printing at home is so horrible. I have a printer connected to my Wifi router. It changes IP every time I reboot. When it changes IP, Windows can't find it. I can give the printer a static IP but how many people know to do this? Wifi has been around for more than 2 decades. Isn't that enough time to figure out a solution?

Is it using a WSD port by any chance? I work at an IT provider and 99.9 percent of the time a printer issue is caused by this useless feature.

Re: Microsoft to kill off third-party printer drivers in Windows

#39
post #18

Earlier quoted context omitted.

It could be your router giving it a new IP address, but the printer itself hopefully has a static MAC address. Check your router settings for static IP assignment, they may be under a section called DHCP. Over there you could give it a static IP address for its current MAC address EDIT: this comment no longer makes sense after the parent comment was edited. It used to be explicitly asking for help and didn't mention…

It's actually sometimes sold as a "security" feature - short DHCP leases with no memory. Which is kinda silly, if the router hasn't needed to give the IP to another client, just remember it forever.

If people start using dynamic IPs as if they are static, when they really aren't, they're just setting themselves up for failure the next time the devices reboots or resets. It's better to either use static addressing if you want static addressing, or use DNS if you don't know what the IP is going to be.
Post reply on HN