[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference decwet::nt-developers

Title:	MS Windows NT Developers
Notice:	See note 1222 for MS bug reporting info
Moderator:	TARKIN::LINEIBER

Created:	Mon Nov 11 1991
Last Modified:	Tue Jun 03 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	3247
Total number of notes:	15633

3233.0. "LN17S printer - TCP/IP printing problem" by ZPOVC::SATISHKUMAR () Mon May 05 1997 21:18

Hello
	I have a problem setting up digital LN17S printer over the
	network.  
	
	I have installed the Digital LN17 printer in the LAN. since
	I want to use the printer over the LAN, i've enabled the BNC
	port and given a valid IP address (using arp -s from the 
	windows NT server).  The IP address is confirmed when I test 
	print the configuration sheet.

	On the Windows NT server, I've created the printer, by adding
	Digital Network Port - Digital RapidPrint Server (via TCP/IP)
	with Telnet Port Number 2051 (in options).  I'm able to ping 
	and telnet to the printer (ip address).  The NT server & the 
	printer are on the same subnet.

	When I print from the NT server, and observe in Print Manager,
	the job status is "Connecting" for a long while and then 
	comes out with an error "The data area passed to a system call
	is too small". 

	I've shared the printer.  so, i connect to this printer from
	WINDOWS'95 client and print.  the job is spooled to the print
	server, and is cleared from client.  But at the NT server its
	the same state "connecting...".

	I've checked the registry.  The spool directory is fine.

	Can someboxy throw light on this ? 

	thanx in advance.
regds
Satish

T.R Title User Personal
Name Date Lines

3233.1 HUMANE::POSTSCRIPT_PRINTING NPSS::GLASER Steve Glaser DTN 226-7212 LKG1-2/W6 (G17) Mon May 05 1997 22:35 16

T.R	Title	User	Personal Name	Date	Lines
3233.1	HUMANE::POSTSCRIPT_PRINTING	NPSS::GLASER	Steve Glaser DTN 226-7212 LKG1-2/W6 (G17)	`Mon May 05 1997 22:35`	16
	See humane::postscript_printing note 5965 for a non-answer. Summary: It's a long running problem that essentially makes our network printers unusable from NT. It's an interaction between broken Microsoft code in the spooler and the Digital Libraries to support our printers. We had worked around the problem somewhat by using a LONG timeout but Microsoft insisted that we change to a shorter timeout so that the problem occurs more frequently :-). The problem has existed for at least 2 years without resolution. It's getting worse internal to digital due to the increased usage of NT. Above note also implies that Windows 95 may have similar problems. Steveg

    See humane::postscript_printing note 5965 for a non-answer.
    
    Summary: It's a long running problem that essentially makes our network
    printers unusable from NT. It's an interaction between broken Microsoft
    code in the spooler and the Digital Libraries to support our printers.
    
    We had worked around the problem somewhat by using a LONG timeout but
    Microsoft insisted that we change to a shorter timeout so that the
    problem occurs more frequently :-).
    
    The problem has existed for at least 2 years without resolution. It's
    getting worse internal to digital due to the increased usage of NT.
    
    Above note also implies that Windows 95 may have similar problems.
    
    Steveg