Micollab test Active directory connection

Just had this issue where the Micollab no longer connects to the customers active directory server.

The test to try and prove the connection is working is done from the console

Via putty for example

openssl s_client -showcerts -connect {AD Server}:636

Which files can i delete on the Micollab server?

Putty on to Micollab (MSL) (If you don’t know how check here)

Despite how it sounds these files are safe to delete

/var/corefiles/*.core

Find other files that might be eating hard drive space here

How to: Where are SOS logs stored once zipped?

/var/cache/e-smith/logcollector

Using putty as a socks5 proxy

You can use the MBG to VPN to a customers network but this is another trick in your box.

From your office putty into the external address of the MBG

(This has to be allowed in the remote access section of MSL)

Setup tunnels in Putty, see below, copy this and click Add. Make sure to choose “dynamic” and “Auto”

 

putty-tunnel1

 

As some of the Mitel kit requires Internet explorer(IE) i will use it as my example.

In IE choose internet options, connections,LAN settings

putty-tunnel2

 

Now you can web browse to any web site on the customer network, including the 3300, MBG, Nupoint, ETC