Print

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

[Coast Oil]

Hello,

I am having a problem with our ICE.TCP PLUS
As of lately we have been getting a DEJAWINT warning it is as fallows

Warning!


Two DejaWinT sessions are using identical sequence numbers.
Please inform your system administrator that sequence number 30
is duplicated and that this warning message was sent from (IP Address)


Please click on OK to continue




Right after you click ok it closes DejiaWinT.  So I opened the program to see what sequence number it was using and the computer was using number 34 not 30
That was the first time I heard of it happening but the users say it happened from time to time and when it happens it happens to a few users at a time.
Now it is happening everyday multiple times a day as well as 7 to 15 warning screens pop up at a time and it is happening to at lest half the users when it happens.

Dose anyone know what is the cause of this is?

[Bob]

It sounds like you are using quite an old version that shows the problem to users not directly involved in the problem, AFAIK that only happened in ICE.TCP not ICE.TCP.PLUS.

You should try to find the 2 machines that are using the duplicates of sequence number 30.

[Coast Oil]

Thanks for the reply

we are using  J. River, Inc. - ICE.TCP Pro 5.0 Version 5.1.05 on all our PC's

there is only one computer using sequence number 30. when the warring message pops up it is the same for all and pops up at the same time on multiple computers

I'm not sure what is happening

[Bob]

Something is not jibbing here. If this is REALLY Pro you are posting in the wrong forum.   

First, the CD for ICE.TCP.PRO for any 5.1 version (like 5.1.05) would say 5.1, NOT 5.0.

Second, I need to know which client you are running, the "classic" client (4.4) or the PRO client (5.1). If you are running the 4.4 client you can do
Help->About Dejawint 
If you are running the Telnet Pro client it's
Help->Version Information
Do this on several of the computers that are complaining and report back the version information.

[Coast Oil]

When I go to help about dejawint I Get


DejaVu TCP PLUS for Windows
                Build 20
 Emulation Version:  7.10a/32
Windows Interface Version: 8.0
       By Robert E Brose II
  © 1992-2002 J. River, Inc.
       All Rights Reserved


SSH Potion Only:
Putty © 1997-2000 Simon
Tatham. All right reserved.

[Bob]

..
we are using  J. River, Inc. - ICE.TCP Pro 5.0 Version 5.1.05 on all our PC's
..

Ok so at least some of the computers are running PLUS, NOT PRO. Please check several of the computers popping up the message and see if there are any other versions out there...

[Coast Oil]

all of our computers are running the same Version

[deanna]

According to our records, you have a 50-user license of ICE.TCP PLUS.  We have no record of you owning any licenses of ICE.TCP Pro.  Per our previous phone conversation, you know where to find the Sequence Number that each computer is using.  I would recommend that you go to each workstation and make a list of which workstation has which sequence number.  Once you have a complete, verified list, check for duplication and for available sequence numbers, and re-assign accordingly.

[Coast Oil]

I checked our computers and they all have their own Sequence Number.
Also they are all running

DejaVu TCP PLUS for Windows
                Build 20
 Emulation Version:  7.10a/32
Windows Interface Version: 8.0
       By Robert E Brose II
  © 1992-2002 J. River, Inc.
       All Rights Reserved


SSH Potion Only:
Putty © 1997-2000 Simon
Tatham. All right reserved.

The Information that I got before (J. River, Inc. - ICE.TCP Pro 5.0 Version 5.1.05 on all our PC's ) was off a Belarc Advisor Report that I now know isn’t that accurate.

[Bob]

There is no question, you have a duplicate number somewhere!

Is someone coming in from outside via a VPN using a duplicate sequence number?

Also, that version is VERY, VERY old. If you updated all of the users to the current version you would only have the users with duplicate numbers locked out.
(though I could have sworn that only versions of ICE.TCP 4.3 had the behavior you are describing).