<< Defense Connect Online User Forum

Discussion Area

ask questions, discuss topics, solve problems

Discussion Home | About | Threads By Date | Search

DCO Connect 'Re-connect' Issue Solved?


Thread posted 04/18/11 by Mike Murtha last edited 04/18/11
3,143 views, 2 comments.

Title
DCO Connect 'Re-connect' Issue Solved?

Content

Since moving to our new multi-site architecture early last year, we have been plagued by a persistent 're-connect' issue where users would get disconnected from a DCO Connect room and then automatically re-connected into it.  From a participant standpoint this was annoying at best and unusable at worst.  From a host standpoint, it was very troublesome because they would have to re-initiate capabilities like broadcasing VoIP, video, and screen/app sharing.  This issue also had other side effects such as inability to enter rooms ('hung connections') and content not fully loading.

Recently DISA Computing Service Directorate network engineers diagnosed what they believed to be the issue - switch/firewall settings.  Since this equipment sits between the DCO Connect servers and users, this may have been the culprit.

The modifications were made this past weekend and early testing looks promising.  We would love to hear back on your experiences, good or bad, so we can see if the issue is truly resolved.

Comments

posted 04/20/11 by Mike Murtha | Report Abuse

Update: I have yet to have a hung connection or reconnect in a room since this CSD mod was made last week! In past I would experience the symptoms nearly 100% of the times I entered a DCO Connect room. Beyond my personal experiences, we still have not received a single negative data point so things are looking good!

posted 06/01/11 by Scott Schaubach | Report Abuse

Having worked a lot on this issue with the DCO Live Remote Training, I am pleased to confirm that the issue appears to have been resolved from our standpoint (as DCO Trainers) and all residual issues appear to be one-offs that point to individual users connections. Good Job to all those who put in MANY hours on finding and resolving this issue and Thank You.