Ever since beta4, I have been unable to connect to a jabber server that my work has in place (Comes up with a "Read Error" when you try and login). If I run Gaim beta3, it will connect fine (Or a different IM client works as well).
It's set up to "Force old (Port 5223) SSL" and the connection port is set to use port 5223 as well.
It's not that big of a deal (Currently using Pandion to get access to the jabber server and gaim for the rest of my IM connections), but I haven't seen anyone else having this issue and thought I'd say something since beta5 is out and it still is not connecting.
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I too am having similar issues. Not sure if it started in Beta 4 but it definitely an issue in beta 5. I had to rolled back to beta3 in my case.
My work runs the Sun Communications Server that is jabber based. In beta 3 and previous versions there is a TLS setting on the Advanced tab. It's missing on in Beta 5. My work requires that it be checked to connect to our jabber server
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The checkbox that was removed was a 'Require TLS' checkbox which didn't actually do anything, that is it was never hooked up to any actual functionality. So the removal of that checkbox will not have affected anything. Jabber supports two ways of doing SSL connections, the old way which uses port 5223 does SSL first and then a jabber connection, the new way which uses the standard port 5222 does a preliminary jabber connection, negotiates the use of SSL, encrypts the connection and then does the primary jabber connection. gaim still supports both of those methods, If 'Force old (port 5223) SSL' is checked than the 'Port' entry box needs to say 5223 and the server needs to be listening on port 5223. gaim should always negotiate the new SSL method when it can. Both of you should get the Debug Window output from your connection attempts and post them here, that way something can be figured out. The thing to note about all of this is that gaim will silently fail to use SSL if gaim was not built with SSL support, so if either of you built beta 5 from source and didn't build the previous versions it is important to check that gaim actually have SSL support, the bottom of the About dialog will tell you.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That is almost certainly a firewall problem, the official Google Talk client is likely trying an alternative connection method that gaim is not. If you search google for "Windows socket error #10061" you will see numerous places where people explain that this is a firewall problem, and what that Windows error message means (it means the remote server refused our connection, which in this case means the firewall blocked it). If you are using a firewall of any kind, Norton, McAffee, Windows, etc. Try disabling them entirely, if that doesn't work you can either try following the wingaim FAQ suggestions for opening up the correct ports (which may or may not list jabber, but jabber uses 5222 and possibly 5223) or you can try uninstalling the firewall. (Many of the Windows firewall software doesn't actually fully disable itself when 'Disabled', due in part to how they have to work on Windows in the first place.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have disabled my firewall entirely (WinXP). But the problem is that I certainly have a corporate firewall. How can I prove to my sysadmin (which is not a very bright person) that those ports (5222 and 5223) are closed ? He shows me that gtalk client working OK..
What alternative connection method of gtalk client you're talking about ? I did not find anything like on the net..
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have the exact same symptoms as Jason Sessler who started this thread (I get a "Read Error" attempting to login). The problem is not related to firewall settings. The problem occurred when I installed Gaim beta5. Nothing else was changed. I was previously using Gaim 1.5. I now installed Gaim beta 3 and jabber works once again without changing anything else. ICQ works with all 3 versions of Gaim that I've installed/used. However, there is definitely a problem with Gaim beta5 and jabber.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just tried beta6 with the same result, as previously stated above (Using my default settings). Funny thing is when I connected to our VPN and pointed to the internal IP address of our jabber server w/o SSL (Port 5223) gaim connected and is currently working.
Did the SSL version change between b3 and b4 (5 & 6)?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ever since beta4, I have been unable to connect to a jabber server that my work has in place (Comes up with a "Read Error" when you try and login). If I run Gaim beta3, it will connect fine (Or a different IM client works as well).
It's set up to "Force old (Port 5223) SSL" and the connection port is set to use port 5223 as well.
It's not that big of a deal (Currently using Pandion to get access to the jabber server and gaim for the rest of my IM connections), but I haven't seen anyone else having this issue and thought I'd say something since beta5 is out and it still is not connecting.
Thanks
I too am having similar issues. Not sure if it started in Beta 4 but it definitely an issue in beta 5. I had to rolled back to beta3 in my case.
My work runs the Sun Communications Server that is jabber based. In beta 3 and previous versions there is a TLS setting on the Advanced tab. It's missing on in Beta 5. My work requires that it be checked to connect to our jabber server
The checkbox that was removed was a 'Require TLS' checkbox which didn't actually do anything, that is it was never hooked up to any actual functionality. So the removal of that checkbox will not have affected anything. Jabber supports two ways of doing SSL connections, the old way which uses port 5223 does SSL first and then a jabber connection, the new way which uses the standard port 5222 does a preliminary jabber connection, negotiates the use of SSL, encrypts the connection and then does the primary jabber connection. gaim still supports both of those methods, If 'Force old (port 5223) SSL' is checked than the 'Port' entry box needs to say 5223 and the server needs to be listening on port 5223. gaim should always negotiate the new SSL method when it can. Both of you should get the Debug Window output from your connection attempts and post them here, that way something can be figured out. The thing to note about all of this is that gaim will silently fail to use SSL if gaim was not built with SSL support, so if either of you built beta 5 from source and didn't build the previous versions it is important to check that gaim actually have SSL support, the bottom of the About dialog will tell you.
I used the pre-built executable from sf.net site:
Debug window during login:
account: Connecting to account xxx@xxx.xxx.xxx/Work
connection: Connecting. gc = 01753A08
dnsquery: Performing DNS lookup for xxx.xxx.xxx
dnsquery: IP resolved for xxx.xxx.xxx
proxy: Attempting connection to 2xx.2xx.2xx.1xx
proxy: Connecting to xxx.xxx.xxx:5223 with no proxy
proxy: Connection in progress
proxy: Connected.
jabber: Sending (ssl): <?xml version='1.0' ?>
jabber: Sending (ssl): <stream:stream to='xxx.xxx.xxx' xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams' version='1.0'>
jabber: Recv (ssl)(383): <?xml version='1.0' encoding='UTF-8'?><stream:stream xmlns:stream="http://etherx.jabber.org/streams" xmlns="jabber:client" from="xxx.xxx.xxx" id="64a71e5b" xml:lang="en" version="1.0"><stream:features><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"></starttls><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"><mechanism>PLAIN</mechanism></mechanisms></stream:features>
jabber: Sending (ssl): <starttls xmlns='urn:ietf:params:xml:ns:xmpp-tls'/>
jabber: Recv (ssl)(50): <proceed xmlns="urn:ietf:params:xml:ns:xmpp-tls"/>
jabber: Recv (ssl)(16): </stream:stream>
account: Disconnecting account 00C73460
connection: Disconnecting connection 01753A08
connection: Destroying connection 01753A08
Debugging Information
Plugins: Enabled
SSL: Gaim was compiled with SSL support.
GTK+ Runtime: 2.10.6
Glib Runtime: 2.12.4
Library Support
Cyrus SASL: Disabled
Gadu-Gadu library (libgadu): Internal
GtkSpell: Enabled
GnuTLS: Disabled
Network Security Services (NSS): Enabled
Perl: Enabled
Tcl: Enabled
Tk: Enabled
Using beta 5 on Windows and having problem with gtalk (jabber) account.
Output of "About box":
Debugging Information
Plugins: Enabled
SSL: Gaim was compiled with SSL support.
GTK+ Runtime: 2.10.6
Glib Runtime: 2.12.4
Library Support
Cyrus SASL: Disabled
Gadu-Gadu library (libgadu): Internal
GtkSpell: Enabled
GnuTLS: Disabled
Network Security Services (NSS): Enabled
Perl: Enabled
Tcl: Enabled
Tk: Enabled
Defined a gtalk account.
Gtalk client installed on same computer work OK, so there is no problem with firewall.
Output of debugger window:
account: Connecting to account michael.sternberg@gmail.com/Work
connection: Connecting. gc = 023BC968
dnsquery: Performing DNS lookup for talk.google.com
dnsquery: IP resolved for talk.google.com
proxy: Attempting connection to 66.102.11.125
proxy: Connecting to talk.google.com:5222 with no proxy
proxy: Connection in progress
proxy: Connected.
proxy: Connection attempt failed: Windows socket error #10061
account: Disconnecting account 00CC3178
connection: Disconnecting connection 023BC968
connection: Destroying connection 023BC968
That is almost certainly a firewall problem, the official Google Talk client is likely trying an alternative connection method that gaim is not. If you search google for "Windows socket error #10061" you will see numerous places where people explain that this is a firewall problem, and what that Windows error message means (it means the remote server refused our connection, which in this case means the firewall blocked it). If you are using a firewall of any kind, Norton, McAffee, Windows, etc. Try disabling them entirely, if that doesn't work you can either try following the wingaim FAQ suggestions for opening up the correct ports (which may or may not list jabber, but jabber uses 5222 and possibly 5223) or you can try uninstalling the firewall. (Many of the Windows firewall software doesn't actually fully disable itself when 'Disabled', due in part to how they have to work on Windows in the first place.)
I have disabled my firewall entirely (WinXP). But the problem is that I certainly have a corporate firewall. How can I prove to my sysadmin (which is not a very bright person) that those ports (5222 and 5223) are closed ? He shows me that gtalk client working OK..
What alternative connection method of gtalk client you're talking about ? I did not find anything like on the net..
> What alternative connection method of gtalk client you're talking about ? I did not find anything like on the net..
Change the port to 443 and turn on "Old-style SSL"
-s.
I have the exact same symptoms as Jason Sessler who started this thread (I get a "Read Error" attempting to login). The problem is not related to firewall settings. The problem occurred when I installed Gaim beta5. Nothing else was changed. I was previously using Gaim 1.5. I now installed Gaim beta 3 and jabber works once again without changing anything else. ICQ works with all 3 versions of Gaim that I've installed/used. However, there is definitely a problem with Gaim beta5 and jabber.
I just tried beta6 with the same result, as previously stated above (Using my default settings). Funny thing is when I connected to our VPN and pointed to the internal IP address of our jabber server w/o SSL (Port 5223) gaim connected and is currently working.
Did the SSL version change between b3 and b4 (5 & 6)?
If you're using Wingaim, the SSL libraries were actually upgraded in beta6.
Ok, thanks for the info... Thinking about reinstalling b3 to find out what's happening in that debug window that's not in b4 and up.
Also a correction on my previous post. The non-SSL port should be 5222, not 5223.