Installing the printer driver by searching for the printer using the Add Printer Wizard. Installing the driver requires the administrator privilege. It may take some time to finish searching the entire list of printers. Click [Have Disk Click [Browse The [Printers] list appears. Follow the instructions on the windows that follow.
Click [Finish]. This completes the printer driver installation. Don't have an account?
- How to Set Up Your Network for PCs and Macs.
- Access a Shared Printer on Windows.
- LPR/LPD printing with Linux, Mac or Windows CE clients!
- archivos 7z abrir en mac.
Sign up. By BlueKnight. Follow Tech Sign In Page. Best of Luck, Marc. October 17, AM.
Something went wrong on our end. Please try again later. October 19, PM.
Site Search Navigation
Hello BlueKnight, I have gotten it to work but need to know more about what you really want to do. Just a place to start. Ed Martin. October 26, PM. Hopefully this will help others having the same problem. October 31, PM. If anyone else finds Blueknights fix helpful, be sure to give it a thumbs up. The settings in this file take precedence over the settings in the global configuration file. The format of the global and user-specific printer configuration file is the same:.
- Subscribe to RSS.
- For previous versions of MAC OS or if the previous solution does not work :?
- the sims 2 ultimate collection mac download.
- convert dts to ac3 mkv mac?
- Connecting to network printers using LPR on Windows 7.
- What can we do for you??
This is the name that users can specify when printing from a UNIX or Linux platform application server. It is also the name that displays in the Print dialog when users print from a Microsoft Windows application server. The printer driver name must be enclosed in double quotes.
The name of the printer driver must match the name of the printer driver installed on the Windows application server exactly. This information is optional, but if it is missing, PostScript is used by default. This information is used to determine whether SGD converts the print job from the format used by the application server to the format needed by the client printer. The first printer listed in the [UNIX] section is the client's default printer.
When SGD is first installed, the default. This means that a printer is available in the Windows application, even if there is no printer connected to the client device. When the user prints from a Microsoft Windows application server to a UNIX platform client device, the following printers are available:.
The user's default printer is drafts , which in this example has been defined as a PCL printer. This section describes the print job management features of SGD and includes the following topics:. SGD Administrators control printing services with the tarantella print command.
This command enables you to do the following:. List spooled print jobs and identify the SGD users they belong to. You can use this to check that print jobs from the application server printing system have reached the SGD print queue. The syntax for the tarantella print command is as follows:. The following table shows the available subcommands for tarantella print. This is useful if you have to manage a high volume of printing. To specify the number of hours that print jobs remain on the server, use the following command:. To return SGD to its default behavior, so that print jobs remain on the server indefinitely, use the following command:.
The Printing area shows the number of jobs currently in the print queue and the controls for managing print jobs. When documents are printing, the workspace tells a user how many print jobs they have in the queue. Users can click Cancel All to delete all pending print jobs. Users can also click Pause to temporarily stop printing. When printing is paused, any print jobs that are pending are held in a queue until the user either cancels them or resumes printing.
The printer icon changes to show you when printing is paused. Click Resume to start printing again. For the tablet workspace, the Pause and Resume options are not available in the Printing area. To manage print jobs individually, click List All Jobs. The workspace displays a list of all the print jobs the user has in the queue, along with information about the job, for example the number of copies and the selected printer.
If you pause printing, click the Resume button to print just that one print job. To cancel a print job, click the Cancel button. When printing from a Microsoft Windows application server, or a UNIX or Linux platform application server, users can choose which printer they print to.
If the user does not select a printer, the output goes to their default printer. For all other application servers, the output always goes to the client device's default printer. Users can see which printer is their default printer by pointing with the mouse at the printer icon on their workspace. A popup displays the name of the default printer. If a user wants to change their default printer, they must log out of SGD, change the default printer and then log in to again.
LPR/LPD printing with Linux, Mac or Windows CE clients | ThinPrint Doc.
Use the following client device troubleshooting steps to diagnose printing problems in SGD. Check the Printing area on the workspace. If so, this means that SGD does not support printing for this client device or printer type, or that there was an error creating client printers. Make sure that the user has not paused printing. Check the Printer Paused icon is not displayed.
Use the tarantella webtopsession list command to see whether the user has paused printing. Make sure that the printer is correctly configured, for example by printing a web page to the printer from a web browser on the client device. Depending on the application server, some print jobs can only go to the client device's default printer.
Check that the supported viewer, or the user's preferred viewer, is installed on the client and that the application is executable. This access is required by several of the Windows application programming interfaces APIs for printing. Use the following application server troubleshooting steps to diagnose printing problems in SGD. Before users can print, you might need to enable printing services on your application server. On Microsoft Windows application servers, printer mapping must be enabled.
Printer mapping is configurable globally, or as a group policy. By default, printer mapping is enabled. Before users can print, you might need to configure a SGD printer on your application server. See the following:. If the user is trying to print from a Microsoft Windows application server, accessed using Windows Remote Desktop Services, then the user's printers are configured automatically.
Connect To Network Printers - Mac OS X
If not, check the System Event log on the application server for the following errors:. Event ID: Description: Driver drivername required for printer printertype is unknown. Contact the administrator to install the driver before you log in again. Event ID: Description: The printer could not be installed. These errors indicate that the printer driver for the client printer might not be supported by the application server.
Either install the printer driver on the application server, or see Printer Driver Mapping for details of how to support other printer drivers, including using wildcards to support a wide range of printer driver names. If this does not resolve the problem, see Microsoft Knowledge Base article for more details.
The application must print to the printer queue you have configured. On UNIX or Linux platform application servers, the application must print using the replacement lp or lpr scripts installed by prtinstall. If more than one user is simultaneously logged in to the same application server with the same user name, SGD might be unable to distinguish which user owns the print jobs.
SGD discards the print jobs, logging that it has done so. To fix this problem, run the prtinstall. Use the tarantella print command to check that print jobs from the application server printing system are reaching the SGD print queue. You can avoid this problem by editing the file hostnamemap. This file enables you to map host names to DNS names. The file contains instructions on how to create the mappings. In the Administration Console, check that the name of the driver matches the name configured in the Postscript Printer Driver field on the Global Settings , Printing tab, or the Printing tab for the user profile or parent object.
The System Event log on the application server shows an error if the names do not match. Use the tarantella print status command to check whether printing is paused or disabled for the array. If necessary, enable printing, using tarantella print start or tarantella print resume. In the Administration Console, check the Global Settings , Printing tab, or the Printing tab for the user profile or parent object. See whether users can access all their client printers, just their default client printer, or no client printers. If the array has changed you might have to reconfigure printing, so that print jobs are sent to the correct printer.
Try upgrading to the latest version of Ghostscript. If the checklists above do not solve your SGD printing problem, try the following troubleshooting steps. These steps enable you to track the progress of a print job from the application server to the SGD server to the client device. Configure an X or character application to run on the SGD server. Display a terminal window, for example xterm , and start the application from your SGD workspace.
Did the first test page print? The problem is related to the movement of print jobs from the application server to the SGD server. Did the second test page print? Then try printing again. Did neither of the test pages print? On some systems, you can use lpstat -t. The problem is related to the movement of print jobs from the SGD server to the client device.
Go to Step 7. Run the prtinstall. Using an application object configured to display a terminal window on the UNIX or Linux system application server, try printing a small text file to the SGD printer. Does the command return an error message? You might need to run the prtinstall. Does the command return a print job ID? Go to Step 4. Is the print job present in the spool directory? There might be a network problem between the application server and SGD server. Go to Step 6.
Is the print job missing from the spool directory? Check that the lpd daemon is running and listening. For example, use the following commands:. Check the print queue on the application server. Consult your system documentation if you need help on how to do this. Is the print job leaving the application server? Check that you can ping and telnet to the SGD server from the application server. If this works, the printer driver on the application server might not be installed or configured correctly. Is the print job present on the SGD server?
Check that you are using fully qualified domain names in the application object, and that name resolution is working correctly. Examine the printing log files for more information. Is the print job missing from the SGD server?