Network file copy error x86/x64

  • Thread starter Thread starter Campbell
  • Start date Start date
C

Campbell

Guest
We currently run a network of 30+ XP Pro PCs. We have a added a few XP x64
machines and, whilst they can get on the network ok (are visible, can browse
and be browsed by others), they give an error when trying to copy files from
other computers (both 32-bit and 64-bit). This is the error message:

"Cannot copy [filename]: The specified network name is no longer available."

However, they work fine if you push the file from another computer (x86 or
x64) to the x64 machine.

Anybody have any ideas? We move around a lot of data and it is really
starting to cause us some issues...

[FYI the network adapters are on-board NICs (Asus Striker Extreme mobos -
Nvidia nForce 680i)]
 
Re: Network file copy error x86/x64

First, and foremost - you really need a server based network. The
limitations on connectivity for XP machines means that you're going to
continue to run into problems. It sounds like your network is a good fit for
Small Business Server.

There are known issues with some settings on GigE network cards that might
be affecting you, but I would have expected problems on both 64 bit and 32
bit Windows. Though the latest service pack on Windows XP x64 _does_ enable
the settings that can cause problems.
To disable checksum offloading:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Click Edit, point to New, and then click DWORD Value.
Type DisableTaskOffload as the entry name, and then press ENTER.
Right-click DisableTaskOffload, and then click Modify.
In the Value data box, type a value of 1 , and then click OK.

Disable RSS (Receive side scaling)
http://support.microsoft.com/kb/912222/en-us

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
On the Edit menu, point to New, click DWORD Value, and then type EnableRSS .
Double-click EnableRSS, type 0 , and then click OK.


--
Charlie.
http://msmvps.com/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"Campbell" <Campbell@discussions.microsoft.com> wrote in message
news:67441E4D-2DB3-4D8F-A632-2E15C6578039@microsoft.com...
> We currently run a network of 30+ XP Pro PCs. We have a added a few XP
> x64
> machines and, whilst they can get on the network ok (are visible, can
> browse
> and be browsed by others), they give an error when trying to copy files
> from
> other computers (both 32-bit and 64-bit). This is the error message:
>
> "Cannot copy [filename]: The specified network name is no longer
> available."
>
> However, they work fine if you push the file from another computer (x86 or
> x64) to the x64 machine.
>
> Anybody have any ideas? We move around a lot of data and it is really
> starting to cause us some issues...
>
> [FYI the network adapters are on-board NICs (Asus Striker Extreme mobos -
> Nvidia nForce 680i)]
 
Re: Network file copy error x86/x64

Thanks for the suggestions. We are, in fact, already running Server 2003 for
limited file server purposes. We are a small media company that uses
high-end PCs for multimedia creation so our current (decentralised) setup
makes the most sense for the moment. As for the RSS, I had already tried
disabling that but to no avail. It is definitely a new problem to us (we
have not had it with the 32 bit machines). I am not 100% sure that XP x64 is
to blame either, as the 4 machines are all running the same hardware and it
could possibly be a hardware (or driver)-related issue. Unfortunately, I
don't currently have access to a different PC running x64 to be able to
provide a fair test. At this moment, however, it would seem to point towards
an OS issue. I will try the TaskOffload suggestion and report back!

"Charlie Russel - MVP" wrote:

