| 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 | ||
| 647065 | 2008-03-07 02:53:00 | Hi all, a client has a little WAN sorted via One Office. The domain controller is a SBS 2003 and we have 2 Terminal servers which take care of the satellite locations. There is a Xerox printer at the H/O and they use TCP/IP printing to print directly to the printer. Now every pc and server can ping the print, however only the workstations can print to it. The DC and both TS's send the print job where it just stay in the print queue. Now I cant think of anything that would stop the printing, only security and that is fine. Any idea's |
SolMiester (139) | ||
| 647066 | 2008-03-07 03:16:00 | Yes, printing from Terminal Services session to network printers . . . . :mad: :yuck: So the jobs are making it across the WAN to the printer, but just stalling in the queue? I'd check your TCP/IP port settings on the printer driver . Are they Raw or LPR? |
nofam (9009) | ||
| 647067 | 2008-03-08 23:40:00 | Hi nofam, the issue at the moment is printing from the servers period. They used to work just fine using lp queue, now that we are on a new switch (they moved from a managed telecom one office switch to unmanaged). I'm actually thinking i need to move both back to the old switch. The silly thing is that both can ping the printers. I have tried both RAW and LPR...guess the only thing is to go in out of hours and swap the cables back.... |
SolMiester (139) | ||
| 647068 | 2008-03-09 06:07:00 | That certainly is odd!:confused: The DC and both TS's send the print job where it just stay in the print queue So the print jobs from the servers are making it onto the print queue, and then just showing as failed to print? |
nofam (9009) | ||
| 647069 | 2008-03-13 01:14:00 | Being potentially "open" to the Internet, the printing system must have a security setting so that the whole world can't print on your printer. ;) Obviously, the remote jobs are entering the queue, so there has to be something you can set so they will print. | Graham L (2) | ||
| 647070 | 2008-03-13 01:38:00 | Being potentially "open" to the Internet, the printing system must have a security setting so that the whole world can't print on your printer . ;) Obviously, the remote jobs are entering the queue, so there has to be something you can set so they will print . Sol says in his first post that the WAN is over One Office; this is a 'private' network that is segregated from the internet by Telecom . . . . . but I think you're on the right track Graham; my gut feeling is that it's a security/permissions issue, whereby the servers can create jobs, and those jobs are making it onto the queue, but they don't have the right credentials to actually spool up and print . . . . . certainly is odd though!! :illogical |
nofam (9009) | ||
| 647071 | 2008-03-13 02:00:00 | This page referring to hanging (labmice.techtarget.com/Terminalsrvcs/troubleshooting.htm -) print jobs might help. "Internet printing terminal server" to Google gave that. | Graham L (2) | ||
| 647072 | 2008-03-13 02:57:00 | That link isn't working Graham - can you re-post? | nofam (9009) | ||
| 647073 | 2008-03-13 03:22:00 | labmice.techtarget.com | stu161204 (123) | ||
| 647074 | 2008-03-17 02:00:00 | Hi guys, thanks for your ideas. Let me just reaffirm for you, TCP/IP printing worked correctly before the servers were moved from a managed Telecom switch with own IP address, to an unmanaged switch without IP address. Since then, even though the servers and workstations can ping the printer, only the workstations can print. The server send the job to the printer, however they just remain in the queue. |
SolMiester (139) | ||
| 1 2 | |||||