Windows Xp Logging-In Screen Problem
#1
Windows Xp Logging-In Screen Problem
I have had to rebuild both my PC's (and my network) over the last fortnight.
I installed Client Service For Netware in an effort to solve a problem (it wasn't the answer) then deinstalled it.
Ever since then I have been getting the Netware Login Screen (single account name & password) rather than the XP screen (multiple account names visible).
The pain now is that if another user wants to use the PC I get logged out completely, as opposed to being able to switch user while keeping my programmes running.
I have tried repairing Windows via the system CD and turned off any services that I think are linked to CS for N but no joy as yet.
Anyone know how I solve this please (its driving me nuts!)? I don't want to rebuild.
I installed Client Service For Netware in an effort to solve a problem (it wasn't the answer) then deinstalled it.
Ever since then I have been getting the Netware Login Screen (single account name & password) rather than the XP screen (multiple account names visible).
The pain now is that if another user wants to use the PC I get logged out completely, as opposed to being able to switch user while keeping my programmes running.
I have tried repairing Windows via the system CD and turned off any services that I think are linked to CS for N but no joy as yet.
Anyone know how I solve this please (its driving me nuts!)? I don't want to rebuild.
#3
After a google search
found this and most do mention the network properties
Go to your network connections, then properties. Click uninstall on the line that says client services for netware. Reboot... no more problem
found this and most do mention the network properties
Go to your network connections, then properties. Click uninstall on the line that says client services for netware. Reboot... no more problem
#5
If, due to problems or corruption, the client can not be successfully removed from the Network control panel, use REGEDIT to manually remove/change the following registry keys and values.
Remove three keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Novell
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\NetWareWorkstation
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Print\Providers\NetWare Print Services
Change the GinaDLL value:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon
Under this key exists a string value named "GinaDLL".
Edit this entry from "NWGINA.DLL" to "MSGINA.DLL".
Prior to rebooting, verify that MSGINA.DLL exists in the Windows SYSTEM32 directory and reflects the appropriate date/version for the installed Windows service pack. Copy MSGINA.DLL from the appropriate service pack if necessary.
Restart the workstation. Note that the above steps only disable the core client functionality (unlike removal from the Network control panel applet where dependant services are also removed). As such, you may likely encounter error messages and/or service start failures from other optional components that are still running, such as ZENworks workstation components or protocol components such as CMD.
Once having achieved a workstation state where the core client functionality is no longer running, the only way to ensure that all client components get properly removed is to install the Novell Client for Windows NT/2000 such that a removal via the Network control panel can be re-attempted. Although the Novell client could not be successfully removed via the Network control panel initially, manually disabling the client and then forcing a re-installation can potentially correct any network or registry configuration issues that are preventing successful un-install.
An additional troubleshooting step would be manually disabling the core client functionality as described above, and then furthermore removing any and all additional Network control panel entries including the network adapter(s). (Note Windows may warn that the network configuration is incomplete.) After restarting Windows with this "empty" network configuration, re-installing the network adapters and services and then finally re-installing the Novell Client for Windows NT/2000 would rebuild as many possible aspects of the Windows networking configuration..
Remove three keys:
HKEY_LOCAL_MACHINE\SOFTWARE\Novell
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\NetWareWorkstation
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Print\Providers\NetWare Print Services
Change the GinaDLL value:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\WinLogon
Under this key exists a string value named "GinaDLL".
Edit this entry from "NWGINA.DLL" to "MSGINA.DLL".
Prior to rebooting, verify that MSGINA.DLL exists in the Windows SYSTEM32 directory and reflects the appropriate date/version for the installed Windows service pack. Copy MSGINA.DLL from the appropriate service pack if necessary.
Restart the workstation. Note that the above steps only disable the core client functionality (unlike removal from the Network control panel applet where dependant services are also removed). As such, you may likely encounter error messages and/or service start failures from other optional components that are still running, such as ZENworks workstation components or protocol components such as CMD.
Once having achieved a workstation state where the core client functionality is no longer running, the only way to ensure that all client components get properly removed is to install the Novell Client for Windows NT/2000 such that a removal via the Network control panel can be re-attempted. Although the Novell client could not be successfully removed via the Network control panel initially, manually disabling the client and then forcing a re-installation can potentially correct any network or registry configuration issues that are preventing successful un-install.
An additional troubleshooting step would be manually disabling the core client functionality as described above, and then furthermore removing any and all additional Network control panel entries including the network adapter(s). (Note Windows may warn that the network configuration is incomplete.) After restarting Windows with this "empty" network configuration, re-installing the network adapters and services and then finally re-installing the Novell Client for Windows NT/2000 would rebuild as many possible aspects of the Windows networking configuration..
#6
Guys,
Thanks. Tried Nick's solution earlier but no joy. Believe it or not the way the problem is solved is "Control Panel - User Accounts - Change the way users log n & off - (tick the boxes shown)".
WB
Thanks. Tried Nick's solution earlier but no joy. Believe it or not the way the problem is solved is "Control Panel - User Accounts - Change the way users log n & off - (tick the boxes shown)".
WB
Trending Topics
#8
Originally Posted by Nicks VR4
lol easiest way first
Did read something regarding that earlier too doh!
Did read something regarding that earlier too doh!
Thread
Thread Starter
Forum
Replies
Last Post
Mattybr5@MB Developments
Full Cars Breaking For Spares
12
18 November 2015 07:03 AM