locked
External IFD Organization URL issue RRS feed

  • Question

  • I have two environments, a Test and a Production environment.

    Both, my Test & Production, use the same org name since we want to be consistent. So the Org name is our Domain name in both environments.

    Internally, we have no issues so users go to internalprod.domainname.com and internaltest.domainname.com.

    When configuring IFD, the issues is

    Both environments have the same org name and domain name so users hitting either environment go to domainname.domainname.com. How can we differenciate or change the URL to go to prod.domainname.com and test.domainname.com

    Wednesday, August 15, 2012 5:56 PM

Answers

  • You may have to bite the bullet and rename one of your organizations as the orgname.domainname naming convention doesn't appear to be something that is configurable. 

    Jason Lattimer

    Friday, August 17, 2012 12:11 PM
    Moderator

All replies

  • You may have to bite the bullet and rename one of your organizations as the orgname.domainname naming convention doesn't appear to be something that is configurable. 

    Jason Lattimer

    Friday, August 17, 2012 12:11 PM
    Moderator
  • Hi,

    We are having exactly the same problem...did you end up finding a solution?

    Cheers,

    Joe

    Friday, January 31, 2014 6:08 AM
  • Hi,

    Just once go through your scenario.

    you have a production and test server CRM deployments, stated as Internal Production and Internal test organizations . 

    Here you are able to access the CRM internalprod*.domainname.com and internaltest*.domainname.com this is dns pointing to internal ip 192.168.1.8 and 192.168.1.9 

    here you said the two org names are same, then how your DNS is point to correct crm while access in internally ???

     Orgname.domain.com 

    Might be this will work, configure your Production CRM to Orgname.domain.com on default port now configure the IFD.

        Now for test CRM Configure as Orgname.domain.com:555 do a port forwarding to test server and configure IFD on selected port.

    Now when you try to access the CRM externally for production CRM *.domain.com and for test CRM will be *.domain.com on selected port diversion pointing to test server.


    Thanks,

     


    Vinay Kumar.





    Friday, January 31, 2014 7:47 AM
  • Hi Vinay,

    2 environments, Prod and Test. Internally users hit the web servers directly on

    https://crm.domain.com/organization

    and

    https://testcrm.domain.com/organization

    trying to set up IFD for both environments but as the organizations are the same this is my dilemma. Port forwarding might work I will try and get this working.

    Thanks,

    Joe

    Sunday, February 2, 2014 10:44 PM
  • Hi,

    Yes for these i was looking for, crm.domain.com and testcrm.domain.com are the two different host headers pointing selected severs.

    Is your SSL cert is wild card certificate ??

    let me know when you have got this working access CRM externally.

    Thanks,

     

     


    Vinay Kumar.

    Monday, February 3, 2014 7:17 AM
  • Hi,

    have you got solution for your configuration, Are you able to access your CRM externally ????

    I have configured and tested the same configuration with same domain name and same organization with different port, its working with port Forwarding.

    EXP : https://cap.test.com:444 ( CRM 2011 Deployment) and https://cap.test.com:81 ( CRM 2013 Deployment)

             

    Thanks,


    Vinay Kumar.



    Wednesday, February 5, 2014 7:42 AM