regards,

  glenn field

I am having the same problem!!!!!

Additonally some conversations are lost in one of the directions.

I can recieve the text from one of the users, but sometimes that user doesnt recevies my conversation.

Having the same issue.  Clients continue to drop connection throughout the day.  Has anyone found a fix???

I am experiencing the same thing ; I am running the product on a dedicated iMail server which uses virtual domains.  I use the iMail database, and in configuration I set up im.domain.tdl as an alias so users can log in with username@im.domain.com, for example.  Of course, this domain name is valid and the A Name record is pointed to the iMail server in DNS.  This worked in version 1.04 and seems to work here, but since I upgraded to version 2.0, I notice that users are logged off without any kind of notificaition ; they appear to be connected, but they are not.  The do not appear in the status window of the IM server manager, and their messages are lost when they send.  Also, if you hit F5 to refresh from the disconnected client (which appears connected still), you get a "invalid user" error.  They are free to log back on again, but at some point they will be disconnected and they will not know that they are disconnected.  Sending an IM to them is properly received offiline, when they log back in, they get the offline message.

That's about as much detail as I can give.  I tried calling tech support, but waited on hold for quite some time and then was forced to voice mail. 

I need to resolve this, I don't enjoy looking foolish.

-- Michael Cummins

Here is a screenshot of the errors I am getting:

http://www.wddx.net/pix/ipswitchError.jpg

ADDING MORE DATA:

Here is an excerpt from the log (cleaned for IPs and Addys) watching two users get bumped off / like most remote offices, the client is NAT, the server is NOT, the server has 5177 and 5178 open:

8/6/2004 12:27:01 PM IMServer Login message from 68.233.
8/6/2004 12:27:01 PM IMServer robert@im.has logged in from 68.233.
8/6/2004 12:27:01 PM IMServer Failed to push status to wendy@im.Error=Error writing data.
8/6/2004 12:27:01 PM IMServer Failed to push status to michael@im.Error=Error writing data.
8/6/2004 12:27:02 PM IMServer Status update message from 68.233.
8/6/2004 12:28:51 PM IMServer wendy@im. NOOP failed. Removing user wendy@im. at 64.135.
8/6/2004 12:28:51 PM IMServer wendy@im. is logging off
8/6/2004 12:28:51 PM IMServer Failed to push status to michael@im.Error=Error writing data.
8/6/2004 12:28:51 PM IMServer michael@im.NOOP failed. Removing user michael@im. at 64.135.
8/6/2004 12:28:51 PM IMServer michael@im.is logging off
8/6/2004 12:29:08 PM IMServer Request Failed: Request=6, IpAddress=64.135., ErrorCode=1244, ErrorMsg=Invalid user.
8/6/2004 12:29:12 PM IMServer Request Failed: Request=30, IpAddress=64.135., ErrorCode=1244, ErrorMsg=Invalid user.
8/6/2004 12:29:12 PM IMServer Request Failed: Request=2, IpAddress=64.135., ErrorCode=1244, ErrorMsg=Invalid user.
8/6/2004 12:29:14 PM IMServer Login message from 64.135.
8/6/2004 12:29:14 PM IMServer wendy@im.has logged in from 64.135
8/6/2004 12:29:15 PM IMServer Request Failed: Request=6, IpAddress=64.135., ErrorCode=1244, ErrorMsg=Invalid user.
8/6/2004 12:29:15 PM IMServer Status update message from 64.135.
8/6/2004 12:29:18 PM IMServer Request Failed: Request=30, IpAddress=64.135., ErrorCode=1244, ErrorMsg=Invalid user.
8/6/2004 12:29:18 PM IMServer Request Failed: Request=2, IpAddress=64.135., ErrorCode=1244, ErrorMsg=Invalid user.
8/6/2004 12:29:20 PM IMServer Login message from 64.135.
8/6/2004 12:29:20 PM IMServer michael@im. has logged in from 64.135.
8/6/2004 12:29:20 PM IMServer Status update message from 64.135.
8/6/2004 12:30:30 PM IMServer Request Failed: Request=7, IpAddress=66.43., ErrorCode=1244, ErrorMsg=Invalid user.
8/6/2004 12:31:03 PM IMServer Request Failed: Request=7, IpAddress=66.43., ErrorCode=1244, ErrorMsg=Invalid user.
8/6/2004 12:31:41 PM IMServer Status update message from 66.43.
8/6/2004 12:31:43 PM IMServer michael@im. is logging off
8/6/2004 12:31:45 PM IMServer Login message from 66.43.
8/6/2004 12:31:45 PM IMServer jtrujillo@im. has logged in from 66.43.
8/6/2004 12:31:46 PM IMServer Status update message from 66.43.
8/6/2004 12:31:57 PM IMServer Status update message from 66.43.
8/6/2004 12:32:11 PM IMServer Request Failed: Request=6, IpAddress=64.135., ErrorCode=1244, ErrorMsg=Invalid user.
8/6/2004 12:32:22 PM IMServer Request Failed: Request=30, IpAddress=64.135., ErrorCode=1244, ErrorMsg=Invalid user.
8/6/2004 12:32:22 PM IMServer Request Failed: Request=2, IpAddress=64.135., ErrorCode=1244, ErrorMsg=Invalid user.
8/6/2004 12:32:24 PM IMServer Login message from 64.135.
8/6/2004 12:32:24 PM IMServer michael@im. has logged in from 64.135.
8/6/2004 12:32:24 PM IMServer Status update message from 64.135.
8/6/2004 12:34:41 PM IMServer Status update message from 64.135.
8/6/2004 12:35:21 PM IMServer Status update message from 64.135.

