Q. How can I stop my Windows 9x clients having to enter a separate Windows password when logging onto a domain?

A. In the old Windows for Workgroups days the admincfg.exe utility was used to disable password caching and a similar functionality exists in Windows 95 and Windows 98.

Start the registry editor (regedit.exe)
Move to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\Network
From the Edit menu menu select New - DWORD Value
Enter a name of DisablePwdCaching and press Enter
Double click on the new value and set to 1. Click OK
Close the registry editor and reboot the machine
Upon reboot clients will no longer have to enter a local password, just the domain.

When clients use the Password control panel applet the "Change Windows Password" button under "Windows password" will be grayed out and only "Other passwords can be set". Clients would then select "Microsoft Networking" as per normal

Q. Some of the Windows 95/98 clients do not show up in Network Neighborhood.

A. This is usually caused by the machines not having "File and Print Sharing" installed

Start the Network control panel applet
Click the button "File and Print Sharing" and then enable them.

Q. How can I stop a Windows 95 machine acting as a browse master or backup browser?

A. To stop a Windows 95 machine acting as a browse master perform the following:

On the Windows 95 machine start the Network Control panel applet (Right click on Network Neighborhood and select properties)
Click the Configuration tab
Check the list of installed network components for "File and Printer sharing for Microsoft Networks". If this is here goto step 5.
If this is not installed click the Add button, select Service and click Add. Select Microsoft and select "File and Printer Sharing for Microsoft Networks" and click OK. Click OK to the configuration tab and when asked reboot the machine.
Select "File and Printer Sharing for Microsoft Networks" and click Properties.
In the property box click Browse Master and select Disabled in the Value box.
Click OK

Q. My Windows 9x clients cannot see shares over 12 characters.

A. Windows NT allows shares to be created that are more than 12 characters and Windows NT based machines can see and use these quite happily. Windows 9x clients however can only connect to shares of 12 characters or less.

There is no fix for this and see if you require Windows 9x clients to connect to a share make sure it is 12 characters or less.

Q. How do I install the Windows 9x directory services client?

A. Windows 2000 ships with a Windows 9x directory services client which allows 95 and 98 to used some of the more advanced features of the Active Directory. To install perform the following:

Insert the Windows 2000 Server
Move to the Clients\Win9x folder
Double click on Dsclient.exe
Click Next to the wizard start-up screen
Select the 'I accept this agreement' on the license screen and click Next
Click Next to the installation start dialog box
A number of files will be installed on the client machine
Once the file copy has completed click Finish to the wizard
Click Yes to restart the machine
You could install the client from a network share by copying the Dsclient.exe to a share on a server.

With the DS client installed you can perform full searches on the Active Directory, for example selecting Start - Find - Printers you can enter your location and it will find printers near you!

This installation also installs the files Secur32.dll, Msnp32.dll, Vredir.vxd, and Vnetsup.vxd which support enhanced authentication. Even if you uninstall the Directory Services Client these files will remain.

Q. How do I enable profiles on a Windows 9x machine?

A. By default all users of a Windows 9x machine share the same profile, however machines can be configured so that each logon name can have individual settings such as background, colours etc. To enable multiple profiles perform the following:

Start the Passwords Control Panel applet
Click the "User Profiles" tab
Check the "Users can customize their preferences tab". You also have to the options to select additional:
- Include desktop icons and Network Neighbourhood
- Include Start menu and Program groups in user settings
Click OK
You will have to restart the computer
Once restarted when you logon for the first time as a user on the machine you will be given the option to retain options. Click Yes.

The profiles are stored in the C:\windows\profiles\ directory (or wherever windows is installed).

If you wanted to automate this process you could create a system policy using the Windows 9x policy editor

Q. My WINS clients have stopped registering/querying the WINS server.

A. Tell-tail signs of clients that have stopped using WINS are as follows:

