Windows 7 Credential Manager and ntlm proxy authentication untrusted domain

Hello experts

I work in an organisation where we have our own local AD and have our upstream internet provided through another section of the organisation complete seperate to us with a totally separate AD with no trust between the two and there will never be one implemented.

Our local AD username and passwords generally match the upstream ones in our parent companies AD environment but we have different domain names. Our parent company has an authenticated proxy whereby windows credential manager has been happily working and supressing the need for the end users to enter logon credentials to the web browsers when we open them until our parent company changed to an NTLM proxy.

Since they implemented the NTLM proxy all users are now prompted to logon and have to remember to put @otherdomain on the end and even though windows credential managers saves the details it prompts every time we open the browser still so its pointless it offering to save the credentials. I'm hoping there is a way to fix it so we suppress the proxy logon prompts again using credential manager or some other fix in windows. Is there a way anyone can suggest for me to somehow automatically submit a username with @otherdomain for the proxy logon for the web browsers ?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JohnBusiness Consultant (Owner)Commented:
Talk to the upstream people. So far as I know, if their proxy prohibits saving passwords there is not much you can do. I see this from time to time and must remember a frequent password or keep my passwords in a password manager for ready access.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
JarrodAuthor Commented:
I don't think its so much the prohibit it its because we are in a different domain, if I use a non domain joined device credential manager seems to work ok, I would guess its my device auto submitting my domain name and it being boucned
JohnBusiness Consultant (Owner)Commented:
It has nothing to do with being a domain. Some web sites will not let you store passwords either. It depends.

I would ask the upstream people for their comments on this. That is what I would do.
JarrodAuthor Commented:
I was able to get one step closer by adding a upn suffix that matches our parent company and then using it with our user accounts, our only problem is when the users passwords don't match it causes a lockout in ad for the user. So whilst I couldn't find any method to tell the browser which domain name to submit with the username I did find a potential workaround
JohnBusiness Consultant (Owner)Commented:
So how do you wish to close this question if I have assisted you?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 7

From novice to tech pro — start learning today.