> If I issue status client=client-name, it is able to connect to the director > thouh. Does it have anything to do?
Are you doing that from bconsole? and if so, are you running that right on the client, or on the director and making the connection to the client from the director? If thats the case then your director can resolve the client address, not the client resolve the director address. Either way the error you are getting is a name to IP resolution failure. What happens if you specify the FQDN in your configuration on the client? Right now it's just looking for 'tracfire' ... what happens if you change that to tracfire.itsdomain.com? > > On 3/28/07, Lonny Selinger <[EMAIL PROTECTED]> wrote: >> >> >> > Hi Lonny, >> > >> > client fd,conf file does not have any place where the server ip or name >> is >> > defined.It justs has the name of the director, which I believe has >> nothing >> > to do with the access. >> >> It has to be able to resolve the director to connect to it though ;-) >> >> > I do however remeber while installing the client it >> > did asked for the the server name, and I gave FQDN there. My host file >> on >> > both the systems don't have the server IP, but the older one is somehow >> > pinging the server with just the hostname, while the new machine needs a >> > FQDN to ping. >> >> >> So you can ping the director *from* the new machine but only if you use >> the >> FQDN? I'm not sure how Windows does it but do you have a default 'search' >> domain specification for DNS in Windows? >> >> On Linux you can specify this in the resolve.conf file with a 'search' >> directive: >> >> search mydomain.com >> nameserver dns.server.com >> >> The specific failure was: gethostbyname() for host "tracfire" failed: >> >> I'm assuming tracfire is the director you can not conenct to, and it looks >> like it's becasue it doesn't know what its' IP is (can't resolve in DNS). >> >> -- >> L >> >> > Regards >> > >> > On 3/28/07, Lonny Selinger <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> > Hi everyone, >> >> > >> >> > I am trying to add a windowes XP client to my backup infrastructure. >> I >> >> > already have one, but when i tried to add the second with exact same >> >> > configuration, I recieve the following errors where tracfire is the >> >> bacula >> >> > server, when i run the job. >> >> > >> >> > 28-Mar 12:53 syru156-51-fd: >> client051-Windows-Job.2007-03-28_14.15.25Fatal >> >> > error: Failed to connect to Storage daemon: tracfire:10103 >> >> > 28-Mar 12:53 syru156-51-fd: >> >> client051-Windows-Job.2007-03-28_14.15.25Error: >> >> > ../../lib/bnet.c:779 gethostbyname() for host "tracfire" failed: >> >> > ERR=Authoritative answer for host not found. >> >> > 28-Mar 14:15 tracfire-dir: >> client051-Windows-Job.2007-03-28_14.15.25Fatal >> >> > error: Socket error on Storage command: ERR=No data available >> >> >> >> This looks like a DNS or hosts file issue. Are you using FQDNs? does >> >> everything resolve from both sides and if you do a lookup for your >> >> director's >> >> IP for the new XP machine? >> >> >> >> > >> >> > Shouldn't be anytthing to do with the server side configuration, as I >> >> have >> >> > three unix and one windows XP cleint alredy running the same >> >> configuration. >> >> > The new windows client has xactly the same configuration apart from >> the >> >> ip's >> >> > ofcourse. Can anyone please point me to what I should be looking at? >> >> > >> >> > >> >> > Regards >> >> > >> >> >> ------------------------------------------------------------------------- >> >> > Take Surveys. Earn Cash. Influence the Future of IT >> >> > Join SourceForge.net's Techsay panel and you'll get the chance to >> share >> >> your >> >> > opinions on IT & business topics through brief surveys-and earn cash >> >> > >> >> >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV_______________________________________________ >> >> > Bacula-users mailing list >> >> > Bacula-users@lists.sourceforge.net >> >> > https://lists.sourceforge.net/lists/listinfo/bacula-users >> >> > >> >> >> >> >> >> -- >> >> "To mess up a Linux box, you need to work at it; to mess up your >> Windows >> >> box, >> >> you just need to work ON it." >> >> >> >> >> > >> >> >> -- >> "To mess up a Linux box, you need to work at it; to mess up your Windows >> box, >> you just need to work ON it." >> >> > -- "To mess up a Linux box, you need to work at it; to mess up your Windows box, you just need to work ON it." ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
