Tried all the suggestions previously. Can map to Windows servers just AS/400s that I cannot map to but get no issues from 95 PCs.
regards
Amo Sohi
Main Topics
Browse All TopicsWe are currently running a project to upgrade all our 95 pcs to XP but I need to resolve a mapping issue I am having, detailed below.
I am trying to map a drive on my XP pc to folder QDLS on a number of our AS/400s. Using a 95 pc, I can map without any issues whatsoever, however when I try the command below I can not map a drive. I have tried all the obvious solutions but still no joy.
Command:
net use x: \\xxx.xxx.xxx.xxx\qdls
I have also tried the above command, specifying my AS/400 user profile and password but still nothing.
Error Message when using above command:
System error 53 has occurred.
The network path was not found.
My profile on the AS/400 is correctly configured through Directory Entries. I have read some reports stating password on XP and AS/400 must be the same but this would not be possible due to the number of users we have on location. I have also tried setting up the AS/400 IP number in to my HOSTS file and also tried starting NetServer on our AS/400, something which is not required to be started for 95 users to gain access but still no joy.
Any help would be greatly appreciated.
Regards
Amo Sohi
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Not sure what you mean when you say create a share using OPSNAV. We do not use Client Access at all, currently use NetManage software (NetSoft).
Do you know what the difference is for communication between 95 & XP, which would stop me from connecting. I have read something about profiles & passwords needing to be the same on the network & AS400. I will try this shortly and see if that works. I have also read some comments about users being able to connect using QSECOFR profile but not their own profile.
I have just started NetServer on another of our AS/400s, running V4R4M0, then tried to map a drive using 'net use x: \\xxx.xxx.xxx.xxx\qdls /user:username password', identical to what I did earlier but it comes up with the message stating 'System error 53 has occurred. The network path was not found.'.
The only AS/400 it currently works on is running V4R5M0. Have also tried on V4R4M0 & V5R1M0 but does not work. Is there anything else I might be missing. My profile is identical on all systems and I have a directory entry added.
Now I am stumped.
On the As/400 that I can map a drive to, if I follow the instructions above, I can see folder QDLS but I cannot see the folder on any of our other AS/400s that I cannot map to.
One thing I have noticed is if I run DSPNETA, on the system I can map to, the Network Server Domain, is the same as the System Name but it is different on the other systems. Is this something I need to worry about?
Hi I am looking through the manuals try this
Troubleshoot iSeries NetServer location on the network
If you experience problems when trying to find iSeries NetServer on the network, you can take several steps to resolve the problems:
Ping the iSeries NetServer server name. Pinging the iSeries NetServer server name reloads the iSeries NetServer IP address into the PC client cache file.
Verify that you are using the correct system name for iSeries NetServer. The QSYSOPR message queue specifies the correct iSeries NetServer server name.
Verify that you have configured your PC client to properly resolve the iSeries NetServer server name to an Internet Protocol (IP) address. Configure your PC client to resolve the iSeries NetServer server name to an IP address in one of the following ways:
Map the iSeries NetServer server name to its IP address by using the Domain Name System (DNS).
Map the iSeries NetServer server name to its IP address by using the Windows Internet Naming Service (WINS).
Map the iSeries NetServer server name to its IP address by adding an entry to the LMHOSTS file.
I am thinking that you need file shares for XP.
Can you load client access on to 1 PC as a lot of config options use the PC interface.
--------------------------
Control access to iSeries NetServer file shares
Designating an access setting for iSeries NetServer file shares through iSeries Navigator allows you to control the level of access that PC clients have to objects in iSeries integrated file system directory paths. If you set the access of a file share to Read only, then clients do not have the authority to change a file. If you set the access of a file share to Read/Write, then client users can change any files they have authority to in the shared directory paths.
To set the access for an iSeries NetServer file share, follow these steps:
Open a connection to iSeries Navigator on your iSeries.
Expand Network.
Expand Servers.
Click TCP/IP to retrieve a list of the TCP/IP servers available.
Right-click iSeries NetServer and select Open.
Expand Shared Objects.
Right-click a file share and select Properties.
Click the pull-down menu in the Access field.
Set the file share access to read only by selecting Read only. Set the file share access to read/write by selecting Read/Write.
And create a share for system that is not working
--------------------------
You may want to check your netserver name
Change the server name of iSeries NetServer
The iSeries NetServer server name is the name you use to install the iSeries Access for Windows and to access your iSeries NetServer over the network and the Internet. Under most circumstances, you do not need to change the server name that iSeries NetServer uses on iSeries. Even though you can connect to iSeries NetServer by using any server name you choose, you should not change the server name from its default. The name should be the same as your iSeries system name but prefixed with a Q (for example, QiSeries if the system name is iSeries). If, however, you must change the server name, review the naming guidelines before doing so. You can view the iSeries system name in the iSeries network attributes by using the Display Network Attributes (DSPNETA) CL command.
Note:
You must have *IOSYSCFG authority to change the iSeries NetServer configuration. The change to the server name does not take effect until the next time that iSeries NetServer is started.
To change the iSeries NetServer server name by using iSeries Navigator, follow these steps:
Open iSeries Navigator and connect to the system you want to work with.
Expand Network.
Expand Servers.
Click TCP/IP to retrieve a list of the TCP/IP servers available.
Right-click iSeries NetServer and select Properties.
On the General page, click Next Start. In the Server name field, specify the name that iSeries NetServer should use.
Dave
Hi
I have always don it via Ops nav and never heard of an AS/400 command.
I am guessing that IBM figured that if you are mapping a network drive, you will have a PC so you can use OPSNAV
The main IFS commands available on the 400 are on these menues
FSDIR
FSOBJ
FSSEC
and there is nothing there?
again sorry
Dave
Note that your Win95 is probably not using Netserver for access to /QDLS. NetManage is probably providing access through the old Original File Server. PC Support and Client Access both could map drives through this server. It's started via STRHOSTSVR *FILE.
When WinNT, Win2K and eventually WinXP became more of a standard for desktop access, the Netserver server became important. Access was linked to Windows Network Neighborhood through Netserver and the older File server became less important.
This is old enough info that I'm no longer sure how much of the IFS was available through the File server. It might be that you could leave Netserver running, end the *FILE host server, and then all your Win95 PCs would lose access while WinXP continued to work. It might also be that _only_ /QDLS folders are available to Win95 using the File server, though Win95 still ought to be able to find the Netserver shares.
I'm pretty sure that WinXP won't use anything that's made available through NetManage. Netserver shares probably _have_ to be created.
Shares can be managed via the Server Support APIs. OpsNav is not required. But it takes a bit of practice before the APIs are useful.
V5R3 makes a QUSRTOOL tool available, the NETS menu and its programs, that used to be downloadable from an IBM site. I don't know if V5R2 has the tool; it's not on the V5R2 system I currently have available. Perhaps it still can be downloaded. I first used it back at least as early as V4R4. This menu has most Netserver functions and gives a green-screen interface for them. I see no reason why it couldn't be compiled back to V4R4 and possibly earlier, though there might be changes needed here and there. The tool demonstrates use of the Server Support APIs.
Tom
Business Accounts
Answer for Membership
by: dedy_djajapermanaPosted on 2004-04-15 at 05:55:08ID: 10832649
Hi,
I presume that you have another 95 PC that’s able to connect to QDLS at the same time you’re trying from XP (this is to verify that the Netserver in AS/400 is up, and yes, Netserver has to be up for file sharing, likely it’s auto started on IPL in your system.)
1. Verify network connection to AS/400, like ping or TELNET (I believe you should have tried this).
2. Verify that the XP PC can connect to a file sharing by “net use” to other server. I suspect the problem is here, i.e., some network setting in the XP PC. E.g., if NetBIOS over TCP/IP is disabled (should be enabled), or Client for Microsoft Network is not selected.
Regards,
DD