"Specified network name no longer available" after transferring fi

[Guest]

Hi,

At what appears to be random intervals when transferring files from my
laptop to my desktop, I get this message "The specified network name is no
longer available." and then the windows explorer window on the destination
locks up. I can still use the destination but that particular window is
frozen and I have to reboot to get rid of it. There is no problem seeing the
various shares and starting the file transfers (5-10gb) but after a while
this message pops up and I'm hosed. I've tried copying individual directories
and eventually run into the same thing. Never the same file.

Relevant info: Windows XP Home, SP2 on both machines. Source is a notebook,
destination is desktop. I've tried this using both direct connect with
Firewire between the two machines and over 100mb Ethernet.

Power-saver settings and screen-savers on both machines are completely off.
Firewalls on both sides are disabled.

In googling this, there was one other person on the cdnet forums who had
exactly the same problem but never received an answer. I've looked in the MS
Knowledgebase and read the FAQ's.

Thanks,
John Q.

 

[Steve Winograd [MVP]]

Hi,

At what appears to be random intervals when transferring files from my
laptop to my desktop, I get this message "The specified network name is no
longer available." and then the windows explorer window on the destination
locks up. I can still use the destination but that particular window is
frozen and I have to reboot to get rid of it. There is no problem seeing the
various shares and starting the file transfers (5-10gb) but after a while
this message pops up and I'm hosed. I've tried copying individual directories
and eventually run into the same thing. Never the same file.

Relevant info: Windows XP Home, SP2 on both machines. Source is a notebook,
destination is desktop. I've tried this using both direct connect with
Firewire between the two machines and over 100mb Ethernet.

Power-saver settings and screen-savers on both machines are completely off.
Firewalls on both sides are disabled.

In googling this, there was one other person on the cdnet forums who had
exactly the same problem but never received an answer. I've looked in the MS
Knowledgebase and read the FAQ's.

Thanks,
John Q.

My first suggestion for that error would usually be to download and
install the latest network card drivers. But, since this happens on
both Ethernet and Firewire, I'm doubtful that it would help. Still,
it can't hurt.

What disk format does each computer use? NTFS should have no problem
with multi-gigabyte files and transfers, but FAT32 could.
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com

 

[Guest]

Hi Steve,

I'll make sure my drivers are up to day (I think they are already)... and
the file system is NTFS. I'm scratching my head on this one... usually
there's something out of date that stick out at me, but not on this one. Can
you gill me in a little bit more on the root cause of this error message... I
understand that it's probably just loss of connectivity somehow, however both
machines are still able to get out to the net when this is happening.

Thanks,
John Q.