PDA

View Full Version : unable to read- gaim



bhikumhatre007
29th September 2005, 05:50 PM
my gaim was working fine till today evening. now its suddenly started giving this error-

unable to read.

i am using 10.3.100.148:8080 (this is the proxy server on our lan which supports 5050 tunneling)

can someone help me out plz?

multescugeorge@
29th September 2005, 05:53 PM
Proxy server settins changed?
I had some succes with nasty firewalls by using port 25 instead of 5050. Could work.

bhikumhatre007
29th September 2005, 05:54 PM
how to change that port?

multescugeorge@
29th September 2005, 06:00 PM
Accounts->Modify account (select your account) ->Show more options->Pager Port..........
Hope it works for you.

bhikumhatre007
29th September 2005, 06:01 PM
k, which port should i give? should i nmap or something to know that port?

bhikumhatre007
29th September 2005, 06:05 PM
still unable to read, what kinda error is that any idea?

multescugeorge@
29th September 2005, 06:07 PM
If you like.
I used port 25 on a friend's computer to get gaim to conect to yahoo. That network had all ports filtered except 80, 25 and a few others.
Does port 25 work you?

bhikumhatre007
29th September 2005, 06:08 PM
its not working...thats why i asked u how do i find out which ports are filtered and all?

bhikumhatre007
29th September 2005, 06:09 PM
its not working. thats why i asked u how do i find out which ports are filtered and all?

multescugeorge@
29th September 2005, 06:11 PM
Anyway, try nmap to see if the proxy server settings changed. Could the proxy be down?.

bhikumhatre007
29th September 2005, 06:14 PM
proxy is not down. also, if 5050 is blocked then it shold say that as the connecting problem right?

this is the nmap result.
nmap 10.3.100.148(The 1657 ports scanned but not shown below are in state: closed)

PORT STATE SERVICE
21/tcp open ftp
23/tcp open telnet
80/tcp open http
139/tcp open netbios-ssn
443/tcp open https
8080/tcp open http-proxy

Nmap finished: 1 IP address (1 host up) scanned in 0.396 seconds

bhikumhatre007
29th September 2005, 06:18 PM
k, confirmed..this is the lan problem. some problem with 5050 tunneling from our side. :)