Video Screencast Help

system error 53 when doing net view or net use

Created: 20 May 2013 | 12 comments

Hi,

I used Ghost Boot Wizard to create a standard Ghost Boot Disk. It boots just fine. However, when I use net use or net view I get system error 53. I am reasonably sure my net use syntax is correct. I am even more sure of that when the net view also returns a system error 53. In the past Super Boot CD's have been used and had no issues mapping drives. I will gladly post some examples, but this error is frustrating......

Operating Systems:

Comments 12 CommentsJump to latest comment

EdT's picture

Version of Ghost?

DOS boot or WinPE boot?

My guess based on the very limited information supplied is that you do not have a functional network driver installed, or do not have the required fileset to support the NET commands.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Briandr88's picture

Symantec Ghost 11.5.1 trial version. Just found out the organization has a license for the full version. Will be removing the trial and installing the full version.

Anyways I first tried with PC-DOS, then with WinPE. I am thinking you might be right, but I thought with the Ghost Boot Wizard I should not have to install a specific driver? I need this to work on three HP laptops and one desktop. Perhaps more down the road.

EdT's picture

First of all, make sure that you have run LiveUpdate to get your version of ghost up to 11.5.1.2266 (unless it is there already).

Secondly, I would recommend using WinPE as DOS has severe limitations when it comes to running on modern hardware, eg no SATA support, requiring the use of "compatibility mode" settings in the bios, if available.

The following two links should help:

http://www.symantec.com/business/support/index?page=content&id=TECH110134

https://www-secure.symantec.com/connect/articles/do-i-have-correct-driver-winpe

When it comes to drivers, new chipsets are arriving all the time, so it is nigh on impossible for any product to provide automatic support for these chipsets, and Ghost has not had any upgrades for some years.

The version of WinPE shipping in the Ghost product is based on the Vista 32 bit kernel, so you need to add Vista 32 bit drivers to WinPE for each chipset you need to support across your hardware range. The second link provides a simple way of mounting candidate drivers from the WinPE command line to check if they work OK.  You need to consider both NIC and SATA drivers as imaging over the network needs both the NIC chipset and the hard drive chipsets to be working correctly.

When using the Ghost Boot Wizard, you need to first add the driver, then ensure it is selected before you  rebuild the boot image. If you want a general "play" with WinPE to familiarise yourself with its operation outside of the Ghost environment, check out this article:

https://www-secure.symantec.com/connect/articles/readyadventures-winpe

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Briandr88's picture

Hi,

Thanks. I will do some homework here and get back in contact with you. Most computers here are W7 SP1 x64. In the past I have used TCP/IP Universal Boot Disk, but I think that website is no longer being updated. It just stinks that if your supporting 15 computers you have to add all the drivers, assuming they need different ones.

Briandr88's picture

Erased contents. Answered my own question. Still may need further assistance. Not sure.

Briandr88's picture

Hi,

Well the Vista x32 network driver I added in worked which is good. Not sure if it will work on the other devices we support, but no big deal. I can circle back and deal with that at a later time. Right now I am getting system error 5 and 50 when doing a net view on different devices. I didn't add the mass storage device driver. I am guessing I will need to? How can I confirm if I won't? I am not sure if the one of the ones in the list is working. As far as the system error 5 and 50, ideas so I can map the shares hosting my images?

EdT's picture

It is easy to check if you need to load a mass storage driver for a particular machine. If you can "see" the hard disk from the WinPE command prompt then you do not need additional drivers. However, WinPE V2 was released at the same time as the first generation of SATA controllers, so it may only work with older machines. 

Regarding System errors 5 and 50, I would recommend Googling on those as there are many possible causes and solutions.  Basically, it is usually due to an "access denied" scenario, and it may well depend on what you are trying to connect to.  Windows 2008, for example, has quite stringent security implemented and you may not be able to log on from a basic client.  You may find it helpful to enable NETBIOS protocol if it is not enabled currently.  Also check whether you need to open any firewall settings.

Are you able to ping from the WinPE command line? Do you have a valid IP address?

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Briandr88's picture

Hi,

Yes, I do have an IP address and I can ping servers on the organization's network. I am trying to authenticate using my AD credentials. I can now map to a share on a server, but when attempting to map to a Buffalo NAS drive that was shared out, no luck. I keep getting System Error 50. Google which I don't put alot of faith in these days is full of links with people having issues mapping to a NAS drive. So what gives?  I can map this drive within Windows 7.

EdT's picture

A lot of NAS boxes run some flavour of Linux as their operating system and their network protocols may require a degree of authentication that the basic WinPE client does not offer as a default. The best approach from my point of view is to go onto the Buffalo NAS support forums and ask about this issue there.

System Error 50 (This request is not supported) does tend to indicate that a request to the server device is not being recognised. Have you checked if NETBIOS is available on the Buffalo device?

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Briandr88's picture

Hi,

I already asked the question in the Buffalo NAS support forums and have not heard back anything. I did find the following options checked:

- Delegate Authority to External SMB Server
- Use Windows Domain Controller as Authentication Server
- There is an option checked to use a WINS and DNS server

I did not see an option there an option to enable NetBIOS. I think I may have mentioned earlier the Super Boot CD has no issues with mapping to the NAS. Is there any way possible to get a expanded Windows PE interface that would allow me to attempt to map to the NAS using the GUI?

EdT's picture

Windows PE is a cut down version of the full windows release, and is intended for deployments of the operating system. The expanded version of WinPE is therefore the full release of the corresponding version of the windows operating system.

Are you able to connect to a server share on your network?  If so, then it would be fair to assume that the problem lies with the configuration of the Buffalo NAS, but unfortunately that is not a product I have ever used so am not able to advise you further.  If you have a weblink to the documentation of your model then I'm hopeful someone in these forums may be able to review the settings and give you some pointers.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

Briandr88's picture

Yes, I can connect to a server share on the organization's network. Only on the NAS at work do I have issues connecting to shared drives. As luck would have it I actually have the same Buffalo Link Station NAS at home as the organization has. I will be testing during the weekend to see if I can connect with my home laptop and eval copy of the Symantec Ghost tools.