Network file copy timeout

List,
I have this problem on our network where a largish file keeps timing out on
copy with the device no longer available error.

All these things were working before but since a reformat of the laptop and
reinstall of XP pro+sp2 it decided to give us the shits.
The network is switched and the file is on a w2.3k server (standard)

I have seen this before on an unswitched network and I am led to believe it
has to do with the SMB timeout (lots of googling) the error does not occur
on other machines so it's clearly workstation related does anyone know how
to resolve this?

Yes we have used downgraded+upgraded+supplied drives for the nic (broadcom
550x)

If anyone could help I'd appreciate it.

thanks
evan

Try to fix the NIC speed to either 10 Mbps or 100 Mbps, and not use
Auto-negotiate. Do the same on the switch.

Alternatively, introduce a working NIC from elsewhere, disable the existing
NIC and repeat the copy process.

"evan b" wrote:

> List,
> I have this problem on our network where a largish file keeps timing out on
> copy with the device no longer available error.
>
> All these things were working before but since a reformat of the laptop and
> reinstall of XP pro+sp2 it decided to give us the shits.
> The network is switched and the file is on a w2.3k server (standard)
>
> I have seen this before on an unswitched network and I am led to believe it
> has to do with the SMB timeout (lots of googling) the error does not occur
> on other machines so it's clearly workstation related does anyone know how
> to resolve this?
>
> Yes we have used downgraded+upgraded+supplied drives for the nic (broadcom
> 550x)
>
> If anyone could help I'd appreciate it.
>
> thanks
> evan
>
>
>

Desmond thanks for the reply
But it's a laptop with inbuilt nic
and all switches are on AUTO and all cards are on AUTO
and this is the only one in about 80 machines it fails with.
I will try a PCMCIA card incase the nic is stuffed but I dont think it is.

Anyone else?

"Desmond Lee" <(E-Mail Removed)> wrote in message
news:2E3D781C-C9DA-4F2A-8E37-(E-Mail Removed)...
> Try to fix the NIC speed to either 10 Mbps or 100 Mbps, and not use
> Auto-negotiate. Do the same on the switch.
>
> Alternatively, introduce a working NIC from elsewhere, disable the
existing
> NIC and repeat the copy process.
>
> "evan b" wrote:
>
> > List,
> > I have this problem on our network where a largish file keeps timing out
on
> > copy with the device no longer available error.
> >
> > All these things were working before but since a reformat of the laptop
and
> > reinstall of XP pro+sp2 it decided to give us the shits.
> > The network is switched and the file is on a w2.3k server (standard)
> >
> > I have seen this before on an unswitched network and I am led to believe
it
> > has to do with the SMB timeout (lots of googling) the error does not
occur
> > on other machines so it's clearly workstation related does anyone know
how
> > to resolve this?
> >
> > Yes we have used downgraded+upgraded+supplied drives for the nic
(broadcom
> > 550x)
> >
> > If anyone could help I'd appreciate it.
> >
> > thanks
> > evan
> >
> >
> >

List,
this is the most crappy thing I can think of but I managed to fix this
problem.
It appears to overcome this problem (milage may vary) I just changed the MTU
for the n/w connection on the workstation to 512 and it all started working.

I think this is crap and should be unrelated as we're talking about a lan.
And an MTU of 1500 is what is standard across our lan. (Windows default) and
most common on the internet.

Anyway that's it. If anyone could shed some light as to why Id love to know


"evan b" <evan_at_cheapaschips.com.au_removethis> wrote in message
news:(E-Mail Removed)...
> List,
> I have this problem on our network where a largish file keeps timing out
on
> copy with the device no longer available error.
>
> All these things were working before but since a reformat of the laptop
and
> reinstall of XP pro+sp2 it decided to give us the shits.
> The network is switched and the file is on a w2.3k server (standard)
>
> I have seen this before on an unswitched network and I am led to believe
it
> has to do with the SMB timeout (lots of googling) the error does not occur
> on other machines so it's clearly workstation related does anyone know how
> to resolve this?
>
> Yes we have used downgraded+upgraded+supplied drives for the nic (broadcom
> 550x)
>
> If anyone could help I'd appreciate it.
>
> thanks
> evan
>
>