Issues with Cisco Jabber for Windows 7

Hello everyone,

We are having problems to getting Cisco Jabber to work: DirectAccess is using a IPv6 tunnel to connect the client to the internal network it seems Jabber doesnt work with IPV6.

When we configure our DNS name as an external domain... Jabber works fine. This isnt a practical solution because so many internal site are using that domain so we have configured it as a internal domain. That is not working, it seems Jabber has issues detecting an external network when the DA link is active, and it thinks that is a internal network... then it attempts to connect to the internal network and not through the gateway.

Any ideas? Thank you.

July 23rd, 2015 5:49pm

Hi,

If I understand correctly, Jabber is trying to connect through the DirectAccess tunnel instead of connecting to your gateway.

Is Jabber using multiple hostnames to connect to your infrastructure?
ex: 1 internet hostname for external access through your gateway while outside your corporate network and one intranet hostname when the client is inside the corporate network.

Gerald

Free Windows Admin Tool Kit Click here and download it now
July 27th, 2015 8:22am

Hello, Yes that is correct. We have a different hostname when accessing from Internet, and another when inside the corporate network. Thank you.
July 27th, 2015 8:59am

Have you tried to exclude the internal domain name in the NRPT tables?

DirectAccess configuration -> Step3 -> DNS : Create an entry for your internal Hostname without adding the DNS Server Address.

If the laptop is not able to resolve the Internal name while outside your network, it should try to contact the Internet name using IPv4.

Gerald

Free Windows Admin Tool Kit Click here and download it now
July 27th, 2015 9:05am

Yes, and that worked. However it's something not "doable" here, since we have thousands of applications that are part of this same domain... we would have to create individual record for every single URL/application, it would be something hard to manage.

So right now we are trying to find a way to make Jabber work with that, however not going Direct Access... and just using the Internet gateway. Officially Jabber client (currently) does not support IPV6, and we believe this is why it's now working with DirectAccess. So if we could find a way to force Jabber to use always Internet gateway.. we believe that would solve our issue. But Jabber has this "mechanism" where it detects the current network, and it's trying to use the internal DNS when connected through Direct Access.

Thanks again!

July 27th, 2015 9:21am

You dont need to exclude the full domain... Just create an entry for the hostname of your internal jabber server...

Ex: yourdomain.local can use DirectAccess but jabberserver.domain.local can't

Gerald

Free Windows Admin Tool Kit Click here and download it now
July 27th, 2015 9:34am

Thanks Gerald, it's still not working... somehow Jabber does not get connected. I will keep trying and update this once I get news.
July 27th, 2015 8:55pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics