Win2K, Netware 3.2 & Network Neighbourhood

[Felix]

Hi there

I'm playing around with Win2K. I have a LAN consisting of a Netware 3.2 fileserver (the login server), an older generic cd rom server ( http://www.axis.com ) emulating a netware 3.x server, a couple of Win9x clients, and 2 Win2K clients.

Without Win2K I would run Client for Netware networks and IPX protocol for basic netware server access. The file and cd servers can be seen then. First network drive is set to J: since there are too few local drives if we start at F:
Then, file and printer sharing for netware networks, to see the other clients in network neighbourhood.
Then finally, TCP/IP for internet access over a router.
Everything is fine so far.

Now I've added the Win2K clients. With the built-in netware client I can logon the netware 3.x network but there is a login script error shown babbling something silly which doesn't matter (empty cd drives cannot be mapped of course).
The first network drive is then mapped as F:\Login AND J:\Sys, and the cdrom server is shown in network neighbourhood but it is "empty", although there are the CD-ROMs mapped.
If I disable login script processing I get no error, first network drive is correct mapped to J: but there is even an empty cdrom server. I can't connect manually, and the cdrom drives aren't mapped. Read: there are no cdroms.

(It could be that the netware emulation of the axis cdrom server is incompatible with Win2K - but this is another story. I've tried to run SMB service on the cd server but it did not work. This is another story.)

I'v tried Netware Client 4.8 from Novell website. With this I can logon, everything seems to be fine, but it refuses to run client for microsoft networks (for network neighbourhood) the same time, wich I'm forced to use now to see the other computers in the LAN, since Win2K does not support fiel and printer sharing for netware networks:

In Win2K I cannot see the other computers in network neighbourhood. So I switched one Win98 machine to client for netware networks AND client for microsoft networks AND file and printer sharing for microsoft networks. Then the computers running client for microsoft networks and its file and printer sharing can see each other, and everything would be fine.

Conclusion
----------------
1) Until now I used file and pritner sharing for netware networks to see the other computers, but this is not supported from Win2K.
2) Therefore I will use client for microsoft network and its file and printer sharing to "peer to peer" the clients with each other. This would basically work.
3) The netware client from Win2K does only logon to a single netware server. (at least it looks like this. ok, it could be that the cd server emulating netware itself is the problem.) But I need to logon the cd server as well.
4) The Novell netware client 4.8 does logon correctly to the netware environment but suppresses the microsoft network, thus rendering it useless. Read: There are the netware servers but no other client computers.

What should I do?
Any help is highly appreciated.

[Felix]

Experimented more. Results:

1) With Novell Client 4.8 it maps on "FMS\Sys\Home" (J:) where FMS is the netware server.
But I want it mapped Sys on "FMS" (J:) Thus Novell Client 4.8 is bad.

2) With M$ client Service for Netware it maps Login on "FMS\Sys" (F:) which is wrong, but maps Sys on "FMS" (J:) which is right.

3) With both clients, if I disable script processing, everything is fine except there is no cdrom server (see below).

4) Network Neigbourhood running on M$ network works with both clients but is terribly sloooooooooooow! If I want to browse a drive on another PC I must wait say, 5 sec until windozze has found it with the flashlight. When I use the same settings on a Win98 PC the drive on the networked PC is there immediately after clicking to it!?!?

5) Axis CD server is not Win2K compatible. Have to evaluate an upgrade solution.