I worked with a support representative named Amy on Friday.  She was very helpful and actually touched base with me two more times that day.  I gave her and her supporting technician copies relevant registry keys, more logs, etc.  They determined that there was a problem with 2.0 server that needed to be fixed and told me that they were going to work hard on the problem, and that they would release version 2.01 some time on Monday.

I was going to wait to implement the upgrade on Monday, but my customers told me this was unacceptable.  I have since rolled back to the 1.04 server, while retaining the 2.0 clients.  This seems, thus far, to be working.  I have several offices online now and do not seem to be encountering the same kind of disconnects as before.  The spellchecking on the 2.0 client is still functional though of course I will not have access to the stored conversations. 

I am still looking forward to upgrading to the 2.01 server as I hope that it will resolve some other connectivity issues that I had in 2 specific offices.  Ipswitch tech support was not help to me in resolving that issue.  At that office, the IM Client would log out several times during the day.  I wonder if it has something to do with the "check for dropped users" feature on the server, as all of my remote clients are in various offices throughout the world, almost always behind a NAT router.

Can anyone else give me insight into that particular problem?

-- Michael Cummins

6 hours later, it seems that I am still experiencing the same kind of disconnect as before ; perhaps not as frequently because of the 1.04 rollback, perhaps it is because the usage over the weekend is minimal.  I don't have the opportunity to tell my users to download and install the 1.04 client, so I will cross my fingers and hope we get through Monday. 

I don't think it is very professional to release a product that obviously has not been thoroughly tested ; to release 2.01 days later underscores the fact that this was not properly tested.  My usage cannot stray so far from the path of what is predictable that I should not expect a quality product the first time around.  The same holds true for the initial release, version 1.0.  It did not support virtual domains on a dedicated iMail server, and I had to hold off for a solution then as well. 

Additionally, I use their FTP server, I bought version 2.0 when it was new.  Version 2.0 supported UNC paths for virtual folders, but omitted this feature in versions 3.0 and 4.0.  It was not until 5.0 that I had an upgrade path, and even now I am afraid to try it.

Ipswitch, you had better get your act together or people like me, who spend thousands of dollars on your products (I have been using iMail Unlimited since version 5.0) will find other solutions. 

I am taking a long hard look at customizing the Jabber server as we speak.