tree connect failed: NT_STATUS_BAD_NETWORK_NAME (Setting up domain controller for w2k clients) - SMB

This is a discussion on tree connect failed: NT_STATUS_BAD_NETWORK_NAME (Setting up domain controller for w2k clients) - SMB ; Hi there.. i was following a tutorial point by point ( http://www.thegoldenear.org/toolbox/...mba-setup.html ) Im a relatvily noobie to samba. Only know how to do basic stuff sharing folders etc. i followed the tutorial and everuthing went smoot until i came ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: tree connect failed: NT_STATUS_BAD_NETWORK_NAME (Setting up domain controller for w2k clients)

  1. tree connect failed: NT_STATUS_BAD_NETWORK_NAME (Setting up domain controller for w2k clients)


    Hi there..
    i was following a tutorial point by point
    (http://www.thegoldenear.org/toolbox/...mba-setup.html)
    Im a relatvily noobie to samba. Only know how to do basic stuff sharing
    folders etc. i followed the tutorial and everuthing went smoot until i
    came to the point: Configuring the Windows workstation.

    My w2k client was able to log in with user name and password according to
    the log file but right after that was done the samba server dropped the
    connection for whatever reason i don't know.

    but what i do know is when i try to smbclient -U netbrain //192.168.0.1/ i
    get the message tree connect failed: NT_STATUS_BAD_NETWORK_NAME

    Now i was wondering if anyone could clarify what this means.

    here is my output from testparm:

    Processing section "[printers]"
    Processing section "[print$]"
    Processing section "[profiles]"
    Processing section "[homes]"
    Processing section "[programs]"
    Processing section "[NETLOGON]"
    Load smb config files from /etc/samba/smb.conf
    Loaded services file OK.
    Server role: ROLE_DOMAIN_PDC
    Press enter to see a dump of your service definitions
    # Global parameters
    [global]
    workgroup = DEBIAN
    server string = the server
    interfaces = eth0, lo
    bind interfaces only = Yes
    passdb backend = smbpasswd, guest
    pam password change = Yes
    unix password sync = Yes
    log level = 2
    log file = /var/log/samba/log.%m
    max log size = 50
    keepalive = 30
    socket options = TCP_NODELAY, IPTOS_LOWDELAY, SO_KEEPALIVE,
    SO_SNDBUF=14596, SO_RCVBUF=14596
    printcap name = cups
    add user script = /usr/sbin/useradd -d /dev/null -g machines -s
    /bin/false -M %u
    logon script = netlogon.bat ; logon script, location defined in
    [NETLOGON]
    logon path = \\%L\profiles\%U
    logon drive = H:
    domain logons = Yes
    os level = 64
    preferred master = Yes
    hosts allow = 127.0.0.1, 192.168.0.0/255.255.255.0
    printing = cups

    [printers]
    comment = All Printers
    path = /var/spool/samba
    create mask = 0700
    guest ok = Yes
    printable = Yes
    browseable = No

    [print$]
    comment = Printer Drivers
    path = /etc/samba/drivers
    guest ok = Yes

    [profiles]
    comment = users profile directories
    path = /home/samba/profiles
    read only = No
    create mask = 0600
    directory mask = 0700
    browseable = No

    [homes]
    comment = home directories
    read only = No
    create mask = 0750
    browseable = No
    volume = HOME

    [programs]
    comment = installed programs
    path = /usr/windows
    write list = @admins

    [NETLOGON]
    comment = The domain logon service
    path = /home/netlogon
    write list = @admins
    browseable = No

    any help is appriciated. thanks.

  2. Re: tree connect failed: NT_STATUS_BAD_NETWORK_NAME (Setting up domain controller for w2k clients)

    Well i figured out the problem. without your guys help. thank you very
    much

    but the NT_STATUS_BAD_NETWORK_NAME still resides. and is giving me quite a
    head ache when im trying to add
    printer support with cupsdaddsmb.

    anyone have an idea of what's wrong now then?

    thanks.

+ Reply to Thread