Anonymous_User Absent Member.
Absent Member.
1217 views

Remote iprint servers

We have about eight remote iprint managers installed, each has it's own r/w
replica.

everything works fine until we loose connection to the master server. When
that happens, all the printers will say "opening" instead of ready.

This is 100% reproducible in all locations.

The way to make it happen is first login and the printers will say ready
everything will work fine. Then drop the connection to the master server
and "RESTART" the clients print spooler.

that's when it will say opening, only when i turn the connection back on to
the master wil it say ready...

So my question is, how do i fix this and is this a bug?





0 Likes
4 Replies
Anonymous_User Absent Member.
Absent Member.

Remote iprint servers

> We have about eight remote iprint managers installed, each has it's own r/w
> replica.
>
> everything works fine until we loose connection to the master server. When
> that happens, all the printers will say "opening" instead of ready.
>
> This is 100% reproducible in all locations.
>
> The way to make it happen is first login and the printers will say ready
> everything will work fine. Then drop the connection to the master server
> and "RESTART" the clients print spooler.
>
> that's when it will say opening, only when i turn the connection back on to
> the master wil it say ready...
>
> So my question is, how do i fix this and is this a bug?
>
>
>
>
>


To clarify a little bit. we DO have local DNS servers at each location and
they can resolve to name and reverse.

so it's not that.

Thanks to anyone willing to help.

0 Likes
Highlighted
Anonymous_User Absent Member.
Absent Member.

Re: Remote iprint servers

Just to make sure I correctly understood your problem:

It's the *workstations* with an iPrint client installed that loose the
connection to the pritners when they loose their connection to the master
server.

If so, could you describe your client environment? E.g. what Windows
version are you using, and above all, what iPrint client? Do your
workstations also have a Novell client installed?
Also, are you using ICM (iPrint client management)?

--
Marcel Cox (using XanaNews 1.18.1.3)
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Remote iprint servers

> Just to make sure I correctly understood your problem:
>
> It's the *workstations* with an iPrint client installed that loose the
> connection to the pritners when they loose their connection to the master
> server.
>
> If so, could you describe your client environment? E.g. what Windows
> version are you using, and above all, what iPrint client? Do your
> workstations also have a Novell client installed?
> Also, are you using ICM (iPrint client management)?
>
> --
> Marcel Cox (using XanaNews 1.18.1.3)


Ok...

This seems to be the real issue.

When the wan connection get's lost to the driverstore and we restart the
print spooler on the workstation, the iprint manager will try to connect
just to the ip of the driver store.

in otherwords.. it doesn't even care if the driverstor is up, it's just try
to get to it's IP. We confirmed this by making a virtual eth0 device and
assiging the driverstores IP to the iprint manager. Once we did that then
the clients were ok.

Also it doesn't matter the client version. We have the latest iprint client
and they are running on XP.

The real problem is why the iprint manager won't just timeout if it can't
get to the IP of the driverstore and check it's local driver cache instead.

this might be by design, that the iprint manager is try to check for the
latest version of a print driver and if it already has it, it checks it
local cache then. but why wouldn't it just timeout if it can't get to the
driverstore ( not even the driverstore, just try to check the IP of the
driverstore ).

Is there a way to set a timout on the iprint manager, that when it can't
contact the IP of the driverstore it just checks it's local cache?

I'm sorry for such a long explanation, just trying to give as much
information as possible.

Thanks for all the help.



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Remote iprint servers

> > Just to make sure I correctly understood your problem:
> >
> > It's the *workstations* with an iPrint client installed that loose the
> > connection to the pritners when they loose their connection to the master
> > server.
> >
> > If so, could you describe your client environment? E.g. what Windows
> > version are you using, and above all, what iPrint client? Do your
> > workstations also have a Novell client installed?
> > Also, are you using ICM (iPrint client management)?
> >
> > --
> > Marcel Cox (using XanaNews 1.18.1.3)

>
> Ok...
>
> This seems to be the real issue.
>
> When the wan connection get's lost to the driverstore and we restart the
> print spooler on the workstation, the iprint manager will try to connect
> just to the ip of the driver store.
>
> in otherwords.. it doesn't even care if the driverstor is up, it's just try
> to get to it's IP. We confirmed this by making a virtual eth0 device and
> assiging the driverstores IP to the iprint manager. Once we did that then
> the clients were ok.
>
> Also it doesn't matter the client version. We have the latest iprint client
> and they are running on XP.
>
> The real problem is why the iprint manager won't just timeout if it can't
> get to the IP of the driverstore and check it's local driver cache instead.
>
> this might be by design, that the iprint manager is try to check for the
> latest version of a print driver and if it already has it, it checks it
> local cache then. but why wouldn't it just timeout if it can't get to the
> driverstore ( not even the driverstore, just try to check the IP of the
> driverstore ).
>
> Is there a way to set a timout on the iprint manager, that when it can't
> contact the IP of the driverstore it just checks it's local cache?
>
> I'm sorry for such a long explanation, just trying to give as much
> information as possible.
>
> Thanks for all the help.
>
>
>



Also the driverstore happens to be on the same server as the master edir
server. So in my first post i thought it had something to do with that.

So we shutdown every service on the server including edir and the
driverstore. this didn't effect any of the clients when we restrated their
print spoolers, only when we cut the connection by bringing down the
network interface did this affect the clients.

Meaning that the remote iprint manager doesn't really care if it can get to
either of those, for some reason it only cares about the IP. This was also
confirmed by putting the ip of the driverstore on the remote iprint manager
and checking apaches access_log. The log showed iprint manager checking the
driverstores ip.

This whole thing sounds like a bad design flaw. why doesn't it just timeout
when it can't connect to the IP and do what ever it's need to do with a
local copy?

Does this mean i might have to put a driverstore in each location? i really
hope not.

Thanks,
Matthew


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.