We help IT Professionals succeed at work.

No GUI logon screen with Client 32 and Windows95/98

kaleb
kaleb asked
on
413 Views
Last Modified: 2012-05-05
I did a hardware upgrade on a NW4.1 server and now 6 out of the 20 workstations can't logon.  2 of witch are Client32 and the other 4 are Windows Netware logon client.  Can logon with Client32 if you go the long way using START/PROGRAMS etc..

What is going on and how do I resolve this issue?

(Please Rush, client is in a fit)
Comment
Watch Question

idt

Commented:
Just firing out a thought, did this server involve a new netowrk card, if so, check that both IPX protocals, Ethernet 802.2 & 802.3 bound succesfully to the network card driver, and check how the win'95 machines are set, protocal specif, or auto.

-iDT

Commented:
Require more information as idt suggests.

When you say you can login when going the long way, what does the client come up with when ws booted - doesnt come up at all or gives error ?

When going the long way - do you supply more information or it just lets you login using just userid and password ?


Author

Commented:
WS boot directly to desktop without logging on both Client32 and Win95/98.  
When going the "long way" (Right mouse click on Network Neighborhood and select Client32 logon) it gives an error saying "Access Denied".

Yes the server involved a new NIC it was a complete upgrade, HDD, Mainboard, NIC.  Checked the IPX protocals and they were bound correctly.
Commented:
Unlock this solution and get a sample of our free trial.
(No credit card required)
UNLOCK SOLUTION

Commented:
Totally uninstall the Novell Client see doc: http://support.microsoft.com/support/kb/articles/q150/9/25.asp and then reinstall the latest netware client (http://www.novell.com/download/index.html).

Make sure that the Primary Network Login is the Netware (Control Panel, Network, Configuration). Check to see if the context is set correctly and that you are using the correct frame type.

If you still get the same problem then try to remove everything from the startup (all tsrs) including from the registry to free up resources for the client. First Backup the registry then Look in: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServices
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
Temperarily get rid of everything except Systray.exe and then install the client. Some TSRs can cause problems with Network clients.

Commented:
Check your registry for autologon and remove it.
hkey_local_machine
software
microsoft
windows
current veresion
network
Real Mode Net

Author

Commented:
Sorry I have been out of town and was just able to try your suggestions.  The one that worked was "myeaman".  I had to remove Client32 manually and then used the Microsoft Netware Client.  For the other workstations I had a chance to look at the problem myself and found that some ports on the switch and both hubs were blown, so i just shut them down and brought them backup.

Thank you all for your help it was much appreciated!!!
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a sample view!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.