Ik heb ff gezocht op technet voor je. Ik vond dit.
Misschien dat je er wat aan hebt.
Troubleshooting Browsing
This section describes common problems that might occur with network browsing. As a general troubleshooting step, before performing the steps listed in this section, verify that you have a browsing problem rather than a problem with network connectivity.
To verify that you have a browsing problem
1. On the Start menu, point to Find, and then click Computer.
2. In the Named box, type the computer name for the network server you want to browse.
3. Click Find Now.
If you can find the computer, you have a browsing problem. If not, you have a problem with your network connection.
As another general troubleshooting step, verify that the master browse server is functioning correctly. At the command prompt, type
net view /workgroup:workgroup_name
If your workgroup name contains spaces, enclose the workgroup name in quotation marks.
This command retrieves a browse list from the master browse server. If you can retrieve a browse list, a backup browse server might not be functioning correctly or might not have an updated browse list. (It can take up to 15 minutes to retrieve an updated browse list.)
You can also test browse master functionality with the net use command. At the command prompt, type
net use \\server\share
If you can connect but not browse, you might have a problem with your master browse server.
For more information about troubleshooting browsing, see the Microsoft Windows NT Server Resource Kit (for Windows NT Server version 4.0).
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 98 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 make sure 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).
Samba server does not accept your password.
For security reasons, Windows 98 no longer allows you to send plain text passwords. It sends only encrypted passwords. However, Samba servers require plain text passwords, so you will not be able to connect to Samba servers unless you change a registry entry to enable plain text passwords.
Caution Enabling plain text passwords will decrease your computers security.
To enable plain-text passwords, add the registry entry EnablePlainTextPassword (as a DWORD) and set the value to 1 in the following registry location:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\Vnetsup
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.
A user cannot connect to any network resource.
·Verify that the user is connected to the network.
·Check the network cable termination.
·Verify that the correct network client is loaded.
·Verify that a common NetBIOS protocol is installed. NetBIOS-compliant protocols include NetBEUI, TCP/IP, and IPX/SPX.
·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.
·Use net view \\computer name to view shared resources.
Others cannot connect to my shared resources.
·In Control Panel, double-click Network, and verify that the file and printer sharing service appears in the list of installed components.
·Make sure other users are running a common protocol.
Network Neighborhood does not 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.
·Verify that you are connected to the correct workgroup. If you do not know what the correct workgroup is, contact your network administrator.
You cannot 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 98 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 98 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 servers Autoexec.ncf file when the network adapter drivers are loaded and IPX is bound to the logical adapter.
Erik heeft bij ons in het dorp best wel een slechte naam. Ik geloof Hans ofzo, of Rob.....
:strip_icc():strip_exif()/u/31644/george.jpg?f=community)
ik denk zelf tog egwel dat t in die client zit, maar op deze manier word het wel weer een echt doesn't-workstation.
:strip_icc():strip_exif()/u/318/29569.jpg?f=community)
:strip_icc():strip_exif()/u/23553/wile_e_coyote.jpg?f=community)
:strip_icc():strip_exif()/u/15123/steanid.jpg?f=community)