Unable to ping a remote computer (across a router) by its computer name (NetBIOS name).
Cannot log on to a domain when the only domain controllers are on other side of routers.
Unable to perform Net View or Net Use computers that are on the other side of routers.
Cannot retrieve the browse list of a remote domain that the client sees in its local browse list.
A known problem exists when a secondary WINS is not defined as the algorithm is as follows

When booting up, register your name with your primary WINS server. Or when performing a normal name query, first send the request to your primary WINS server.
If the primary WINS server does not respond after 3 attempts, send your registration or query to the secondary WINS server listed.
If the secondary WINS server does not respond after 3 attempts, send the query again to the primary WINS server, and continue alternating between primary and secondary WINS server until one of them responds.
The problem results if there is no secondary WINS server listed. The client may revert to B-Node (broadcast only) behavior and stops querying the WINS server completely.

To fix this make sure you have a secondary WINS server defined. If you only have one WINS server, list it in both the primary and secondary boxes.

Clients can be updated by starting the Network control panel applet, select the Protocols tab, select TCP/IP, select the WINS tab and fill in the boxes. If the clients use DHCP ensure the scope if configured with both primary and secondary.

Q. "Unable to Browse the Network" When You Click Network Neighborhood

Microsoft Windows 98
Microsoft Windows 98 Second Edition

This article was previously published under Q260214
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry

SYMPTOMS
After you upgrade to Windows 98 or Windows 98 Second Edition from a previous version of Windows, you may receive an "Unable to browse the network" error message when you click Network Neighborhood.
CAUSE
This behavior can occur if there is an AutoLogon key in the registry at the following location:
HKEY_Local_Machine\Software\Microsoft\Windows\CurrentVersion\Network\Real Mode Net

RESOLUTION
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this issue, delete the AutoLogon value from the registry location listed in the "Cause" section.

If you can view other computers using only a UNC connection, consider the following possible causes:

