Network printers in an SBS Small Business Server 2003 R2 environment - RJ45 or USB connections ?
We have 2 laserjet printers within 6' of the new SBS 2003 R2 server. They are brother HL2070N printers... (network capable). So the question is, best practices, would you connect the printers to the server with USB cables or put them on the network with RJ45s? The desktops will deal with them via the server either way (taht's what we want, right?) So is there a rationale for using USB or putting them on the network directlly / have them get an IP address?
thanks!
thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
netadmin - you mention security... you as admin have more control over a usb pritner, right? a network printer a user can connect to directly (rather than through the server, which is how you'd do it?) and print at off hours, etc.?
Right guys? You would still share the network printer from the server? Or just have the PCs talk directly to the printer?
Right guys? You would still share the network printer from the server? Or just have the PCs talk directly to the printer?
Yes, I'd still connect the printer locally to the server by creating a TCP/IP port on the server, then share the printer from the server to all clients. This allows you to set printing defaults and preferences on the server, then all the clients have the same defaults. ie, easier to administer.
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/print_add_tcpip_port.mspx?mfr=true
But yes users *could* connect to the printer directly using a local TCP/IP port (bypassing server). However, most users i don't think know how to connect to a TCP/IP printer in that manner. In addition, a standard windows 'user' cannot install local printers, they would have to be 'power user' or have admin rights on there computer. Even still, if they were a power user and had power user rights, I wouldn't be too worried about it from a security stand point. My point about security was to keep users physically away from the server.
Hope this helps
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/print_add_tcpip_port.mspx?mfr=true
But yes users *could* connect to the printer directly using a local TCP/IP port (bypassing server). However, most users i don't think know how to connect to a TCP/IP printer in that manner. In addition, a standard windows 'user' cannot install local printers, they would have to be 'power user' or have admin rights on there computer. Even still, if they were a power user and had power user rights, I wouldn't be too worried about it from a security stand point. My point about security was to keep users physically away from the server.
Hope this helps
I agree with NetAdmin2436. On a simple network, I'd use direct TCP/IP connections. If you like security, most networked printers let you nominate a list of IP addresses that can use the printer. Any other address is rejected.
However, a TCP/IP connection from the server gives you more control. It also makes it easier to deploy the printer through a large workgroup. At the simplest level, users can simply install the driver from the server. You can also set up scripts to propagate the driver to the users automatically. Ditto for any driver updates or other changes. And you can set the printer to only accept jobs from the server's IP address.
However, a TCP/IP connection from the server gives you more control. It also makes it easier to deploy the printer through a large workgroup. At the simplest level, users can simply install the driver from the server. You can also set up scripts to propagate the driver to the users automatically. Ditto for any driver updates or other changes. And you can set the printer to only accept jobs from the server's IP address.
ASKER
thanks again guys!
ASKER
Now try this question:
https://www.experts-exchange.com/questions/22733310/Network-printers-do-you-just-use-DHCP-or-static-reservation-IP-address.html