![]() Run the command /etc/init.d/samba stop, wait a second or two, and then run /etc/init.d/samba start. Login to the machine and use the su command to become root. Alternatively, you can reboot the PC which will cause a re-registration to take place. You may have to wait up to 2 minutes to retry registrations. Make sure that the command does not return any errors. Login to the machine (locally or remotely using the SMS help desk if it is an SMS client) and run the command nbtstat -RR from a command prompt. If the records are still missing, the machine will need to re-register itself with WINS. If any of the records are missing or are marked as Tombstoned, repeat steps 3 through 6 for FISSION. Under the Type field there should be 1 entry of type Workstation and 1 of type File Server. If the machine is properly registered, it should have at least 2 entries present. When the search completes, you will see a list of machines that begin with the name you entered in the Find by Name dialog. In the Find by Name dialog, enter the name of the computer that is not being found and click the Find Now button. Right-click Active Registrations and choose Find by Name. Start the WINS manager by clicking the WINS icon in the Administrative Tools folder.ĭouble-click the BLUEMOON server icon or click the + to expand the folder. Once you have the snap-in installed, perform the following steps: To verify that the machine has the necessary records registered, you will need to use the WINS snap-in for MMC.įor information on installing and configuring the WINS snap-in, see the links referenced at the bottom of this article. In order to fix this problem you should verify that the machine being connected to is in the WINS database. Windows 2000 clients connecting to other Windows 2000 clients use DNS for name resolution by default. ![]() This only affects connections to downlevel clients such as Windows NT 4.0, Windows 9x, and Samba servers. It typically occurs when a machine has not registered properly with the WINS servers. This problem occurs when no DNS to NetBIOS name resolution was performed. When a user attempts to connect to a network share via the Map Network Drive option or the DOS net use command, the system returns with an error code of 53 (The network path was not found). Map Network Drive or NET USE results in System Error 53 (The network path was not found)įor instructions on how to map a network drive, please see Mapping ECN Drive using Windows XP.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |