• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 162
  • Last Modified:

Forcing the Client for MS Networks Logon Box

I have a windows 95 computer which I have just installed with a realtek 10/100 network card. I am using TCP/IP as the protocol and Client for MS Networks as the Primary Logon

I have Client for MS Networks loaded as the only Network component for Clients
Under this client I have ticked the Logon to Windows NT Domain and entered the relative domain name

When the system reboots or restarts or I logoff and ask to logon as another user, I am only able to get the Windows logon box not the Client for MS Networks Logon Box

How can I force the Client for MS Networks box to appear
1 Solution
If you have given Client for Ms Networks as primary logon.. had that other settings are correct. It should prompt for Ms Client Logon.

Check your settings allover again.

Also check your NIC status by Pinging to ( If your protocol is TCP/IP).

Correct me I'm worng if any.

Take a look if the computername is correct, and in the workgroup field, fill in your domain name, you can find this in the networkpanel. Check also your nic setting, if it does'nt work try reinstalling your nic, and the tcp/ip protocol.
nmilmineAuthor Commented:

Have tried all of your suggestions a number of times.  This is now happening on more than one computer. I have tried installing a different NIC but result stays the same.  Have tried deleting all networking in both normal mode and safe mode.  Still no change.


Will try pinging today.  There has been no problem with recognition of any cards I install.
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Check for Duplicate computer names and/or IP addresses on your LAN.  Are you using DHCP?  Has the DHCP server been recently added or changed?

nmilmineAuthor Commented:
he computer at this point has not even been connected to the network.

I tried your pinging today and received a positive response

I installed the netbui protocol today, then deleted tcpip.  Then reloaded tcpip and removed netbui.  This brought back the correct dialog box on one machine.

I'm not sure if this was a fluke or if there is some logical explaination that I have missed.

Unfortunately this didn't work one the second machine.

Thanks for your comments thus far.

I ran across this problem with several computers we got pre loaded with 98, I spent hours trying to fugure out why I couldn't get the domain input box up so that I could log in to the domain. I Don't know if this will help for you but it did for me.  In your network setup make sure you remove the Microsoft Family Logon Service and leave the Client for MS Networks as your lone logon service.  The other thing you may want to check is the Access Control Tab, ensure that you enter the domain in for accessing the domain user list for shared resources.  Even though it may not find one tell it to use it anyway and select NT Domain for Provider.. this worked for me.. good luck.

I came across this problem in my last job. There seems to be a bug in certain versions of windows 95 that puts the clients in the wrong order in the registery.
Try a different version of 95 if you have one or downlaod the patches from the Microsoft Web site.
Fraid I can't remember the registry entry's to edit.
Try this:  Go to your windows directory and look for any and all files with a .pwl and .acl extension.  Delete them.  Warning if you had any passwords saved previously, such as your isp, this will most likely wipe them out, but if you know your passwords shouldn't be a problem.  Now close all programs and log on as a new user.  Do you get a windows logon or ms network?  If that didn't work check to see what your workgroup is set as in the identification tab of the network properties.  Try setting it to your domain name.
here's what helped me:
flush your IP (winipcfg -> release all)
renew it again

see if it helps
If you set the Logon to Windows NT to true you don't need to set the MS Networks as the Primary Logon. It should automatically ask for the password. Try reinstalling the Clients for MS Networks.
ABCStoreand BChew may have a point in here.  If you use DHCP and the client was unable to secure an IP (and you already  clicked on NO when asked for future notifications of DHCP messages), the logon window won't be displayed.  You could try extending the IP lease period to a much longer window (say 7 days).
nmilmineAuthor Commented:
Thanks to everyone for their comments.  I have awarded the points to ABCStore because after flushing, renewing and rebooting the dialog box reappeared.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now