Both urllib and socket fail to work with MS proxy with 
winsock client install.

urllib's proxy detection will correctly detect the 
existing of the proxy server but fail to work with it. 
It will return an empty page when an read() is issued.

socket will report 1006 winsock error.

Logged In: YES 
user_id=31392

Can you provide more details?  What is MS proxy?  What URLs 
have you tried and what exactly is the response -- headers 
would help?  Under what conditions does socket raise a 
winsock error?

Do socket and urllib work on your platform without the 
proxy?

Logged In: YES 
user_id=44345

Jeremy,

I assigned this to you simply because you commented on 
it.
It was submitted anonymously and the OP never responded 
to
your comment.  I think it should be marked "invalid" and
closed.  Whaddya think?

Skip

Logged In: YES 
user_id=6380

Can you see if the patch from SF bug 503031
(http://www.python.org/sf/503031) solves your problem?

Logged In: YES 
user_id=698929

Maybe this hint helps:

The MS proxy apparently uses NT's built-in authorization,
not really the 'basic' authentication as in RFC 2068. The
distributed.net RC5 client suffered from the same problem,
but they managed to work around it. You may find the
solution there.

The MS Proxy is included with MS Exchange server.

Logged In: YES 
user_id=6380

That's a good hint, but nobody here has access to MS
Exchange server to test this, nor do we have time to
reverse-engineer distributed.net code.

So I'm closing this bug as WON'T FIX -- the OP has had half
a year to respond.

If you have a patch, please upload to a new patch tracker issue.