You’re offline. This is a read only version of the page.
3,877
I've been trapped by the strange issue for many days...
I installed the CRM 4.0 on the server without IFD firstly. It works well, and the client can use the "on Premise" authentication strategy to access it("crm.amt.com.cn").
Later, I tried to use the IFD configuration tool to enable the IFD follow the steps in the doc "setup scenarios", I set the IFD App Root Domain and IFD SDK Root Domain to "amt.com.cn", AD App Root Domain and AD SDK Root Domain to AMTCRMServer:5555, and keep the IFD Internal Network Address and Subnet Mask empty, and the unique organization is "org". The DNS check always failed with "DNS Could Not Resolve amt.com.cn". Why the "org.amt.com.cn" was not checked?
I ignored the DNS check error, and went on creating the DNS alias "org" which points to the "crm.amt.com.cn". Finally, I used the "org.amt.com.cn" to access it. It seems that the IFD doesn't work, and the authentication strategy is still "on premise".
Is there anyone can tell me how to config the IFD correctly? It's really appreciated.
*This post is locked for comments
I have the same question (0)
althought I'm having issues myself with IFD..the one thing that you might want to add is the internal network address and subnet mask. (try your server or lan IP with the subnet) then test your dns entry.
I was able to get past this portion...however i'm having issue with the webaccess portion that's not in great detail on how to go about the basics of getting the page over http (in the ms IFD tool doc).
I purchases a domain from my ISP with the company name, set up my asa to allow communications outside/in...set up ifd...I can get the sign on page locally but not external over http. (???) weird. I'm sure i'm missing or over looking something...just not sure what that something is.
Share
Report
All responses (
Answers (
