Bug 72723 - libsmbcclient reported an internal error
Summary: libsmbcclient reported an internal error
Status: RESOLVED DUPLICATE of bug 66381
Alias: None
Product: kio
Classification: Unmaintained
Component: smb (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-16 01:05 UTC by Alexander Naumann
Modified: 2004-07-27 10:10 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Naumann 2004-01-16 01:05:19 UTC
Version:            (using KDE KDE 3.1.4)
Installed from:    SuSE RPMs
OS:          Linux

Internal error comes up when browsing the 'network' Suse 9.0 client and Windows XP server.Did not specifiy where the problem is, the workgroup could be seen, the windows xp server could be seen, but a click on this server brought up the error. Here's the tcpdump:

linux:~ # tcpdump
tcpdump: listening on eth0
00:38:30.739198 KISTE.microsoft-ds > linux.local.33540: . 1583521538:1583521539(1) ack 1290737910 win 62432 (DF)
00:38:30.739251 linux.local.33540 > KISTE.microsoft-ds: . ack 1 win 7504 <nop,nop,sack sack 1 {0:1} > (DF) [tos 0x10]
00:38:31.505479 linux.local.32786 > 192.168.2.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST (DF)
00:38:31.505676 KISTE.netbios-ns > linux.local.32786: NBT UDP PACKET(137): QUERY; POSITIVE; RESPONSE; UNICAST
00:38:31.779415 linux.local.32786 > KISTE.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; UNICAST (DF)
00:38:31.779573 KISTE.netbios-ns > linux.local.32786: NBT UDP PACKET(137): QUERY; POSITIVE; RESPONSE; UNICAST
00:38:31.780093 linux.local.33540 > KISTE.microsoft-ds: P 1:5(4) ack 1 win 7504(DF) [tos 0x10]
00:38:31.780172 linux.local.33540 > KISTE.microsoft-ds: P 5:135(130) ack 1 win 7504 (DF) [tos 0x10]
00:38:31.780277 KISTE.microsoft-ds > linux.local.33540: . ack 135 win 62423 (DF)
00:38:31.780899 KISTE.microsoft-ds > linux.local.33540: P 1:101(100) ack 135 win 62423 (DF)
00:38:31.780918 linux.local.33540 > KISTE.microsoft-ds: . ack 101 win 7504 (DF)[tos 0x10]
00:38:33.483961 arp who-has 192.168.2.3 tell 192.168.2.1
00:38:33.485146 arp who-has 192.168.2.1 tell linux.local
00:38:33.485673 arp reply 192.168.2.1 is-at 0:4:e2:3b:45:b4
00:38:33.485691 linux.local.32786 > www-proxy.B1.srv.t-online.de.domain:  23630+ PTR? 3.2.168.192.in-addr.arpa. (42) (DF)
00:38:33.539286 www-proxy.B1.srv.t-online.de.domain > linux.local.32786:  23630NXDomain 0/1/0 (119)
00:38:33.539578 linux.local.32786 > www-proxy.B1.srv.t-online.de.domain:  23631+ PTR? 1.2.168.192.in-addr.arpa. (42) (DF)
00:38:33.594486 www-proxy.B1.srv.t-online.de.domain > linux.local.32786:  23631NXDomain 0/1/0 (119)
00:38:33.594799 linux.local.32786 > www-proxy.B1.srv.t-online.de.domain:  23632+ PTR? 1.100.5.217.in-addr.arpa. (42) (DF)
00:38:33.651388 www-proxy.B1.srv.t-online.de.domain > linux.local.32786:  236321/0/0 PTR[|domain]
00:38:33.844890 linux.local.32786 > KISTE.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; UNICAST (DF)
00:38:33.845093 KISTE.netbios-ns > linux.local.32786: NBT UDP PACKET(137): QUERY; POSITIVE; RESPONSE; UNICAST
00:38:33.845685 linux.local.33540 > KISTE.microsoft-ds: P 135:139(4) ack 101 win 7504 (DF) [tos 0x10]
00:38:33.845753 linux.local.33540 > KISTE.microsoft-ds: P 139:265(126) ack 101 win 7504 (DF) [tos 0x10]
00:38:33.845853 KISTE.microsoft-ds > linux.local.33540: . ack 265 win 62415 (DF)
00:38:33.846077 KISTE.microsoft-ds > linux.local.33540: P 101:169(68) ack 265 win 62415 (DF)
00:38:33.846097 linux.local.33540 > KISTE.microsoft-ds: . ack 169 win 7504 (DF) [tos 0x10]
00:38:36.500803 arp who-has 192.168.2.3 tell 192.168.2.1
00:38:40.203484 arp who-has 192.168.2.3 tell 192.168.2.1
00:38:43.034224 arp who-has 192.168.2.3 tell 192.168.2.1
00:38:46.218393 arp who-has 192.168.2.3 tell 192.168.2.1
00:38:49.637938 arp who-has 192.168.2.3 tell 192.168.2.1
00:38:55.644494 arp who-has 192.168.2.3 tell 192.168.2.1
33 packets received by filter
0 packets dropped by kernel
Comment 1 Stephan Kulow 2004-01-16 10:02:04 UTC
the fact that it did a query to the t-online DNS, makes me believe it's your network's fault (btw, you really should give your host a better hostname :)

*** This bug has been marked as a duplicate of 66381 ***