Crossover cable followup

[cucuklotz]

HI, thanks for all the help.I used the crossover cable and was able to determine(reasobly sure) the problem was in network.Their IT guy came at my suggestion and he was able top repair.The machine now prints.However before this the customer would click print and printer would respond right away.now since it guy was here ,the customer now clicks to print and there is 30-45 second delay between print and click.Does anyone have any ideas what problem may be? Thjanks again,ANDY

[slimslob]

Re: Crossover cable followup

Sounds like he may have set it up to through a server.

[Tonerbomb]

Re: Crossover cable followup

Sounds like he may have set it up to through a server.

Sounds like that is what it is. It's not your question to answer, it's the IT guy's question to answer....... He won't have a clue.

[cucuklotz]

Re: Crossover cable followup

Hi I know he must have set up different this time(don't know the reason),but this is my best customer ,and if I can score a few brownie points,I think it wil go a long way,and that's why I even bothered to post again,besides for letting all know what resolved initial problem. THANKS ANDY

[rthonpm]

Re: Crossover cable followup

If it's set up through a server, that would explain the reason for the delay since there's an extra step. The server does work pretty well as a traffic cop as it were though, especially in larger offices where you may have multiple people using the same device: in this instance the server can do a better job of ordering and prioritizing the jobs coming in

[cucuklotz]

Re: Crossover cable followup

Hi Thank you all for informative insights.One more question from an ignorant bliss copier guy.Why would he now set up thru server when it has always been connected to network.Is he circumventing a problem (possible the original network probem)? As you can tell Im not well versed in thje way of network operations. Thanks for your patience.Andy

[blackcat4866]

Re: Crossover cable followup

There is point at which it becomes much easier to manage your print drivers when they are in a central location. Please imagine if you had a server installation in which you had 1000 users sharing a single iteration of the print driver, as opposed to 1000 locally installed print drivers.

Which do you think would be easier to do:
1) First installation of a new MFP that can print
2) Upgrading an existing print driver
3) Changing defaults, like color printing, or job accounting

Yes to all of them, by a factor of 1000.

There is a tipping point, somewhere around 20 workstations/employees, at which point it makes more sense to set up a server to manage print services (and lots of other things). =^..^=

[draph]

Re: Crossover cable followup

He set it up to run through a print server on the network server. IT guys do this because they are lazy assholes. My sales orders all call for new installations to be set up on all computers as a local printer. Everything runs smother and there are about 90% fewer problems. But doing so requires visiting every work station individually. Something fat arrogant IT people don't want to do.

[slimslob]

Re: Crossover cable followup

As rthonpm mentioned, the print server does act as a traffic cop. In the early days of HP JetDirect network print access devices which allowed connecting serial and parallel printers to a network, if print jobs from multiple computers hit the device at about the same time, it would lockup. Thus the use of print sharing through a server became the norm for large networks, the server handled the queuing of the print jobs so that there was no collision at the printer.

[rthonpm]

He set it up to run through a print server on the network server. IT guys do this because they are lazy assholes. My sales orders all call for new installations to be set up on all computers as a local printer. Everything runs smother and there are about 90% fewer problems. But doing so requires visiting every work station individually. Something fat arrogant IT people don't want to do.

Server printing is no lazier than setting up Active Directory or any other management system. When you have to support hundreds of users or computers, are you going to spend an entire day, or more, just to install a print driver or update a setting on every workstation, or are you going to make one change that propagates to all connected systems? On the MFP support side, you deal with each machine as a separate entity, for an IT admin the issue is how does that machine communicate with everything else in the network. That network is potentially huge, so why would I want to chase my tail and make my work harder?

Yes, there are arrogant IT people, but there are just as many techs with the idea burned in that IT is the enemy. I'm now doing both sides of the house with my own company so I've seen both sides of the issue.

--sent from my BlackBerry using the Android app