ICE
TCP/IP Products => TCP-PRO => Topic started by: astout on September 30, 2005, 07:41:54 am
-
I have about a dozen users that when they start up Ice.TCP first thing in the morning it sits there with a black screen for sometimes up to 5 minutes before it connects. I've done a complete wipe/reinstall on these machines. On some, it seems to help a litte, but the problem always resurfaces. I have some VERY frustrated users at this point and I don't know what to do to fix it. I haven't made any changes to the Unix server it's connecting to - so I don't think the problem is there. It must be on the client PC because about 3/4 of my users work fine.....
-
I forgot to mention that this is on Windows XP Pro machines that the problem occurrs....
-
okay - I checked one of the problem computer's event logs - I get this:
Hanging application deja32.exe, version 0.0.0.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Hanging application ntvdm.exe, version 5.1.2600.2180, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Fault bucket 127132899.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
-
I don't think any of those microsoft messages mean anything. It is more likely to be a DNS issue. Try windows telnet (start->run type in telnet 1.2.3.4 and hit enter (replace 1.2.3.4 with your unix machine IP address)). I'm thinking windows telnet will do the same thing.
-
I can get in fine with Telnet - it logs right in with no delays or problems. It's definately an Ice.TCP issue. I have another older emulator that connects with no problems also.
-
What's the terminal type set to? Number of lines?
Try unblocking dejawint in exceptions in windows firewall.
Try the 5.1 client to compare.
-
WYSE60 - 24Line
That's a good thought on the firewall. I think most of my users have it disabled.... that would explain it only doing this on a few machines. I'll let you all know how it works.