Announcement

Collapse
No announcement yet.

nmbd fails to start due to bogus IP address it finds somewhere.

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    nmbd fails to start due to bogus IP address it finds somewhere.

    nmbd -D -d 2 produces the following error in log.nmbd

    [2009/02/08 03:57:21, 0] nmbd/nmbd.c:main(727)
    Netbios nameserver version 3.0.22 started.
    Copyright Andrew Tridgell and the Samba Team 1992-2006
    Becoming a daemon.
    started asyncdns process 7099
    Registered MSG_REQ_POOL_USAGE
    Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
    added interface ip=192.168.1.4 bcast=192.168.1.255 nmask=255.255.255.0 [This is the correct IP address JTS]
    added interface ip=216.24.138.137 bcast=216.24.138.255 nmask=255.255.255.0
    added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0
    create_subnets: Ignoring loopback interface.
    bind failed on port 137 socket_addr = 216.24.138.137.
    Error = Cannot assign requested address

    where is nmbd getting the bogus address 216.24.138.137 from??
    This is preventing both nmbd AND smbd from running on two different PCs
    The only thing they have in common is that they're running Kubuntu.

    smbclient does work however, so all is not lost!


    #2
    Re: nmbd fails to start due to bogus IP address it finds somewhere.

    Never mind, I figured out how to fix the smb.conf problem. nmbd and smbd should never
    try to connect to the bogus address of 216.24.138.137 IMHO however -- why not
    something generic like 192.168.1.1
    The laptop does not always get connected to the ethernet via a cable, so the eth1
    interface specified in smb.conf returns the goofy IP address of 216.24.138.137.
    Deleting the eth1 from the interfaces list in smb.conf fixes the problem.

    Comment

    Working...
    X