similar to: IPv6 DNS Confusion

I noticed that samba is listening on IPv6, so I became curious and wondered if I could actually use it, and so far, it looks like it isn't usable. Running nbtstat -A fe80::216:3eff:fe6f:1f3a on Windows returns the stupid message that the address must be in the a.b.c.d format. I then tried using nbtlookup from linux: nmblookup -S -U '[fe80::216:3eff:fe6f:1f3a]' \* 10.1.1.232

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

Perfect thanks. Do you have a web proxy in your network? That would explain this sequence of events. ------------------------------------------------------------------------ Dr David Holder CEng FIET MIEEE Erion Ltd, An Cala, Inverkirkaig, Lochinver, Sutherland, IV27 4LR, UK Reception: +44 (0)1422 207000 Direct Dial: +44 (0)131 2026317 http://www.erion.co.uk Registered in England and Wales.

On 02/03/15 16:21, sandy.napoles at eccmg.cupet.cu wrote: > My OS is Debian 7 and I only writte git pull > >> On 02/03/15 15:05, sandy.napoles at eccmg.cupet.cu wrote: >>> ifconfig -a >>> eth0 Link encap:Ethernet HWaddr 00:0c:29:82:ec:80 >>> inet addr:172.18.68.8 Bcast:172.18.68.31 >>> Mask:255.255.255.224 >>>

On 02/03/15 16:45, sandy.napoles at eccmg.cupet.cu wrote: > root at samba:/home/samba-master# git pull > error: Failed to connect to 2001:638:603:d06e::80:230: Network is > unreachable while accessing http://git.samba.org/samba.git/info/refs > fatal: HTTP request failed > root at samba:/home/samba-master# > > > >> On 02/03/15 16:21, sandy.napoles at eccmg.cupet.cu

Hi Sandy, Thanks! Curious. Do you have any other interfaces? ifconfig -a should show them all including loopback. What is puzzling me is that it should not even attempt to use IPv6 to reach a global address when it only has a link-local address. It should gracefully fall back to IPv4 (as per RFC 6724 or RFC 3484 depending on the kernel version). Since you have an IPv4 address and I assume an

On 02/03/15 15:05, sandy.napoles at eccmg.cupet.cu wrote: > ifconfig -a > eth0 Link encap:Ethernet HWaddr 00:0c:29:82:ec:80 > inet addr:172.18.68.8 Bcast:172.18.68.31 Mask:255.255.255.224 > inet6 addr: fe80::20c:29ff:fe82:ec80/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:107940 errors:0

Thanks. No other interfaces (ifconfig -a)? Also output of ip -f inet6 route would be useful. David ------------------------------------------------------------------------ Dr David Holder CEng FIET MIEEE Erion Ltd, An Cala, Inverkirkaig, Lochinver, Sutherland, IV27 4LR, UK Reception: +44 (0)1422 207000 Direct Dial: +44 (0)131 2026317 http://www.erion.co.uk Registered in England and

Try lynx http://git.samba.org/ Or indeed telnet git.samba.org 80 GET / HTTP/1.0 OR telnet6 git.samba.org 80 GET / HTTP/1.0 There are blank lines after the GETs. These will show if you have connectivity over HTTP to the Samba git repository over v4 and/or v6. David ------------------------------------------------------------------------ Dr David Holder CEng FIET MIEEE Erion Ltd, An

I do not understand that you say me???? > Any reason you are not using the git protocol? > > git://git.samba.org > > David > ------------------------------------------------------------------------ > Dr David Holder CEng FIET MIEEE > > Erion Ltd, An Cala, Inverkirkaig, Lochinver, Sutherland, IV27 4LR, UK > > Reception: +44 (0)1422 207000 > > Direct Dial: +44

On 02/03/15 17:20, David Holder wrote: > Hi Roland, > > It will be useful to see the resolv.conf. However, I don't think that > this is a name resolution issue as it is clear that git.samba.org is > being resolved to at least the v6 address. If that works then A & AAAA > records should be returned to the resolver regardless of the transport > used. There must be

Hi Sandy, Please can you provide the output from an *i**fconfig -a* command? This should give an idea of what is going on. Turning off IPv6 will not be necessary if you can find the actual cause of the problem. You would not get this error message if you only have a link local address configured on your interface. You must have some form of global address. Also, the IPv6 address is that of

Matthias Busch schrieb am 12.03.2015 22:38: > further testing, log reading and googling has revealed further possible > problem sources... with ipv6? > I think to remember vaguely... on my very first tests running Samba 4.0 I used the home.local as domain name - and I had to completely disable IP v6. This has vanished when I switched over to home.serbe.ch... but maybe I eradicated

Dear Sir, I am trying to use the shared files from Windows 7 using IPV6 address. But I couldn't able to map or access it through V6 address, though I can access it through IPV4 address. I tried almost every thing whatever I did find on the internet community. I would be grateful to you if you could help me to make this working. If possible please provide all the steps including

Why would the samba list be looking for a reverse host name via IPV6? IFAIK I only have an IPv4 addr and reverse addr. I don't know if the original went to the person in france or not. Anyone else getting bounces like this? -------- Original Message -------- Subject: Returned mail: see transcript for details Date: Tue, 7 Apr 2015 13:19:19 -0700 From: Mail Delivery Subsystem

I do not working with ipv6, I have disable, but I have the same error, I can read in internet that this ipv6 ip 2001:638:603:d06e::80:230: belong to url samba.org.... If I try to connect to this url using some navegator I connected perfect....but when I run git pull using command line I can not connect.. > Am 28.02.2015 um 15:37 schrieb sandy.napoles at eccmg.cupet.cu: >> Hello list,

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

Hello In samba log file I've a message like this: [2011/01/18 16:04:04, 0] lib/util_sock.c:matchname(1749) matchname: host name/address mismatch: ::ffff:192.168.168.202 != pc-ser-tun.eda that fills log.smbd. I've never used ipv6 and ping pc-ser-tun.eda returns: PING pc-ser-tun.eda (192.168.168.202) 56(84) bytes of data. 64 bytes from pc-ser-tun.eda (192.168.168.202): icmp_seq=1

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

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