PDA

View Full Version : Barcode printing limited by Network User



R. J. Porter
22-Oct-2005, 03:56 PM
Hello,
I have just noticed that a particular barcode application I use for printing
labels in our laboratory does not print readable barcodes unless I print
them. All other users can print to the Zebra printer just fine with the
exception of a readable barcode. The acutual print job looks fine with of
course some suibtle differences that make the barcode unreadable to our
scanners unless they are printed from my login. We are using Crystal
Reports 10, VDF 7 apps, and Azalea Code39 fonts. Our network uses a Windows
2003 Small Business Server as the Domain Controller and Print Server. The
VDF and Crystal apps run on Windows 2000 Terminal Server. BTW... I have
already granted Administrator rights to one of the users and tried to get
the barcode to work and it does not. I think it is something to do with how
I installed the Azalea barcode fonts or the print drivers for the Zebra. I
installed the Azalea through the Control Panel add/remove programs just as I
would any other application I wanted to be available for the entire server
user group. The printer is accessable to all users also and has even been
shared. I have verified the dll's are in the right place according to both
Azalea and the Crystal whitepaper.

Any help would be greatly appreciated. Thanks

Randy

Garret Mott
23-Oct-2005, 09:42 AM
Hi Randy -

Do all users have exactly the same Zebra Driver? I've had issues with
slightly different drivers producing different printing results (& barcodes
can be really finicky!).

HTH

Garret

"R. J. Porter" <rjporter@emilab.com> wrote in message
news:MsquNs01FHA.3012@dacmail.dataaccess.com...
> Hello,
> I have just noticed that a particular barcode application I use for
> printing
> labels in our laboratory does not print readable barcodes unless I print
> them. All other users can print to the Zebra printer just fine with the
> exception of a readable barcode. The acutual print job looks fine with of
> course some suibtle differences that make the barcode unreadable to our
> scanners unless they are printed from my login. We are using Crystal
> Reports 10, VDF 7 apps, and Azalea Code39 fonts. Our network uses a
> Windows
> 2003 Small Business Server as the Domain Controller and Print Server. The
> VDF and Crystal apps run on Windows 2000 Terminal Server. BTW... I have
> already granted Administrator rights to one of the users and tried to get
> the barcode to work and it does not. I think it is something to do with
> how
> I installed the Azalea barcode fonts or the print drivers for the Zebra.
> I
> installed the Azalea through the Control Panel add/remove programs just as
> I
> would any other application I wanted to be available for the entire server
> user group. The printer is accessable to all users also and has even been
> shared. I have verified the dll's are in the right place according to
> both
> Azalea and the Crystal whitepaper.
>
> Any help would be greatly appreciated. Thanks
>
> Randy
>
>

R. J. Porter
23-Oct-2005, 09:49 AM
Thanks Garret,
The printer is installed as a network printer on our Windows 2000 Terminal
Server. I am not really all that familiar with how this works, except I
have installed this printer the same way as our others. Of course barcode
fonts are a bit unusual that way.


"Garret Mott" <garret_atsign_automatesoftware_dot_com> wrote in message
news:9dNVAA%231FHA.2796@dacmail.dataaccess.com...
> Hi Randy -
>
> Do all users have exactly the same Zebra Driver? I've had issues with
> slightly different drivers producing different printing results (&
barcodes
> can be really finicky!).
>
> HTH
>
> Garret
>
> "R. J. Porter" <rjporter@emilab.com> wrote in message
> news:MsquNs01FHA.3012@dacmail.dataaccess.com...
> > Hello,
> > I have just noticed that a particular barcode application I use for
> > printing
> > labels in our laboratory does not print readable barcodes unless I print
> > them. All other users can print to the Zebra printer just fine with the
> > exception of a readable barcode. The acutual print job looks fine with
of
> > course some suibtle differences that make the barcode unreadable to our
> > scanners unless they are printed from my login. We are using Crystal
> > Reports 10, VDF 7 apps, and Azalea Code39 fonts. Our network uses a
> > Windows
> > 2003 Small Business Server as the Domain Controller and Print Server.
The
> > VDF and Crystal apps run on Windows 2000 Terminal Server. BTW... I have
> > already granted Administrator rights to one of the users and tried to
get
> > the barcode to work and it does not. I think it is something to do with
> > how
> > I installed the Azalea barcode fonts or the print drivers for the Zebra.
> > I
> > installed the Azalea through the Control Panel add/remove programs just
as
> > I
> > would any other application I wanted to be available for the entire
server
> > user group. The printer is accessable to all users also and has even
been
> > shared. I have verified the dll's are in the right place according to
> > both
> > Azalea and the Crystal whitepaper.
> >
> > Any help would be greatly appreciated. Thanks
> >
> > Randy
> >
> >
>
>

