News Stay informed about the latest enterprise technology news and product updates.

Interesting Network Printer Shenanigans on Win10

I’ve got a Samsung ML-2850 monochrome laser printer on my network, and I’ve been chasing around various ways to interact with it lately. It seems that unless you’ve got access to a print server, and set up that print server to offer the network printer up to network users, you can’t access a network printer by name. You must instead access it using its IP address. Perforce, at the same time I also realized that it really makes sense to reserve an IP address for a networked-attached printer in DHCP to prevent the occasional automatic renumbering that sometimes occurs from rendering an old DHCP-assigned address obsolete and non-functional.

This required some futzing around with my Arris TG1672G boundary device, which combines cable modem, router, firewall, and WAP capabilities in a single package (in my area, Time-Warner requires such a device to access their fastest consumer-grade Internet service, rated at a putative 300 Mbps, but which I’ve seen running as fast as 353 Mbps lately). I had to create a DHCP reservation (what the device itself calls a “Reserved IP client”) using the device name along with its IP and MAC addresses, all of which I discovered easily using Nir Sofer’s excellent Fast Resolver utility.

After that, I was able to use either the “Add a printer using a TCP/IP address or hostname” or the “Add a local printer or network printer with manual settings” option in the Add printer dialog box to add the device using its now-static IP address. This dialog box is available either through the Settings (Devices –> Printers & Scanners) app or the Devices and Printers widget in Control Panel in Windows 10. Here’s what that drop-down menu looks like, from which I knew I needed to select, that being the static IP assigned to the Samsung printer.

The secret to successful setup is knowing the right IP address.

Though it’s not as easy as it could be with the network printer discovered automatically, it’s still workable enough. Perhaps these observations can make it work better for you.

Join the conversation


Send me notifications when other members comment.

Please create a username to comment.

Interesting post this and I'm glad you got it sorted out to your satisfaction. That said, I would have thought this is more of an "Arris TG1672G boundary device" issue than a Windows 10 issue. No?

Actually, for Windows 10 users the situation requiring IP address use to access network printers is uniform and universal. The Arris thing is really more of a sidenote to recognizing that you need to know the IP address for network-attached printers, and related to making that address static rather than dynamic. Thanks for your input and feedback, in any case!


Is that not the case for all versions of Windows? From my own experience you've almost always needed to know what the IP address of the printer is, or at least know how to find it and change it to the same address set as your router/switch/server/network device supplied IP address.
I suppose my point was is this a Windows 10 issue or something else.

OK, we're getting into recollection here. What I recollect is that prior to Windows 7, network printers would actually manifest NetBIOS names, and thus be discoverable in the native add printer interface. Either with the first release of 7 or perhaps starting with 7 SP1 this functionality dropped out of play. But as I said, we're getting into recollection here. If it needs researching, let me know and I'll go digging into TechNet and/or the Wayback Machine and find out what's what further back.

Thanks for pointing this out. No reason to misrepresent the facts, such as they may be.


Hi Ed,

Perhaps a bit of hair splitting on my part but thought it was worth discussing with you. Appreciate your initial post and replies.


No problem, Kraig! I enjoyed it, too. And with as little hair as I have, I have to split all the ones I can find...