Highlighted
Anonymous_User Absent Member.
Absent Member.

Re: Novell Client breaks Windows Domain Printing

Also check to see if Post Script drivers are available.
Often these resolve issues present in PCL drivers on lower end printers.

If this is an option and helps I will explain why it may help, but for
now I will avoid the diatribe.

gwertman@lccc.edu wrote:
> Both excellent ideas - I'll try them out and let you know..
>
> Thank you again. Have a great weekend Alan.
>
> -Gary
>
>> gwertman@lccc.edu wrote:
>>
>>> Issue: Printing to an HP LaserJet 2600n fails when accessing the

> printer
>>> through a Windows 2000 domain while running Novell Client for XP.
>>>
>>> If either of those 2 factors is eliminated printing is successful.

>> If pushing LanMan to the top (and just to be sure, I would reboot
>> after making that change, if you hadn't already included that in your
>> testing) did not change the problem, then I'm guessing its probably
>> not an issue related to the installed Novell print provider.
>>
>> But just to be sure, one additional test you could perform would be to
>> export (backup) the contents of the
>>

> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Providers\Netwa
> re
>> Print Services] key in the registry and then delete that key entirely
>> and reboot. This would remove the registration of the Novell
>> queue-based print provider (which should be the only Novell one
>> present from the Novell Client, since you didn't install NDPS
>> support.)
>>
>> The only other thought coming to my mind for "why only when printing
>> through the domain" would be to disable the "UNC Path Filter" in the
>> Novell Client Properties "Advances Settings" tab. Although that
>> setting is about UNC path resolution (and the Novell Client trying to
>> prevent certain calls from reaching the Microsoft provider), its
>> possible there is some direct or indirect ramification to the actions
>> being performed underneath this printer driver.
>>
>> Aside from that, it seems like it would take a LAN trace or similar to
>> try and find more clues of "how far does it get before failing when
>> the Novell Client is present" verus a LAN trace of the completely
>> successful domain-based printing without the Novell Client there.
>>
>> Alan Adams
>> alancrumbadams@drcrumb.com
>> (for email, remove the crumbs)

>



--
Craig Wilson
Novell Product Support Forum Sysop
Master CNE, MCSE 2003, CCN
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Novell Client breaks Windows Domain Printing

It was a long Memorial Day Holiday Weekend, but I'm back to work on
this. I'll try both the novell spool renaming trick and if that doesn't
work I'll try the postscript printer drivers.

Thank you again!

-Gary

> Also check to see if Post Script drivers are available.
> Often these resolve issues present in PCL drivers on lower end printers.
>
> If this is an option and helps I will explain why it may help, but for
> now I will avoid the diatribe.
>
> gwertman@lccc.edu wrote:
> > Both excellent ideas - I'll try them out and let you know..
> >
> > Thank you again. Have a great weekend Alan.
> >
> > -Gary
> >
> >> gwertman@lccc.edu wrote:
> >>
> >>> Issue: Printing to an HP LaserJet 2600n fails when accessing the

> > printer
> >>> through a Windows 2000 domain while running Novell Client for XP.
> >>>
> >>> If either of those 2 factors is eliminated printing is successful.
> >> If pushing LanMan to the top (and just to be sure, I would reboot
> >> after making that change, if you hadn't already included that in your
> >> testing) did not change the problem, then I'm guessing its probably
> >> not an issue related to the installed Novell print provider.
> >>
> >> But just to be sure, one additional test you could perform would be

to
> >> export (backup) the contents of the
> >>

> >

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Providers\Netwa
> > re
> >> Print Services] key in the registry and then delete that key entirely
> >> and reboot. This would remove the registration of the Novell
> >> queue-based print provider (which should be the only Novell one
> >> present from the Novell Client, since you didn't install NDPS
> >> support.)
> >>
> >> The only other thought coming to my mind for "why only when printing
> >> through the domain" would be to disable the "UNC Path Filter" in the
> >> Novell Client Properties "Advances Settings" tab. Although that
> >> setting is about UNC path resolution (and the Novell Client trying to
> >> prevent certain calls from reaching the Microsoft provider), its
> >> possible there is some direct or indirect ramification to the actions
> >> being performed underneath this printer driver.
> >>
> >> Aside from that, it seems like it would take a LAN trace or similar

to
> >> try and find more clues of "how far does it get before failing when
> >> the Novell Client is present" verus a LAN trace of the completely
> >> successful domain-based printing without the Novell Client there.
> >>
> >> Alan Adams
> >> alancrumbadams@drcrumb.com
> >> (for email, remove the crumbs)

> >

>
>
> --
> Craig Wilson
> Novell Product Support Forum Sysop
> Master CNE, MCSE 2003, CCN


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.