Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[daltoncomputer]

Hi,

I have a customer running TCP ICE Plus (v7.10a/32 Build 27) to access their AIX RS6000 that recently purchased a networked HP Color Laserjet CM1312nfi MFP and after installing the driver/software on about 4 PC's in their office, ICE TCP has stopped responding when it is launched on those PC's.

I've searched and found some similar issues, but in other cases uninstalling the HP software has fixed the problem.  The troubleshooting steps I have tried so far are:

1. Uninstall all HP printer software - problem persists.
2. Reinstall ICE TCP - had a similar problem as someone else where ICE's setup.exe does nothing when attempting to reinstall -- a reinstall from safe mode worked, but problem is still there.
3. Switched affected PC's from HP's full "Recommended" software install to the basic "Express" install that doesnt load things such as HP Toolbox or HP Updater. - same result
4. Tested on another working PC that hadn't previously had the full HP install - Installed HP's basic "Express" drivers only , but express affects ICE TCP as well.

Something I did find in my tests was that it doesnt seem as if the HP software itsself is whats affecting ICE, but rather something the windows print spooler or fax service is doing.  Perhaps the HP software updated something, as both services were already present before the HP install?  I can manually stop the fax service and ICE will respond immediately with the AIX login prompt.  I can also stop the print spooler service and get the same result, however the fax service stops too since it relies on the print spooler. 

Whatever is going on behind the scenes is simply stopping the initial connection between ICE and the AIX, because once the fax/spooler service is disabled and ICE logs in, i can re-enable the service and ICE's connection is unaffected, and the customer can login and print as normal.  We've been using this as a crutch so the customer can continue to work, however they certainly dont view it as an acceptable fix, and I'm out of things to try, aside from uninstalling windows fax service, and hoping they never need it...

Has anyone else seen this or is this a known issue?  Would a patch/update for TCP ICE possibly help?

Thanks!
-Devin Padgett
Dalton Computer Services

[Bob]

Hi Devin,
Nice detective work!

I'd like to try and duplicate your problem. I have one other question first, did you update outlook during this process??

[daltoncomputer]

Hello Bob,

As far as I am aware, Outlook was not involved at any point.  The customer originally installed the HP software themselves, and got me involved *after* ICE went down so I can't be 100% certain.  I am fairly sure that the customers use outlook express.   I CAN tell you that the machine I duplicated the problem on was not running Microsoft Office/Outlook at all.  In fact it was a freshly installed, brand new ACER PC at our shop -- right out of the box w/ XP Pro.  Also that reminds me, I should have stated previously that all the machines that have encountered this error were running Windows XP -- a variety of Home, Professional, and the 2 or 3 I worked on were SP2.  I'm not sure if any were SP3 or not, but I can check with them to see, if necessary.  I was also using the most up-to-date drivers available from HP on their website for the above mentioned printer.  I hope this helps.

Thanks for your prompt reply,
I look forward to hearing how your test goes.

-Devin Padgett
Dalton Computer Services

[Bob]

With everything in place that would prevent Plus from running, can you pull up a dos box and do a

netstat -a

copy/paste the results here...

[Chris]

I also have the same problem at my company, and it was only after I installed an HP Printer to 5 of the machines in the office, we did figure out that it was the print spooler after shutting down all services and doing a trial and error test. But my question is, how was this fixed? or can it be fixed?

[Bob]

Chris, could you try that netstat -a test with the conditions in place to prevent a connections (from the post above yours) and copy/paste the results in a message here??

[Chris]

as it pertains to the ICE Ten Program, everything else was standard operating procedures in the netstat report the following apply

TCP       1356 190.10.10.1 telnet    TIME-WAIT
TCP       1357 190.10.10.1 telnet    TIME-WAIT

190.10.10.1 is the location of the ICE TEN box

After I turn off the print spooler the following happens

TCP 1357  190.10.10.1 telnet TIME-WAIT
TCP 1362  190.10.10.1 telnet Established

that is all I have and I know it was because I installed an HP Printer, as a PC next to this one works ICE TEN just fine and does not have the printer networked to it.

[Bob]

Chris,
would you please do a
netstat -an
and post it all. I'm looking for something other than the obvious telnet connection info.

BTW, I'm looking for this info ON THE PC (from a command prompt), not the unix box.

[Chris]

