Wireless and Dorm Printing Overview

Transcription

1 Wireless and Dorm Printing Overview Updated: 2/1/2009 IMPORTANT: IPP printing is not supported In order for wireless and dorm users to successfully print to print queues installed on a GoPrint system, a successful network connection must be established. In complex network environments where specific buildings, floors, and even rooms in the same building may be configured on separate subnets, it is the responsibility of the client to make the required configuration changes (routers, switches) to allow network traffic to pass between the client and the GoPrint print server. This is to include the availability of the required ports ( ) used by GoPrint. Challenges with wireless users when sending print jobs to a print release station In environments where Machine Name is required at the Payment Station, computer name resolution may be an issue for dorm and wireless users due to networking and security constraints preventing DNS, hostname or NetBios resolution. With Windows clients, if NetBios ports cannot be enabled from the client to the GoPrint server machine names cannot be resolved. Regardless, when using SMB, port 445 must remain open in order to successfully connect to the print shares. A Best Practice policy must be determined to help users successfully identify their print jobs at the Payment Station. All home computers and laptops, by default, come with a generic machine name and default administrator account. The default machine is usually a mixture of letters and numbers, not user-friendly by any means. It s recommended when machine names are going to be used at the Payment Station, that users change their computer names to one they could uniquely and easily identify at the station A similar situation occurs with user names. The default OS comes with a default user account such as Administrator, Owner etc It s highly recommended users create a user account on their local system which distinctively identifies themselves from all other users. This must be a requirement due as an alternative to Machine names, due to possible name resolution issues that may occur. GS-4 Web Client Popup If resolving print jobs to machine names and user names becomes to big of a challenge the GS-4 Web Client Popup can help to resolve this issue. End-users can install the Web Client onto their machines and can be required to supply either a domain user account via LDAP or generate some type of login code and pass code which helps to uniquely identify and protect their print job when releasing to a print release station. Please refer to the web client configuration summary in this document as well as the Web Client configuration guide. 1

2 Printing Scenarios When setting up clients to print to printers (Print queues) on a Windows print server there are two methods you can use to connect: Windows SMB (Server Message Blocks) Printing and LPR (Line Printer Printing (used by Unix and Macintosh, Windows). When it comes to wireless and dorm users, the challenge arises because their computers are not part of the domain, nor in many cases, are they logging in using their domain account. This becomes a challenge when they cannot resolve their machine name on the network, which in return cannot resolve at a Payment Station. The results usually display the IP address of the machine. Secondly, if a Windows print server is used, printers are usually shared so they be searched and viewed so users can connect to them. This entire process uses the Microsoft SMB protocol which requires permissions in the form of a valid user account and password to connect to the share. This may not be possible with dorm and wireless users when they are not required to login to the network with their domain account or an account which has been granted permissions to the print share. The ADD Printer Wizard regards an local account with Rights to add printers. When dorm and wireless users create their unique user accounts they must add the new account to the local Administrators group or grant ADMIN privileges. Adding a printer using the Add Printer Wizard using the Windows SMB protocol requiring a valid user name and password to the share resource, in this case a shared printer. This method can be used if dorm and wireless users have access to their domain user accounts which have been granted access to the shared printer. If this is not possible, then to bypass the required SMB protocol authentication, the LPR print protocol must be implemented. 2

3 LPR Printing Protocol Requirements LPR printing can be a reliable solution when SMB printing cannot be used: LPR demon is not installed by default on Microsoft Windows servers. A valid Operating system installation CD is required to add the LPD (Print Services for UNIX) printing component using Add/Remove Programs. Print Services for UNIX must be installed on the print server and the service running. Once installed the service must be up and running 3

4 The specific print driver must be installed locally on the client machine compared to using SMB which is designed to automatically search the print server for updated print drivers and automatically download and install them on the client. If the print driver does not appear in the Windows print driver list then the user must manually obtain the driver, download it, and install it. If the driver is changed on the server, it may have to be updated on the client. Print Jobs are not locally spooled going directly to the spooler on the print server. Users will not be able to see the status of their print job in the local spooler in instances where the print job errors out or not paused. See below Troubleshooting LPR If the TCP/IP Print Server service for Unix is not installed on the Windows server or is not running, all LPR print jobs from the client machines will not be allowed to communicate to the daemon and will error out Example: client print queue 4

5 Enabling LPR Print ports from the End-User Important: Recommended method for wireless users 1. Do one of the following: In Windows XP, click Start > Printers and Faxes. In Windows Vista, click the Start button, then type printers in the "Start Search" section at the bottom, then press Enter. Click the Add a Printer link (Windows XP) or button (Windows Vista In Windows XP, the first screen that appears is a Welcome screen. Click Next. The next screen gives you a choice to add either a local or a network printer: In Windows XP, select Local printer attached to this computer and clear the Automatically detect and install my Plug and Play printer checkbox, and then click the Next button. In Windows Vista, select the Add a local printer option. Select the Create a new port: radio button, then select Standard TCP/IP Port from the list of options, then click the Next button. In Windows Vista, select TCP/IP Device in the Device type: list. Type servername: printserver.goprint.edu in the Printer Name or IP Address text box. Remove any initial text and type name of the printer you are setting up in the Port name text box (for example, librarybw). For Windows Vista, be sure the Query the printer and automatically select the driver to use checkbox is cleared (NOT selected). Click the Next button. In the next window, select the Custom radio button then click the Settings... button. In the Configure Standard TCP/IP Port Monitor windows, do the following: Select the LPR radio button. Type the name of the printer in the Queue name text box. (Ex.LibaryBW) Select (check) the checkbox next to LPR Byte Counting Enabled Click OK. Click the Next button and the Finish button to get back to the Add Printer Wizard. In the Install Printer Software (Windows XP) or Install the printer driver (Vista) window, find the driver that matches the type of printer to which you are connecting Note: Use the Postscript version of the driver if one exists. Note: If you do not see your driver listed under its manufacturer, try clicking the Windows Update button, which whill update the driver list after a few minutes. 5

6 If you still do not see the driver, try downloading it from the manufacturer's web site, unpacking it, and then clicking the Have Disk... button to tell Windows where to find the driver. After selecting a driver, click the Next button, then type a printer name. The default name is just the name of the driver, so you can highlight the default name then type whatever you want. As a best practice, use the same name that you used to set up the printer port- for example, LibraryBW. Next, select whether you want the printer to be the default printer, then click the Next button. In the Printer Sharing window, click the Next button, then select Yes to printer a test page, click the Next button, then click the Finish button LPR Example on client machine: LPR with LINUX and Macintosh Linux and Macintosh systems use the LPR printing system by default; no changes need to be made on a Linux server or Mac client. The newer Macintosh systems now come with built-in SMB support (see the Macintosh printing guide) while Linux servers can incorporate Samba support which simulates a SMB environment. Refer to the GS-4 Mac Printing document for instructions on adding LPR printing ports to a Windows LPD printing processor. 6

7 Dorm and Wireless Users The GopPrint quota system may be used with dorm and wireless (using LPR) users which require the use of Payment Stations. After a user sends a desired print job, If the job is sent using their local user account, then they are required to authenticate at the Payment Station (after first identifying their print job) by entering their quota ID and password, in most cases a domain account implemented using LDAP. Please refer to the Quota System Quick start guide for attention information. Important: the sign-in screen by default auto-fills the machine name or user name that was used to send the job. Users must manually delete this entry and enter their quota ID and password in its place. Additionally, due to name resolution differences advanced Initial View options such as Sign In and Restricted Access cannot be used because their functionality forces into the sign-in field the name of the user who sent the print job and cannot be changed. Configuring the web client for Anonymous s login The web client can help to resolve usernames at a PayStation and allow administrators the option of having end-users resolve their users name to a PayStation via LDAP driven accounts or by simply allowing users to login to anonymously and generate a secure pass code to help them identify their print jobs at the PayStation. In the following steps it is assumed you have a Web Client profile configured and the web client popup installed and running on a client machine. For additional information refer to the Web Client Configuration guide. Step1 - Enable Guest access Prompts Authentication: Guest Allow Payment at: PayStation 7

8 Step 2 Custom the Guest and Release User and Release Code Labels The web client buttons and fields can be customized to display branding messages which you feel meets the needs for your end users. Step 3 test and Training end-users When generated the Web Client login screen displays the custom login message you created. 8

9 Important: By default users will automatically be logged into the web client when a print job is sent from their workstation. Users will NOT be allowed to login unless a job is sent. 9

10 Once logged in, users follow the 3 step process to send their job to a PayStation: 10

11 Jobs are displayed at the PayStation with the Release code the user generated: In this example stan was the generated Release code: User clicks on their name and their jobs are displayed: 11

12 When an attempt is made to click on a print job the user is forced To enter their Pass Code If successful, the user is allowed to continue with the payment process 12