Some senseless babbling from Lee Aroner to Mike Ruskai
on 02-15-98  12:28 about SOCKS problems...
 LA> So far as I can see, one of the weaknesses of the SOCKS system is 
 LA> that it seems to *require* a DNS server that exists on or links 
 LA> to the outside of the lan.
SOCKS v5 does host lookups on the server side, obviating the need for a DNS 
inside the LAN.
 LA> My guess is your local bind is the problem. In order to get 
 LA> outside the lan, SOCKS needs to be addressing the external DNS 
 LA> server, not your local one.
That wasn't the case.  The name server was doing lookups just fine.  The 
machine had no problem resolving addresses.  The problem turned out to be a 
route statement in the SOCKS server config file, which the documentation 
was extremely vague about needing.
 LA> May I suggest trying IGATE102?
 LA> It's free for a single connection at a time and, despite the 
 LA> really crappy docs, works fairly well. If you do try it, bear in 
 LA> mind that the default POP3 proxy he supplies requires a client 
 LA> that has specific support for a proxy. You're probably best off 
 LA> to delete his POP3 and use a Mapped Link instead.
I found that and tried it out.  Using the Web proxy, and mapped links for 
mail and news, it did work, but it was as slow as hell, especially the 
mapped links.  SOCKS5 (now that it's working), is very nearly transparent 
concerning throughput.  
 LA> Also, SocksCap works...but adds an unwelcome additional measure 
 LA> of instability to Win95: Better to configure mapped links for 
Explain this.
 LA> POP3, News and Time, if you need em, and forego SocksCap. 
 LA> Netscape will work perfectly if you configure it to use the HTTP 
 LA> and Socks proxies as recommended in the IGate docs.
Yes, but it's SLOW.  I've not noticed any *additional* instability as the 
result of using SocksCap, either.
Mike Ruskai [Team OS/2]
thanny@home.com
... Existence is not only temporary, but also pointless.
___ Blue Wave/QWK v2.20
--- Renegade v5-11 Exp
---------------