network printer in 2003 domain??

Hewlett-packard Microsoft windows server...
February 22, 2010 at 19:52:54
Specs: Windows xo, 1222
I have a 2003 Domain, with xp clients. I have a printer with an ethernet port, but it does not have 2003 drivers!! I will use the printers ethernet port and connect it to a switch.

Can i install this printer on an xp client, share it, and then publish it in active directory for all others to be able to print?? or does this printer have to be installed on a 2003 server (but there are not 2003 drivers made for this printer)??

I want the printer to be available all the time, so if a the computer i install it on is off, will i need to install it on all other clients??


See More: network printer in 2003 domain??

Report •

#1
February 23, 2010 at 07:11:17
If it's a network printer, plug it in, configure it with a static IP (that's not in your DHCP scope) and then go around to the workstations and install it.

If the clients are XP you won't have any worries about driver issues. If your server sees the same kind of usage most servers see, it won't need a printer (ie: most don't use a server like a desktop right) so the lack of 2003 drivers is not an issue.

If you need instructions on how to install the printer to clients click on my name above in my reply and read my "how-to" guide on configuring a network printer.


Report •

#2
February 23, 2010 at 08:24:10
so plug the printer into the switch, and configure its ip address from the printers control panel?

why give printer an ip address out of the dhcp scope? (so computer not in the LAN can also use the printer?)
why choose local and not network printer?

Then go to each Win XP client and add the printer? i will then be prompted for drivers. how do i do this so i will not have to be prompted to install drivers on each xp client, each time the printer is added?

but what if i want to PUBLISH this printer in Active Directory on the 2003 domain controller? won't it then need to be installed on the 2003 ?


Report •

#3
February 23, 2010 at 09:42:06
so plug the printer into the switch, and configure its ip address from the printers control panel?

Correct.

why give printer an ip address out of the dhcp scope? (so computer not in the LAN can also use the printer?)

You'll want to use an IP that is outside the DCHP scope so as to avoid any chance of a duplicate IP error.

A DHCP scope is a set of contiguous IP's that will be given out by the DHCP server to clients requestiong TCP/IP settings. Most SOHO Routers (for example) come with a default scope of 192.168.0.100 to 192.168.0.199 already defined on them.

why choose local and not network printer?

Because it's the only way to install a new TCP/IP port that you can then put the IP address of the printer in. You can't communicate with the printer without knowing it's IP address.

Then go to each Win XP client and add the printer? i will then be prompted for drivers. how do i do this so i will not have to be prompted to install drivers on each xp client, each time the printer is added?

Yes, go to each client and install the printer. You have to add the drivers for the printer during the install process. Without drivers, there's no way to print ergo you need to install drivers. If it's a common printer like an HP Lasertjet 4050 then you won't need drivers on a disk (or accessible on a network share somewhere) as Windows itself has those drivers included in the OS.

but what if i want to PUBLISH this printer in Active Directory on the 2003 domain controller? won't it then need to be installed on the 2003 ?

I've never done that myself so I can't say for sure how it will work. In the smaller environments I've mostly worked in, it was just as easy to do them one at a time. In the larger environments I've worked in, they used a print server and you just went to the "printer" web page, clicked on the one you installed and the process was done automatically.

Read up on publishing a printer in AD, I'm sure there's plenty of info available on that topic.


Report •
Related Solutions


Ask Question