?
Solved

No GUI logon screen with Client 32 and Windows95/98

Posted on 1999-01-18
7
Medium Priority
?
393 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)
0
Comment
Question by:kaleb
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
7 Comments
 
LVL 3

Expert Comment

by:idt
ID: 1594797
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
0
 
LVL 4

Expert Comment

by:Zombite
ID: 1594798
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 ?


0
 

Author Comment

by:kaleb
ID: 1594799
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.
0
On Demand Webinar: Networking for the Cloud Era

Did you know SD-WANs can improve network connectivity? Check out this webinar to learn how an SD-WAN simplified, one-click tool can help you migrate and manage data in the cloud.

 
LVL 5

Accepted Solution

by:
jstegall earned 800 total points
ID: 1594800
If the GUI logon does not appear on bootup, check the MSDOS.SYS file to see if BootGUI=1 is
under the [options] section.  If not add it isn't, add it. You will have to change attributes since that
file is Read Only, Hidden, and System.  For the DOS/Windows systems,  Do you have the workstations attaching to the network in DOS mode before launching windows.  Windows 3.x
logon was never good IMHO so I never used it and required users to login before launching
Windows.  You will need to make sure the Netware drivers are where they can be loaded when
windows starts, so it sounds like a file is missing or not loading. As IDT said check your
autoexec.ncf on the server then make sure the frame type on the Win95 system match that
and is not set to Auto, since some NIC drivers don't do auto to well.  On the DOS/Windows
systems check the NET.CFG in the \NWCLIENT\ directory  you should have a line that say
frame=<whatever frame the server is using in its load statement>
HTH
0
 

Expert Comment

by:myeaman
ID: 1594801
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.

0
 

Expert Comment

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

0
 

Author Comment

by:kaleb
ID: 1594803
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!!!
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will show how Aten was able to supply easy management and control for Artear's video walls and wide range display configurations of their newsroom.
The top devops trends for 2017 are focused on improved deployment frequency, decreased lead time for change and decreased MTTR.
In this video we outline the Physical Segments view of NetCrunch network monitor. By following this brief how-to video, you will be able to learn how NetCrunch visualizes your network, how granular is the information collected, as well as where to f…
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
Suggested Courses
Course of the Month9 days, 11 hours left to enroll

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question