micollab client error

[sunspark]

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

 

[brewski6666]

try to add the subnet 192.168.1.0 to the trusted networks list on your Micollab server (usually, this the main cause for many communication issue)

 

[sunspark]

the 192.168.0.0 already accepted

 

[Billz66]

from pc in 192.168.2.x
can you ping micollab server
can you ping fqdn

what does the deployment profile have set ( names or IP?)
can they all be pinged

If I never did anything I'd never done before , I'd never do anything.....

 

[sunspark]

From 192.168.2.0 i can ping both ip and fqdn. And resolve the fqdn correctly.

Il the profile deployment i tried both ip and fqdn, same result

 

[sunspark]

any other suggestion ?

 

[SNJQuintin]

Hi there. The question I would have, is on a device in the 192.168.1.x subnet, can you ping the 192.168.2.10 system? If not, are you sure you have your netmask correct on either the pbx, or the device you are pinging from?

Quintin

 

[sunspark]

yes from 1.x i can ping 2.10 ,

 

[ADB100]

From the workstation try and telnet to the MiCollab server's FQDN on TCP/36008 - this is the web-portal as I recall.
It could be the local firewall on the PC maybe? Have you disabled it to test?
When you say 192.168.0.0 is in the trusted networks - is it definitely there with a 16-bit mask (255.255.0.0)?

Other than that, logs and Wireshark...

 

[SNJQuintin]

Then what ADB100 said

Hope you figure it out...sounds like a mystery

 

[Joe King]

have you added trusted networks on the MiVB MSL