Netware Client 3.32 for win95/98

[rcpis]

A windows 95 user is trying to login to a Netware 3.12 server using the Novell client v3.32 sp1 for win95/98. When the machine boots up, it goes directly to the desktop bypassing the Novell login totally. It displays the red "N" on the task bar but never runs login scripts, maps drives, or anything Novell related. If I uninstall the client using unc32.exe, the windows network login box appears and logs the machine into the NT network. The minute I put the Novell client back on, it goes directly to the desktop. I should also mention that with the Novell client installed, it does log the machine into the NT network. The Novell client is picked in the "primary network logon" box under network neighborhood. I also looked for s setting resembling "auto logon" under the client settings and didn't see any such animal. But if there were an "auto logon" setting, if it were on one might assume that the logon would run scripts and map drives. I hate to use that "assume" word. I'm so confused? Thanks for the help.

 

[BELITD]

You do have the prefered server, trees etc. all set in the network novel client under network properties I take it?
If so why not just use the client 3.1, it works fine for me(@least @win 95/98 level!!) are there any real benefits?

 

[JockMullin]

Hi, RCPIS

I have seen the problem you are reporting. The time it happened to me someone had been fooling with the config of the client and got it messed up somehow so it just would not log in, no matter what.

However, first be sure you are indeed communicating over the network and that your frame type is set to agree with the server. If it still won't work then you likely have the same situation. Here is what I did:

- In Network/Configuration tab remove the Novell client.
- Restart the computer
- Install the Microsoft client for Netware
That should enable you to log into the Novell network and
see the servers.
- Then reinstall the Novell client.

That did the trick for me.

Brgds
Jock

 

[Bluenose]

You can also get this fault if the network card driver does not autosense the network connection correctly. Go into the NIC properties and set the correct connection properties e.g. 100mb full duplex.

 

[paintedline]

I have seen this happen to... You might want to check the server console and see if you are exceeding the maximum license connections.