search for: aliasnames

Hi all, While working on alias support for the LLVM-ML project, I ran into a feature implemented back in 2010: default-null weak externals in COFF, a GNU extension. https://reviews.llvm.org/rG17990d56907b I'd like to disable this feature when targeting MSVC compatibility. Does anyone have more context on this, and why it'd be a terrible idea? For context: This seems to be designed to let

Hello, I have setup a Samba 4 ADDC following the tutorial in the wiki. I need it to be a DC and a fileserver. Everything works fine and dandy except that I cannot access the file shares via a DNS alias, instead of the original hostname/DNS name. And I need this for various reasons, enough to halt going live with it if it doesn't work. :-( When accessing via the machine's fqdn

Hello all This is my first post to Samba lists so I hope I have picked the correct list. Please let me know if I haven't. My question is what is the maximum amount of names or characters that can be put on the "netbios aliases" line in the smb.conf. We have situation where we potentially need to put up to 200 names on the line (big machines, one name per application). Cheers

that should work fine, if .. dnsdomain and search domain are set correct on the clients and on the server in smb.conf dns proxy = yes wins server = yes ping a netbios aliasname probly wont work. greetz, Louis Begin doorgestuurd bericht: Van: Rowland Penny via samba <samba at lists.samba.org> Datum: 3 september 2016 23:28:21 CEST Aan: samba at lists.samba.org <samba at

your keytab setup looks wrong. Can you also explain why there are 2 netbios names in there,normally only one should be in there. only the real resolving hostname (-s) should be in there. if you follow this basic rules for your (internal) revolving. hostname -f is the real hostname. hostname -i is the real ip hostname -d the dnsdomain hostname -s the local aliasname (on the linux

I was playing with the "netbios aliases" option to have my samba server provide different netbios names with different shares. I made a minimal global smb.conf file with a [global] section ending in: include = /etc/smb.conf.%L and moved all the share config info into the appropriate smb.conf.%L file. Everything works fine. The only problem I encountered was with the server string.

Hai, > > Change this one. > > /etc/hosts > > 10.0.0.2 fs-a.dom.corp fs-a oldsamba # Old/wrong > > 10.0.0.2 fs-a.dom.corp fs-a oldsamba.dom.corp oldsamba # > new/correct > > Or > > 10.0.0.2 fs-a.dom.corp fs-a oldsamba.dom.corp # new/correct > No, none of them are correct No, Rowland, your really wrong here. ( i dont say that often.. ) :-p But i give

Thanks for the suggestions! > The latter is easiest to deal with, replace it with a CNAME in the AD dns. I did the CNAME, but when I remove the netbios alias I can see the shares list when accessing \\aliasname, but then I'm not allowed into any of them. I tried rebooting the client but same result, and I also don't see anything in the logs :( > The first will require a bit more

About the root problem of the thread, it seems a permission problem, but again I need some help on how to investigate further. I've just been reported a share wasn't accessible, I checked on another client and I was able to enter the folder but NOT to see the content, looked like empty. I have "hide unreadable" enabled, and while entering the share several times I noticed the

> trying again. here's the output. thanks! Config collected --- 2020-05-18-23:08 ----------- Hostname: fileserver DNS Domain: wdc.mydomain.it Realm: WDC.MYDOMAIN.IT FQDN: fileserver.wdc.mydomain.it ipaddress: 10.0.0.3 ----------- This computer is running Ubuntu 18.04.4 LTS x86_64 ----------- running command : ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc

Ok, Your keytab looks ok now. oldsamba.dom.corp is an alias for fs-a.oldsamba.dom.corp. fs-a.dom.corp has address 10.0.0.2 i would have expected here. oldsamba.dom.corp is an alias for fs-a.dom.corp. fs-a.dom.corp has address 10.0.0.2 Or was that a typo? I assuming a typo.. About your setup from the script outpout. Change this one. /etc/hosts 10.0.0.2 fs-a.dom.corp fs-a oldsamba #

Luis, my typos, I'v to mask the output sorry (compliance) # su - testuser $ smbclient --option='client min protocol=NT1' -U testuser //oldsamba/testuser -c 'ls' Unable to initialize messaging context Enter DOM\testuser's password: session setup failed: NT_STATUS_LOGON_FAILURE [2019/11/05 15:50:50.009481, 1] ../../source3/librpc/crypto/gse.c:660(gse_get_server_auth_token)

samba-tool computer remove oldsamba Il giorno mar 5 nov 2019 alle ore 17:04 L.P.H. van Belle <belle at bazuin.nl> ha scritto: > Hai, > > Well that great you found it. > > Ah.. so you removed the entry from the DNS or ADDB? > Can you tell what you exactly did, that might help the next person with a > problem like this. > > And not many list messages today.. ;-)

Ok, you did to much as far i can tell. You want to see this: i'll show my output, then i is better to see what i mean. this is where you start with. klist -ke |sort ( default member ) ---- -------------------------------------------------------------------------- 3 host/HOSTNAME1 at REALM.DOMAIN.TLD (aes128-cts-hmac-sha1-96) 3 host/HOSTNAME1 at REALM.DOMAIN.TLD