Anonymous_User Absent Member.
Absent Member.
3814 views

Winsock error 10101

NW6.5/SP7
Client 4.91/SP4

After moving broker and manager to another context and creating a bunch
of new PAs and enabling them for iPrint, some users get winsock error
10101 when attempting to install a printer. Doesn't matter if install
is via iPrint page or iPrntCmd, result is the same.

Older PAs that were installed via RPM still work.

So far, the only work around has been to recreate the user profile in
Windows.

UserBOB gets the winsock error. UserFRED logs in to Bob's PC, a new
profile is created and Fred can install printers. Bob logs in again,
and can see the printer is install, but for him its status is
'unavailable' in 'Printers and Faxes'. Fred can log back in and it
works just fine.

Clearly a workstation-based problem, but how to fix without having to
recreate user profiles for all these users?

--
-Barry.


0 Likes
6 Replies
nekstedt1 Absent Member.
Absent Member.

Re: Winsock error 10101

Barry St.John,

Well, well, long time no see You still hammering away 🙂

Which version of the iPrint client on the machines? Version 4.34 is
available from www.novell.com/download you might give that a try.

I assume the machines are fully patches as far as Windows Update goes?


--
_________________________________________
Niclas Ekstedt, CNA/CNE/CNS/CLS
Systems Engineer/NSC Sysop
Telindus Sweden AB

Niclas Ekstedt Sr Consultant Atea Sverige AB
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Winsock error 10101

In article <bW6Oj.5253$Dh4.3850@kovat.provo.novell.com>, Niclas Ekstedt
wrote:

> Well, well, long time no see You still hammering away 🙂


Hammering? Yes, with my head lately.

> Which version of the iPrint client on the machines? Version 4.34 is
> available from www.novell.com/download you might give that a try.


Already have it.

> I assume the machines are fully patches as far as Windows Update goes?


Some yes, some no. But some that are fully patched exhibit the problem,
some that are not fully patched are working fine.

--
-Barry.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Winsock error 10101

Got it worked out. Turns out uninstalling iPrint client via Add/Remove
Programs is the wrong way to go. If uninstalled using NIPP-U or
NIPP-SU, then reinstalling takes care of the problem. Would be nice if
Add/Remove Programs would point to this.

Thanks just the same!

--
-Barry.

0 Likes
nekstedt1 Absent Member.
Absent Member.

Re: Winsock error 10101

Barry St.John,

> Got it worked out. Turns out uninstalling iPrint client via Add/Remove
> Programs is the wrong way to go. If uninstalled using NIPP-U or
> NIPP-SU, then reinstalling takes care of the problem. Would be nice if
> Add/Remove Programs would point to this.
>
> Thanks just the same!


No, thank you! Glad you got it sorted out.

You got some more info on this you think could be worth to share, and I'll
pass it on to the iPrint folks, or make sure a TID gets worked up.


--
_________________________________________
Niclas Ekstedt, CNA/CNE/CNS/CLS
Systems Engineer/NSC Sysop
Telindus Sweden AB

Niclas Ekstedt Sr Consultant Atea Sverige AB
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Winsock error 10101

It seems the problem stemmed from applying iprntnw65sp7a to the server.
Workstations that already had NIPP432 installed gradually developed the
winsock problem.

Those that didn't have any iPrint client installed before the
iprntnw65sp7a patch was applied did not have any trouble. I could
install either NIPP432 or NIPP434 and it worked.

Uninstalling NIPP432 via Add/Remove Programs and installing NIPP434 did
not solve the problem. But using NIPP-U.EXE or NIPP-SU.EXE to remove
the iPrint client (either NIPP432 or NIPP434), followed by a fresh
install of NIPP434 fixes the problem.

So I would say installing NIPP434 *before* iprntnw65sp7a is a good
idea, at least from my experience.

Furthermore, don't rely on Add/Remove Programs to properly uninstall
the iPrint client.

And since you're passing this along, the iprntnw65sp7a patch *did* fix
the problem where installing a printer to a Mac would crash iPrint.
And if it matters, the Mac was running NIPP432.

--
-Barry.


0 Likes
nekstedt1 Absent Member.
Absent Member.

Re: Winsock error 10101

Barry St.John,


OK, thanks Barry. I'll pass it along.


--
_________________________________________
Niclas Ekstedt, CNA/CNE/CNS/CLS
Systems Engineer/NSC Sysop
Telindus Sweden AB

Niclas Ekstedt Sr Consultant Atea Sverige AB
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.