APAR= II09493
CA400WINOPT  CLIENT ACCESS NETWORK DRIVE TROUBLESHOOTING

*** Last updated  5/19/97 ***


Unable to "Explore" the AS/400 or assign network drives
_______________________________________________________

Network drives will not work on a PC with a real mode
paging device.  That is, if the drive Win 95 pages to
is run by DOS drivers, network drives will not work.
Your PC may hang when you try to connect a network
drive in this case.  If you cannot assign a network drive
see the Client Access history log to see if network drives
discovered a real mode paging device.  You can also look
at the performance tab of the system icon on the Windows 95
control panel to see if your PC has a real mode paging device.


Another common cause for this problem is that the
client access network provider is not running.  Press
Ctl-Alt-Del once to bring up the Win95 task list.
You should see the tasks cwbbs (network drive) and
cwbnpred (print).  If these are not active, see the
section "Policy Management" below.

Another cause is a possible conflict with another
network provider.  Windows 95 allows multiple network
providers to be loaded (unlike Windows for Workgroups).
Windows 95 will pass certain requests to each
each registered network provider.  If another OEM
product is loaded that provides AS/400 network functions,
it may "grab" and attempt to process the request.
To resolve this conflict remove the conflicting AS/400
network provider.


PC Reboots at Startup
_____________________

This problem exists on certain PCs after CA/400 Network
Drives is started. If your PC Reboots when you sign on to
Windows 95 or Client Access, it may be because too many
applications are being started at Windows 95 startup time
after CA/400 Network Drives is started.  You may want to try
deferring CA/400 Network Drives connections until the PC is
fully started, or not have as many applications started via
the Windows 95 Startup folder.  Defer CA/400 Network Drives
connections by eliminating all CA/400 reconnected drives and
taking the Client Access Login Service Check (CWBCKVER)
program out of the Windows 95 Startup folder.

If these functions are needed, you may want to put the
CWBCKVER command and appropriate CA/400 Network Drive
connection requests, which can be done by using either the
NET USE command or by building the NETDRIVE program than
can be found in the CA/400 Toolkit, in a batch file that is
run after the Windows 95 operating system is fully up and
running and the applications that are going to be used have
also been started.

This problem seems to be most common on slower PCs with low
amounts of RAM or on very busy networks.  Switching to faster
PCs with larger amounts of RAM or improving your network's
performance seems to often minimize or eliminate the problem.


Naming Files for 16-Bit and 32-Bit Applications
_______________________________________________


If you plan to create AS/400 files or directories that are
shared between 16-bit and 32-bit PC applications, you must
use standard DOS naming conventions (8-characters plus a
3-character extension) when creating the file or directory.
If you use long file names or directories, 16-bit PC
applications will not be able to find the file or directory.


Running DOS Programs from the Network Neighborhood
__________________________________________________

DOS programs stored on the AS/400 system cannot be run when
you use the Windows 95 Network Neighborhood to access the
program.  If you need to run a DOS program stored on the AS/400
system, you can set up a network drive to the AS/400 system
where the DOS program is stored, then use the Windows 95
Explorer or a DOS prompt to run the program.


Drives Cannot Be Assigned by DOS Applications
_____________________________________________

You cannot assign a drive using a DOS application such as
DOSREDIR.EXE.  You must assign drives using the Windows 95
Explorer, the Network Neighborhood, or an application thatS/400
uses Windows 95 "WNet" API calls.



Preventing Network Drive Users From Accessing QSYS.LIB
______________________________________________________


Network drives users can access the AS/400 library/file/member
structure through a directory called QSYS.LIB.  QSYS.LIB is
at the root of the AS/400 directory tree.  If you do not
want your users to access this data through network drives
(via a drive letter, UNC name or network neighborhood) change
AS/400 authorization list "QPWFSERVER".  This authorization
list is checked by the AS/400 file server before a network
drive request to QSYS.LIB is performed.  For example, changing
*public to *exclude in this authorization list will prevent
all network drives access to QSYS.LIB.


Mapping Network Drives
______________________

Windows 95 provides four methods for mapping a network drive:

1) From an application -- you can write your own application to
   map a network drive using the 'WNet' Win 32 APIs.  See the
   Net400 example program in the Client Access for Windows 95
   toolkit for an example that uses these APIs.

2) From the DOS prompt -- the 'net' command that comes with
   Windows 95 can be used to map network drives.  For example,
   'net use w:   systemx dir' will attach drive w.  Note the
   path on the net command must be   system dir.  You cannot
   map a drive to the root of the AS/400 or to a directory
   more than one level deep with the net command (see the
   following note).  NOTE: Change all the " " to backslashes.

3) Using the Windows 95 Explorer -- Select Map Network Drive
   from the Tools pulldown menu, then specify the drive,
   system name and the path.

4) Using the right mouse button on a folder from the Network
   Neighborhood -- in some cases 'map network drive' is a
   selection when you press the right mouse button on a folder.
   You are prompted for the drive to map to that point in the
   directory tree.  Note as you traverse the tree using network
   neighborhood that map network drive is not always a choice
   on the menu displayed with the right mouse button.  It is a
   choice only on folders displayed when you double click on a
   system name (see following note).

Note for number 2 and number 4 - these methods of attaching a
network drive strictly follow the Windows Networking definition
of a network drive.  That definition is a network drive can be
mapped only to a shared point of a system.  Share points are
only direct children of systems.  Client Access/400 supports
more than this definition.  You can connect a Client Access
network drive directly to a system or anyplace in the directory
tree of the system.  If you want to connect a network drive to
the root of the AS/400 or deeper than one level deep in the
directory tree you must map the drive via number 1 or 3.

CAWINOPT cannot create a folder in QDLS
_______________________________________

When Win95 explorer creates a directory it creates a temp one
called "new folder" then puts the user in input mode.  When
the user types the folder name, Win 95 sends a rename request
to rename 'new folder' to what the user really wants.  If the
user doesn't want the folder then we get a delete directory.
There is support in Win 95 to vary the name of the original
folder by adding digits to the end of it.  For example, if
'new folder' exists then it will create 'new folder1', if that
exists they create 'new folder2', etc.

The create of the original folder fails in QDLS because QDLS
only supports the 8.3 naming convention.  'Net folder' violates
this convention because it contains a space and because the
name is over 8 characters long.

The work around is to create the folder in a DOS box using the
MKDIR command.


Policy file serving may delete required registry entries
________________________________________________________

If you use Windows 95 Policy Serving from a Windows NT or
Novell server you may you need to review your policies.  If
enabled, policy management is run automatically each time you
start your Windows 95 PC.  If a change is found it is
down loaded to your personal computer.  This may include
updating the registry with new settings that delete the entries
necessary to run network drives.  Network drives will not work
if required registry entries are deleted.  You must reinstall
client access to restore the registry.

To determine if your PC is under policy management
check with your LAN administrator or search for a *.pol
file in the Netlogon directory of NT or public directory
of Netware.
KEYWORDS:  CA400WINOPT NETDRIVE FOLDER CLIENT ACCESS
WINDOWS 95 WIN95 NETWORK
