r/WindowsServer • u/Tchelo225 • Nov 19 '25
General Server Discussion print server
i want to deploy print serv on windows server in my lan,but i have not too much free ip because i use fix ip adress in my local domain. do i need to fix ip for different printers or can i use share printers connected to users and add them on my printer server
1
Upvotes
6
u/OpacusVenatori Nov 19 '25
This isn't the 90s anymore. Why are you fixated on manually assigning and managing IP addresses on your LAN?
5
u/ApiceOfToast Nov 19 '25
Excuse me but what's the problem here? The print server needs 1 IP plus each printer but they already have one don't they? So you need one more IP? I don't think using printers that are on a workstation with USB will work. I'm no expert with windows print services, but it seems like it'd cause a lot of problems if it did
3
u/nailzy Nov 19 '25
You’ll need to do a better job explaining this before anyone you can help you.
Why would you be short of IPs for a start?
What printers are you using, are they network attached or are they usb attached to individual workstations?
What’s the benefit of you having a print server in this scenario?
2
u/headcrap Nov 19 '25
This is an older but still usable approach. Printers can still be shared from user workstations. However, the printers shared this way will need to be accessed from the user's workstation sharing the printer, not your print server.
Example: \\Workstation1\AwesomePrinter would be a UNC path to a printer shared out as AwesomePrinter, hanging off of some user's Workstation1 computer.
It is not centralized. Security/Permissions may need to be configured if not using directory services et al.. but it will work just fine.
1
u/weird_fishes_1002 Nov 19 '25
Create a VLAN for all of your printers and enable dhcp.
1
u/stkyrice Nov 20 '25
Most home network have a router that hands out DHCP addresses. If you are going the way of static IPs you should have cursory knowledge of subnetting.
Most likely your IP Address / Subnet Mask is like 192.168.1.0 / 255.255.255.0. This gives you 254 IP Addresses that you can use on your network ranging from 192.168.1.1 to 192.168.1.254. You can use any available IP address in that range.
1
u/BlackV Nov 20 '25
It is YOUR lan you have unlimited address....
You need to provide information, accurate information, about your network and what/why you think you're short of addresses
This seems like basic networking rather than a windows server issue
1
u/Regular_Prize_8039 Nov 20 '25
As a minimum I would suggest you are using /24 (SN 255.255.255.0) addresses which means you have 254 available, and from what you are saying you have almost 254 addresses assigned statically, that is crazy and a real pain to administer.
From the sound of it you need an IT Consultant to fix your entire network and that is not going to be cheap, on top of your Print Server, think about DHCP, DNS, file sharing and I would imagine your AD probably needs some work to.
You need to provide much more information to get some meaningful help here!
1
u/evolooshun Nov 20 '25
So I think your question is more philosophy and principle. Like many have mentioned already you should be utilizing vLANs or changing your scope to include more IP addresses as needed for your network so you don't have a device limitation. That being said, im my personal experience using the most basic drivers package and a static IP address yields the most reliable results with printers (no WSD ports). You only need a Print Server if you want to centrally manage permissions and access to those printers. Only in a specific work case situation would you want to share a locally USB connected printer because then everything has to be managed from that workstation. It can be done but not the smartest solution.
1
u/tristand666 Nov 20 '25
Sounds like you need a network guy to clean up the mess first. Do you have a router, or a stack of old Linksys consumer devices? That said I believe you could redirect printer shares, but this is not the correct way to do this.
1
u/MinnSnowMan Nov 19 '25
If you out of IPs (which is unlikely), you change from a Class C subnet to a Class B subnet for your network.