Does it matter if you have a lot of busy machines on the same subnet?

[undeterred]

Fixed IP Printers...

[bemildred]

1. Not unless they are busy on the net. nt

[undeterred]

2. Computer users are logged in to servers across a WAN

via terminal services. The print job (document image in pdf) must have to come across the WAN from NY to Chicago... would that count as busy?

[bemildred]

3. You need to explain the problem better.

There are all sorts of variations and all I keep thinking is "it depends".
Is it that you have a slow network or a stalled printer or what?

[undeterred]

4. Users are complaining that their print jobs aren't printing fast enough

but the jobs aren't stalled or anything. Anything that goes from my desktop to the network printers in the same office goes very fast. The printers are Canon fax/print/scan capable, very high end.

But many users are using a terminal server interface to get to servers in another office across the country. They large print jobs from there back to our office. The WAN between the New York office and the satellite offices is monitored by our admin, but I don't know anything about the traffic within the office.

I had to do an inventory of all the printer equipment recently and I got all the IP addresses while I was doing it just for reference. I noticed that they were all on the same subnet. I just wondered if that could be a reason for slow printing.

[bemildred]

5. There is a reason they are using terminal servers: the WAN is slow.

And that is why it takes a while for the print jobs to show up and get printed. If they want to fix it they need to pay for more WAN bandwidth.

If your local jobs are snappy then your local network is not overloaded and neither are your local printers.

QED.

[undeterred]

6. Thanks!