Net View System Error 52
network resources The net view command is ever useful network troubleshooting utility. You can system error 53 use it to displays a list of domains, computers, or shared resources available system error 53 has occurred on a specific computer. To list all shared resources on a domain or workgroup, at the command prompt, type net disablestrictnamechecking view. To display the shared resources on a computer, do net view \\ComputerName where ComputerName is the name of a specific computer whose resources you want to view. When using net view, you may see different messages. The following are some of them and resolutions. Symptom: net view ip successful but not net view \\computername. Resolutions: 1) name resolution. 2) cache credential - net use \\computername /user:username. 3) make sure the remote computer is in the same workgroup or domain. Symptom: If you can net use \\ip but not net use \\computername. Resolutions: you may just need to cache the credential pointing to the computername by using net net use \\computername /user:username command. Symptom: There are no entries in the list. Resolution: this is because no shared drive or folder. Go to a folder you want to share, right-click>sharing and select sharing. System error 5: access is denied. Resolutions:1) check permission or 2) need to cache credential: logon the same username and password on both computers or use net net use \\computername /user:username command. System error 51 has occurred. Windows cannot find the network path. Verify that the network path is correct and the destination computer is not busy or turned off. If windows still cannot find the network path, contact your network administrator. Resolution: enable file and printer sharing. Can't net view computername - error 52 Symptoms: you can ping a host but not net view it. When using net view \\hostname, you get system error 52 - a duplicate name exists on the network. Resolutions: there are two host names or alias name (cname) are pointed to the same IP. 1) check the WINS records. 2) check DNS records. Can't ping or net view computername - error 53 S
message when using the NET USE command to connect to a network share on a server that I have assigned a DNS Alias to. I am using the DNS Alias name in the NET USE statement. I can ping the Alias and it resolves and responds correctly. The reason I am wanting to use an Alias is that in the future the share may be moved to another server and the server name is embeded in a WINPE boot disk's script that we use for deployment, else I would have looked at DFS. Both machines are W2K3 Server sp1 and use Microsoft DNS and WINS in the domain. The server http://www.chicagotech.net/netviewerrors.htm I am trying to connect to has both an A (Host) and CNAME (Alias) record entry in DNS, ie: SERVER1 A(Host) 192.168.1.10 SERVER1-ALIASNAME CNAME (Alias) 192.168.1.10 The full error message I am getting when performing a basic NET USE command is: "Error 52 - a duplicate name exists on the network" Does anyone know how to resolve this issue, is it possible or is it a limitation of using the NET USE command with Alias DNS records? Thanks in advance, http://www.winvistatips.com/threads/net-use-error-52-when-using-dns-alias.733750/ Simon Kiwi Si, Feb 16, 2007 #1 Advertisements Kevin D. Goodknecht Sr. [MVP] Guest Kiwi Si wrote: > Hi all, > > I am getting the following error message when using the NET USE > command to connect to a network share on a server that I have > assigned a DNS Alias to. I am using the DNS Alias name in the NET USE > statement. I can ping the Alias and it resolves and responds > correctly. > > The reason I am wanting to use an Alias is that in the future the > share may be moved to another server and the server name is embeded > in a WINPE boot disk's script that we use for deployment, else I > would have looked at DFS. > > Both machines are W2K3 Server sp1 and use Microsoft DNS and WINS in > the domain. > > The server I am trying to connect to has both an A (Host) and CNAME > (Alias) record entry in DNS, ie: > > SERVER1 A(Host) 192.168.1.10 > SERVER1-ALIASNAME CNAME (Alias) 192.168.1.10 > > The full error message I am getting when performing a basic NET USE > command is: > > "Error 52 - a duplicate name exists on the network" > > Does anyone know how to resolve this issue, is it possible or is it a > limitation of using the NET
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn http://serverfault.com/questions/308585/unable-to-connect-to-second-name-of-windows-2008-server-r2-machine-from-xp more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and system error rise to the top Unable to connect to second name of Windows 2008 Server R2 machine from XP up vote 4 down vote favorite I used the command netdom computername /add:newname.domainname.com to add a second name to a server running Windows 2008 Server R2. After restarting the server, I had DNS "A" entries for both names. In addition, the second name was added to HKLM\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters\OptionalNames, which I believe should system error 53 have taken care of any NetBIOS resolution. From my Windows 7 workstation, I can ping both names and running net view on both names reveals the same list of resources. From Windows XP, I can ping both names, but net view only works on the first name. Running net view on the second name returns: System error 52 has occurred. You were not connected because a duplicate name exists on the network. Go to System in Control Panel to change the computer name and try again. What do I need to do to make the second name usable from XP clients? Update: I was able to resolve the problem by adding the REG_DWORD key DisableStrictNameChecking = 1 to HKLM\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters, then restarting the Server service. However, I do not understand why this was necessary. domain-name-system windows-xp windows-server-2008-r2 server-message-block netbios share|improve this question edited Sep 6 '11 at 15:40 asked Sep 6 '11 at 14:58 Tumba 2316 The Update of the question contains the answer that worked for us: DisableStrictNameChecking = 1. Tumba should make an actual answer that can get upvoted, and perhaps add some SMB 1 vs. 2 information. We had this problem when we tried a CNAME (alias) records, or the alt