similar to: IPv6?

Hi Phil, NBT name resolution is IPv4 only. Samba does work over IPv6, but NetBIOS name resolution is and always will be IPv4 only. It is a feature of the protocol not Samba. Take a look at http://www.ipv6consultancy.com/ipv6blog/wp-content/uploads/sambaxp-2015-deploying-ipv6-only-samba-4-environments-v0_4.pdf and other presentations on the subject at

I am using Samba 4.2.2 with Internal DNS. I haven't deliberately set up IPv6, but I know our ISP allocates us a 64 block and auto-configuration seems to be doing the rest. Generally machines seem to be able to ping using IPv6 and Windows seems to be using that by default. But looking in DNS there seem to be around 100 IPv6 addresses showing for the domain controller server, which surely

On 4/11/2017 9:24 AM, David Holder wrote: > Hi Phil, > > NBT name resolution is IPv4 only. Samba does work over IPv6, but > NetBIOS name resolution is and always will be IPv4 only. It is a > feature of the protocol not Samba. How can this be? Everything I have read about SMB for the last 20 years or so has said that it is based entirely on NetBIOS, and has no concept even of

I was directed to the following site by one of our customers regarding a keyserver built into openssh. There's a patch for 3.4p1 on their site, but the license isn't very clear, nor is it clear if they have approached the openssh team regarding the inclusion of this subsystem into openssh proper. I've been asked to patch Mandrake's openssh with this feature, but I'm

Hi All, I need to establish an IPSec tunnel between two FreeBSD systems, using IPv6 addresses.The connetcion is host-to-host between two FreeBSD( RELEASE 4.11) systems with KAME IPSec implementation. I tried to establish the connection, but it has some problems which are explained below. |----------------->| host1-[mohan]| |host2-[ram]

Hi All, I need to establish an IPSec tunnel between two FreeBSD systems using IPv6 addresses.The connetcion is host-to-host between two FreeBSD( RELEASE 4.11) systems with KAME IPSec implementation. |----------------->| host1-[mohan]| |host2-[ram] |<-----------------| host1 IPv6 address : fe80::2b0:d0ff:fe6f:dfa0 host2 IPv6 address :

Hi All, In the previous mail, I have sent is only the problem that occurs, because of using IPv6 addresses. But the connection works with IPv4 addresses without any problem. Thanx, Mohan. __________________________________________________________ How much free photo storage do you get? Store your friends 'n family snaps for FREE with Yahoo! Photos http://in.photos.yahoo.com

I have Apache/2.4.6 installed in a minimal CentOS 7 VM. I am trying to access the default page when Apache is installed by accessing the CentOS IP as http://192.168.3.130 (is a host only interface) but I got "This webpage is not available: ERR_CONNECTION_TIMED_OUT" and I can't find why. I have stopped iptables and then checked: # service iptables status Redirecting to /bin/systemctl

Hi Chris, This sounds like a bug and a configuration issue ;-) . You are correct your domain controller IPv6 address should not change. Is your /64 a static prefix that does not change with time? If it is, then this probably means that you have temporary addresses configured on your DC. Either scenarios are likely to cause a DNS update and add new records. The old records should be deleted

Hi Phil, The answers are in the links but I'll expand a little below! 😉 > How can this be? Everything I have read about SMB for the last 20 years or so has said that it is based entirely on NetBIOS, and has no concept even of IPv4; that it is NBT that translates NetBIOS to run over IPv4. SMB does not have to be carried by NetBIOS. The too protocols can be decoupled. This is

Greetings all. I usually don't get involved in the mailing lists unless it is of a major importance. Here is a new problem that came up with the 3.3.p1 version, which I already reported to the Mandrake Developers on their RPM build. Basically, it boils down to this. In the Priv Seperation Mode or not, the public Key Authentication is throughly broken on all 3 versions of Keys,

Hello, I have recently compiled and installed release 3.8.1p1. This was done on a Solaris 8 system using LDAP as its naming service. The new release, however, will not let me log in (as a regular user). I repeatedly get "Permission denied, please try again" messages. The root user, though, can log in okay. The same thing happened with the 3.7.1p2 release. The 3.6.1p1 release

An observation and a question on the new version of OpenSSH. With previous version of OpenSSH, using something like pam_ldap to authenticate users against an LDAP directory worked great, however with 3.8p1 this is no longer the case. If I try to log into a machine with an account under "LDAP's control", I always get password failures. However, using an account with a ssh key

I'm curious as to whether or not there is a way to restrict forwarded ports server side. For instance, I'm running an IRC server and am allowing users to connect via ssh forwarding (so I can take advantange of using openssh's public key method for authentication). Each client I tell to setup their ~/.ssh/config in a certain way, but the relevant line is: LocalForward 6667

Troubleshooting steps fail. Trying to replace a standalone Netware server with a Samba4 server with AD. To isolate this test setup, changed server's static IP address and separated the wiring. Then went through the Troubleshooting portion of The Samba Checklist. Some tests pass. Some tests fail. I'm weak on Samba, DNS and AD. I appreciate your instructions on how to overcome the

I realize this is not a strictly a samba "problem" but I am hoping that there is a samba solution. I have a samba 3.6.20 PDC. I am running WINS. We use an IPSec client VPN to allow users with Windows 7 laptops to connect to the office remotely. The windows 7 laptops are joined to the Samba domain. Password expiration policies are enforced. When you login to

Hi, My apologies if this is a FAQ that I missed. This is my first attempt at setting up samba4. Following the howto instructions: kinit administrator seems to work fine. samba is latest git (alpha19). however the join fails (as below): [root at ads bin]# ./samba-tool domain join tribalnova.local DC -Uadministrator --realm=tribalnova.local -d4 GENSEC backend 'gssapi_spnego'

On Fri, May 8, 2009 at 10:14 AM, Javier Barroso <javibarroso@gmail.com> wrote: > Hello, > > I have a etch xen server with a virtual machine with 2 network > interfaces configured. Every interface has a different mac, and inside > the host has a different ip. > > However I can see with tcpdump and arpwatch (I discover this because > arpwatch told me), about the two ips

OS = Ubuntu 18.04 LXD container Samba version = 4.11.12 Repo = Louis' (many thanks) I recently upgraded from 4.10.14->4.10.17->4.11.12 Now the samba-ad-dc service fails with the following upon reboot: --- root at samba:~# systemctl status samba-ad-dc ? samba-ad-dc.service - Samba AD Daemon Loaded: loaded (/lib/systemd/system/samba-ad-dc.service; enabled; vendor preset: enabled)

Thanks a lot for your hints Pasi. Due to your suggestion I open a new thread here. I have tested with model=e1000 (HVMs). As HVM configs are identical (not iso images and LVM volumes) I guess it is a xen 4.1.2* issue .. or just involved domU OS-kernels (however as it is HVM it should not play any role) Tested and correctly working OSes (getting an IP address and pinging of