Quoting Sam Morris (s...@robots.org.uk): > Package: samba > Version: 2:3.4.7~dfsg-1 > Severity: normal
> I run Debian in a VirtualBox virtual machine and often find that I am > unable to resolve the hostname of the system from my Windows host. This > is always caused by nmbd not running in the virtual machine. > > I'm attaching my log.nmbd file; this was produced with 'log level' set > to 3. It appears that nmbd was launched but then immediately failed with > these messages: > > [2010/03/29 20:45:01, 3] nmbd/nmbd.c:948(main) > Opening sockets 137 > [2010/03/29 20:45:01, 3] > ../lib/util/util_net.c:56(interpret_string_addr_internal) > interpret_string_addr_internal: getaddrinfo failed for name 0.0.0.0 > [Address family for hostname not supported] > [2010/03/29 20:45:01, 0] nmbd/nmbd.c:693(open_sockets) > > I have tried to correlate this time with other log messages and it > appears that the system was still booting when the message occurred. > Here are the syslog messages from around the same time: networkmlanager seems to be starting *after* nmbd. Could you do "ls /etc/rc2.d/*network-manager* /etc/rc2.s§*samba*"?
signature.asc
Description: Digital signature
