Hello Group,
Using Win2K Server / SP4
We have recently started getting the following error message while trying to
copy files from office server to remote server in data center.
"cannot copy file: The specified network name is no longer avilable - path
is too deep"
This is a daily function that until about a month ago was done on a daily
basis without error or issue.
Just to throw a twist into the mix ........ we have 1 PC in the office that
is still able to perform the task without error using the same OS and
applying same MS Patches as the failing PC's.

I Have tried a couple of things already without success.
1) Changing affected PC's NIC settings from "auto" to hard coded "duplex /
half duplex" or "10 mbps / 100 mbps".
2) Changed the NIC card to match the one in the PC that is still allowing
file transfers with no success.
3) Increased Memory in failing PC with no success.
4) Tried replacing Cat5 data cable with no success.
5) Tried switching port on switch for failing PC to port that does allow PC
to file transfer with no success.

Thanks in advance for your time and suggestions

RHill

What OS is on the computer you are having problems?

How long is the path?

DDS
"RHill" <RHill@discussions.microsoft.com> wrote in message
news:B5C7DC23-1FCD-468D-BFB3-84C59BEC2D81@microsoft.com...
> Hello Group,
> Using Win2K Server / SP4
> We have recently started getting the following error message while trying
> to
> copy files from office server to remote server in data center.
> "cannot copy file: The specified network name is no longer avilable - path
> is too deep"
> This is a daily function that until about a month ago was done on a daily
> basis without error or issue.
> Just to throw a twist into the mix ........ we have 1 PC in the office
> that
> is still able to perform the task without error using the same OS and
> applying same MS Patches as the failing PC's.
>
> I Have tried a couple of things already without success.
> 1) Changing affected PC's NIC settings from "auto" to hard coded "duplex /
> half duplex" or "10 mbps / 100 mbps".
> 2) Changed the NIC card to match the one in the PC that is still allowing
> file transfers with no success.
> 3) Increased Memory in failing PC with no success.
> 4) Tried replacing Cat5 data cable with no success.
> 5) Tried switching port on switch for failing PC to port that does allow
> PC
> to file transfer with no success.
>
> Thanks in advance for your time and suggestions
>
> RHill

See your second post on the same subject.

Danny,
We use Win2k Pro for Workstations.
The # of characters in my path is less than 100
"Path is too Deep" is a bogus / generic MS message ..... IMO.
And again, this process still works on 1 PC in our office.
This all worked up until about a month ago.
I think it's an MS Security Patch issue that will hopefully be repaired in a
follow up release that MS is unaware of.
I have seen other issues develop and clear up when applying MS Patches.
I was hoping to find others out here that were experiencing similar problems.

Thanks for your input,

RHill

"Danny Sanders" wrote:

> What OS is on the computer you are having problems?
>
> How long is the path?
>
> DDS
> "RHill" <RHill@discussions.microsoft.com> wrote in message
> news:B5C7DC23-1FCD-468D-BFB3-84C59BEC2D81@microsoft.com...
> > Hello Group,
> > Using Win2K Server / SP4
> > We have recently started getting the following error message while trying
> > to
> > copy files from office server to remote server in data center.
> > "cannot copy file: The specified network name is no longer avilable - path
> > is too deep"
> > This is a daily function that until about a month ago was done on a daily
> > basis without error or issue.
> > Just to throw a twist into the mix ........ we have 1 PC in the office
> > that
> > is still able to perform the task without error using the same OS and
> > applying same MS Patches as the failing PC's.
> >
> > I Have tried a couple of things already without success.
> > 1) Changing affected PC's NIC settings from "auto" to hard coded "duplex /
> > half duplex" or "10 mbps / 100 mbps".
> > 2) Changed the NIC card to match the one in the PC that is still allowing
> > file transfers with no success.
> > 3) Increased Memory in failing PC with no success.
> > 4) Tried replacing Cat5 data cable with no success.
> > 5) Tried switching port on switch for failing PC to port that does allow
> > PC
> > to file transfer with no success.
> >
> > Thanks in advance for your time and suggestions
> >
> > RHill
>
>
>

RHill wrote:
> *Hello Group,
> Using Win2K Server / SP4
> We have recently started getting the following error message while
> trying to
> copy files from office server to remote server in data center.
> "cannot copy file: The specified network name is no longer avilable -
> path
> is too deep"
> This is a daily function that until about a month ago was done on a
> daily
> basis without error or issue.
> Just to throw a twist into the mix ........ we have 1 PC in the
> office that
> is still able to perform the task without error using the same OS
> and
> applying same MS Patches as the failing PC's.
>
> I Have tried a couple of things already without success.
> 1) Changing affected PC's NIC settings from "auto" to hard coded
> "duplex /
> half duplex" or "10 mbps / 100 mbps".
> 2) Changed the NIC card to match the one in the PC that is still
> allowing
> file transfers with no success.
> 3) Increased Memory in failing PC with no success.
> 4) Tried replacing Cat5 data cable with no success.
> 5) Tried switching port on switch for failing PC to port that does
> allow PC
> to file transfer with no success.
>
> Thanks in advance for your time and suggestions
>
> RHill *



--
james01
------------------------------------------------------------------------
Posted via http://www.webservertalk.com
------------------------------------------------------------------------
View this thread: http://www.webservertalk.com/message1695152.html

hai,
i think u may not enable disk opetions in MSTSC option tab, please
check is it enable or not

RHill wrote:
> Hello Group,
> Using Win2K Server / SP4
> We have recently started getting the following error message while trying to
> copy files from office server to remote server in data center.
> "cannot copy file: The specified network name is no longer avilable - path
> is too deep"
> This is a daily function that until about a month ago was done on a daily
> basis without error or issue.
> Just to throw a twist into the mix ........ we have 1 PC in the office that
> is still able to perform the task without error using the same OS and
> applying same MS Patches as the failing PC's.
>
> I Have tried a couple of things already without success.
> 1) Changing affected PC's NIC settings from "auto" to hard coded "duplex /
> half duplex" or "10 mbps / 100 mbps".
> 2) Changed the NIC card to match the one in the PC that is still allowing
> file transfers with no success.
> 3) Increased Memory in failing PC with no success.
> 4) Tried replacing Cat5 data cable with no success.
> 5) Tried switching port on switch for failing PC to port that does allow PC
> to file transfer with no success.
>
> Thanks in advance for your time and suggestions
>
> RHill