Is there anything special about the Zope environment, which would prevent it from being able to use SOCKS5 in a normal configuration (i.e. using the standard python interpreter and libraries bundled with Zope) on Solaris 8 (Sparc)? I have set up SOCKS5, and am able to get through our socks proxy with a simple "runsocks python" environment. So I know that my SOCKS client config is good, that python is able to go through the SOCKS libs, and that the SOCKS server is working correctly. As a sanity check, I verified that it fails without the "runsocks". When I try changing the "start" script to use "runsocks python z2.py ...", and then use an External Method to talk to a server on the other side of the proxy, it seems to ignore the SOCKS libs and timeout. I have verified that LD_LIBRARY_PATH and LD_PRELOAD are visible in my External Method, that my External Method gets called, and that the SOCKS server is not receiving traffic from my host when the External Method is called. It seems as if the Zope libs are forcing my method to use the builtin libsocket.so.1 instead of the desired libsocks5_sh.so. I could try building a SOCKS-aware version of python's _socket.so module, but it seems like that shouldn't be necessary given that I can successfully use SOCKS from python outside of Zope. Any suggestions? Thanks, Jon __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com