Garret Mott
23-Oct-2005, 12:12 PM
You bet.

Have you checked the printer driver versions on your machine vs. the others
that don't work? Is yours a different OS?

When you installed the printer - did you get the driver from the same cd (or
location) for all installations?

To check (XP - I think 2000 is similar):

Go to printers & right click on the Zebra, then
Choose Properties, then
Advanced tab

That'll show the driver.

You might also check Zebra's web site for updated drivers - as they do
update 'em fairly regularly.

Best of luck!

Garret




"R. J. Porter" <rjporter@emilab.com> wrote in message
news:eeLn4D%231FHA.4600@dacmail.dataaccess.com...
> Thanks Garret,
> The printer is installed as a network printer on our Windows 2000 Terminal
> Server. I am not really all that familiar with how this works, except I
> have installed this printer the same way as our others. Of course barcode
> fonts are a bit unusual that way.
>
>
> "Garret Mott" <garret_atsign_automatesoftware_dot_com> wrote in message
> news:9dNVAA%231FHA.2796@dacmail.dataaccess.com...
>> Hi Randy -
>>
>> Do all users have exactly the same Zebra Driver? I've had issues with
>> slightly different drivers producing different printing results (&
> barcodes
>> can be really finicky!).
>>
>> HTH
>>
>> Garret
>>
>> "R. J. Porter" <rjporter@emilab.com> wrote in message
>> news:MsquNs01FHA.3012@dacmail.dataaccess.com...
>> > Hello,
>> > I have just noticed that a particular barcode application I use for
>> > printing
>> > labels in our laboratory does not print readable barcodes unless I
>> > print
>> > them. All other users can print to the Zebra printer just fine with
>> > the
>> > exception of a readable barcode. The acutual print job looks fine with
> of
>> > course some suibtle differences that make the barcode unreadable to our
>> > scanners unless they are printed from my login. We are using Crystal
>> > Reports 10, VDF 7 apps, and Azalea Code39 fonts. Our network uses a
>> > Windows
>> > 2003 Small Business Server as the Domain Controller and Print Server.
> The
>> > VDF and Crystal apps run on Windows 2000 Terminal Server. BTW... I
>> > have
>> > already granted Administrator rights to one of the users and tried to
> get
>> > the barcode to work and it does not. I think it is something to do
>> > with
>> > how
>> > I installed the Azalea barcode fonts or the print drivers for the
>> > Zebra.
>> > I
>> > installed the Azalea through the Control Panel add/remove programs just
> as
>> > I
>> > would any other application I wanted to be available for the entire
> server
>> > user group. The printer is accessable to all users also and has even
> been
>> > shared. I have verified the dll's are in the right place according to
>> > both
>> > Azalea and the Crystal whitepaper.
>> >
>> > Any help would be greatly appreciated. Thanks
>> >
>> > Randy
>> >
>> >
>>
>>
>
>

Baz
23-Oct-2005, 05:46 PM
Let's go down into the depths of TS a little harder.

You say:
" . . for printing labels in our laboratory does not print readable barcodes
unless I print them."
Do you mean, YOU can print to the Zebra & nobody else?

Baz.

