samba - Sep 2004 - cannot copy from win2k client to samba share

good afternoon all,

i am running samba 3.0.7-2.FC1 on fedora core 1.

i have a strange problem.  when the win2k clients at one of my sites try to
copy a file to a samba share on a different subnet, i get the following
message:

Cannot copy filename:  the specified network name is no longer available.

i can copy the files to shares on a samba share on the same subnet, and i
can copy the files from thte samba share on the different subnet to the
win2k clients, but i cannot copy files from the clients to the samba share
on the different subnet.

no firewalls, and the permissions do not appear to be a factor.

any ideas?

stuart

----- Original Message ----- 
From: "Stuart Highlander" <fsb@ntwsdb.com>
To: <samba@lists.samba.org>
Sent: Thursday, September 16, 2004 3:08 PM
Subject: [Samba] cannot copy from win2k client to samba share

> good afternoon all,
>
> i am running samba 3.0.7-2.FC1 on fedora core 1.
>
> i have a strange problem.  when the win2k clients at one of my sites try
to
> copy a file to a samba share on a different subnet, i get the following
> message:
>
> Cannot copy filename:  the specified network name is no longer available.
>
> i can copy the files to shares on a samba share on the same subnet, and i
> can copy the files from thte samba share on the different subnet to the
> win2k clients, but i cannot copy files from the clients to the samba share
> on the different subnet.
>
> no firewalls, and the permissions do not appear to be a factor.
>
> any ideas?
>
> stuart
>
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba
good morning all,

this turned out to be a network problem and not a samba problem.

the input side of one of my routers happened to be throwing CRC and frame
errors when trying to copy the files in question from the one site to the
share on another site across the t1.

after wrestling with the provider for a week, they appear to have found and
corrected the problem.

stuart