Networks

Ask something
Discussion Locked

Netware 4.11 sp8& Netwar6.0 sp2

0 helpful
8 replies

by brian

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We put up a new Netware 6.0 server just out of the box from Compaq. We still have our existing 4.11 Server but we can not connect to it from the client side anymore. We have 4.83 SP1 client and ip running on the new server and ipx running on the 4.11 Server. Sporadically we can connect to the 4.11 Server. When we try to login into the 4.11 server it gives us tree or server name can not be found. I have tried changing the preferred protocol on the client to IPX and still get the same error. I also tried using the Microsoft client for Netware and can not connect. It seems the client has some registry setting so it will not connect to the 4.11 Server. Do I need to change a registry setting in windows on the client side. Any help would be great.

8 replies

by budthegrey

For the time being, you'll should use IPX to connect to your servers. Make sure IPX is loaded and bound at both servers, and that they agree on frame type and the IPX network address. On the NW4.11 server, when you type DISPLAY SERVERS at the console, you should see the name of the NW6 server in the list. If you didn't configure IPX when you installed NW6 on the new server, you'll have to add a server ID line to the autoexec.ncf before you can bind IPX to the network card (see novell knowledge base TID 10073957).

Once that's done, remove any existing vlients from the workstation, and re-install 4.83. Do a custom installation and tell it to install IPX only as the protocol.

At that point, you should be able to browse/login to theboth servers.

HTH

by budthegrey

I should have expanded my remark "make sure they agree on frame type and IPX network address".

In theory, you can indeed connect to different trees or servers with different protocols. In practice, the performance is horrible; the workstation spends much time deliberating which protocol to use, waiting for timeout s, etc. We tried it here, and when we took the time to move to all one protocol, performace was greatly enhanced.

by deroode

The solution of Bud may work, but in theory it should be no problem connecting to one tree with IP and another with IPX.

Your problem may have to do with automatic frame type detection. It may be that IPX is already configured on the NW6 box, but with a different frametype than the 4.11 box. There may be others causes that the client picks up a wrong IPX frame type.

On the 4.11 server load another instance of the networkdriver, with a different frametype. Netware 4.11 defaults to 802.2,load the additional frametypes 802.3 and ethernet_II, and bind IPX to these frametypes.

LOAD CPQNF3 SLOT=2 FRAME=Ethernet_II NAME=cpq_ether_II
BIND IPX cpq_ether_II NET=100
LOAD CPQNF3 SLOT=2 FRAME=802.2 NAME=cpq_8022
BIND IPX cpq_8022 NET=102
LOAD CPQNF3 SLOT=2 FRAME=802.3 NAME=cpq_8023
BIND IPX cpq_8023 NET=103

(of course use the network numbers and lan drivers that are appropriate for your environment.)

by dragon_45

Off you Network goto your IPX/SPX protcol properties. Peg your frame as opposed to automatic. This works for me here with Netware 6.0 and 4.11. We use the Novell client running IPX/SPX with Ethernet II frame type.

Good luck
Richard F. Bolha

This discussion is closed to new replies.