Navigation
17 users online :: 17 Guests and 0 Registered
Most popular FAQs 
- HP Install Network Printer Wizard 4.0 - Configuring a ... (18163 views)
- How to configure Apache versions 1.3.x - 2.0.x ? ... (16513 views)
- Why in my workgroup user names in statistics and ... (16289 views)
- The application failed to initialize properly (0xc0000142). Click on ... (14252 views)
- Moving XP User Profile (12408 views)
- How to set proxy for my Windows XP computer ... (11575 views)
- HP Jetdirect Print Servers - Installing and Configuring a ... (10670 views)
- Windows Vista: SuperFetch and External Memory Devices (8814 views)
- Shutdown is very slow - Windows XP (8103 views)
- Troubleshooting Windows XP Shutdown Issues (7278 views)
Latest FAQs 
- What is HSLAB HTTP Monitor? (2010-03-09 07:39)
- Why in my workgroup user names in statistics and ... (2010-03-09 07:36)
- For maintenance of the exact accounting you should to ... (2010-03-09 07:32)
- Only Guest account when mapping to network drive (2010-03-09 07:30)
- How I Can Completely Remove Windows Vista/7 Printer Drivers ... (2010-03-03 21:04)
Sticky FAQs
See Also:
HSLAB Print Logger
ID #1063
Printing to a Network Device
| 1. | Verify basic network connectivity.
Check user rights, protocols, share names, and so on to determine if you can see the server. Copy files to a share on the print server using File Manager in Windows NT 3.x or Windows Explorer in later versions of Windows. If you cannot access the server, you may not be able to access the printer. |
||||
| 2. | Create a local printer and redirect the port to the network server.
Create a local printer and in the Ports section, create a new port. Click Local, and type the server and printer name for the printer (use the \\servername\printername syntax). Use this port for the local printer. This determines whether there is a problem with the copying of files from the server to the workstation that occurs when you use a Connect To Setup or click Network Printer in the Add Printer Wizard. |
||||
| 3. | Printing from an MS-DOS-based program.
Make sure that the NET USE command has been run to map the LPT port to the network share. If it has, delete it and re-map the port. If it then works, there may be an issue with ghosted connections. A command may need to be run in the login script to remap the port each time you log on. If it is still not printing, try typing "dir > LPT<x>" (without quotation marks) where <x> is the number of the port being mapped. If it still does not print, double-check the networking. NOTE: Printing from MS-DOS-based programs does not work if the printer is a Postscript Printer. |
||||
| 4. | If you are using LPR or printing to a JetDirect card using the TCP/IP protocol, try these items:
124735 (http://support.microsoft.com/kb/124735/EN-US/) How Windows NT LPD Server Implements LPR Control Characters
124734 (http://support.microsoft.com/kb/124734/EN-US/) Text of RFC1179 Standard for Windows NT TCP/IP Printing
|
||||
| 5. | Determine whether you can print locally.
If possible, try printing locally. This determines whether it is a network or computer-specific problem. Also see the "Program" and "Print Stack" sections of this article. |
Tags: -
Related entries:
- What is HSLAB Print Logger?
- What is HSLAB Sys Monitor?
- What is HSLAB Force Down?
- What is HSLAB Prefetch Manager?
- Software Licensing
- What is HSLAB Shutdown Folder?
- HSLAB Shutdown Folder does not shut down a computer or not shut down to a power-off state.
- About Performance Monitoring
- Locating Performance Bottlenecks
- For maintenance of the exact accounting you should to adjust some printer's parameters
- What is HSLAB Print Logger PE?
- Force Down does not shut down a computer or not shut down to a power-off state.
- Troubleshooting Windows XP Shutdown Issues
- Why windows takes so long to start up
- HP Jetdirect and Embedded Jetdirect Inside Print Servers - Creating a Standard TCP/IP Port in Microsoft Windows XP
Last update: 2007-02-13 02:39
Author: Oleg
Revision: 1.0
You cannot comment on this entry