Installing a network printer under small business server SBS 2003
What is the proper way to install a network printer under SBS 2003 R2? I have several HP printers and plotters which have internal NICs and hard drives. Since they are attached direcly to the switch and not to any particular machine I think they would be considered "network printers" as described below but I can't figure out how to install them as such.
While going through 'Add a Printer' under the ToDo list and initially I have 2 options:
1. Add a printer attached to this computer (I know to install the printer using this option and adding a TCP/IP port and publishing in AD but maybe there is a better way).
2. A network printer.
If I select network printer (Option 2) now I have 3 options:
1. Directory (the printers do not yet appear in the directory since i haven't installed them yet)
2. Name
3. URL
What name would I use under option 2? Do i use the ip address of the printer or network name assigned by HP (like NPIF1A7DF)?
How would I install the printers using a URL under option 3?
While going through 'Add a Printer' under the ToDo list and initially I have 2 options:
1. Add a printer attached to this computer (I know to install the printer using this option and adding a TCP/IP port and publishing in AD but maybe there is a better way).
2. A network printer.
If I select network printer (Option 2) now I have 3 options:
1. Directory (the printers do not yet appear in the directory since i haven't installed them yet)
2. Name
3. URL
What name would I use under option 2? Do i use the ip address of the printer or network name assigned by HP (like NPIF1A7DF)?
How would I install the printers using a URL under option 3?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok, that's how I usually do it. It just seems like there should be a more elegant way to do it. Especially for a network printer that has it's own NIC and IP address and plugs directly into the switch rather than directly into a workstation or server like a parallel printer. In this case, windows server is not reallly acting as a print server since i could do the same thing from any workstation. I gues AD is the key.
Thx.
Thx.
It is still a little "rinky-dink" isn't it.
The difference between doing it this way on the server as opposed to the workstation, which does work, is it is published in Active directory. Rather than going through all that the workstation user just goes to start | run | search | printers on the network | find now | and double clicks on the printer.
With SBS they will automatically be added to the the users printer directory, and they don't even have to do that.
The difference between doing it this way on the server as opposed to the workstation, which does work, is it is published in Active directory. Rather than going through all that the workstation user just goes to start | run | search | printers on the network | find now | and double clicks on the printer.
With SBS they will automatically be added to the the users printer directory, and they don't even have to do that.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Jeff, are the "To Do List/Add a printer" and the "Server Management/Printers/Add a Printer" wizards different ?
Thanks, again ArkAdmin.
--Rob
--Rob
No those are the same. I was referring to not using "START > PRINTERS & FAXES > Add a printer". But truth be told... there's really no difference there either. However, you will note that the query listing for printers might show differently in "Server management > Printers" than "Start > Printers". (Server Mangement only shows printers that are published to Active Directory).
I had actually been thinking about something else when I posted that.
The fact is that the real answer to the question is NO, there is no better way... adding a TCP/IP port and publishing to AD is exactly the way to do it.
Jeff
TechSoEasy
I had actually been thinking about something else when I posted that.
The fact is that the real answer to the question is NO, there is no better way... adding a TCP/IP port and publishing to AD is exactly the way to do it.
Jeff
TechSoEasy
ASKER