Here ya go
TCP 0.0.0.0:135      0.0.0.0:0   Listening
0.0.0.0:445            0.0.0.0:0   Listening
127.0.0.1:1061       0.0.0.0:0   Listening
190.10.10.44:139    0.0.0.0:0   Listening
190.10.10.44:1031    190.10.10.30:135 Time_Wait
190.10.10.44:1032    190.10.10.30:1026 Time_Wait
190.10.10.44:1033    190.10.10.30:1026 Time_Wait
190.10.10.44:1034    190.10.10.30:445 Time_Wait
190.10.10.44:1040    190.10.10.30:445 Time_Wait
190.10.10.44:1042    190.10.10.30:1026 Time_Wait
190.10.10.44:1046    190.10.10.30:389 Time_Wait
190.10.10.44:1048    190.10.10.30:389 Time_Wait
190.10.10.44:1049    190.10.10.30:445 Time_Wait
190.10.10.44:1052    190.10.10.30:445 Time_Wait
190.10.10.44:1056    190.10.10.30:1026 Time_Wait
UDP 0.0.0.0:445       *:*
0.0.0.0:500             *:*
0.0.0.0:1067           *:*
0.0.0.0:4500           *:*
0.0.0.0:5501          *:*
0.0.0.0:54925         *:*
127.0.0.1:123          *:*
127.0.0.1:1025          *:*
127.0.0.1:1045          *:*
127.0.0.1:1900          *:*
190.10.10.44:123       *:*
190.10.10.44:137       *:*
190.10.10.44:138      *:*
190.10.10.44:1900       *:*

[Bob]

Is that WITHOUT Dejawint running? (if not c+p again).

Also, please do one without the spooler running or whatever it is you have to do to allow Dejawint to connect. This should also be without Dejawint running.

Thanks...

Bob

[Chris]

This is without the spooler running and without ICE Ten running, the post above was with Dejawin running and the print spooler off

TCP 0.0.0.0:135      0.0.0.0:0   Listening
0.0.0.0:445            0.0.0.0:0   Listening
127.0.0.1:1062       0.0.0.0:0   Listening
190.10.10.101:139    190.10.10.25:135 Time_Wait
190.10.10.101:1028    190.10.10.25:445Time_Wait
190.10.10.101:1029    190.10.10.25:1026 Time_Wait
190.10.10.101:1031    190.10.10.25:1026 Time_Wait
190.10.10.101:1032    190.10.10.25:1026 Time_Wait
190.10.10.101:1037    190.10.10.25:389 Time_Wait
190.10.10.101:1041    190.10.10.25:389 Time_Wait
190.10.10.101:1043   190.10.10.25:1026 Time_Wait
190.10.10.101:1046    190.10.10.25:389 Time_Wait
190.10.10.101:1050    190.10.10.25:389 Time_Wait
190.10.10.101:1052    190.10.10.30:139 Time_Wait
190.10.10.101:1055    190.10.10.30:139 Time_Wait
190.10.10.101:1058    190.10.10.25:445 Established
190.10.10.101:1060   190.10.10.25:389  Time_Wait
190.10.10.101:1068   65.55.25.125.8:Established
190.10.10.101:1070  65.55.25.125.8:Established
UDP 0.0.0.0:445       *:*
0.0.0.0:500             *:*
0.0.0.0:4500           *:*
0.0.0.0:54925         *:*
127.0.0.1:123          *:*
127.0.0.1:1025          *:*
127.0.0.1:1040          *:*
127.0.0.1:1900          *:*
190.10.10.101:123       *:*
190.10.10.101:137       *:*
190.10.10.101:138      *:*
190.10.10.101:1900       *:*

[Bob]

Ok, one more with just the spooler running.

Also, I can tell by the netstat that this isn't PLUS, it looks to be PRO w/ the classic client (4.4). Confirm please.

Finally, a version please (help->About Dejawint).
the build is in the first couple of lines, i.e. 4.4.x

[Chris]

here ya go
TCP 0.0.0.0:135      0.0.0.0:0   Listening
0.0.0.0:445            0.0.0.0:0   Listening
127.0.0.1:1045       0.0.0.0:0   Listening
190.10.10.101:139  0.0.0.0:0 Listening
190.10.10.101:1063  190.10.10.30:135   Time_wait
190.10.10.101:1064  190.10.10.30:1026   Time_wait
190.10.10.101:1066  190.10.10.25:445   Established
190.10.10.101:1069  190.10.10.25:135   Time_Wait
190.10.10.101:1070  190.10.10.25:1026   Time_Wait
190.10.10.101:1075  190.10.10.25:389   Time_Wait
190.10.10.101:1077  190.10.10.25:389   Time_Wait
190.10.10.101:1078  190.10.10.25:445  Time_Wait
UDP 0.0.0.0:445       *:*
0.0.0.0:500             *:*
0.0.0.0:1052       *:*
0.0.0.0:4500           *:*
0.0.0.0:54925          *:*
127.0.0.1:123          *:*
127.0.0.1:1025          *:*
127.0.0.1:1041         *:*
127.0.0.1:1900          *:*
190.10.10.101:123       *:*
190.10.10.101:137       *:*
190.10.10.101:138      *:*
190.10.10.101:1900       *:*

[Chris]

sorry I forgot the version
ICETCP 4.4 32Bit

Emulation version 7.09b

[Bob]

That's a VERY old version. Can you try the trialware version on one machine and see if you still have the problem?
It might be easier to use the trialware version of plus to just test on one machine.
http://www.icetcp.com/cgi-bin/download.cgi?ICE.TCP-Plus