Copying files across network: "Network drive no longer available"

[bigjon]

Setup:
- 2 Win98se boxes, one Linksys NIC, the other Netgear NIC, through Linksys 5-port hub.
- TCP/IP (default protocol), NetBEUI, M$ IPX/SPX-compatible.

Here's the problem:
If I try to copy a bunch of files from one PC to the other in Windows Explorer or within a program (Synchronix), it randomly pops up errors like "Cannot copy xxxxx, network drive no longer available" or "File Error 1026".

Any ideas? Would assigning buffer space to each NIC help (can't remember the system.ini command, something like IRQ5=4096 etc)?

 

[bigjon]

Please?

 

[obenton]

Only with a multiple file copy? - or also when transfering one very large file.

 

[Edski]

Try this:
http://support.microsoft.com/support/kb/articles/Q180/6/80.ASP
or this:
http://msdn.microsoft.com/library/psdk/wmisdk/cmperr_8tm8.htm

 

[bigjon]

Yeah only with multiple files (never noticed it on one file anyway). It can be with a transfer of 10 files or 2000 (successfully copied 2000 last night). Usually I have better luck with small transfers, so if an entire folder won't copy, I have to copy a dozen or so files at a time til it's done.

I have plenty of space on both hard disks (on both PCs), so I doubt it's the Temporary cache filling up. I wonder though about that last blurb on network traffic:
Note that this error message can also appear if the server has problems sending the file because of security issues or network traffic. In this case, the file is never created in the cache because of the bad transfer.
Could that be an issue? There are only 2 pc's and a cable modem connected to the hub. Is it possible to overrun the hub or the NICs' buffers?

Oh and BTW sometimes the error is non-recoverable and locks up Windows (ctrl-alt-del doesn't work, only thing that moves is the mouse :|). Usually though I can just restart the file transfer and it works.

Thanks guys for the suggestions - keep em coming!

 

[Scarpozzi]

So...you're using Microsoft networking? Are you mapping your drives? Just a thought...

Edit: If you don't play network games or use it for anything else, you can delete IPX/SPX because you don't need it for internal file transfers. NetBEUI does just fine. Removing any protocols you don't use always helps. However if you do have it installed and you do need it, go into your network setup and click on properties when you have IPX/SPX highlighted....then you can go to where it says frame type and change that from Auto(default) to 802.3 One final thing I would do is try swapping cables. This could be as simple as a bad connection. Good luck.

 

[bigjon]

yep, M$ Networking. I am not mapping any drives, just using UNC paths (copying from \\pc2\c\whatever). Is that a problem?

Yep, I'm a gamer UT doesn't use IPX tho, so I might kill IPX I'll try setting 802.3 today - what does that mean exactly?!

Thanks everybody!

 

[Homerboy]

had same problems with my home setup... I moved the NICs in one box around from slot to slot and it eneded up fixing the prob... dunno why, it just didn't work and now it does.

 

[obenton]

Make sure all NICs are in PCI slots 2 or 3, and not sharing an IRQ. Also, try Netbeui as the default LAN protocol.

 

[Scarpozzi]

802.3 is the standard for Ethernet set by the IEEE(Institue of Electrical and Electronics Engineers). They set standards for pretty much every type of computer cable you'll ever use... If you're going to get rid of IPX/SPX, you won't have to worry about it, but if you were to keep it, it tries to identify what kind of system you are using such as a serial connection or what not... So if you have that set to Auto, it should pick up on the fact that you have an ethernet card in your computer and not give you any problems, but often, Novell and Microsoft networks sometimes have difficulty and this setting can sometimes be the simple solution.

Mapping your drives is a thought because sometimes that will help your computer by making a solid address with the computer you are trying to connect with. Also, if you do have a network connectivity problem, you will be promted if your connection to the drive times out or is disconnected. And for the fellows that suggested changing slots....that could definitely help....more than anything, it would reseat your card and make sure that it all pins are making a good connection.

 

[FuzzyBee]

This has something to do (I'm pretty sure) with the receiving end. I had this problem all the time - it made copying ripped mp3s to my "jukebox" a real pain. Since I switched that box to linux, though, I haven't had a single problem with it. The "sending" box is still win98.

 

[brewty]

yeah, i used to have that prob too. but it only happened going one way... that was quite a long time ago though. been through a lot of reinstalls, etc since. i think back then the setup was nt 4 server and win98. nt=>win98 problems, but win98=>nt no problems. or maybe it was the other way around.

 

[bigjon]

Well I checked my IRQs last night and get this - the network card and the TNT2U are shared!!! Doh! I haven't been able to test it again but I don't think that's the problem (I just reinstalled Windows a couple weeks ago and before that I had the same problem but the IRQs weren't shared).

Thanks obenton for the heads up Which way are PCI slots numbered? Is slot 1 closest to AGP slot or ISA slots? Why are slots 2-3 the best? Are the IRQs allocated in order of slots or something?! Thanks everybody, you're all great!

 

[obenton]

Slot 1 is next to AGP. Slots two and three are best because in most MB's they are busmastering and don't share a PCI-IRQ with other devices.

 

[bigjon]

OK, I've tried a few different PCI slots (it's in slot 3 now - thanx obenton), got the NIC on its own IRQ (9), and I've removed IPX (had to remove it from both PCs for it to work right ). Heck, I even reinstalled Windows 98 on one box (it was near death anyway).

Then last night I tried copying 200mb of mp3s, and it got about half-way before crapping out again.

The only stuff left to try tonight is setting NetBEUI as the default protocol (forgot to try that last night), mapping the drives (forgot to try that too ), setting IRQ[9]=4096 in the 386Enh section of system.ini (that will give it a little buffer space), and I'm gonna try copying files the other direction (I think it'll still fail, but I can't remember if I've ever tried).

