Unable to copy files

[krugan]

I have two computers with win98 on them and a ethernet mini hub. One computer uses an ISA 10mb NIC and the other uses a PCI fast ethernt NIC.

Now the problem I am having is that when I go to one computer and try to copy the files from the other I end getting this:

Error Copying File

Cannot create or replace "filename": The specified network resource or device is no longer available.

I'm wondering if this hub (it is just a cheap hub and it doesn't say whether it supports 10/100 ethernet) cannot support the different NICs. Any ideas other then replacing the ISA NIC first?

[iamtheman]

Can you ping between the two machines???

[krugan]

Ya, I am able to ping each other and I can both see each others computer in network neighborhood. I can share files and look around but when it starts to copy after 10 seconds or so that error comes up.

[Ron Prestenback]

This message means that the share you have created is no longer valid. For instance, let's say you share a directory on computer 1 called "C:\files". You share the directory as "Shared Files". So computer two now has this share mapped to "\\Computer1\Shared Files". Now, if you happen to rename this directory, or move it to somewhere else, or anything like that, the other computer will not delete that reference automatically, and you would receive the error message you're getting. Sometimes, you actually didn't change anything, but for some reason, the computer thinks you did. This will also happen if you change the computer name, etc.

The way to resolve this is to unshare everything on both computers; make sure that you also delete any entries in "Network Neighborhood" that refer to these old shares. (After you have accessed a share a couople of times, Windows will put a shortcut on the root directory of "Network Neighborhood". This is the most common cause of these types of glitches.) Anyway, once you unshare everything, then you can go back and reshare everything, and reconnect. Everything should be OK after that. If this doesn't work let me know, as there are a few technicalities that could arise. They are minor, but they may show up. If you still aren't able to share files properly between the two computers, don't give up just yet. <IMG SRC="smilies/wink.gif" border="0"> We've still got plenty more answers here!

[Gabriel]

I have Bypassed a similar Scenario before.
What i did is to boot up in Command prompt (with network Support) and "net use" and it worked like charm.

Sure it isn't a Cure but it will work.

[Twisted_Mister]

Originally posted by Gabriel:
<STRONG>I have Bypassed a similar Scenario before.
What i did is to boot up in Command prompt (with network Support) and "net use" and it worked like charm.

Sure it isn't a Cure but it will work.</STRONG>

Samr here, Gabriel. I have seen the problem a few times, but I have a universal network boot disk that I use in those instances. I can get an image of the disk if it helps, but I have never spent time to resolve the REAL problem.

[Ya_know]

I had a funny one with Win2k moving files to a NT server, following a NIC upgrade to 3com 10/100. The error I recieved refered to not being able to move the directorys the files were coming from, as they were in use or something like that. Now I am talking about a standard drag and drop, selecting move as the option, errors every time. I could move from the NT server, to the 2k PC, but the other way would give errors. I could even copy from 2k to NT, just not move.

The fix, believe this, SP2 was just released. I installed that, and never had a problem since.

Just thought I would share...

[Ron Prestenback]

Well, it still happens post-SP2. I can attest to it. It seems like a problem with the (net)browser service of Win2K itself. I've run into many situations where Win2K had trouble concerning browser issues.

For instance, if you are logged into a workstation, you cannot join a domain if you have already initiated contact with that DC during the same session as workgroup computer (copying files from it for instance). The domain controller will tell you something like "The credentials you provided conflict with an existing set of credentials" or something similar. If you logoff and log back on, you fine.

Similarly, with this file transfer thing - if you are getting a message that the file is in use, and you know it's not, chances are that the last computer to connect to the share still shows as being connected. You can test this by trying to unshare the drive. If Win2K has goofed and forgot to update who's accessing what, it will tell you that "so and so number are users are logged on. If you unshare this share, all users will be disconnected. Are you sure you want to do this?" It once told me I had 4 users connected on my home computer, and I only have 2 computers! Once you unshare, however, everything is set back to normal, and upon resharing the folder, you should find that you have no problems.