CraigWU

There was another post on the Black Screen problem with Carbon Copy, but this may be different. We eventually get a connection, it just consistently takes 11 minutes to happen (actually 10:59). During that time, we get a Black Screen on the simple version, and no screen at all on the Advanced version. Here is an example of the Event Log entries we see each time:

11/18/2008 11:24:02 AM Security Info A connect request from User1 has been ACCEPTED.
11/18/2008 11:35:01 AM Communications Info The Carbon Copy session with User1 has been successfully established.

Does anyone know why it takes 10:59 minutes to establish the session after the connect request has been accepted? Althought this may still be faster than driving to a remote location, I don't think Symantec intends to see this response time...

Another point of interest - we get this exact same timing whether we are connecting two machines on different subnets or two machine on the same subnet.

CraigWU

I found what is causing the problem, but I would still like to know the fix.

We are getting this latency only when we don't provide an Authentication method in the Carbon Copy configuration. When I specificy an Authentication (Native NT Groups, CC Profiles, etc), the response time is excellent.

We would like to turn off Authentication and just PW protect the CC functionality, so we would like this to work. Do you know why not having any Authentication specified would cause this 10:59 delay?