> First, and foremost - you really need a server based network. The
> limitations on connectivity for XP machines means that you're going to
> continue to run into problems. It sounds like your network is a good fit for
> Small Business Server.
>
> There are known issues with some settings on GigE network cards that might
> be affecting you, but I would have expected problems on both 64 bit and 32
> bit Windows. Though the latest service pack on Windows XP x64 _does_ enable
> the settings that can cause problems.
> To disable checksum offloading:
>
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
> Click Edit, point to New, and then click DWORD Value.
> Type DisableTaskOffload as the entry name, and then press ENTER.
> Right-click DisableTaskOffload, and then click Modify.
> In the Value data box, type a value of 1 , and then click OK.
>
> Disable RSS (Receive side scaling)
> http://support.microsoft.com/kb/912222/en-us
>
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
> On the Edit menu, point to New, click DWORD Value, and then type EnableRSS .
> Double-click EnableRSS, type 0 , and then click OK.
>
>
> --
> Charlie.
> http://msmvps.com/xperts64
> http://mvp.support.microsoft.com/profile/charlie.russel
>
>
> "Campbell" <Campbell@discussions.microsoft.com> wrote in message
> news:67441E4D-2DB3-4D8F-A632-2E15C6578039@microsoft.com...
> > We currently run a network of 30+ XP Pro PCs. We have a added a few XP
> > x64
> > machines and, whilst they can get on the network ok (are visible, can
> > browse
> > and be browsed by others), they give an error when trying to copy files
> > from
> > other computers (both 32-bit and 64-bit). This is the error message:
> >
> > "Cannot copy [filename]: The specified network name is no longer
> > available."
> >
> > However, they work fine if you push the file from another computer (x86 or
> > x64) to the x64 machine.
> >
> > Anybody have any ideas? We move around a lot of data and it is really
> > starting to cause us some issues...
> >
> > [FYI the network adapters are on-board NICs (Asus Striker Extreme mobos -
> > Nvidia nForce 680i)]
>
 
Re: Network file copy error x86/x64

Right, I've tried the registry changes but they've had no discernible effect.
Here's the current situation:
- x64 PCs can access files shared on x86 PCs.
- x86 PCs cannot access files on x64 PCs - they receive the following error:
"Cannot copy [filename]: The specified network name is no longer available."
- x64 PCs cannot access files on other x64 PCs - they receive one of the two
following errors:
"Cannot copy [filename]: The specified network name is no longer available."
OR (occasionally and, seemingly, unpredictably)
"Cannot copy [filename]: Cannot read from the source file or disk."

Also, when I try to copy a file from any PC using x64, I get an Internet
Explorer window asking "Do you want to move or copy files from this zone?".
Is this a new security step that has been added in x64 or could this have
anything to do with it?

Regards
Campbell



"Campbell" wrote:

> Thanks for the suggestions. We are, in fact, already running Server 2003 for
> limited file server purposes. We are a small media company that uses
> high-end PCs for multimedia creation so our current (decentralised) setup
> makes the most sense for the moment. As for the RSS, I had already tried
> disabling that but to no avail. It is definitely a new problem to us (we
> have not had it with the 32 bit machines). I am not 100% sure that XP x64 is
> to blame either, as the 4 machines are all running the same hardware and it
> could possibly be a hardware (or driver)-related issue. Unfortunately, I
> don't currently have access to a different PC running x64 to be able to
> provide a fair test. At this moment, however, it would seem to point towards
> an OS issue. I will try the TaskOffload suggestion and report back!
>
> "Charlie Russel - MVP" wrote:
>
> > First, and foremost - you really need a server based network. The
> > limitations on connectivity for XP machines means that you're going to
> > continue to run into problems. It sounds like your network is a good fit for
> > Small Business Server.
> >
> > There are known issues with some settings on GigE network cards that might
> > be affecting you, but I would have expected problems on both 64 bit and 32
> > bit Windows. Though the latest service pack on Windows XP x64 _does_ enable
> > the settings that can cause problems.
> > To disable checksum offloading:
> >
> > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
> > Click Edit, point to New, and then click DWORD Value.
> > Type DisableTaskOffload as the entry name, and then press ENTER.
> > Right-click DisableTaskOffload, and then click Modify.
> > In the Value data box, type a value of 1 , and then click OK.
> >
> > Disable RSS (Receive side scaling)
> > http://support.microsoft.com/kb/912222/en-us
> >
> > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
> > On the Edit menu, point to New, click DWORD Value, and then type EnableRSS .
> > Double-click EnableRSS, type 0 , and then click OK.
> >
> >
> > --
> > Charlie.
> > http://msmvps.com/xperts64
> > http://mvp.support.microsoft.com/profile/charlie.russel
 
