Troubleshooting for Logon, Browsing, and Peer Resource Sharing

This section provides some general methods for troubleshooting.

Setup doesn't run the login script.

If the network logon server or domain controller is not validating the user account, the login script will not run. Check the following:

• The network connection
• The user name
• The user password
• The basic network functionality
• The domain or server logon validation

If the network logon server or domain controller is validating the user account, do the following:

• Check the network connection.
• Verify that the login script is present in the home directory (on a Windows NT network) or in the user's mail directory (on a NetWare network).
• Check for enough memory on the client computer.
• Check for and remove unnecessary drivers and TSRs, and then try to log on again.

You cannot browse to find SMB-based servers in the workgroup while using Client for Microsoft Networks.

There might be no SMB-based servers in the workgroup (computers running Windows NT, LAN Manager, or File and Printer Sharing for Microsoft Networks). Windows 95 does not support browsing in a workgroup that does not contain an SMB-based server if the computer is running Client for Microsoft Networks. The following presents a solution.

To ensure there is an SMB-based server in the workgroup

• On a computer running File and Printer Sharing for Microsoft Networks, make sure the service is configured as the master browser server.

  – Or –

• Make sure that a Windows NT server computer is a member of the workgroup (or domain).

Access to an NCP-based server changes if SAP Advertising is defined.

Where you access an NCP-based peer resource server in Network Neighborhood can change, depending on whether the server is configured for Workgroup Advertising or SAP Advertising.

• If the computer running File and Printer Sharing for NetWare Networks is configured for Workgroup Advertising, that peer server appears as a computer in its workgroup.
• If the File and Printer Sharing server is configured for SAP Advertising, it appears with the other Novell NetWare servers at the beginning of the list of workgroups in the Entire Network window of Network Neighborhood.

To set SAP Advertising or Workgroup Advertising, follow the procedures in "Configuring Browsing for Resource Sharing on NetWare Networks" earlier in this chapter.

User cannot connect to any network resource.

• Check the workgroup assignment.
• Check the domain or preferred server assignment for the protected-mode network client.
• Check the rights for the user as defined on the domain or preferred server.
• Check the basic network operations.
• Use net view \\computer name to view shared resources.
• Check for the termination of the local network cable.

Others cannot connect to my shared resources.

• In the Network option in Control Panel, verify that the File and Print Sharing service appears in the list of installed components.
• Make sure other users are running a common protocol.

Network Neighborhood doesn't show servers.

• Verify that at least one active server is on the local network.
• Verify that the proper network clients are installed and, if necessary, reinstall them.
• Verify that the user is logged on to the particular network.
• Check the network protocol settings.
• Check that the IPX Frame Type is set to Auto or to the same type as the server.
• Check the network cable termination.

You can't connect to a specific server.

• Check error message details, if available.
• Verify that you can connect to any server.
• Verify that you can connect to a specific server from other computers. If you cannot connect to the specific server from other systems, it probably indicates a problem with that server or the cabling or routing to it. Also verify termination of the local network cable.

The network redirector or server is not responding.

If the computer running Windows 95 is not responding properly as a client or server, use System Monitor to view statistics about the activity of the installed network servers and redirectors. If there is no activity, remove the client or server on the Network option in Control Panel, and then reinstall and try again.

You cannot see computers running Windows 95 on the other side of a router on a NetWare network.

This might be related to the IPX network number. An IPX client (such as a computer running Client for NetWare Networks) determines its network number by sending Routing Information Protocol (RIP) requests to the nearest IPX router. If the router is configured incorrectly, all IPX clients on that network can be adversely affected. Network numbers are assigned in the server's AUTOEXEC.NCF file when the network adapter drivers are loaded and IPX is bound to the logical adapter.

Access is denied for Windows for Workgroups users trying to connect to shared resources on a computer running File and Printer Sharing for Microsoft Networks.

If the user with the Windows for Workgroups client computer is logging on to a different domain from the computer running File and Printer Sharing services (the peer server), then Windows 95 cannot confirm logon validation for access to shared resources. To solve this problem, do one of the following:

• Upgrade the Windows for Workgroups clients to Windows 95 (recommended).
• Set the LM Announce option to Yes in the Advanced properties for File and Printer Sharing for Microsoft Networks on the peer server.
• Switch to share-level security on the peer server.
• Change the logon domain for the Windows for Workgroups clients.

This problem will not occur in these cases: if the client computers are running Windows 95 or Windows NT; if the peer server uses share-level security; or if the same domains are used for the client computer's logon domain and the domain specified for pass-through validation in the peer server's Access Control properties.

A user is incorrectly denied access to resources on a peer server on a Windows NT network.

If a user is denied access to resources on a computer running File and Printer Sharing for Microsoft Networks with user-level security, you should first determine which security provider is specified for the peer server. Then, see if the client can be validated by that security provider directly without going through the peer server.

If this is successful, verify that the user is on the access control list for the shared resource on the peer server. Remove that user from the list of users and then add the name back. If this is unsuccessful, reconfigure the peer server to use another security provider that you know can validate the user.