ICE
TCP/IP Products => TCP-PLUS => Topic started by: pds-jeff on September 06, 2007, 01:32:17 pm
-
I am a re-seller and I have been receiving an increasing number of calls about problems with Dejawint and long delays to get logins or just not working at all after they installed a new HP printer. The printers have been both inkjet and laserjet and have been network based. When the client removes the HP software everything returns to normal.
1. Is J.River aware of this?
2. Is there a fix?
-
I am a re-seller and I have been receiving an increasing number of calls about problems with Dejawint and long delays to get logins or just not working at all after they installed a new HP printer. The printers have been both inkjet and laserjet and have been network based. When the client removes the HP software everything returns to normal.
That's rather bizzare
1. Is J.River aware of this?
First I've heard of it.
We have several HP printers here and haven't seen this behavior
2. Is there a fix?
Sounds like a bug in the HP printer driver, wouldn't be the first...
-
After checking into this some more we have a theory that it might have something to do with the HP driver replacing a mfc library on your system. To avoid such problems, we've compiled in the library statically. This also might relate to your other printer problem with the current version. Which version are you having trouble with on login timeouts?? (help->about dejawint).
-
Sorry about the delay in my replay.
So far it seams that several builds of ICE.TCP PLUS are affected and I just had a client have the issue with a Kyocera network laser printer too. I will gather more info and post it.
-
Hi Jeff,
If you could, please note which versions work and which don't and I may be able to get a pattern from that...
Thanks,
Bob
-
Sorry about the delay, I've been out of town.
I'm going to concentrate on one client with this issue.
The client is running a 100 user ICE.TCP PLUS build 27. They are testing a Kyocera Ecosys FS-4000DN network printer and report that logins with Dejawint take up to an hour to come up. The windows telnet client is un-affected by this. They also report that when they take the printer off the network that the problem goes away.
-
Update: The client is giving me mixed info on this issue. I will sort it out and report back the "REAL" issues.
-
Ok, let me know when you hear more..