The name-discovery phase succeeded, but the system cannot find the requested resource on the server, for one of the following reasons:
A user attempted a connection to a TAS host with an invalid UNIX name. Verify the validity of the user name at realm->realm Connected Users->Connection Information. Check the spelling and case. Make sure a tilde (~) precedes each upper-case character.
You set the NetBIOS naming scope incorrectly. The naming scope must match the one designated by NetBIOS Name scope at Transports->TCP/IP NetBIOS Configuration. You may also check it with the tntransport command. NetBIOS Name scope also defaults to no naming scope. If you do not set the NetBIOS Name scope attribute, TAS ignores the client's naming scope.
When a user attempted a connection to a TAS host, an attach point defined in TAS's configuration of .profile.file in the user's home directory matched a UNIX user name or directory. Change the name of the attach point at realm->Manage File Services->[select the service]->Administer->Attach Points or with the tnattach command and retry the connection.
The user attempted connection to a directory with a user limit, and the directory has reached its limit. Try again later.
A user attempted to establish a print service connection to a nonexistent printer. Verify that either the server configuration contains a reference to the printer, at realm->Manage File Services->[select the service]->Administer->Configuration->Printer references or with the tnservice command, or the user's .profile.file contains a prdefault or printer command for the requested printer.
An attempted extended connection contains a path to a nonexistent directory. Verify the directory exists and try again. Stop and restart TAS if you modify the directory configuration by following "4.1.2 Shutting Down TAS Services", then "4.1.1 Starting TAS Services", or with the tnshut and tnstart commands.