Capture problem in Intranetware client

We capture printers on netware 4.11 server over a container login script from an Intranetware Client 4.11 using the following syntax:
If we endcap these capture over a user login script it makes problem under NT.
There are the sign:"LPT1 is not configured or not present"
If we endcap the capture over "Network properties Endcap" it works fine.
Any ideas??
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Try referencing the with Q=<queue name> s=<server name>
and not the NDS name.  This worked to solve a simular problem so
may work for you.
brauner071697Author Commented:
sorry, but it doesnt't work.
If I endcap in the login script I get the following error message:
Error returned from '#CAPTURE /endcap L=1' command: 3101
any ideas

Are you using Win95 or DOS workstations?

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Do you have print job configurations? Check this TID: 2931424
This problem may apply to NT also.
LOGINW31.EXE Not Capturing Print Job Config.  (Last modified: 09JAN1998)

     This document (2931424) is provided subject to the disclaimer at the end of this document.
         Forward this document to a colleague
         Submit comment about this document to its author


     A Print Job Configuration is created and made default for a user under their user's properties
     page in NetWare Administrator. Using the Novell intraNetWare Client for DOS/Windows
     version 2.20 , the user's login script is edited to include the line"#CAPTURE" which should read
     the Print Job Configuration and run the capture for the user. However, the following error is
     generated and appear in the login script results window:

          Error returned from '#CAPTURE ' command: 3101


     The problem is in the LOGINW31.EXE file dated 06-27-97 9:18a file size 5,512 bytes. With version
     2.20 of the client, the capture utility was internalized into the GUI login, and Print Job
     Configurations won't run.

     This problem has also been seen with LOGINW95.EXE from the 2.20 Windows 95 client.


     There is no solution at this time. Novell engineering is working towards a fix.

     A workaround is possible if the user's script maps their defaut drive (ie.
     F:=SERVER_NAME/SYS:\) BEFORE the capture statement runs and then the external command
     "#F:\PUBLIC\CAPTURE.EXE" is called in the login script. The external capture command will run
     the Print Job Configuration.

     SEARCH: DOS Windows 3.11 for Workgroups External Command 2.2 2.20 loginw95 print job
     capture.exe gui

                    Please select if this document solved your problem.

      Document Title:
                          LOGINW31.EXE Not Capturing Print Job Config.
      Document ID:
      Creation Date:
      Modified Date:
      Document Revision:
      Novell Product Class:
                          NetWare OS
                          Novell BorderManager
      Novell Product and Version:
                          NetWare 4.11
                          NetWare 4.11 Kayak
                          NetWare 3.12
                          NetWare 3.2
                          intraNetWare Client CD (August 97)


     The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this
     information. However, the information provided in this document is for your information only. Novell makes no
     explicit or implied claims to the validity of this information.

     Any trademarks referenced in this document are the property of their respective owners. Consult your product
     manuals for complete trademark information.
brauner071697Author Commented:
We are using Windows NT 4.0 with SP3 and the Intranetware Client for NT ver.4.11.

Sorry Jstegall,
but it doesn't work. I've tried it with your information but it is always the same.
LPT1: is an unknown device after #Capture /endcap L=1.
If we endcap it manually over NT it works.

any ideas?
I almost sure this will work - Remove the # before the capture, in this client capture is an internal command, not requiring capture.exe.

The option to endcapture is "EC" not "/endcap"
CAPTURE EC L=1 should do what you want, using the internal
client32 command.  For the external command you must use #.
brauner071697Author Commented:
To Avi
I have removed the # in front of capture and the capture work but in the endcap section of my login script I'll receive the following error:
"Error returned from '#CAPTURE /endcap L=1' command: 3101"
My endcap line was "CAPTURE /endcap L=1"
It looks like executing an external command.

To Jstegall
It is the same result, if I take EC or ENDCAP, both ending the capture but in NT I'll receive the message:
"LPT1: is an unknown device "

Any other Ideas?

Try using EC without the leading "/" and see if you get the message if You use EC ALL then re-capture the port you want.  If
you try it use capture sh to see if all ports are back to local.

Try putting your end capture command in a batch file and call
it from the login scriptwith:  
  #command /c <my end capture>.bat replace text between "<>"
with the name of your batch file.
If these suggestions you have gotten from us here you might want
to open an incident with Novell to resolve this.
brauner071697Author Commented:
sorry experts,
nothing of that what you said will working.
If I place the commands like jstegall said the LPT is set to local mode, with capture /sh it looks right, but if I print on LPT1 I got the message:
LPT1: is an unknown device

Now I've put the batch file into the startup folder and it worked. That is not so good but the only way it works.

silly question, but you are using the current 4.11A client for NT?
Do you have a local printer connected to the workstation where
you end capture? No printer on lpt1 will give you an error when
you try to print to it.  After you endcap have you looked at the
port in device manager to see its status?  What is it?

If you have the latest client and these suggestions still doesn't work, I would try using NAL, if you don't want to have to update all the remote users startup folder.
With nal you can force run any executable file, you can set it up
so it won't intrude on the users.
brauner071697Author Commented:
Yes, I have a local printer connected to LPT1. This is the reason why I would like to endcapture LPT1!!!
In the device manager the drivers for the parallel port are active.
Yes I have the latest client and the latest SP for NT.
brauner071697Author Commented:
To paulnic,
yes we using the client 4.11a
You can not capture the ports of the systems that have local printers.   You can use a if statement something like this:
if "%P_STATION" = "<station address>" goto localp
do your normal capture after doing this for all the stations with
local printers

do the commom stuff from here to the end of the script.

You can get the station address in monitor, or set an environment
variable to %P_STATION and check the variable when you need it.
or you can set an environment variable for all stations with local printers.
SET LOCALP=YES in the stations startup file.
then branch on LOCALP in the login script.
These are some of the workarrounds you can use.
If as you say, the batch files work, you can call the batch to end capture based on the localp variable.
Could you post the capture segment of the Login script here, AND
Could you post the capture /endcap segment as well?

Is this the Latest version of Client32?
Will you please give reasons why you reject answers?  I am confused, you said a batch execution of capture works, I showed
you how you could use that to solve you problem.  You rejected
the answer but didn't say why, so I am not sure of what you are
trying to do.  Since you know the users that have the local printers you have the address in NWadmin if they are logged on.
Did you try the batch from the personal login script by
EXIT "NAME OF BATCH FILE" have it in the workstation search path.

brauner071697Author Commented:
Hy Jstegall,
I 've rejected your answer, because nothing of your answer worked.
I've tried all the things you said.

If that didn't work you have an issue we are not aware of.
Will you post the login script you tried using my suggestions?
If you would rather, you can e-mail them to me at  I would like to see them as
jrhelgeson also asked.  If you do the capture based on if the
machine has a local printer, you will not need to use endcap.
When you send me what you tried tell what message you received
with that try.
brauner071697Author Commented:
Hy experts,
here are my capture line from the container login script and the endcapture line from my personal login script.

If I endcap using the following command:
         "CAPTURE /endcap L=1"

I get the following error message:
"Error returned from '#CAPTURE /endcap L=1' command: 3101"
You didn't show me the tries you made of my suggestions.  Why are
you using the external command when capture is internal to Client32?  You do not seem to be using print job configurations, this is an assumption since you didn't answer that question.
Did you try:
IF "%P_STATION" = "<what ever the station address is>" then goto local:
use the above for each local printer workstation, do not include
the < > but the " " are required.  After all the workstations are listed put the capture statement, after the capture statements put the lable local:.  I asked you to post that portion of your container login script or email it to me.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Novell Netware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.