I have had reports from my coworkers that FQDN clients cease to work after
upgrading the windows client from 6.1.3 to 7.1. This is happening on
several machines, and downgrading to 6.1.3 restores backup/restore
capability.

The clients are defined like this:

hostname.domain.com

Under aliases, only hostname.domain.com is listed (no short name is
listed). Listing the hostname "hostname" solves the problem, but it is not
an option, since there might be conflicting client names if FQDN is not
used. This worked fine with 6.1.3 clients. The clients are aware of that
they are known as the FQDN name. This has been verified by doing a ping -a
ipofhost to see what the client resolves to. However, when starting
networker user, it starts prompting for directed recover of the FQDN
client name. Recovers do not work however. The client name listed in the
networker user is the short hostname "hostname".

As far as I can see, what I'm trying to do should be possible, and perhaps
even the desirable setup. And it has been done in networker 6.

Does anyone have any idea why this has ceased to work? Is there a patch
availbale for this problem?

//Oscar

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=