similar to: Cannot resolve name <name>#0x3

I have just posted this message, forgetting to add the subject....: Bonjour, I have recently somme difficulties to use samba -M, the answer is: Cannot resolve name <name>#0x3. Here is an exemple: $ smbclient -M falstaff added interface ip=192.168.0.1 bcast=192.168.0.255 nmask=255.255.255.0 Cannot resolve name falstaff#0x3 But if I use -L, the name is resolved: $ smbclient -L falstaff

On my network I have one Samba PDC (Version 3.0.28 running on FreeBSD 6.3-PRERELEASE), one mail server (FreeBSD + Dovecot + Postfix) and a dozen or so WinXP/Win2K machines. The WinXP/Win2K machines all have static IP addresses. The Windows clients are configured to look up the Samba PDC machine for both DNS and WINS. The Windows clients seem to be able to find other machines as well as the PDC:

Hi, we' ve got some probs regarding the smbclient.. it's odd, coz all seems te be working ok, except the smbclients. we use samba 3.2.4, here is a debug level 10 nmblook up is working, also it's a pdc and seems to function normal ?! i did add wins with the nsswitch, and can ping the host. anny idea where to look for ?!?! Cheers, Collen [root@green var]# echo "huh" |

I have 4 Linux servers all running samba. Everything has been working fine until yesterday. With no changes to the network or to the servers samba has quit working right. The problems all relate to samba not being able to look up names against the master browser. When I try to mount using a windows pc name I get this error... [root@fileserver pdk]# mount -t smbfs -o username=pdk,passowrd=XXXXX

Hi, Ive got samba 2.2.3a-6 setup on my Redhat 7.3 box, winbind is also configured, wbinfo can resolve NT machine names to IP's, and IP's to NT machine names: wbinfo -h core 192.168.179.250 core wbinfo -i 192.168.179.250 192.168.179.250 CORE @CORE In /etc/nsswitch.conf I have: hosts: files nisplus wins dns I can ping core : ping core PING core (192.168.179.250) from

On Sun, Feb 01, 2015 at 04:08:47PM +0900, crocket wrote: > If tincd is started before name resolution comes up, it keeps failing > for ever to resolve domain names in Address= host configuration > variable after name resolution becomes possible. > > I think tincd should succeed in resolving domain names after name > resolution becomes available. The problem is when

Agreed. On Feb 1, 2015 4:21 AM, "Etienne Dechamps" <etienne at edechamps.fr> wrote: > On Sun, Feb 1, 2015 at 11:19 AM, Guus Sliepen <guus at tinc-vpn.org> wrote: > > On Sun, Feb 01, 2015 at 04:08:47PM +0900, crocket wrote: > > > >> If tincd is started before name resolution comes up, it keeps failing > >> for ever to resolve domain names in

+1 I was noticing the same thing and currently solved it using dnsmasq. On Feb 1, 2015 1:48 AM, "crocket" <crockabiscuit at gmail.com> wrote: > If tincd is started before name resolution comes up, it keeps failing > for ever to resolve domain names in Address= host configuration > variable after name resolution becomes possible. > > I think tincd should succeed in

On Sun, Feb 1, 2015 at 11:19 AM, Guus Sliepen <guus at tinc-vpn.org> wrote: > On Sun, Feb 01, 2015 at 04:08:47PM +0900, crocket wrote: > >> If tincd is started before name resolution comes up, it keeps failing >> for ever to resolve domain names in Address= host configuration >> variable after name resolution becomes possible. >> >> I think tincd should

Am 02.02.2015 um 19:32 schrieb Nicol?s Reynolds: > William Kennington <william-5Om/gJxqp8Dx9BLsLxWUfA at public.gmane.org> writes: > >> Agreed. >> On Feb 1, 2015 4:21 AM, "Etienne Dechamps" <etienne-ypMCQUleWbRvynnTyRI/EA at public.gmane.org> wrote: >> >>> Considering how cheap that operation seems to be, would it make sense >>> to

If tincd is started before name resolution comes up, it keeps failing for ever to resolve domain names in Address= host configuration variable after name resolution becomes possible. I think tincd should succeed in resolving domain names after name resolution becomes available.

Per http://us1.samba.org/samba/docs/using_samba/ch12.html ... That is "Chapter 12. Troubleshooting Samba" in the "Using Samba, 2nd Edition" book by Jay Ts, Robert Eckstein, and David Collier-Brown from O'Reilly. Under the section "Troubleshooting Name Services/Identifying what's in use" it says, "First, see if both the server and the client are using

I had a working container with dovecot configured as proxy. And all of a sudden I am getting these messages 'dovecot: auth: Error: DNS lookup for roosit03 failed: Name does not resolve' Pinging/nslookup these hostnames is ok

William Kennington <william at wkennington.com> writes: > Agreed. > On Feb 1, 2015 4:21 AM, "Etienne Dechamps" <etienne at edechamps.fr> wrote: > >> Considering how cheap that operation seems to be, would it make sense >> to call res_init() every time tinc retries a metaconnection? It's not >> doing that very often anyway... and it would solve

On Mon, Feb 09, 2015 at 10:57:05AM +0100, Florian Klink wrote: > I have some hosts which converted to systemd-networkd (which doesn't > support hooks by now), and most of the time, tinc simply won't come up > after bootup (or won't be able to reconnect when the network is > changed), which is really ugly. > > Having a local dns in front is somewhat hacky, I'd

Marc> I had a working container with dovecot configured as proxy. And Marc> all of a sudden I am getting these messages 'dovecot: auth: Marc> Error: DNS lookup for roosit03 failed: Name does not resolve' Marc> Pinging/nslookup these hostnames is ok Does nslookup work inside the container? Sounds to me like the setup isn't working properly, but it's hard to know unless

I am a little confused. In the smb.conf man page under the "name resolve order" section, it states that setting "name resolve order = wins" will be ignored if the "wins server" parameter is not set. Elsewhere in the man page it states that if you set "wins support = yes" then you cannot set the wins server parameter. Does this mean that a machine that is

My LAN has a single linux/samba server as a PDC/file server, and several windows workstations. The workstations get their IP addresses from a Linksys cable router DHCP server. I can't get the linux machine to resolve the NETBios names of the windows machines. >From the Linux machine I can see the Internet through the DSL router, I can ping the windows machines by IP address, but

I am using samba 2.2.1a , in an NT-4 domain. security = DOMAIN on the first logon to the samba server, I can see a message: Attempting host lookup for name MYPDCNAME<0x20> the next message appears after 10 seconds (that is the delay). samba tries to resolve MYPDCNAME with the wins server, and succeeds. Higher debug level (debug level = 10) does not produce more debug messages. Any ideas

I am writing this letter and I hope that I'll have answers about the generation of smb.conf by the way of smb.conf.master with testparm command. Like is described on page 5 of Samba3-HOWTO.pdf. The situation is: - The manual of smb.conf says that the default value of the parameter ?name resolve order? is ?lmhosts host wins bcast?, but when I type the command like: # testparm -s