This is an odd one as we are not having a problem with the DNN install on the same server. Our IIS server is in the same forest domain as our users. Our remote offices are trees of that forest. When one of our users in a tree of that forest tries to log in, they are able to authenticate and browse into the project, but not able to see the "New Issue" button.
Their screen shows them logged in, and the project is public. Other users that are in the main forest domain are able to create new tickets with out being added to the public project.
I'm not sure what can cause this as the DNN portion of our site works find for them. I am not a network administrator so if you have suggestions, please include a description on how to do it. And our IT is working at a skill level of the mid 90's so they will probably need that too.
Their screen shows them logged in, and the project is public. Other users that are in the main forest domain are able to create new tickets with out being added to the public project.
I'm not sure what can cause this as the DNN portion of our site works find for them. I am not a network administrator so if you have suggestions, please include a description on how to do it. And our IT is working at a skill level of the mid 90's so they will probably need that too.