[K12OSN] printing bandwidth on client
Petre Scheie
petre at maltzen.net
Mon Mar 13 15:23:55 UTC 2006
Not to play the 'money is no object' card, but you could pick up a little 5-port switch
for under $20, and plug the network drop, the terminal, and the printer into it. That
way, you don't have to have the terminal on for the printer to be available. I
generally prefer the 'whatever costs the least amount of cash' approach, but that isn't
always the top priority.
Petre
Burke Almquist wrote:
> Whoops, I missed the part about only having one network drop in the
> room. That's a good reason to hook it up to the thin client. The only
> thing about that is that the thin client would need to stay on in order
> for people to print to it.
>
> On Mar 11, 2006, at 4:02 PM, Jim McQuillan wrote:
>
>> I'd have no problem suggesting that you just connect the printer to
>> the thin client.
>>> Is there any difference in network traffic by having the printer
>>> standalone on the network as compared to being connected to the
>>> terminal? There is only one cable drop in that room, and would
>>> require a hub/switch to share the connection. That network segment is
>>> 100mbit, with a gigabit switch upstream aggregating the other traffic
>>> to the server.
>>>
>
> _______________________________________________
> K12OSN mailing list
> K12OSN at redhat.com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>
>
More information about the K12OSN
mailing list