On 03/06/13 15:16, Ed Greshko wrote:
> The only difference I can surmise is that my command refers to a
2 TB share on a 64 bit Windows 7 machine.
> >
> > If I change the address from the .17 to a nonexistent .127 the invalid argument
error goes away.
> > (the command times out).
> >
Why don't you try setting up a smaller share to see if that influences anything?
You may also want to use wireshark and see if there is an indication during the protocol
exchange that would give a hint as to the problem.
--
From now on, at least during winter time, Im going to blame all
spelling an grammar erros on the cat sitting on my chest every time I sit down at the
computer....