Re: Network file copy error x86/x64

I'd look into the drivers for those NICs as a start. Since it only happens
on the 64 bit machines, and it happens between 64 bit machines and they're
the only ones with that hardware...

I routinely copy very large files between machines. To and From 64 bit
machines, and to and from 32-bit machines on my network. I did this for 2
years on XP x64, Windows Server 2003 x64, and various 32-bit machines. I no
longer run XP x64 in my daily work - those two machines have moved to Vista
64. But I never experienced this. Nor do others here. So I seriously doubt
it's the OS.

--
Charlie.
http://msmvps.com/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel


"Campbell" <Campbell@discussions.microsoft.com> wrote in message
news:963B0C99-6580-413C-B776-18D07C1F0B8B@microsoft.com...
> Right, I've tried the registry changes but they've had no discernible
> effect.
> Here's the current situation:
> - x64 PCs can access files shared on x86 PCs.
> - x86 PCs cannot access files on x64 PCs - they receive the following
> error:
> "Cannot copy [filename]: The specified network name is no longer
> available."
> - x64 PCs cannot access files on other x64 PCs - they receive one of the
> two
> following errors:
> "Cannot copy [filename]: The specified network name is no longer
> available."
> OR (occasionally and, seemingly, unpredictably)
> "Cannot copy [filename]: Cannot read from the source file or disk."
>
> Also, when I try to copy a file from any PC using x64, I get an Internet
> Explorer window asking "Do you want to move or copy files from this
> zone?".
> Is this a new security step that has been added in x64 or could this have
> anything to do with it?
>
> Regards
> Campbell
>
>
>
> "Campbell" wrote:
>
>> Thanks for the suggestions. We are, in fact, already running Server 2003
>> for
>> limited file server purposes. We are a small media company that uses
>> high-end PCs for multimedia creation so our current (decentralised) setup
>> makes the most sense for the moment. As for the RSS, I had already tried
>> disabling that but to no avail. It is definitely a new problem to us (we
>> have not had it with the 32 bit machines). I am not 100% sure that XP
>> x64 is
>> to blame either, as the 4 machines are all running the same hardware and
>> it
>> could possibly be a hardware (or driver)-related issue. Unfortunately, I
>> don't currently have access to a different PC running x64 to be able to
>> provide a fair test. At this moment, however, it would seem to point
>> towards
>> an OS issue. I will try the TaskOffload suggestion and report back!
>>
>> "Charlie Russel - MVP" wrote:
>>
>> > First, and foremost - you really need a server based network. The
>> > limitations on connectivity for XP machines means that you're going to
>> > continue to run into problems. It sounds like your network is a good
>> > fit for
>> > Small Business Server.
>> >
>> > There are known issues with some settings on GigE network cards that
>> > might
>> > be affecting you, but I would have expected problems on both 64 bit and
>> > 32
>> > bit Windows. Though the latest service pack on Windows XP x64 _does_
>> > enable
>> > the settings that can cause problems.
>> > To disable checksum offloading:
>> >
>> > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
>> > Click Edit, point to New, and then click DWORD Value.
>> > Type DisableTaskOffload as the entry name, and then press ENTER.
>> > Right-click DisableTaskOffload, and then click Modify.
>> > In the Value data box, type a value of 1 , and then click OK.
>> >
>> > Disable RSS (Receive side scaling)
>> > http://support.microsoft.com/kb/912222/en-us
>> >
>> > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
>> > On the Edit menu, point to New, click DWORD Value, and then type
>> > EnableRSS .
>> > Double-click EnableRSS, type 0 , and then click OK.
>> >
>> >
>> > --
>> > Charlie.
>> > http://msmvps.com/xperts64
>> > http://mvp.support.microsoft.com/profile/charlie.russel
>
 
Back
Top