View Full Version : Cant login to any chat program
keziah
2005-05-08, 09:21 PM CDT
I have tried Gaim, Kopete , Yahoo messenger, but wasnt able to connect in any one of them there must be a problem with my fedora,i already diaabled firewall, reinstalled these client , but still unable to connect. pls HELP
shams
2005-05-08, 09:54 PM CDT
can you browse any website?
keziah
2005-05-08, 09:56 PM CDT
yes i i have internet connection
shams
2005-05-08, 10:06 PM CDT
enable dhcp and named in menu -> system sittings -> server settings -> services
keziah
2005-05-09, 02:32 AM CDT
I dont have DHCP or named on the menu
AndyGreen
2005-05-09, 02:56 AM CDT
Not sure how dhcp and named would have helped you anyway.
Best way forward is to try to collect more info on what is happening on the network when you try to connect.
Get to root with su - and run
tcpdump
in a terminal window. Then try to connect, and paste the results of tcpdump in a post here. Ctrl-C will terminate tcpdump.
keziah
2005-05-09, 03:08 AM CDT
17:08:04.284994 IP 192.168.1.126.netbios-ns > 192.168.1.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:08:04.800982 802.1d config TOP_CHANGE 8001.00:0d:bc:2a:ab:40.8018 root 8000.00:01:42:97:7e:00 pathcost 19 age 1 max 20 hello 2 fdelay 15
17:08:05.035410 IP 192.168.1.126.netbios-ns > 192.168.1.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:08:05.224568 NetBeui Packet
17:08:05.224925 IP 192.168.1.202.netbios-ns > 192.168.1.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:08:05.725243 NetBeui Packet
17:08:05.785803 IP 192.168.1.126.netbios-ns > 192.168.1.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:08:06.230185 NetBeui Packet
17:08:06.400533 arp who-has 192.168.1.224 tell 192.168.1.2
17:08:06.400561 arp reply 192.168.1.224 is-at 00:08:a1:55:bf:d5
17:08:06.579604 arp who-has 192.168.2.100 tell 192.168.2.1
17:08:06.579865 IP 192.168.1.224.32788 > dsl.info.com.ph.domain: 28423+ PTR? 1.2.168.192.in-addr.arpa. (42)
17:08:06.597964 IP dsl.info.com.ph.domain > 192.168.1.224.32788: 28423 NXDomain 0/1/0 (119)
17:08:06.735034 NetBeui Packet
17:08:06.803709 802.1d config TOP_CHANGE 8001.00:0d:bc:2a:ab:40.8018 root 8000.00:01:42:97:7e:00 pathcost 19 age 1 max 20 hello 2 fdelay 15
17:08:07.240311 NetBeui Packet
17:08:07.744905 NetBeui Packet
17:08:08.810056 802.1d config 8001.00:0d:bc:2a:ab:40.8018 root 8000.00:01:42:97:7e:00 pathcost 19 age 1 max 20 hello 2 fdelay 15
17:08:08.944578 arp who-has 192.168.1.234 tell 192.168.1.98
17:08:09.431339 IP 192.168.2.100.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:08:10.181232 IP 192.168.2.100.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:08:10.812434 802.1d config 8001.00:0d:bc:2a:ab:40.8018 root 8000.00:01:42:97:7e:00 pathcost 19 age 1 max 20 hello 2 fdelay 15
17:08:10.880474 arp who-has 192.168.1.125 tell 192.168.1.128
17:08:10.931238 IP 192.168.2.100.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:08:11.428129 IP 192.168.2.100.25140 > 192.168.2.200.netbios-ssn: S 539942008:539942008(0) win 65535 <mss 1460,nop,nop,sackOK>
17:08:11.428375 IP 192.168.1.224.32788 > dsl.info.com.ph.domain: 11541+ PTR? 200.2.168.192.in-addr.arpa. (44)
17:08:11.445370 IP dsl.info.com.ph.domain > 192.168.1.224.32788: 11541 NXDomain 0/1/0 (121)
17:08:11.834945 arp who-has 192.168.1.3 tell 192.168.1.22
17:08:11.947787 arp who-has 192.168.1.234 tell 192.168.1.98
17:08:12.427593 IP 192.168.2.100.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
258 packets captured
258 packets received by filter
0 packets dropped by kernel
AndyGreen
2005-05-09, 03:20 AM CDT
Am I missing something? There are no attempts to connect to a remote server in this dump. Are you certain this dump represents the period that you started up Gaim or whatever and tried to connect? Which of these IPs is yours? 192.168.?.?
keziah
2005-05-09, 03:27 AM CDT
192.168.1.224,
here is another,i run tcpdump then try to connect using kopete
17:26:39.390126 IP 192.168.1.224.32814 > dsl.info.com.ph.domain: 55471+ A? scs.msg.yahoo.com. (35)
17:26:39.390677 IP 192.168.1.224.32815 > dsl.info.com.ph.domain: 49588+ AAAA? scs.msg.yahoo.com. (35)
17:26:39.412761 IP dsl.info.com.ph.domain > 192.168.1.224.32814: 55471 9/5/5 CNAME[|domain]
17:26:39.598123 IP dsl.info.com.ph.domain > 192.168.1.224.32815: 49588 1/1/0 (136)
17:26:39.599195 IP 192.168.1.224.46747 > cs12.msg.dcn.yahoo.com.5050: S 444505015:444505015(0) win 5840 <mss 1460,sackOK,timestamp 4715007 0,nop,wscale 2>
17:26:39.599448 IP 192.168.1.224.32816 > dsl.info.com.ph.domain: 52540+ PTR? 139.193.155.216.in-addr.arpa. (46)
17:26:39.625517 IP dsl.info.com.ph.domain > 192.168.1.224.32816: 52540 1/5/5 (252)
17:26:39.690604 IP 192.168.2.87.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:26:39.946487 IP 192.168.2.100.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST17:26:40.441081 IP 192.168.2.87.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
17:26:40.500091 802.1d config 8001.00:0d:bc:2a:ab:40.8018 root 8000.00:01:42:97:7e:00 pathcost 19 age 1 max 20 hello 2 fdelay 15
17:26:40.860988 arp who-has 192.168.1.34 tell 192.168.1.46
17:26:40.861059 arp who-has 192.168.1.58 tell 192.168.1.46
17:26:40.861252 IP 192.168.1.224.32816 > dsl.info.com.ph.domain: 3394+ PTR? 34.1.168.192.in-addr.arpa. (43)
17:26:40.861442 arp who-has 192.168.1.86 tell 192.168.1.46
17:26:40.932313 IP dsl.info.com.ph.domain > 192.168.1.224.32816: 3394 NXDomain 0/1/0 (120)
17:26:40.932555 IP 192.168.1.224.32816 > dsl.info.com.ph.domain: 51068+ PTR? 46.1.168.192.in-addr.arpa. (43)
17:26:40.950634 IP dsl.info.com.ph.domain > 192.168.1.224.32816: 51068 NXDomain 0/1/0 (120)
17:26:40.950767 IP 192.168.1.224.32816 > dsl.info.com.ph.domain: 62814+ PTR? 58.1.168.192.in-addr.arpa. (43)
17:26:40.975449 IP dsl.info.com.ph.domain > 192.168.1.224.32816: 62814 NXDomain 0/1/0 (120)
17:26:40.975748 IP 192.168.1.224.32816 > dsl.info.com.ph.domain: 61134+ PTR? 86.1.168.192.in-addr.arpa. (43)
17:26:40.993659 IP dsl.info.com.ph.domain > 192.168.1.224.32816: 61134 NXDomain 0/1/0 (120)
17:26:41.661125 arp who-has 192.168.1.125 tell 192.168.1.128
17:26:42.499952 802.1d config 8001.00:0d:bc:2a:ab:40.8018 root 8000.00:01:42:97:7e:00 pathcost 19 age 1 max 20 hello 2 fdelay 15
17:26:42.597951 IP 192.168.1.224.46747 > cs12.msg.dcn.yahoo.com.5050: S 444505015:444505015(0) win 5840 <mss 1460,sackOK,timestamp 4718007 0,nop,wscale 2>
17:26:43.175696 IP 192.168.1.126.netbios-dgm > 192.168.1.255.netbios-dgm: NBT UDP PACKET(138)
17:26:43.175935 IP 192.168.1.224.32816 > dsl.info.com.ph.domain: 15856+ PTR? 255.1.168.192.in-addr.arpa. (44)
17:26:43.197131 IP dsl.info.com.ph.domain > 192.168.1.224.32816: 15856 NXDomain 0/1/0 (121)
17:26:43.197317 IP 192.168.1.224.32816 > dsl.info.com.ph.domain: 2152+ PTR? 126.1.168.192.in-addr.arpa. (44)
17:26:43.213872 IP dsl.info.com.ph.domain > 192.168.1.224.32816: 2152 NXDomain 0/1/0 (121)
17:26:43.251128 arp who-has 192.168.1.3 tell 192.168.1.202
17:26:43.251348 IP 192.168.1.224.32816 > dsl.info.com.ph.domain: 27194+ PTR? 3.1.168.192.in-addr.arpa. (42)
17:26:43.268574 IP dsl.info.com.ph.domain > 192.168.1.224.32816: 27194 NXDomain 0/1/0 (119)
17:26:43.268686 IP 192.168.1.224.32816 > dsl.info.com.ph.domain: 8196+ PTR? 202.1.168.192.in-addr.arpa. (44)
17:26:43.304308 IP dsl.info.com.ph.domain > 192.168.1.224.32816: 8196 NXDomain 0/1/0 (121)
17:26:44.056581 arp who-has 192.168.1.234 tell 192.168.1.98
17:26:44.056825 IP 192.168.1.224.32816 > dsl.info.com.ph.domain: 43468+ PTR? 234.1.168.192.in-addr.arpa. (44)
17:26:44.074256 IP dsl.info.com.ph.domain > 192.168.1.224.32816: 43468 NXDomain 0/1/0 (121)
17:26:44.074390 IP 192.168.1.224.32816 > dsl.info.com.ph.domain: 21934+ PTR? 98.1.168.192.in-addr.arpa. (43)
17:26:44.091839 IP dsl.info.com.ph.domain > 192.168.1.224.32816: 21934 NXDomain 0/1/0 (120)
17:26:44.503066 802.1d config 8001.00:0d:bc:2a:ab:40.8018 root 8000.00:01:42:97:7e:00 pathcost 19 age 1 max 20 hello 2 fdelay 15
17:26:46.200644 arp who-has 192.168.1.1 tell 192.168.1.65
17:26:46.200878 IP 192.168.1.224.32816 > dsl.info.com.ph.domain: 7038+ PTR? 1.1.168.192.in-addr.arpa. (42)
17:26:46.218418 IP dsl.info.com.ph.domain > 192.168.1.224.32816: 7038 NXDomain 0/1/0 (119)
17:26:46.218564 IP 192.168.1.224.32816 > dsl.info.com.ph.domain: 32198+ PTR? 65.1.168.192.in-addr.arpa. (43)
17:26:46.235085 IP dsl.info.com.ph.domain > 192.168.1.224.32816: 32198 NXDomain 0/1/0 (120)
17:26:46.505675 802.1d config 8001.00:0d:bc:2a:ab:40.8018 root 8000.00:01:42:97:7e:00 pathcost 19 age 1 max 20 hello 2 fdelay 15
17:26:47.918063 00:0d:bc:2a:ab:58 > 01:00:0c:cc:cc:cc snap ui/C len=35
17:26:47.918756 00:0d:bc:2a:ab:58 > 01:00:0c:00:00:00 snap ui/C len=65
17:26:48.316213 NetBeui Packet
17:26:48.391063 arp who-has 192.168.1.2 tell 192.168.1.224
17:26:48.391314 IP 192.168.1.224.32816 > dsl.info.com.ph.domain: 26918+ PTR? 2.1.168.192.in-addr.arpa. (42)
17:26:48.391651 arp reply 192.168.1.2 is-at 00:11:3b:00:31:c0
17:26:48.409035 IP dsl.info.com.ph.domain > 192.168.1.224.32816: 26918 NXDomain 0/1/0 (119)
17:26:48.508616 802.1d config 8001.00:0d:bc:2a:ab:40.8018 root 8000.00:01:42:97:7e:00 pathcost 19 age 1 max 20 hello 2 fdelay 15
17:26:48.597038 IP 192.168.1.224.46747 > cs12.msg.dcn.yahoo.com.5050: S 444505015:444505015(0) win 5840 <mss 1460,sackOK,timestamp 4724007 0,nop,wscale 2>
17:26:50.511467 802.1d config 8001.00:0d:bc:2a:ab:40.8018 root 8000.00:01:42:97:7e:00 pathcost 19 age 1 max 20 hello 2 fdelay 15
17:26:50.936348 IP 192.168.1.49.netbios-dgm > 192.168.1.255.netbios-dgm: NBT UDP PACKET(138)
17:26:50.936595 IP 192.168.1.224.32816 > dsl.info.com.ph.domain: 12218+ PTR? 49.1.168.192.in-addr.arpa. (43)
17:26:50.958189 IP dsl.info.com.ph.domain > 192.168.1.224.32816: 12218 NXDomain 0/1/0 (120)
17:26:51.453928 IP 192.168.2.100.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST17:26:51.661990 arp who-has 192.168.1.125 tell 192.168.1.128
17:26:52.203500 IP 192.168.2.100.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST17:26:52.514618 802.1d config 8001.00:0d:bc:2a:ab:40.8018 root 8000.00:01:42:97:7e:00 pathcost 19 age 1 max 20 hello 2 fdelay 15
17:26:52.953529 IP 192.168.2.100.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST17:26:52.987042 arp who-has 192.168.1.234 tell 192.168.1.98
17:26:53.403929 arp who-has 192.168.1.224 tell 192.168.1.2
17:26:53.403955 arp reply 192.168.1.224 is-at 00:08:a1:55:bf:d5
17:26:54.455831 IP 192.168.2.100.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST17:26:54.520475 802.1d config 8001.00:0d:bc:2a:ab:40.8018 root 8000.00:01:42:97:7e:00 pathcost 19 age 1 max 20 hello 2 fdelay 15
17:26:55.205513 IP 192.168.2.100.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST17:26:55.455064 IP 192.168.2.100.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST17:26:55.955535 IP 192.168.2.100.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST17:26:56.204561 IP 192.168.2.100.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST17:26:56.523004 802.1d config 8001.00:0d:bc:2a:ab:40.8018 root 8000.00:01:42:97:7e:00 pathcost 19 age 1 max 20 hello 2 fdelay 15
17:26:56.954579 IP 192.168.2.100.netbios-ns > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
104 packets captured
104 packets received by filter
0 packets dropped by kernel
AndyGreen
2005-05-09, 03:35 AM CDT
17:26:39.599195 IP 192.168.1.224.46747 > cs12.msg.dcn.yahoo.com.5050: S 444505015:444505015(0) win 5840 <mss 1460,sackOK,timestamp 4715007 0,nop,wscale 2>
...
17:26:42.597951 IP 192.168.1.224.46747 > cs12.msg.dcn.yahoo.com.5050: S 444505015:444505015(0) win 5840 <mss 1460,sackOK,timestamp 4718007 0,nop,wscale 2>
...
17:26:48.597038 IP 192.168.1.224.46747 > cs12.msg.dcn.yahoo.com.5050: S 444505015:444505015(0) win 5840 <mss 1460,sackOK,timestamp 4724007 0,nop,wscale 2>These are the only relevant packets, three attempts to contact yahoo with nothing coming back. Is it possible that something between your machine and yahoo is dropping connection attempts on, or responses from, port 5050? For example a router on your site, or some policy from dsl.info.com.ph?
keziah
2005-05-09, 03:41 AM CDT
the weird thing is i can use my yahoo using windows , before i can use gaim suddenly it just wont work, i did not change any settings. is it possible i am infected with worms or viruses i dont have any protection installed on my pc.
AndyGreen
2005-05-09, 03:45 AM CDT
No, it is unlikely you are infected with anything. For sure there is no suspicious traffic coming out of your network.
What is the difference between your Windows machine and the Linux one in terms of network topology? Or is it the same box?
the weird thing is i can use my yahoo using windowsIs that true right now? If not maybe the problem is coming from your ISP. Apparently some ISPs have a "Yahoo box" that handles that traffic separately, maybe that has black smoke coming out of it at the moment.
keziah
2005-05-09, 04:03 AM CDT
that is good news !it is the same box , i am using dual boot,,i dont know about my isp if theyre using any yahoo box.is it wise if i re install my fedora?
AndyGreen
2005-05-09, 04:05 AM CDT
is it wise if i re install my fedora?Nope.
You need to find out if your Windows box is working at the moment for Yahoo. So I would reboot into Windows and try it, then back into Linux and try it. If it worked in Windows and not Linux then I am scratching my head. For sure your Linux box is trying to contact Yahoo but not hearing anything back.
keziah
2005-05-09, 04:09 AM CDT
guess what? youre right theres some problem with my isp, i am now using another one..but the question is i cant use gaim with fedora but with windows i can use my yahoo messenger, thank you very much anyway, you guys make internet a better place..(applause!)
vBulletin® v3.7.3, Copyright ©2000-2008, Jelsoft Enterprises Ltd.