Author Topic: Micollab client error  (Read 4239 times)

Offline sunspark

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 986
  • Country: mx
  • Karma: +16/-1
    • View Profile
Micollab client error
« on: November 18, 2020, 12:37:01 PM »
hello fellows,

I have an issue with the micollab client V8.
micollab server: 192.168.2.10

if i install the client in the same  subnet it works 192.168.2.0
if i install it in the 192.168.1.0 subnet it doesn't work.
I have error 41 which corresponds to a port 36008 or firewall problem.

I don't have a firewall between these two subnets and the TNA tells me that port 36008 is open.


any idea ?

cheers


Offline NEPhoneGuy

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 218
  • Country: us
  • Karma: +5/-0
    • View Profile
Re: Micollab client error
« Reply #1 on: November 18, 2020, 03:27:06 PM »
Check DNS - does the fqdn of the MiCollab server resolve correctly on the nonworking subnet.

Offline sunspark

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 986
  • Country: mx
  • Karma: +16/-1
    • View Profile
Re: Micollab client error
« Reply #2 on: November 18, 2020, 04:58:31 PM »
Check DNS - does the fqdn of the MiCollab server resolve correctly on the nonworking subnet.

Yes the dns is correct

Offline NEPhoneGuy

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 218
  • Country: us
  • Karma: +5/-0
    • View Profile
Re: Micollab client error
« Reply #3 on: November 18, 2020, 05:26:39 PM »
Definitely a bit of head scratcher. If this was me my next step would probably have a wireshark capture running on the client machine at the same time I fired up or tried to complete the MiCollab Client deployment and see filter down between my IP and the MiCollab Server and see if anything sticks out.

Offline johnp

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2209
  • Country: us
  • Karma: +67/-0
    • View Profile
Re: Micollab client error
« Reply #4 on: November 18, 2020, 06:12:57 PM »
The other network trusted?

Offline sunspark

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 986
  • Country: mx
  • Karma: +16/-1
    • View Profile
Re: Micollab client error
« Reply #5 on: November 19, 2020, 03:37:36 AM »
The other network trusted?

Yep , i accept 192.168.0.0

Offline sunspark

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 986
  • Country: mx
  • Karma: +16/-1
    • View Profile
Re: Micollab client error
« Reply #6 on: November 19, 2020, 03:40:02 AM »
Definitely a bit of head scratcher. If this was me my next step would probably have a wireshark capture running on the client machine at the same time I fired up or tried to complete the MiCollab Client deployment and see filter down between my IP and the MiCollab Server and see if anything sticks out.


you mean run WireShark on the client and try a new registration?

Offline johnp

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2209
  • Country: us
  • Karma: +67/-0
    • View Profile
Re: Micollab client error
« Reply #7 on: November 19, 2020, 05:53:07 PM »
Quote
you mean run WireShark on the client and try a new registration?

Why worry about registration if the client never connects, get an error lo from the client and see what it says

Offline sunspark

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 986
  • Country: mx
  • Karma: +16/-1
    • View Profile
Re: Micollab client error
« Reply #8 on: November 20, 2020, 04:54:09 AM »
Quote
you mean run WireShark on the client and try a new registration?

Why worry about registration if the client never connects, get an error lo from the client and see what it says

this what i describ in the main subject :

I have error 41 which corresponds to a port 36008 or firewall problem.

I don't have a firewall between these two subnets and the TNA tells me that port 36008 is open.

Offline mark.vanderheijden

  • Full Member
  • ***
  • Posts: 130
  • Country: nl
  • Karma: +8/-0
    • View Profile
Re: Micollab client error
« Reply #9 on: November 20, 2020, 09:52:48 AM »
Check the MiCollab client log C:\Users\[user]\AppData\Roaming\Mitel Networks Corporation\MiCollab\log

Maybe this will tell some more.

Offline sunspark

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 986
  • Country: mx
  • Karma: +16/-1
    • View Profile
Re: Micollab client error
« Reply #10 on: November 20, 2020, 11:49:40 AM »
Check the MiCollab client log C:\Users\[user]\AppData\Roaming\Mitel Networks Corporation\MiCollab\log

Maybe this will tell some more.

ok, thanks Mark, i will do a test and look at the logs.

Offline pmhaynes

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 238
  • Country: gb
  • Karma: +11/-0
    • View Profile
Re: Micollab client error
« Reply #11 on: November 26, 2020, 06:37:03 AM »
Hi sunspark
could you tell us more about what doesnt work
what error is displayed?
legacy app on version 8 server?
can the user login via http://FQDN-of-server/ucs/micollab (certificate must be trusted fro this to work, preinstalled cert or third party)
To prove the trusted network setting try to login to /server-manager from the client pc.

have you added a third party certifcate at all ( i know you dont need one internally but you may have added one anyway)

I have had issue where updating the cert works for everything but the 36008 port connections. The old certificate is still used

Good luck
Paul

Offline sunspark

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 986
  • Country: mx
  • Karma: +16/-1
    • View Profile
Re: Micollab client error
« Reply #12 on: November 26, 2020, 10:29:05 AM »
Hi sunspark
could you tell us more about what doesnt work
what error is displayed?
legacy app on version 8 server?
can the user login via http://FQDN-of-server/ucs/micollab (certificate must be trusted fro this to work, preinstalled cert or third party)
To prove the trusted network setting try to login to /server-manager from the client pc.

have you added a third party certifcate at all ( i know you dont need one internally but you may have added one anyway)

I have had issue where updating the cert works for everything but the 36008 port connections. The old certificate is still used

Good luck
Paul

Hi paul , i'm trying to deploy the micollab client V8 .
i'm able to log in my serverhostame/server-manager from the client subnet.
to deploy the client I double click on the mitel logo, then I enter the fqdn of my server + login / password, then I have the error 41 ( the user account can t be imported because the client has no access to micollab client service server.Please check your network connection and if the problem persists please contact your administrator.The access could be limited due to firewall on the corporate network.the phone must be able to reach the tcp port 36008 on the micollab server).

In my case , with TNA : the 36008 is OK
i have no firewall between the subnet client ; and the micollab server subnet.
in the micollab server , i, the networks form i accept all subnet.
the pc firewall already desactived.

in the micollab client Logs :

 sendDiagnosticsEmail: Error with MiCollab Client Deployment - Code : 41

<I/deployu> applyBtnClick(MANUAL_LOGIN) attempting self deployment
<I/deployu> importUser() trying to deploy the user from manually entered credentials
<E/statuses> Comms failed with HTTP code 0 for com.mitel.ucs.ws.model.GetAccountInfo/getAccountInfo, POST https://myserverhostname/ucs/json/JsonServlet
<E/userInfo> Failed to get account info
<W/deployu> applyBtnClick(MANUAL_LOGIN) self deployment failed
<E/deployu> importUser.validateData() legacy client user account found but the account isn't deployed.





 

Sitemap 1 2 3 4 5 6 7 8 9 10