Re: [Plug] telnetting around a firewall

[Kyle Burton <mortis@voicenet.com>]

I seem to remember being able to telnet thorugh an MS proxy -- to do so,
I had to telnet to the proxy machine, login in using some combination of
a user/pass command, and then, once I was authenticated to the MS proxy,
I was able to enter a host address to telnet to and it made the connection
on my behalf.

Same type of thing worked for ftp, though the auth/connection process was
wacked in comparision -- had to do something like:  

ftp proxy_user@external.host.com

Then type in my password to the proxy...I dont' remember, but it only took
a little hackign around to figure out the proxy's syntax for doing this.


k

------------------------------------------------------------------------------
The streets will flow with the blood of the non-beleivers! 
    -- Beavis
mortis@voicenet.com                            http://www.voicenet.com/~mortis
------------------------------------------------------------------------------

On Mon, 25 Oct 1999, Nick R wrote:

> no dice. m$ proxy over here. I'm making some progress w/ the cgi script 
> though. I just need to figure out how to login w/o typing in the password. 
> Like
> su laktar <pass
> but w/o having to put my password in a file called pass
> 
> 
> >From: "Sean R. Cummins" <beaner@Op.Net>
> >Reply-To: plug@lists.nothinbut.net
> >To: Plug <plug@lists.nothinbut.net>
> >Subject: Re: [Plug] telnetting around a firewall
> >Date: Mon, 25 Oct 1999 21:17:08 -0400 (EDT)
> >
> >
> > > Recently I've been spedning some time trying to work around my schools
> > > telnet restrictions so I can use my computer.  There is a firewall in
> > > place which seems to make some telnet connects impossible, while
> > > others work.  I can telnet to my ISP, which runs NT, but my computer
> > > and CCIL both report that the connection was dropped.  I thought this
> > > may have something to do with firewalls and the way the server
> > > interacted with the client, but I don't know.
> >
> >Well, a lot of this depends on exactly what kind of firewall you're
> >dealing with here.  If its a packet filtering or stateful inspection
> >firewall (ie, a firewall that actually routes data at the network layer
> >rather than proxying it at the application layer), you can just tell
> >in.telnetd to run on port 80, like this:
> >
> ># /usr/sbin/in.telnetd -debug 80 &
> >
> >Then just telnet to port 80 of your machine.  To do this in UNIX/Linux,
> >you would just use:
> >
> >$ telnet host 80
> >
> >In Windows, you'd need to run the telnet application specify the port in
> >the connect to window or whatever.
> >
> >This won't work if your school happens to be using a proxy firewall, like
> >MS Proxy server or something like that.
> >
> >- Sean
> >
> >--
> >Sean R. Cummins
> >Lead Network Engineer
> >e-Vend.net Corporation
> >scummins@op.net
> >echo njdsptpgu tvdlt | tr [b-z] [a-y]
> >
> >
> >_______________________________________________
> >Plug maillist  -  Plug@lists.nothinbut.net
> >http://lists.nothinbut.net/mail/listinfo/plug
> >
> 
> ______________________________________________________
> Get Your Private, Free Email at http://www.hotmail.com
> 
> _______________________________________________
> Plug maillist  -  Plug@lists.nothinbut.net
> http://lists.nothinbut.net/mail/listinfo/plug
> 


_______________________________________________
Plug maillist  -  Plug@lists.nothinbut.net
http://lists.nothinbut.net/mail/listinfo/plug