Quantcast
Viewing all articles
Browse latest Browse all 2021

CEM clients to try and fail communication to alternate NS

I need a solution

All clients are external CEM on HTTPS Persistant connection or were.  some are upgraded to 8.5 RU2 some are still at 8.5

We have 3 Internet gateways setup.  They all have the first FQDN:443 in them with the certs.  The clients had been communicating fine. 

I have tried using RAAD but since they are not on the network and not pingable by network I cannot reach them without some type of RDP.

Problem:

in the communication profile I appended to the first fqdn:443;another.domain.com

I hit the save button and many of the CEM clients started using the another.domain.com FQDN as their NS.  This was very unexpected.

But the switch happened almost immediately.

I took out the appended FQDN and saved.  Of course the clients did not revert back.

I did take a look at one of the clients and it has both server names listed but using the wrong one.

Q: Will the client revert back to the original FQDN for the NS? if so, how long to wait.

Q if Clients will not revert back on there own what if anything can be done remotely to get them to revert back.

0

Viewing all articles
Browse latest Browse all 2021

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>