QTP Home page | ||||
Laptop and desktop network printer configurationNOTE Before connecting to the Slater Lab printers you should first verify that the network connection and your password work coprrectly. This is most easily done by connecting to your home disk on the QTP server by following these instructions.
Defining QTP printers on Windows 2000 and Windows XP systemsNOTE At this time it seems that it is necessary to install \\buddy\lj first. Then you can install \\crunch\lj and it will also install the correct driver that has duplex-option enabled.
To define the HP LaserJet printers on a Windows machine,
click on the Install new printer icon in the
Start - Settings - Printer folder. Then select
network printer
and specify one of in the Name field
Because your computer may have been connected to crunch
before the move to the new network, it may remember an
old IP address that no longer works. To force it to
connect to the correct server, type in the IP address
form
Browsing for the printer in the network neighborhood no longer works for an as yet unknown reason. It is only necessary to define lj since it will print on either lj1 or lj2 whihcver is not busy. You can make the printer your default printer or not. You can change the choice later. Windows will automatically download the correct driver for your system from crunch. The supported operating systems are Windws 2000, and XP, both the 32-bit. Winodws 98 and ME are not supported.
If the above does not work...
Then you must resort to the procedure outlined below for Windows Vista, which also does not understand the printer model description given by the SAMBA server. if the steps below do not work, that they will work after you install the driver. The driver can be downloaded from Hewlett-Packard at ftp://ftp.hp.com/pub/softlib/software10/COL23978/lj-62396-2/HP_CLJ_CP3525_PS_32bit_HPDIU.exe or from here The PCL driver does work even though the printer system requires PostScript.
Defining QTP printers on Windows Vista and Windows 7 systemsWindows Vista and Windows 7 will not automatically connect to a SAMBA server, which presents itself as an older version Windows server. One must force it to connect to the printer. Windows 7 already has the correct driver installed. So you can proceed directly to the next step. For Windows Vista, and if Windows 2000 and Windows XP "Printer Installation" wizard fails, you need to download and install the driver first. The driver can be downloaded from Hewlett-Packard at ftp://ftp.hp.com/pub/softlib/software10/COL23978/lj-62396-2/HP_CLJ_CP3525_PS_32bit_HPDIU.exe or from here (The PCL driver does work even though the printer system requires PostScript.)
You can also install the local printer first and then connect to the printer using the following script launched with administrative rights: net use LPT1 /delete net use LPT1 \\crunch.qtp.ufl.edu\lj /persistent:yesYou must click on "Run as Administrator" to execute the commands. This will install a local printer on port LPT1 connected over the network to the SAMBA server. Now the printer will use its own driver, which you installed or was already present, instead of the driver supplied by SAMBA. Defining QTP printers on MacOS X 10.3 and 10.4You must activate the "Samba Server" capability in MacOS. The info on starting the Samba Server is on this web page http://www.macdevcenter.com/pub/a/mac/2003/03/18/samba.html Basically, you have to do the following: Printers shared by Windows PCs that are on a different subnet than your Mac will not be listed. You can manually add printers shared by a Windows computer on another subnet using the steps below. Be sure to use the computer's IP address---not the computer's workgroup and name when adding the printer manually. How to manually add a Windows shared printer
(These instructions are taken from http://docs.info.apple.com/article.html?artnum=301397) Defining QTP printers on MacOS X 10.5 and higher systemsYou must activate the "Samba Server" capability in MacOS. The info on starting the Samba Server is on this web page http://www.macdevcenter.com/pub/a/mac/2003/03/18/samba.html Basically, you have to do the following:
It is only necessary to define lj since it will print on either lj1 or lj2 whihcver is not busy. Sometimes, you may also have to start Windows Sharing under System Preferences -> Sharing. More information, especially if the above steps dor not work, can be found at this site Defining QTP printers on Linux and UNIX systemsNOTE On Ubuntu the installation has a GUI to help you. From laptops running Linux it is recommended to install the Samba software. Do not configure the SAMBA server, only use the smbclient program, as follows.
To print a file, for example plaintext.txt, to the
printer
laptopuser@laptop% cat plaintext.txt | \ smbclient //crunch/lj" -U qtpuser \ -c "print -"You will be prompted for your SAMBA password. Notice that Linux will translate the / into \ for convenience, since \ means something special in Unix shells. You will see output like added interface ip=192.168.8.64 bcast=192.168.8.255 nmask=255.255.255.0 Password: Domain=[QTPDOMAIN] OS=[Unix] Server=[Samba 2.2.3a] putting file - as stdin-18684 (10.1 kb/s) (average 10.1 kb/s) laptopuser@laptop ~% The file will be sent to the samba server using the QTP username qtpuser as authetication and the SAMBA printer will convert the text file into proper PostScript for the printer lj and print the file. It will also record the page charges to the correct QTP account for the QTP username qtpuser even if the username does not match the username laptopuser on the laptop. All security advisories state that it is a bad idea to configure a printer daemon on a laptop. It may make it easier to print from any window, but it also opens the LPR port on your system. If you configure the lp system to print to a SAMBA server with your QTP username and password, then anyone on the network can send files to your LPR port and have their documents print at your expense. It may be inconvenient to have to type the smbclient password every time you send a file. You can create a script, only executable and readable by you that uses the password argument of the smbclient command to avoid this.
It would be a simple task for any skilled programmer to
modify the smbclient program to take your password
interactively and listen to a named pipe $HOME/lj
to which only laptopuser has write permission. Then
a simple laptopuser@laptop ~% cat postscrip.ps > $HOME/lj laptopuser@laptop ~% would print using your credentials as long as you are longged in. This functionality is very similar to that in Windows 2000 and Windows XP provided by network printers established in a login session. You can download the HP CP 3525dn PPD file and provide it to the Linux CUPS system to define the printer in an alternative way. |
||||
Have
a Question? Contact us. Last Updated 9/14/09 |