R. J. Porter
27-Oct-2005, 10:54 AM
Thanks Baz,
Everyone can print to the Zebra, but only I print can print barcodes that
are actually readable by the scanner. Anyone else printing the same report
with barcodes to the same printer gets something that looks to the eye like
a barcode but the scanner does not read it correctly. If I print them it
reads them just fine. I can print from any network machine and get the same
results. I even tried giving Administrator rights to one of the other users
to see if she could get the barcode to work with Admin rights and she still
could not. It must have something to do with the fact that I installed the
barcode fonts for Crystal and or the fact that I installed the printer.
Asside from the barcode everyone on the network works fine with the Zebra.
Really strange.
"Baz" <baz@nospamstuff.doodle> wrote in message
news:BjFuwOC2FHA.1312@dacmail.dataaccess.com...
> Let's go down into the depths of TS a little harder.
>
> You say:
> " . . for printing labels in our laboratory does not print readable
barcodes
> unless I print them."
> Do you mean, YOU can print to the Zebra & nobody else?
>
> Baz.
>
>

Baz
28-Oct-2005, 09:22 PM
Presuming all the users are on the TS server,
ummm, you DID install the fonts (Azealea ?) on the TS server too?
If the users are on workstations, I reckon they will need the extra fonts on
'em as well.

RANDY PORTER
29-Oct-2005, 10:43 AM
All of the fonts are installed on the TS server. Basically with Terminal
Server the workstations serve like dummy terminals. From what I understand
all of the processor activity and program access etc. is performed on the
server machine.

I can log in on any user machine under my TS account and can print the
readable barcodes, but no one else can. It does seem as if it were some
security or access problem either to the particular printer drivers or the
fonts. I did try granting Admin rights to one of the other users and she
still could not print the correct barcode font. Again, never had this
particular type of problem before. Thanks for any assistance. I am at
this point pretty much dead in the water.

Thanks
"Baz" <baz@nospamstuff.doodle> wrote in message
news:VMIQL$C3FHA.1316@dacmail.dataaccess.com...
> Presuming all the users are on the TS server,
> ummm, you DID install the fonts (Azealea ?) on the TS server too?
> If the users are on workstations, I reckon they will need the extra fonts
> on
> 'em as well.
>
>

Garret Mott
29-Oct-2005, 11:53 AM
Hi Randy -

It still sounds like a driver issue to me. Are you sure the other users
aren't accessing a different driver than you?

Beating a (maybe) dead horse...

Garret

"RANDY PORTER" <rjporter1@verizon.net> wrote in message
news:JVlH6BK3FHA.1316@dacmail.dataaccess.com...
> All of the fonts are installed on the TS server. Basically with Terminal
> Server the workstations serve like dummy terminals. From what I
> understand all of the processor activity and program access etc. is
> performed on the server machine.
>
> I can log in on any user machine under my TS account and can print the
> readable barcodes, but no one else can. It does seem as if it were some
> security or access problem either to the particular printer drivers or the
> fonts. I did try granting Admin rights to one of the other users and she
> still could not print the correct barcode font. Again, never had this
> particular type of problem before. Thanks for any assistance. I am at
> this point pretty much dead in the water.
>
> Thanks
> "Baz" <baz@nospamstuff.doodle> wrote in message
> news:VMIQL$C3FHA.1316@dacmail.dataaccess.com...
>> Presuming all the users are on the TS server,
>> ummm, you DID install the fonts (Azealea ?) on the TS server too?
>> If the users are on workstations, I reckon they will need the extra fonts
>> on
>> 'em as well.
>>
>>
>
>

R. J. Porter
30-Oct-2005, 08:42 AM
That could be it Garret,
How do you actually check to see which driver each user is using? Thanks

