It appears that the port number for yahoo messenger has changed. While windows clients don't have a problem, the linux client has the port number written in its .ymessenger/preferences file
Change 5050 to 23 in there.
Same is true for everybuddy - change in the preferences window, or in .everybuddy/prefs
gaim too probably.
Philip
On Wed, Nov 13, 2002 at 04:31:08PM +0530, Philip S Tellis wrote:
It appears that the port number for yahoo messenger has changed. While windows clients don't have a problem, the linux client has the port number written in its .ymessenger/preferences file
Change 5050 to 23 in there.
Same is true for everybuddy - change in the preferences window, or in .everybuddy/prefs
gaim too probably.
??
23 is telnet.
Is this you Philip, or some forged mail??
On Wed, Nov 13, 2002 at 05:46:23PM +0530, Philip S Tellis wrote:
On Wed, 13 Nov 2002, Ravindra Jaju wrote:
23 is telnet.
Is this you Philip, or some forged mail??
yes, it's me, yes, 23 is telnet. my yahoo won't work on 5050, but it works on 23.
strange! really strange.
how did you "guess" 23 when things stopped working? clues please!
On Wed, Nov 13, 2002 at 06:23:52PM +0530, Philip S Tellis wrote:
On Wed, 13 Nov 2002, Ravindra Jaju wrote:
how did you "guess" 23 when things stopped working? clues please!
man netstat - then realise that netstat works on other platforms too.
you mean to say that the application itself started to connect to port 23? ymessenger or libyahoo?
On Wed, 13 Nov 2002, Ravindra Jaju wrote:
you mean to say that the application itself started to connect to port 23? ymessenger or libyahoo?
yahoo messenger on windows connected automatically to port 23. ymessenger on linux doesn't, and afaik, none of the other linux clients do either, although almost all are configurable.
Although, at this point i'm inclined to believe that it's a firewall thing - at my end, and that the yahoo clients and servers have a smart workaround.
I'm guessing here, but it seems plausible.
Yahoo has a few servers for Yahoo messenger only. All they have to do, is have ipchains do port forwarding for all ports to port 5050. That way, a client can connect on any port and still work.
Ok, maybe they don't do all ports (I'm not going to do a port scan), but well known ports is a good gamble.
Firewall administrators may block outgoing packets on many ports, but ports like 80, 23, 25, 110 need to be kept open.
The client just needs to cycle through these if 5050 fails - the same way it cycles through host names ({scsa,scsb,scsc}.msg.yahoo.com)
Thoughts.
Philip
If any of you were using everybuddy behind a firewall, you may be interested in knowing that a new CVS RPM is out. It is at http://db.ilug-bom.org.in/Applications/everybuddy/
In this version, the yahoo module does automatic port cycling if it cannot connect on port 5050.
libyahoo2 has these changes in CVS if anyone is interested. (http://libyahoo2.sf.net/)
NOTE: This cycling is handled in the lib. If you link against it, you do not need to change your application at all.
Philip
On Wed, 13 Nov 2002, Philip S Tellis wrote:
It appears that the port number for yahoo messenger has changed. While windows clients don't have a problem, the linux client has the port number written in its .ymessenger/preferences file
Change 5050 to 23 in there.
On further investigation, this could also be a firewall issue. If your firewall blocks port 5050, you can connect on port 23. Few firewalls block port 23 going out.
"Philip" == Philip S Tellis <Philip> writes:
Philip> It appears that the port number for yahoo messenger has Philip> changed. While windows clients don't have a problem, the Philip> linux client has the port number written in its Philip> .ymessenger/preferences file
Philip> Change 5050 to 23 in there.
Philip> Same is true for everybuddy - change in the preferences Philip> window, or in .everybuddy/prefs
Philip> gaim too probably.
Gaim's working just fine without any config changes. Unless it did something automatically which I'm not aware of.
-- Raju