Any other ideas?

 

[bigjon]

The NIC moved itself to IRQ11 which is shared by the HighPoint UDMA66 controllers! IRQ9 is free When I try to manually set the NIC's IRQ, it says "The Resource Setting cannot be modified." What gives? I don't really want to have to move the NIC cuz I've only got a couple free PCI slots left.

:|

 

[tech]

Why netbeui? Use TCP/IP. Remove NetBEUI. Check your cables, bad cables can create all sorts of problems. Make sure that nothing is bent on the cables. I moved over 2GB of data between 2 boxes before without any problems. Another possiblity is a bad nic.

 

[bigjon]

Maybe this is a stupid question, but can you network within a LAN using Windows Explorer with only TCP/IP? I want to be able to use UNC naming (\\PC2\Share) and map drives. What is Netbeui for then? Ah - maybe a "lite" protocol? I think the bulb is coming on now in my head....

I'll check the cables again too. I know they run within a foot of a few power-line cords. I'll try temporarily re-routing the cat5 and see how it does.

Thanks!

 

[bigjon]

tech, I tried removing NetBEUI from both PCs and now neither one can see the other in Win Explorer (and shared printer is unaccessible too). Guess I'll be going back to NetBEUI.

Or am I doing something wrong? I don't really want NetBEUI if I don't need it.

 

[1keyguy]

bigjon

I had the same problem, except I have 3 computers, all with linksys nics,all else the same as yours. My problem started when one of my motherbosrds died(soyo 6iza). I replaced it with a matsonic 7137c,everything worked fine and I was able to overclock my old celeron 333to 560, 112 mhz bus (the best I could get on the soyo was 515). Then I started having problems copying files,but only to and from this computer from either of the other two, (I could copy between the other two with no problems)so the problem had to be on this one. I tried everything I could think of, even reinstalled windows, no luck.
Anyway I finally changed the bus speed to 103 like I had it before and now it works again......


Anyway, are any of your machines using an odd bus speed ? If so you might give this a try

 

[SufferinSuccotash]

bigjohn -- You are thinking of NetBIOS which is what lets you access computers by their UNC name (\\computer\share). NetBEUI is a protocol made by Microsoft and stands for NetBIOS Enhanced User Interface. You can actually run NetBIOS over TCP/IP, NetBEUI, and NWLink IPX/SPX. [EDIT]Or just plain ol' IPX/SPX.[/EDIT]

 

[bigjon]

Sufferin Succotash Batman! The lite upstairs has come on! I do kinda remember hearing that way back, but that's why I could never get Explorer to find the other computer when just TCP/IP was enabled! I'll try again with just TCP/IP but this time I'll enable NetBIOS. Thanks!

1keyguy, thanks I'll check that, but I'm almost certain they're both running at 66mhz bus now (although 1 of the PCs was overclocked until recently). [edit]Yep, they're both running at 66mhz bus.[/edit]