We have two Novell 3.12 Server and one Novell 5.1SP5 Server. All of our workstation are Win2000 with Novell Client 4.83SP1 (IP/IPX) and able to map the volumes on 3.12/5.1 servers through Novell logon script without any problem. Recently we add some Windows XP workstations with the same Novell Client, but they are facing mapping issues. On the logon process, it’s able to map all the volumes on 3.12 server (IPX), but failed mapped 5.1 server volumes (IP). It seems to me, it is something wrong with XP, as all of our workstations with Win2000 not facing any mapping issue. On Netware connection window (RED-N), 5.1 server show IPX, which supposed to be IP. The errors are as follows: LOGIN-4.22.00-430: The following drive mapping operation could not be completed. [ROOT O:=AND730S1/SYS:] The error code was 8804. Need help from the Novell Guru’s.

First off, is IPX bound to your NIC in the 5.1 server? It looks like you are running IP only on the 5.1 server, and IPX on the 3.x servers. If you are also running IPX on the NW5.x servers, or want to, run "nwconfig" and bind IPX to the NIC. I have heard tell that XP may not support IPX protocol. That may be the difference between Win2k and XP. To use IPX, the PC also has to be running IPX. Check your protocols on the PC to check, or add if possible. I would think that if IPX was running on all PC's and servers, your map statements would work. If no IPX is possible on the XP boxes, you will probably need to set up SLP on the 5.1 servers to run IP only for those XP clients. SLP stands for Service Location Protocol. NetWare uses it to find services that belong to the NDS tree that the server exists in. Similar to Windows netbios, and nbtstat funtions etc for finding windows network services. SLP in novell finds the Servers, volumes, printers, etc. that exist in the NDS tree for and IP only NetWare network. The error message you have indicates that the volume could not be found when trying to map to. To test, add a new mapping in the login script pointing to the IP address of the server\volume, instead of the typical worded statement of NW3.x. example: [Map Root O:=172.16.16.15/SYS:] where the IP address would be that of the NW5.x server. If that will map, then your SLP is not working. To set up slp on the server, just type in at the command prompt on the main 5.x server "SLPDA". That will set up a SLP Directory Agent on the 5.x server. In addition, if you have other 5.x servers, you will need to edit their sys\etc\slp.cfg file. In the file is a remarked statement to add the static IP to the SLPDA server. Unmark the remark, and add the SLPDA server IP. There is an example IP in the file. Leave the da lpv statement as it is. Only add the SLPDA Server IP address where the sample IP address is. Save the file. Go to that servers console, and enter "set slp reset = on" You will see the SLP register statically with the SLPDA server IP. Look in the NDS tree, and you will find a new container called "unscoped". Services registered will start showing up in this container and/as NDS uses those to find volumes and etc for mappings to work etc. In addition, in the client properties on the PC, there is a tab called "service Location". In the bottom half, add the IP of the SLPDA server you have set up, and check the "static" box. Click OK, and it will prompt you to reboot. It is easier to do than to explain. Hope it helps your XP boxes see the network services. Also, there are many articles at http://www.novell.com support link about SLP. Netware 5.x used SLP version 1 and this kind of setup is called a "static SLP setup". Netware 6.x uses SLP version 2, and creates a container called "scoped" now, and works quite a bit better than version 1. We had to set up our 5.x servers with Static SLP for them to work right. NW6.x SLP seems to work as it comes out of the box without having to do all the static setup stuff. Good luck...