"HELP" CAN'T CONNECT USING NOVELL CLIENT

I have had a similar situation with the client. Found that some anti-virus software causes conflicts with certain client revs, make sure your using the latest drivers for your nic. Some e.g. 3Com need modifications in the client properties ( check vendor site for information and drivers ). Also make sure that your lan cable and connectors are in excellent shape ( we had to re-make alot of ours ).

Good Luck,

What is the exact message ?

I assume that you have got the 5.1 server running IP only?
When the Novell client was installed, was the option for IPX or IPX & IP chosen? If unsure, try reinstalling it making sure that you have chosen the option of IP (for 5.1) AND IPX (for 3.2).
However, are you doing this just for data migration and then going to lose the 3.2 server? If so, have you considered restoring a backup tape, which will ensure that all trustee rights are included (assuming that the trustees exist in the NDS tree).
If I am wrong about IP and you are using IPX to connect to the 5.1 server, what frame type are you using? Is it the same on both servers and the client?
Do you have an exact error message available, and if so, what have you done to receive the message. Mail me off-line if it helps.

Roger

I doubt it is a NDS problem. My guess is it is a Frame type issue. You said you were using frame type 802.3, my question is are you also running 802.2 on any servers? The client defaults to Auto Frame type, this meeans when the client broadcasts requests in all frame types. The first responding server sets the frame type for the client. A client machine can only use one frame type, either 802.3 or 802.2 not both! Netware 3.2 and 5.1 default to 802.2 frame type. I would verify IPX network numbers to be sure they are the same on the 3.2 box and the 5.1 box. If you only use 802.3 lock the client to the 802.3 frame type under IPX protocol and under IPX32. There is a good TID on this #10022157 . I would suggest for you not to run both frame types on your network, I would also suggest to you to run 802.2 instead of 802.3 . Be careful of Jetdirect cards and other print servers that they are configured properly and do not have both frame types either. To troubleshoot this problem type TRACK ON at both consoles before you turn on the Problem PC, then watch both consoles for the Get nearest server requests and make sure you see the requests from your PC. Hope this helps.

Greg

Make sure you check the properties of the Novel Netware Client, then go to Client Tab, then check to make sure you have the proper tree and the correct context and your drive letter for the network

I would go with answer # 5. If you can see the tree and server then the protocols are correct. It is probably your context.

This question was closed by the author