> It seems to be due to a problem in /etc/hosts. Could you please tell me > if you have IPv6 enabled on this machine, and send me (possibly > privately if they contains private information) the contents of > /etc/hosts, /etc/gai.conf and /etc/hostname?
I do not have any IPv6 network devices since I am still using an old network router, switch, etc. How can I check if IPv6 is enabled? If it is enabled, how can I disable it? I have been using the same hosts file for like 3-4 years in this Debian installation. Here are the details: # more /etc/hosts 127.0.0.1 localhost.localdomain localhost ANTian 127.0.1.1 ANTian.fauna ANTian 192.168.0.46 ANTian 192.168.0.82 Harvester # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts I tried deleting my /etc/hosts (kept a backup), and I was able to get into my shares except access one (my own account's home directory -- same account name and password in updated XP Pro. SP3 and Debian's Samba). Then, I tried restarting Samba service, but it got stuck for a minute during its restart (note the missing period, the period came up after a minute): # /etc/init.d/samba restart Stopping Samba daemons: nmbd smbd. Starting Samba daemons: nmbd smbd I tried again after deleting Samba's logs to see what's up in logs: # cat log.nmbd [2009/03/15 05:15:52, 0] nmbd/nmbd.c:main(850) nmbd version 3.3.1 started. Copyright Andrew Tridgell and the Samba Team 1992-2009 # cat log.smbd [2009/03/15 05:15:52, 0] smbd/server.c:main(1260) smbd version 3.3.1 started. Copyright Andrew Tridgell and the Samba Team 1992-2009 [2009/03/15 05:16:22, 0] printing/print_cups.c:cups_connect(103) Unable to connect to CUPS server localhost:631 - Interrupted system call [2009/03/15 05:16:52, 0] printing/print_cups.c:cups_connect(103) Unable to connect to CUPS server localhost:631 - Interrupted system call Then, tried to connect to my home directory's share and Explorer told me "\\192.168.0.46\AntsStuff is not accessible. You might not have permission to use this network resource..." "Incorrect function." Logs showed: log.__ffff_192.168.0.82 was empty (0 byte). # cat log.harvester [2009/03/15 05:20:43, 0] smbd/map_username.c:map_username(141) can't open username map /etc/samba/smbusers. Error No such file or directory [2009/03/15 05:20:44, 1] smbd/service.c:make_connection_snum(1103) harvester (::ffff:192.168.0.82) connect to service AntsStuff initially as user ant (uid=1000, gid=1000) (pid 14778) Weird. It can't find smbusers file. # ls /etc/samba/smbusers ls: cannot access /etc/samba/smbusers: No such file or directory locate smbusers command found nothing. # ls -all /etc/samba/ total 42 drwxr-xr-x 2 root root 1024 2009-03-14 18:40 . drwxr-xr-x 146 root root 10240 2009-03-15 05:02 .. -rw-r--r-- 1 root root 8 2007-07-01 06:27 gdbcommands -rw-r--r-- 1 root root 8566 2009-03-14 18:40 smb.conf -rw-r--r-- 1 root root 8566 2008-12-31 12:31 smb.conf-backup -rw-r--r-- 1 root root 11917 2008-12-24 12:50 smb.conf.ucf-dist I reran smbpasswd -a command to readd my Samba account, but that still didn't fix the problem. I still don't see /etc/samba/smbusers file. Something is weird here. :( /etc/samba.conf showed this for my account that is giving me errors (other shared folders seem fine now with no hosts file): [AntsStuff] path = /home/ant comment = Ant's Home Folder on ANTian box. writable=yes browseable=yes # cat /etc/gai.conf # Configuration for getaddrinfo(3). # # So far only configuration for the destination address sorting is needed. # RFC 3484 governs the sorting. But the RFC also says that system # administrators should be able to overwrite the defaults. This can be # achieved here. # # All lines have an initial identifier specifying the option followed by # up to two values. Information specified in this file replaces the # default information. Complete absence of data of one kind causes the # appropriate default information to be used. The supported commands include: # # reload <yes|no> # If set to yes, each getaddrinfo(3) call will check whether this file # changed and if necessary reload. This option should not really be # used. There are possible runtime problems. The default is no. # # label <mask> <value> # Add another rule to the RFC 3484 label table. See section 2.1 in # RFC 3484. The default is: # #label ::1/128 0 #label ::/0 1 #label 2002::/16 2 #label ::/96 3 #label ::ffff:0:0/96 4 #label fec0::/10 5 #label fc00::/7 6 #label 2001:0::/32 7 # # This default differs from the tables given in RFC 3484 by handling # (now obsolete) site-local IPv6 addresses and Unique Local Addresses. # The reason for this difference is that these addresses are never # NATed while IPv4 site-local addresses most probably are. Given # the precedence of IPv6 over IPv4 (see below) on machines having only # site-local IPv4 and IPv6 addresses a lookup for a global address would # see the IPv6 be preferred. The result is a long delay because the # site-local IPv6 addresses cannot be used while the IPv4 address is # (at least for the foreseeable future) NATed. We also treat Teredo # tunnels special. # # precedence <mask> <value> # Add another rule to the RFC 3484 precedence table. See section 2.1 # and 10.3 in RFC 3484. The default is: # #precedence ::1/128 50 #precedence ::/0 40 #precedence 2002::/16 30 #precedence ::/96 20 #precedence ::ffff:0:0/96 10 # # For sites which prefer IPv4 connections change the last line to # #precedence ::ffff:0:0/96 100 # # scopev4 <mask> <value> # Add another rule to the RFC 3484 scope table for IPv4 addresses. # By default the scope IDs described in section 3.2 in RFC 3484 are # used. Changing these defaults should hardly ever be necessary. # The defaults are equivalent to: # #scopev4 ::ffff:169.254.0.0/112 2 #scopev4 ::ffff:127.0.0.0/104 2 #scopev4 ::ffff:10.0.0.0/104 5 #scopev4 ::ffff:172.16.0.0/108 5 #scopev4 ::ffff:192.168.0.0/112 5 #scopev4 ::ffff:0.0.0.0/96 14 # cat /etc/hostname ANTian I hope that helps. :) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
