ConfigCID.exe changes

Hello JFC,

thanks for the details (although I'm still struggling to figure out your setup). I'll summarize what I understand so far and please correct me where I'm wrong:

• you have "just" the management server with one CID
• the CID is also published by IIS
• the server is on the internal LAN and you want outside clients to be manageable (you want them to be able to communicate with the server via RMS)
• you do not use a message relay(?) but you are port-forwarding a public IP for your management server

Coincidentally Jak has posted this great summary - while it might not exactly apply to your situation it is worth reading and perhaps helps to disentangle your problem.

As said, there are IMO distinct but not independent issues which have to be addressed individually but with the whole in mind:

1. Downloading from the WebCID: the catalogue/SDDS error is inconsequential. What we need is "the other" error which should be logged shortly after a line containing: CIDUpdate(SyncProduct.Start): RMSNT, http://public_ip:2221 .... Can't say what it could be. If there's indeed only the one default CID which is also published I'd rather assume a MIME-type issue than an inconsistency in the CID (as in that case UNC updates should encounter an error as well).
2. ConfigCID.exe: If it does not work then the clients will not be able to pick up the changes to mrinit.conf. BTW: The "outside" clients are not yet managed, are they? But before trying to make it work there's ...
3. ... last but not least the (intended) configuration: Wondering if it really works this way (using an IP for hostname_in_ior). If you open the Network Communications Report on a LAN client - what's in there for Parent addresses and Current parent address?

Christian

Hello JFC,

thanks for the details (although I'm still struggling to figure out your setup). I'll summarize what I understand so far and please correct me where I'm wrong:

• you have "just" the management server with one CID
• the CID is also published by IIS
• the server is on the internal LAN and you want outside clients to be manageable (you want them to be able to communicate with the server via RMS)
• you do not use a message relay(?) but you are port-forwarding a public IP for your management server

Coincidentally Jak has posted this great summary - while it might not exactly apply to your situation it is worth reading and perhaps helps to disentangle your problem.

As said, there are IMO distinct but not independent issues which have to be addressed individually but with the whole in mind:

1. Downloading from the WebCID: the catalogue/SDDS error is inconsequential. What we need is "the other" error which should be logged shortly after a line containing: CIDUpdate(SyncProduct.Start): RMSNT, http://public_ip:2221 .... Can't say what it could be. If there's indeed only the one default CID which is also published I'd rather assume a MIME-type issue than an inconsistency in the CID (as in that case UNC updates should encounter an error as well).
2. ConfigCID.exe: If it does not work then the clients will not be able to pick up the changes to mrinit.conf. BTW: The "outside" clients are not yet managed, are they? But before trying to make it work there's ...
3. ... last but not least the (intended) configuration: Wondering if it really works this way (using an IP for hostname_in_ior). If you open the Network Communications Report on a LAN client - what's in there for Parent addresses and Current parent address?

Christian