- A browse server may not be selected on the network. In a Windows 98 network, a computer that maintains a list of workgroup servers is selected. It can take anywhere from 5 to 15 minutes to establish a browse server. If no browse server exists, you cannot browse computers on the network. Wait a few minutes and then try again.
 

  1. Remove and reinstall the network adapter drivers. To do so, follow these steps:

     
    1. Click Start, point to Settings, and then click Control Panel.
    2. Double-click Network.
    3. In the list of installed network components, click your network adapter, click Remove, click Client For Microsoft Networks, and then click Remove.
    4. Click OK, and then click Yes when you are prompted to restart your computer.
    5. Repeat steps A-B.
    6. On the Configuration tab, click Add.
    7. Click Adapter, and then click Add.
    8. In the Manufactures box, click the network adapter's manufacturer, and then click the appropriate model in the Network Adapters box.
    9. Click OK, click OK again, and then click Yes when you are prompted to restart your computer.

      NOTE: If the network adapter is hardware configurable (uses jumpers or switches), the settings on the network adapter and in Device Manager must match. To determine the settings for the network adapter, refer to the documentation included with the adapter or contact the network adapter's manufacturer.

      If the network adapter is software configurable, you may need to specify a different IRQ, DMA channel, I/O address, or RAM address in Device Manager. For example, some hard disk controllers are configured to use an I/O address of 300h by default, which is also the default for some network adapters. To change the network adapter's resource settings in Device Manager, refer to step 3.
    10. Try to connect to the computer using its UNC name. For information about how to do so, refer to step 6.
    11. If you are unable to connect to the computer using its UNC name, double-click the Network Neighborhood icon on the desktop to see if the local computer is listed.
  2. If you are still unable to view the local computer in Network Neighborhood, there are several other possible causes:

    - The wrong network adapter driver is being used. If the adapter is emulating another adapter (such as the NE2000), it may be necessary to change jumpers or switches on the adapter for the driver to work properly. For more information about configuring the network adapter or obtaining updated drivers, contact the network adapter's manufacturer.

    - The network adapter is in a slot that is not functioning correctly. To verify this, put the network adapter in another slot in the computer or install the network adapter in another computer to determine if the adapter itself is defective.

    - The network adapter is malfunctioning. Try using a different network adapter or run a diagnostic test if one is included with the adapter.

    - The bus speed on the computer is too fast for the network adapter. Most network adapters are designed to work at Industry Standard Architecture (ISA) bus speed, which is 8.33 megahertz (MHz). Setting the bus speed any faster may result in unreliable performance.

    The bus speed setting is usually changed in the computer's CMOS. Try lowering the computer's bus speed if intermittent problems occur.

    - There is a bad or missing connection. Some network adapters, such as the Intel EtherExpress 16, include a utility that checks the integrity of wiring and connectors between two computers. If one of these utilities is available, use it to determine whether or not the two computers are physically connected.
     
  3. Run a diagnostic test on the network adapter to ensure it is functioning correctly. Some network adapter diagnostic programs can also test communication between computers (this tests the network adapter and cabling). If this test works, Windows 98/95 should also work, provided the correct drivers are being used. If this low-level test does not allow two network adapters to communicate, some type of hardware problem exists with a network adapter, the cabling, or the connectors. Contact your hardware vendor if either the network adapter diagnostic test or the network test fails.

    Windows 98/95 includes the NET DIAG utility, which can be used to perform a low-level communications test between two computers. To perform this test, follow these steps:

    NOTE: Both computers must have the same protocols installed in order for this test to work.
     
    1. On one computer, click Start, point to Programs, and then click MS- DOS Prompt.
    2. At the command prompt, type "net diag" (without quotation marks) and press ENTER.

      NET DIAG searches for a diagnostics server and should display the following prompt:

      No diagnostic servers were found on the network. Is Microsoft Network Diagnostics currently running on any other computers on the network?
    3. Press N (for No). This causes the computer from which you are running NET DIAG to be a diagnostic server until you press a key.
    4. On another computer, click Start, point to Programs, and then click MS-DOS Prompt.
    5. At the command prompt, type "net diag" (without quotation marks) and press ENTER.

      If a NetBIOS-capable protocol (such as NetBEUI or TCP/IP) and IPX/SPX are both installed, you receive the following prompt:

      IPX and NetBIOS have been detected. Press I to use IPX for diagnostics, N to use NetBIOS, or E to exit this program.
    6. Press I (for IPX) or N (for NetBIOS) to test the network connection using that particular protocol.

      If you are unable to communicate with the diagnostic server using the protocol you chose, try the other protocol.

      If you are able to communicate with the diagnostic server using one protocol but not the other, the network is working properly. For the protocol you are unable to communicate with, verify that it is installed correctly on both computers, and then run NET DIAG again.

      If you are unable to communicate with the diagnostic server using either protocol, run NET DIAG again, but this time reverse the role of each computer.

    If your network adapter is not on the supported network adapter list, you may want to contact the network adapter manufacturer for information about the correct emulation or for an updated network adapter driver. The manufacturer may also have information about jumpers and switches that may need to be reconfigured for a particular emulation mode (for example, NE2000 emulation).

    For more information about diagnosing problems with your network adapter or cabling, contact the hardware vendor.

SearchWin2000.com member: I have two mapped network drives on my PC using the Windows 2000 Professional operating system. The mapped drives are folders on a Windows 98 box. Each time I log on, it asks for the passwords to these drives. Why won't Win2k retain these passwords once they are entered correctly?

Jerry Honeycutt: You need to enable the Guest account in Windows 2000, which is not enabled by default. This is due to limitations in Windows 98, not Windows 2000. See KB article Q258938 for more information.

SearchWin2000.com member: I have a peer-to-peer network with Windows 98, Windows ME and Windows XP systems in a LAN. I can browse all the systems from Windows XP, but when I browse an XP system from Windows ME or Windows 98, the XP system asks for a password. The message displayed is: "You must supply a password to make this connection, resource system nameIpc$, password." I never set a password, so I have no idea why I'm being prompted for one.

Jerry Honeycutt: See article 139592 in Microsoft's Knowledge Base for the solution.