"Garret Mott" <garret_atsign_automatesoftware_dot_com> wrote in message
news:qT5kElK3FHA.500@dacmail.dataaccess.com...
> Hi Randy -
>
> It still sounds like a driver issue to me. Are you sure the other users
> aren't accessing a different driver than you?
>
> Beating a (maybe) dead horse...
>
> Garret
>
> "RANDY PORTER" <rjporter1@verizon.net> wrote in message
> news:JVlH6BK3FHA.1316@dacmail.dataaccess.com...
> > All of the fonts are installed on the TS server. Basically with
Terminal
> > Server the workstations serve like dummy terminals. From what I
> > understand all of the processor activity and program access etc. is
> > performed on the server machine.
> >
> > I can log in on any user machine under my TS account and can print the
> > readable barcodes, but no one else can. It does seem as if it were some
> > security or access problem either to the particular printer drivers or
the
> > fonts. I did try granting Admin rights to one of the other users and
she
> > still could not print the correct barcode font. Again, never had this
> > particular type of problem before. Thanks for any assistance. I am at
> > this point pretty much dead in the water.
> >
> > Thanks
> > "Baz" <baz@nospamstuff.doodle> wrote in message
> > news:VMIQL$C3FHA.1316@dacmail.dataaccess.com...
> >> Presuming all the users are on the TS server,
> >> ummm, you DID install the fonts (Azealea ?) on the TS server too?
> >> If the users are on workstations, I reckon they will need the extra
fonts
> >> on
> >> 'em as well.
> >>
> >>
> >
> >
>
>

Garret Mott
30-Oct-2005, 09:55 AM
Not sure how to do it on Terminal Server, but a guess would be to print
something to the printer & when the choose printer dialog comes up, take a
look in the properties page/tab.

If you know what driver you are using, you could change their driver to
match (through the New Driver Wizard).

I'm sure some of the folks more familiar with TS (an apt acronym in this
instance, eh?;-) could help you more here.

HTH

Garret

"R. J. Porter" <rjporter@emilab.com> wrote in message
news:bxrjGfV3FHA.2168@dacmail.dataaccess.com...
> That could be it Garret,
> How do you actually check to see which driver each user is using? Thanks
>
> "Garret Mott" <garret_atsign_automatesoftware_dot_com> wrote in message
> news:qT5kElK3FHA.500@dacmail.dataaccess.com...
>> Hi Randy -
>>
>> It still sounds like a driver issue to me. Are you sure the other users
>> aren't accessing a different driver than you?
>>
>> Beating a (maybe) dead horse...
>>
>> Garret
>>
>> "RANDY PORTER" <rjporter1@verizon.net> wrote in message
>> news:JVlH6BK3FHA.1316@dacmail.dataaccess.com...
>> > All of the fonts are installed on the TS server. Basically with
> Terminal
>> > Server the workstations serve like dummy terminals. From what I
>> > understand all of the processor activity and program access etc. is
>> > performed on the server machine.
>> >
>> > I can log in on any user machine under my TS account and can print the
>> > readable barcodes, but no one else can. It does seem as if it were
>> > some
>> > security or access problem either to the particular printer drivers or
> the
>> > fonts. I did try granting Admin rights to one of the other users and
> she
>> > still could not print the correct barcode font. Again, never had this
>> > particular type of problem before. Thanks for any assistance. I am
>> > at
>> > this point pretty much dead in the water.
>> >
>> > Thanks
>> > "Baz" <baz@nospamstuff.doodle> wrote in message
>> > news:VMIQL$C3FHA.1316@dacmail.dataaccess.com...
>> >> Presuming all the users are on the TS server,
>> >> ummm, you DID install the fonts (Azealea ?) on the TS server too?
>> >> If the users are on workstations, I reckon they will need the extra
> fonts
>> >> on
>> >> 'em as well.
>> >>
>> >>
>> >
>> >
>>
>>
>
>

wila
30-Oct-2005, 08:42 PM
Just check the eventlog on the server.

--
Wil

