Proxy authentication problems for local, non-domain account
Posted on 2007-07-24
When I login to my account which is defined on our corporate domain I find no problem connecting any software to the Internet after configuring it to go through our HTTP proxy, but when I login to an account that only exists locally on my PC I have to provide my domain user name and password to any proxy definition besides the IP and port, and here I encounter two problems:
1. Like the case in FlashGet, it keeps telling me that authentication failed on the proxy despite the fact that I provided the right values (I tested them successfully on other software like NOD32).
2. Some software just don't allow you to enter user name and password to proxy definition (the connection won't go of course)
Now my question is: isn't there a way to tell Windows that when any software tries to connect to the proxy the authentication credentials should be supplied automatically along with the proxy definition (IP and port)? Did anybody experienced the same situation I face with FlashGet and can explain why it's unable to authenticate against the proxy?