> > > I`m running Linux on a 100mb network, isolated fom the exterior by a
> > > gateway (MS, I think).
> >
> > A gateway, or a proxy?
>
> It's MS Proxy Server.
Does this use SOCKS, or some proprietary MS protocol? If it's the
former, you will be able to get some things to work. If it's the
latter, then you may have a hard time getting Linux programs to talk
to it.
> > > I`ve setted the default route to the IP of the gateway.
> >
> > This is sufficient if the `gateway' is a gateway, but not if it's a
> > proxy.
>
> I think MS Proxy server acts like both of them, because when I boot up my
> machine in NT I can ssh, telnet an *JDBC* outside. With ftp and http there
> is no problem, because the browser is configured, but everything else fails.
If applications need to be configured to use the proxy, then you can
only use applications which know how to use the proxy.
> Should I point out some specific port on the gateway, or giving the IP
> address is just enough?
If it's a SOCKS proxy, then you will need to use applications which
understand SOCKS (Netscape does, Lynx can be configured to, other
programs may need to be patched). I recall there being a version of
libc which provided automatic SOCKS support, but I don't recall any
details.
-- Glynn Clements <glynn@sensei.co.uk> - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.rutgers.edu