>From Fixed Bug List for 6.1.2:

LGTpa33957 Using spaces in the userid might cause an error in the
Remote Access attribute. This has been resolved.

NOTE: if upgrading, I'd recommend skipping 6.1.2 - go directly to 6.1.3 -
do not pass GO!

Also, a work-around would be to specify a group of users, i.e.
Administrators@hostname, but this may not be desireable in your situation.

Carl Farnsworth
DigiDyne Inc.

On Thu, 20 Feb 2003 13:39:16 -0500, Ty Young <phillip_young AT I2 DOT COM> 
wrote:

>I'm sure I'm not the only person in this situation, but I can't find
>anything in the listserv's archives.  So, here goes.
>
>I have a user, John Doe, whose NT domain login is "John Doe" (i.e.,
>not "jdoe" or "johndoe" or "johnd" -- two words, separated by space.)  I am
>unable to configure the Remote Access field for a client such that "John
>Doe@*" or "John Doe@host" (or a number of other variations I've tried)
>enables John to perform a directed recovery.  However, other users with
>single-word logins, i.e. "janedoe" work flawlessly.
>
>I've opened a ticket with Legato on this, but have yet to hear back.
>Anybody seen this behavior, and have a fix?
>
>tia
>-ty

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=