search for: nbtlookup

...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 *<00> Looking up status of 10.1.1.232 DEVSERV2 <00> - B <ACTIVE> Why is it reporting the IPv4 address when I queried it with the IPv6 address? It looks like nmbd is listening...

...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 *<00> Looking up status of 10.1.1.232 DEVSERV2 <00> - B <ACTIVE> Why is it reporting the IPv4 address when I queried it with the IPv6 address? It looks like nmbd is listening...

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