You can get 100% functionality without that. Forward a set of ports to the machine you intend to run ICQ on (assuming you have a simple setup where it's mainly to be run from 1 machine behind the masq). Then set ICQ up to go through a firewall using those specific ports. Voila, filereceive, chat requests, everything works perfectly. -- Frode -----Original Message----- From: Sandy Coyne <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: 28. august 1998 20:24 Subject: Re: [masq] [masq] [masq] ICQ Chat (was: Problem with rc.local) [snip] >In fact, everything except Chat did not work when you said you were not >behind a firewall. You should also not be able to receive incoming messages >unless they are sent through the server. Saying you are behind a firewall >will maximize what works, but it is still not fully functional because of >the restriction inherent in being behind a firewall (that you cannot >receive incoming connections). The best solution, and the only way to >achieve full functionality of ICQ behind a Masq box, is to install a SOCKS5 >proxy server on your Masq firewall. Then you can tell ICQ that you have a >SOCKS5 proxy server and it will work 100%. I was pointed to this answer >some months ago on this very list and my ICQ has worked perfectly ever since. > >HTH, >-- >Sandy Coyne, obviously "A day without sunshine is like >[EMAIL PROTECTED] a day without orange juice" >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] >For daily digest info, email [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For daily digest info, email [EMAIL PROTECTED]
