Now, we would like to image form pc1 to pc2 but DI7 says"access in
denied. unable to save location information "or if we try to restore
form one pc to another pc into network.
I had two problems with a similar set up but managed to get it working. See
if these two apply to you...
Problem 1
========
Drive Image kept saying it didn't have permission to access the shared
folder... Here is my solution....
If you are sure you have set up your accounts and shares correctly but you
still can't access a machine over your LAN and you get either access
permission errors or "Not enough server storage" (or perhaps other
messages?) then his might be worth checking.
Look in the event log on the "server". This might be an ordinary PC in the
case of a home LAN, either way it's the PC hosting the share you are trying
to contact. See if there is an entry telling you the irpstacksize is too
small.
I believe this problems may be due to Norton Antivirus S/W...
Norton have this advisory (long URL may wrap to new line and need repair)
http://service1.symantec.com/suppor...88256d03005eb145?OpenDocument&src=bar_sch_nam
and Microsoft have this one..
http://support.microsoft.com/default.aspx?scid=kb;EN-US;106167
HOWEVER the above only mention the error message being "Not enough server
storage...". I found it can also give access permission errors (something
like "Access denied" or "Insufficient acesss", I can't remember exactly).
These are really confusing to someone trying to set up a home LAN.
Here is what I found...
irpstacksize = 11 (dec) causes access permission errors.
irpstacksize = 13/14 the error changed to "Not enough server storage" or
similar.
irpstacksize = 15 and my network shares now work fine.
Problem 2
========
Once I had fixed the above I found my backup would abort half way through
with a "Delayed Write Failure". This is tricky to explain. The problem seems
to occur because shared folders can cause excess network traffic. I read
somewhere that every time the content of a shared folder is changed messages
are sent to all computers/accounts that have access to the share (eg every
time Drive Image appends a byte or two of data to the backup multiple
messages are sent out and this slows down the LAN to the point that a "write
buffer" gets overwritten).
The fix for me was to restructure the folders I was using to hold backups
and "push the share down a level"....
Before...
I shared a folder called "Backups" on PC1 and arranged for PC1 to write to
subfolder "Backups\PC1" and PC2 to write to Backups\PC2 etc.
After...
I removed the share from "Backups" and shared Backups\PC2 only. (Backups\PC1
does not need to be shared).
This seems to have cured the problem.
