Sunday, January 13, 2013 10:49 PM
Happy New Year everyone !
New Year and new issues, so here it goes.
basic background of the setup/network:
We have two domains, Production (Prod) and Test, we use the Test domain for testing of all new/software/patches before moving onto Prod. Between the domains are a firewall; which worked fine all these time.
-client - Windows XP sp3 (will be upgrading soon)
Then, some where in November; the Wintel team blasted out Window server 2003 patches (I don't know which ones as it takes them some time to go through the Test first so by the time it makes it to Prod, it could be several months or more) so the date shouldn't reflect that month's release from MS. After the patch, our users experiences authentication issue when they use try to cross-domain.
We have Applications on the Test domain / servers (web app) and user access these resource (via webapp) from their Windows XP pc which is in Prod environment via Internet Explorer. when they do so, it prompts them for the Test domain's authentication which worked fine until the patch(es) were applied.
Now when our users enter their Test id/password, the authentication window disappears for 2 seconds and comes back with ID and Password still filled, if you keep hitting the Ok button, it just keeps bouncing back but it DOES NOT lock the Test domain's ID. After about 5 tries, it will error out in IE. BUT if you copy that error's link and paste it onto another browser, it'll bring to you the correct information/link.
If the user remote desktop into the Test domain's box(es) (server/client), this wouldn't happen.
This is an issue that affects our testing and also all of our users who are not technical.
This is not limited to webapp but are affecting the users the most as everyone is now deploying webapp.
Greatly appreciate your help.
- Edited by Henry828 Sunday, January 13, 2013 10:52 PM