• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

IIS double login problem

A

Alphathree33

Platinum Member
Hello Everyone,

The company I work for is concerned about a double login problem that all of our users are facing.

Essentially we're running two external web servers. One for somedomain.mycompany.com and another for someotherdomain.mycompany.com.

Most users will go to somedomain, log in, do some things, and then eventually end up on someotherdomain where they will be again required to log in.

Has anyone had experience with this before? Is there anything we can do in the way of setting the servers to "trust" one another -- or any other IIS-level configurations?

Or, would a server upgrade accomplish anything? We're currently running NT4/IIS4 on one server and W2K/IIS5 on the other. We could potentially upgrade to W2K3/IIS6 on both servers if there were a basis for it.

Thanks,
Alphathree33 🙂
 
Essentially we're running two external web servers. One for somedomain.mycompany.com and another for someotherdomain.mycompany.com.
Click to expand...
I guess, you don't really mean different domains, just differently named web servers, because the domain is the same: mycompany.com.
Anyway, from what you said, I understood that web user would always come in to the website hosted on, let's say, SERVER-1, which would raise NT challenge response, they would login, and perform some actions. Those actions, as part of their structure, to be completed would redirect the user to a totally different website, hosted on SERVER-2. Which would also raise the same NT challenge response. If this scenario basically summarizes your web application architecture, then you have no issue of "trust" between the two servers and no updates will solve it for you. What will solve this case without any updates is:
instead of redirecting the user to a totally different website, within the first website create a virtual directory, select it as a directory located on a different computer on the network. If that second website has any global variables declared (i.e. global.asa), create an application within the virtual directory (it's just a push of a button, nothing major). This way, the user will never leave the main website, and, therefore his/her login credentials will not be discarded, but will, rather, be executing a separate application, a subset of the same website.

Good luck 🙂
Let me know if you have any ???
 
That is an accurate description. Indeed, I meant to say sub-domains not domains.

Anyway, I'm looking into your solution. I'll let you know if we make any progress.

(In the mean time I've been toying with Windows Server 2003 on a test box 🙂)
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top