You may also want to try increasing the send/rec. buffers. It could be that the target server is getting pounded so hard that enough packets are dropping to loose the connection.
This happend to one of my SMS servers when we used to run Token Ring. The server would get pounded so hard that it would actually blue screen. I increased the buffers to the max and it helped out considerably until we moved to Ethernet. No blue screens in over a year. lenny > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of > [EMAIL PROTECTED] > Sent: Wednesday, January 30, 2002 17:29 > To: MSWinNT Discussions > Subject: RE: Large File copy over network > > > Use 2 completely different computers connected to the same hub to > move large > files > if fails definately hub, if ok then take a closer look at you > packet size on > each computer, they maybe different length. > You should use netmon while copying to monitor whats going on at packet > level. > > William > > > -----Original Message----- > From: Randall Yoo [mailto:[EMAIL PROTECTED]] > Sent: Thursday, 31 January 2002 11:11 > To: MSWinNT Discussions > Subject: RE: Large File copy over network > > > I was thinking the same thing (how did they run the servers all > these times > like this??). In any case, they insisted on hard-coding things, so I > told'em to change the NIC's to half-duplex or Auto, and to change back to > full-duplex when they purchase a switch. > > Randall > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Ed Esgro > Sent: Wednesday, January 30, 2002 02:01 PM > To: MSWinNT Discussions > Subject: RE: Large File copy over network > > > That works great! > How did the server work at all? > > -----Original Message----- > From: Randall Yoo [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 30, 2002 4:59 PM > To: MSWinNT Discussions > Subject: RE: Large File copy over network > > I've seen similar thing happen at a customer site where they had > hard-coded > the NIC's to 100mb/full-duplex, but they were connected to a hub! > > Randall > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of MacDonald, Bruce > (VAN_Exchange) > Sent: Wednesday, January 30, 2002 01:43 PM > To: MSWinNT Discussions > Subject: RE: Large File copy over network > > > The last (and only) time that I had a problem copying large files (in this > case > 4MB) the problem was a bad hub port. The log stated ???? encoding > error. > > Check your closet gear... > > Bruce MacDonald > Manager, Information Technology > Pacific Newspaper Group (Kennedy Heights) > (604) 605-7269 ph > (604) 605-7239 fax > [EMAIL PROTECTED] > > > > -----Original Message----- > From: Bill Kuhn - MCSE [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, January 30, 2002 13:25 > To: MSWinNT Discussions > Subject: RE: Large File copy over network > > > I have seen that before at a client site. In their case it was copying > 1+gig zip files between an NT4 server and a Win2000 Server. > > We found a MS Q article on the error message, and it indicated that 2000 > SP1 should fix. It didn't. > > We tried newer network card drivers on both machines at the suggestion > of someone on this list several months ago. Still no dice. > > We gave up and went to plan B which didn't involve copying files that > large. I wish we had found a real solution. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Gagrani, Kishore > Sent: Wednesday, January 30, 2002 12:11 PM > To: MSWinNT Discussions > Subject: Large File copy over network > > > when I try to copy large size files (1 GB and up, eg .pst > files and other folders) from Win2000 Prof machine to my Snap Server > (Win2k > Server) on > network, after some progress of data copy, it throws me with the > following > error: > Cannot copy <filename>: The specified network name is no longer > available. > When I open Windows explorer I can browse into the network drive of my > snap > server, wheras when I try to copy large filesizes it fails. Small file > sizes > it copies. Is there some fine tweaking of some settings I can try on my > Windows2000prof so that the network name remains available for a longer > time > before it times out? Request help solving this mystery!!! > > Thanks > Kishore > > ------ > You are subscribed as [EMAIL PROTECTED] > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe send a blank email to [EMAIL PROTECTED] > > ------ > You are subscribed as [EMAIL PROTECTED] > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe send a blank email to [EMAIL PROTECTED] > > ------ > You are subscribed as [EMAIL PROTECTED] > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe send a blank email to [EMAIL PROTECTED] > > > ------ > You are subscribed as [EMAIL PROTECTED] > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe send a blank email to [EMAIL PROTECTED] > > ------ > You are subscribed as [EMAIL PROTECTED] > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe send a blank email to [EMAIL PROTECTED] > > > ------ > You are subscribed as [EMAIL PROTECTED] > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe send a blank email to [EMAIL PROTECTED] > > > ------ > You are subscribed as [EMAIL PROTECTED] > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe send a blank email to [EMAIL PROTECTED] > ------ You are subscribed as [email protected] Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe send a blank email to [EMAIL PROTECTED]
