Forum Home
Press F1
Thread ID: 87867	2008-03-07 02:53:00	TCP/IP Printing conumdrum	SolMiester (139)	Press F1

Post ID	Timestamp	Content	User
647075	2008-03-18 03:10:00	The switch shouldn't (if I didn't know better, I'd say "can't ;) ) make any difference. A managed one merely has an address so that it can be managed though an Ethernet connection, rather than a serial line to a terminal. Its function as a switch does not use that address in any way. The switch is functioning correctly: the files go through it to the queue. There has to be a setting somewhere in the administration part of the printer software which is causing the problem. It's nothing to do with "TCP/IP" -- the jobs are getting into the queue. I wonder if the default condition causes "remote" jobs to be held until they are released for printing manually. This would be a logical security thing: you might not want confidential printouts to be lying around.	Graham L (2)
647076	2008-03-18 03:35:00	The switch shouldn't (if I didn't know better, I'd say "can't ;) ) make any difference. A managed one merely has an address so that it can be managed though an Ethernet connection, rather than a serial line to a terminal. Its function as a switch does not use that address in any way. The switch is functioning correctly: the files go through it to the queue. There has to be a setting somewhere in the administration part of the printer software which is causing the problem. It's nothing to do with "TCP/IP" -- the jobs are getting into the queue. I wonder if the default condition causes "remote" jobs to be held until they are released for printing manually. This would be a logical security thing: you might not want confidential printouts to be lying around. Hi Graham, all of the above has crossed my mind. I did however forget to add that the NIC in the printer failed after we moved onto the new switch and we had to get Xerox to install another one. The only thing I can think of is a setting on the new NIC, however the fact that workstations are printing to it the same way has me stumped.	SolMiester (139)
647077	2008-03-18 03:41:00	How do you administer the printer? The problem has to be in that software. The NIC has done its work too: the jobs are in the queue.	Graham L (2)
647078	2008-03-18 03:53:00	How do you administer the printer? The problem has to be in that software. The NIC has done its work too: the jobs are in the queue. Xerox docucentre 350, no management required really. No setting that I can think of have changed, used to work for the servers, now it doesnt! Workstations are still printing to the printer successfully using TCP/IP and RAW format.	SolMiester (139)
647079	2008-03-18 03:59:00	Just out of interest, have you tried changing the port to lpr?	nofam (9009)
647080	2008-03-18 04:08:00	Just out of interest, have you tried changing the port to lpr? Only the format queue to lp!	SolMiester (139)
647081	2008-03-18 05:39:00	have you got any queue management software running ie somthing that allows printing under certain conditions. The reason I ask is because the job is getting to the queue where it is being held. If this was a Novell network I would looking at pcounter or simular software.	beama (111)
1 2