similar to: Guest access to share, user-level security issues

Displaying 20 results from an estimated 8000 matches similar to: "Guest access to share, user-level security issues"

2006 Mar 29
1
NT_STATUS_BAD_NETWORK_NAME
Hello, I could use a bit of help with a samba install. Installation is Samba 3.0.21c on fedora 4 No major changes to smb.conf just added a share point. [disk] comment = Disk shares path =/disk public = yes writable = yes printable = no guest ok = yes I opened my share up wide. ls -l drwxrwxrwx 10 bob users 1024 Mar 21 16:07 disk I get my share
2007 Jun 09
3
vcpu performance : 1 vcpu for all guets or 4 vpcu ?
Hello all ;) Tell I have a Xeon server with 4 vcpus If on this box I have some guets, tell 10, what is the best solutions : - Set all guests to 1 vcpu ? - Set all guests to 4 vcpus ? I well understand that if I set a guest with 4 vcpus and all others only with one vpcus, then the one with 4 vcpus will have more "cpu time" available than others guests. But in case I''d like
2010 Feb 02
1
OS X Clients Can't Create Sub-Directories
I'm running samba on a local linux server, with a bunch of shares. Over the last several years, this has worked perfectly in our heterogenous network of OS X and Windows. All my windows clients still work perfectly - my users can mount the samba shares and create, rename, move etc files and folders. However, recently (starting yesterday) my OS X clients are unable to rename any sub
2018 Sep 05
2
Migration samba 3 to 4
Hello, Indeed when I copied the result for the mailing I made a mistake. MY.DOMAIN is a dummy name. The result of the migration command is Reading smb.conf WARNING: The "idmap backend" option is deprecated WARNING: The "idmap uid" option is deprecated WARNING: The "idmap gid" option is deprecated Provisioning Exporting account policy Exporting groups Severe DB
2009 Dec 28
1
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
Hi, I can't get access to any shares when running "smbclient //DUCK/test -U Dominic". I'm getting the message: tree connect failed: NT_STATUS_BAD_NETWORK_NAME I'm pretty sure it's authenticating properly as it says "session setup ok" in the debug output. If I enter the wrong password I get: "session setup failed: NT_STATUS_LOGON_FAILURE" I'm
2009 Sep 06
1
NT_STATUS_BAD_NETWORK_NAME
Hi i'm trying to list the shares on my Brother HL-5250DN printer with the smbtree command on linux but i keep getting the NT_STATUS_BAD_NETWORK_NAME error message. I can however print to one of the shared printing services with cups through the Device URI: smb://BRN_E1BEFA/BINARY_P1. Does anyone know what the problem could be? linux-wick:~ # smbtree Password: WORKGROUP
2002 Nov 14
1
Citrix trigging printing bug??
Hi We have a mystical error occurring in a special case. When we run a citrix client on the Windows client we will not receive any printouts - no printer dialogue box are opened either. From windows we get nothing - no message box no nothing. * We are running SAMBA 2.2.6 on solaris 7 * We are running a citrix client on Windows 2000 Pro SP3 connected to the SAMBA without domain. The Citrix
2006 Jul 31
2
NT_STATUS_BAD_NETWORK_NAME
Hello, I installed samba 3.0.23 on Fedora Cora 4 and I configured it with this smb.conf file: [global] dos charset = UTF-8 workgroup = OAF_ADMIN server string = OAF Samba PDC Server passdb backend = tdbsam username map = /etc/samba/smbusers password level = 1 log level = 13 log file = /var/log/samba/log.%m max log size = 50
2010 Feb 05
3
IPv6 name resolution problem
Hi, I'm trying to set up a small network over IPv6. It will have IPv4 too but the dhcp server may not work and Ubuntu (9.04) automatically configure a .local domain IPv6 addresses, so I must run the samba server and clients over IPv6. Only one machine will act as a server, but samba is up and running in all of them. The problem is that smbclient can't resolve the server's name, my
2002 Jun 23
2
NT_STATUS_BAD_NETWORK_NAME
What is the cause of this particular error. # smbclient -L localhost will either work or return this added interface ip=192.168.0.16 bcast=192.168.0.255 nmask=255.255.255.0 Got a positive name query response from 192.168.0.16 ( 192.168.0.16 ) Anonymous login successful Domain=[HOME] OS=[Unix] Server=[Samba 2.2.4] tree connect failed: NT_STATUS_BAD_NETWORK_NAME It working is an intermittent
2010 Dec 18
1
samba 3.5.6 - ''smbclient -U% -Llocalhost' results in error - using hostname works fine, new feature?
Guys, I have probably missed an announcement or overlooked something in a changelog, but I just want to confirm what I'm seeing is expected behavior. I run samba in standalone mode and I have always checked operation with smbclient -U% -Llocalhost Now the faithful command returns an error: Connection to localhost failed (Error NT_STATUS_BAD_NETWORK_NAME) Simply using the hostname
2017 Jan 22
4
答复: ??????: Is the "\\x.x.x.x" type tree connect request a client related feature?
Thanks for your reply, Louis However, I am still blocked by this problem now. !-_- I tried to set the samba server as the DNS server and visit the shared folder by input "\\aaa.bb.com" at windows 7 client. In some cases it works and will not fail. However the similar abnormal phenomenon also occasionally happens (especially at changing the authentication, such as local to ldap): 1) I can
2005 Jul 08
1
fwd: tree connect failed: NT_STATUS_BAD_NETWORK_NAME
I sent this out yesterday. Can anyone offer any advice? I'm really at a loss on what to do. thanks! ----- Forwarded message from Mike Soh <sohmc@cs.umd.edu> ----- From: Mike Soh <sohmc@cs.umd.edu> To: samba@lists.samba.org Subject: [Samba] tree connect failed: NT_STATUS_BAD_NETWORK_NAME Date: Thu, 7 Jul 2005 08:27:33 -0400 User-Agent: Mutt/1.4.1i X-Spam-Status: No, score=-2.6
2005 Apr 11
1
/tmp does not exist or is not a directory
Hi All, [2005/04/11 11:26:58, 0] smbd/service.c:make_connection_snum(620) '/tmp' does not exist or is not a directory, when connecting to [IPC$] This wierd and wacky thing has just started for no apparent reason no upgrades were done no system mods were performed, the file server is just never played with except to add shares, testparm says all OK. This also happens when a user
2008 Aug 07
1
smbclient failed --> NT_STATUS_BAD_NETWORK_NAME
I make all steps in the guide: http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/install.html#id2546028 but command (exetuded in the same computer where is samba): smbclient //fc9/tester -Utester%test gives error: Domain=[DZTI] OS=[Unix] Server=[Samba 3.2.0-17.fc9] tree connect failed: NT_STATUS_BAD_NETWORK_NAME The user tester have been created by commands: useradd tester smbpasswd -a
2015 Mar 26
2
BAD_NETWORK_NAME
H! I am getting such messages in log.samba: ../source4/nbt_server/dgram netlogon.c:198(nbtd_mailslot_netlogon_handler) nbtd netlogon handler failed from 192.168.0.125:138 to DOMAIN<1c> - NT_STATUS_BAD_NETWORK_NAME What means that <1c>? seems like special char... There are two domains sharing one network - one - NT-style named DOMAIN and the second, AD, named DOMAIN2 (samba
2011 Jan 13
2
Cannot list shares on a host
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, linux 2.6.34.7-0.7-desktop x86_64 smbclient 3.5.4-5.1.2-2426-SUSE-SL11.3 I issue this command: smbclient -L SMA-STN14L -U jmoe I get: Connection to SMA-STN14L failed (Error NT_STATUS_BAD_NETWORK_NAME) In <smb.conf> [globals] section: workgroup = SOHNEN-MOE netbios name = SMA-STN14L Adding the -I option made no difference.
2006 Feb 03
3
Sharing a Secondary Hard Drive
I just recently installed a second hard drive in my Samba server with the hopes of sharing it with the rest of my home network. It seems like Samba can not get the correct permissions to the drive, however. I have the drive mounted under /media/public, and when I try to map a share directly to it and open the share with a client, I get an NT_STATUS_BAD_NETWORK_NAME error. When I map the
2007 Jun 09
1
smbclient error: NT_STATUS_BAD_NETWORK_NAME, on shared foler with a Chinese name
Hi folks, I am trying to access the shared folders on a Windows XP PC from a Linux (FC5) PC using smbclient. Linux config info: $ locale LANG=en_US.UTF-8 $ rpm -q samba samba-3.0.24-6.fc5 smb.conf: [global] dos charset = CP936 <--- Simplified Chinese unix charset = UTF-8 display charset = LOCALE Now, here is the problem:
2010 Nov 11
5
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
Let me start off by apologizing for this rambling post. I have been working on this problem all day and have not gotten anywhere. This is my first time working with samba and I have been tasked to set up a share that does not require a password for access. I have been tinkering with the configuration file but I cannot get it to work. Here is my current smb.conf file that I have: global]