I've heard that, "nothing has changed" before :) Seriously, are you sure nothing restarted on the legato machines? The daemon wasn't restarted possibly resulting in a setting change suddenly taking effect? Wouldn't be the first time I've seen that happen.
As for FQDN vs. short name resolution, what were you using for name services? DNS, Host names, what? -----Original Message----- From: Juan Ibarra [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 24, 2004 4:00 PM To: [EMAIL PROTECTED] activedir. org ([EMAIL PROTECTED]) Subject: [ActiveDir] Strange issue with host name Hello to all, I have a strange issue happening in my corp. I hope some of you can shed some light here. The issue is as follows: We use Legato Backup Software for enterprise back ups, NT 4.0 and 2000 servers. Everything was working fine but this weekend I started noticing some failed jobs on the back ups. After doing some investigation discovered that the legato servers, running on sun machines, were no longer looking at the host name as "hostname" which is the way they are defined on the legato groups, but they were looking at it as "hostname.mycorp.com" the FQDN. If I try to do a restore on the client I get an error saying that the host is not a registered client. Nothing on the legato side has changed for sure. What could cause this on the windows side? Could the latest MS patch be responsible? Thanks for any input Regards, Juan List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
