CweAdmin/CollaborationToolSupport

WikiHomePage | CweAdmin | RecentChanges | Preferences

Collaboration Tool Support (AS)

Reference (AT)

CWE File Workspace structure, access policy and instructions -- see: http://community.cim3.net/cgi-bin/wiki.pl?FileWorkspaceAccess (AU)

WebDAV - Web-based Distributed Authoring and Versioning. See: http://www.webdav.org/ (AV)

VNC connectivity (AW)

generally the setup will allow access as follows (vnc server name and passwords will vary, see announcement for a particular session), by pointing your java enabled browser to: (AHL)

           URL(i):  http://vnc2.cim3.net:5800
           view-only password = "password1"; or
           view-and-control password = "password0" 
            (substitute "password0" or "password1" with the password provided for your session)    (AHM)

(i) this is from a java enabled browser (via an internet connection that does not have port 5800 blocked) (AHN)
those who work from within a firewall which has port 5800 blocked can try to (ii) download the tightvnc viewer and run it locally. That circumvents the need for port 5800 (which is actuall used for the on-demand download of the javascript viewer to one's browser), and be able to do the shared-screen traffic over port 80 (which is the same port http uses). That said, there are firewalls that will block traffic to-and-from applications that are not already "allowed" (which tightvnc would be unless so allowed previously ), or even block to-and-traffic from hosts that are not already "allowed" (which <vnc2.cim3.net> would be unless so allowed previously). (AHO)

(ii) the tightvnc viewer can be downloaded from: http://www.tightvnc.org/download.html. Download the v1.3.10 version client (we are currently using the "tightvnc-2.0.2" server to share the windows desktop now) that is designed for your platform, and invoke the viewer locally after you have installed it on your machine. (ASB)

(if this is the only just what you need) the windows tightvnc viewer (v1.3.10) can be found here -- just download and run the vncviewer.exe from your desktop (no installation is necessary) - use: <vnc2.cim3.net::80> and the appropriate password (ASC)

The access will be: (AHP)

                     VNC Server:  <vnc2.cim3.net> on port: 80 ... or, simply, <vnc2.cim3.net::80> or <vnc2.cim3.net:80> (as your viewer requires)
                     view-only password = "password1"; or
                     view-and-control password = "password0"
                      (substitute "password0" or "password1" with the password provided for your session)    (AHQ)

earlier ref: http://ubl.cim3.org/~lcsc/collaboration_tools/VNC_connectivity_faq.html (AX)

for more details, see: TightVNC (also ref VNC) (AZ)
Mac users may want to take a look at "chicken of the VNC (cotvnc)" - http://sourceforge.net/projects/cotvnc/ - use: <vnc2.cim3.net:80> and the appropriate password (AR3)
I have just installed (the free version of Wyse) PocketCloud (on a MacBook), and found that the (PocketCloud) client, which I then installed on the iPhone, iPad and an Android phone, all worked very well as the vnc client to access our VNC shared-screen server. (--PeterYim/2011.05.02) (ASA)

Configuring your firewall to allow MS-NetMeeting to work properly (B0)

See: http://ubl.cim3.org/~lcsc/collaboration_tools/NetMeeting_firewall_config.html (B1)