R. J. Porter wrote:
> That could be it Garret,
> How do you actually check to see which driver each user is using? Thanks
>
> "Garret Mott" <garret_atsign_automatesoftware_dot_com> wrote in message
> news:qT5kElK3FHA.500@dacmail.dataaccess.com...
>
>>Hi Randy -
>>
>>It still sounds like a driver issue to me. Are you sure the other users
>>aren't accessing a different driver than you?
>>
>>Beating a (maybe) dead horse...
>>
>>Garret
>>
>>"RANDY PORTER" <rjporter1@verizon.net> wrote in message
>>news:JVlH6BK3FHA.1316@dacmail.dataaccess.com...
>>
>>>All of the fonts are installed on the TS server. Basically with
>
> Terminal
>
>>>Server the workstations serve like dummy terminals. From what I
>>>understand all of the processor activity and program access etc. is
>>>performed on the server machine.
>>>
>>>I can log in on any user machine under my TS account and can print the
>>>readable barcodes, but no one else can. It does seem as if it were some
>>>security or access problem either to the particular printer drivers or
>
> the
>
>>>fonts. I did try granting Admin rights to one of the other users and
>
> she
>
>>>still could not print the correct barcode font. Again, never had this
>>>particular type of problem before. Thanks for any assistance. I am at
>>>this point pretty much dead in the water.
>>>
>>>Thanks
>>>"Baz" <baz@nospamstuff.doodle> wrote in message
>>>news:VMIQL$C3FHA.1316@dacmail.dataaccess.com...
>>>
>>>>Presuming all the users are on the TS server,
>>>>ummm, you DID install the fonts (Azealea ?) on the TS server too?
>>>>If the users are on workstations, I reckon they will need the extra
>
> fonts
>
>>>>on
>>>>'em as well.
>>>>
>>>>
>>>
>>>
>>
>
>

Baz
31-Oct-2005, 05:03 PM
When a user logs onto a TS server, the server looks over the remote box's
spooler for installed printers to auto-create & connect.
You NEVER install a non windoze driver on a TS server, they have the ability
to bring down your server for unrelated applications used by users not
involved in the sessions of interest too.
You also NEVER leave a printer installed in a TS server spooler area, create
it - then delete it,
but do not delete it using the Print Spooler properties, or it won't be
avail for sessions.
That said, there is room to move, you can indeed take the plunge & install
some drivers, just test it up bigtime first - before you show it the back of
your head.
(lotsa do not's & dont's in here !! sorry)

Substitute drivers can be rerouted to a 2nd inf list, by entering a new
entry in the TS server's registry, here you can redirect say;
a HP G55 to a HP 550c, which gives the remote user colour printing just the
way they like - without them knowing or caring.

Now, one of the problems with TS seems to lie in printers that use a
'monitor' to continually check that a printer is online, has ink etc,
they create a new channel thru the spooler when they are installed (THIS
hurts TS a lot) that cannot connect over the RDP protocol.
I have never found a barcode printer driver that did not use a monitored
channel.
In the Zebra example, it may be that logging onto the TS with an ordinary
user account without launching an app, and setting each user's locale,
setting the Zebra driver to LPT1: in their session, will work on subsequent
logons.
I have done this in the past, it works great - when it works at all.
Be aware, when making changes to a user profile, do not logoff for more than
60 seconds, to permanently set them.
Roaming profiles work best with TS, store 'em on yer PDC or somewhere nice.

It maybe that Zebra printer drivers will not work over TS, yet you say you
can work with it just fine, but not the users.
This is where my remedial little mind gets confused.
If you can get it to work as a remote user over the internet and NOT from
within the LAN, you are nearly there.

I was about to spec & buy Zebra barcode printers, but held off when I saw
your problems.
This may be a candidate for a 3rd party app launcher, like GoGlobal (if they
will respond to mail).
A fella called Claude ~~ makes a product called Screwdriver, that fixes this
printer stuff too.
Such launchers use a 3rd party PDF creater in some astonishing way, that
gives the remote user printing from any printers on their own desktop.
All very expensive . . .
One day, MS Product Support may even call for it to be implemented in a TS
revision in the future, instead of a small program that just looks for event
errors in the event logs to reco printer drivers (which don't exist).
We live in hope.

This whole thread is off topic in respect to VDF, perhaps we shouldn't
devote much more traffic here over it?
Regards,
Baz.