Networking Problem

[tman2k]

Hello, I am having some problem with networking, and am hoping someone can help.

I have two machines...my "home" machine is running Windows 2000 PRO, and my cabinet is running XP PRO.  I want to be able to transfer files back and forth.  Here is my problem.

I am able to copy files from the 2000 to the XP machines, using the XP machine (ie. in Explorer, I can map a network drive to my shared folder in 2000, and copy files, delete files, etc. from my 2000 machine).  However, I cannot do it the other way around.

If I try to copy a file to the 2000 machine from the XP one, using the XP machine, I get the hourglass for a couple of minutes, and then a "The network name is no longer available" error.

If I try to copy a file to the 2000 machine from the XP one, using the 2000 machine, I get the same error.

I can also use the 2000 machine and copy files down to the XP machine no problem.  It seems as though it is a one way connection.  Note that I can see my shared folder on the XP machine...and the files in it...I just can't do anything with them.  Explorer gives me the hourglass for a couple of minutes, and then the "Network name no longer available" error message.

I have shared folders set up on both, with the proper permissions to let me modify files on each machine.  I also have it set up so I am using the same user name and password on each, both with Administrator privelages.  The computer names are different, and the workgroup name is the same.

Any ideas?  I have a bunch of stuff I need to copy from the XP machine to the 2000 machine.

Thanks!

[hyiu]

I think there is a firewall problem....

(assuming you're using a router for your home network...)

I also have a 2000 Server and an XP....

when I install the XP... they asked about the firewall thing... I set no....

I ended up having a similar pblm as you have....

you have to disable a firewall so that other machines in the same local home network can gain access.. then you should be able to transfer files....

I forgot exactly where it is.... try the control panel.... (or maybe help...)

I'm at work now and cannot check for you....

but if you can't figure out where that option is... (and if noone else posts the details...)

I can go home and check it out....
(I might not check msgs over wkend....) so... maybe Sun night / Mon night....

[ntjedi]

I agree with hyiu.  It does sound like the XP firewall is messing you up.

[Valence]

While I don't think it is the firewall to enable/disable it
Go to the control panel/network connections. Right click and select properties. Go to the advanced tab.

You call always use the admin account to access it.

\\computername\c$   (you can also use the IP)

make sure your account is the same on both computers and you will get right in.

[tman2k]

Thanks everyone for your input, but it is still not working.

The XP firewall was turned off all along.  So that is not the problem.

The computer names are the same on both, so that is not the problem.

Again, when using the 2000 machine to try and access the files on the XP machine, I can see my shared folders.  When I click on one of the folders (using Explorer), it opens the folder, and then seems to freeze for about 5 minutes, during which time I cannot access Explorer.  Finally, the folder opens and I see the files in them.  When I try to copy one of the files from the XP to the 2000, it starts to do it, and then "times out" after about 5 minutes and gives me an error, which says "Cannot copy filename: Error performing inpage operation."

If I use the 2000 machine to copy files to the XP machine, it works perfectly.

If I use the XP machine to copy files from the 2000 to the XP, it works perfectly.

If I use the XP machine to copy files from XP to 2000, I get the following error:  "Cannot copy filename: The network name is no longer available".

So, it seems I can copy from the 2000 machine to the XP machine, but NOT the other way around.  I cannot copy anything to the 2000 machine.

Any other ideas?  Possibly a bad network cable, maybe?  Perhaps one of the twisted pairs (ie. the one FROM the 2000 machine TO the XP machine) is OK, and the the pair FROM the XP machine TO the 2000 machine is flaky?  Could this cause the problem?

Any help would be appreciated!  Thanks!

[Valence]

I'm not really sure if a wire is broken what it would do. But one thing you can try in addition to checking the wire would be to edit the lmhost file. It basicall statically load the name and associates it to an IP.  Give it a try. It worth a shot. And if all else fails. You can try and use an ftp program.

[u_rebelscum]

IIRC, the last (well, only) time I saw winXP being installed (not on my computer, either), there was a windows that popped up at some point that said something to the effect: "If you want to this winXP computer talk to win9x (not sure if winNT/2000 was included) using the "My Network" stuff, you need to update the drivers on those computers to be winXP compatable."

However, I was just hanging around, and dude didn't have to worry about win9x computers, so I didn't get a good look at it before it was clicked past.  Of course, it could have been something else like printer sharing or internet sharing, so I could be way off base here.

[liquid8]

this sounds to me like a hardware issue..there should be no issues with 2k and XP talking to each other, assuming like you said that you have the proper permissions and there is no firewall. More than likely you are right about the cable.. did you make it yourself or did you buy it at a store?

LiQuiD8

[SirPoonga]

This may sound dumb, but I *think* I heard about this.  Have the user that is logged in on one machine be added to the users list on the other machine.  I know that is part of the solution for 9X to NT based connetions, But I don't think that applied to NT to NT based connections.

I'd start from scratch.  Make sure each computer can ping the other, by name first THEN by IP.  If not by name but by IP that may be an issue, means the name isn't resolving.  If you can't ping at all from both directions there is a router problem/cable problem.
If only one side can ping but the other can't there is a cable/possible software setup issue.  If both sides can ping there is a software setup issue.

If both sides can ping, hmmm, what else can you try.  Something in the pemissions or networking is screwed up.  That will take a little more involvement in determining.

If a hardware issue that should be pretty easy to figure out.

[tman2k]

Thanks everyone for the responses...

I do have the same name in the users list that is logged into the other machine....

Haven't tried ping...will try that when I get home tonight.

FWIW, I am going through a router and cable modem, and I CAN surf the net perfectly from both machines.  That makes me think that the network cable must be fine, or I would not be able to surf the net from the cabinet (the XP machine).
However, I will still keep plugging away.

Very frustrating...maybe I will just install XP on the 2000 machine...

Thanks again for all your help...

[Malachai]

If your users are setup correctly, there should not be any problems browsing shares.  I'd do some ping testing by IP and NetBIOS name.  Could be a name resolution problem.

But I have to go with liquid8 on this one.  It really sounds like a hardware issue.  What kind of NIC's are you using?  If you have a spare somewhere, you might try swapping NIC's one at a time to see if that's the problem.

[tman2k]

OK, the latest updates here:

Malachai:  I can ping both ways, using both IP and NetBIOS names, with no errors at all.  I therefore don't think it is a hardware error....

SirPoonga:  I am pretty sure the permissions are set OK...I have both sides set to allow Everyone access to each other's files.

Liquid8:  I did make the cable myself, but I have the proper tools, and have made over 100 cables in the past few years with no problems.  In fact, I even cut both ends off and crimped two new ones on to be sure...still no go...  

u_rebelscum:  I did not see any message box like that at all when I installed XP....

Well, thanks everyone for your help...any more ideas?

If not, then it looks like I will install XP on the 2000 machine...

Thanks!

[Valence]

Have you tried using FTP? win2k and XP have both the client and server built in. Have you tried editing the lmhosts file? Could be a master browser problem.

I have had similar problems on my network at work. Just a nice little bug in windows.

There are a lot of other solutions to the problem beside reinstalling them (I would at least remove TCP/IP and put it back on first)

[grafixmonkey]

I am pretty sure the permissions are set OK...I have both sides set to allow Everyone access to each other's files.

Try adding NETWORK to the permission list.  I remember having to do that frequently, and I don't think EVERYONE includes access for network users.

[SirPoonga]

GUEST might have to be added too

[Malachai]

When you ping, you may try sending larger packets to see if the NIC is fragmenting packets correctly.  Try this ping -t -l 4096 ip_address.  This will send continual 4MB ping requests.  If any of these timeout your NIC may not be fragmenting packets correctly.  Use Crtl + c to stop the ping, or just close the command window.

I've had this happen several times.  Connectivity is fine until larger packets start getting transfered.  It can cause some strange problems.  The NIC is functioning, just not 100%.

Explorer gives me the hourglass for a couple of minutes, and then the "Network name no longer available" error message.

I've never seen an error like this with a permissions problem.  The windows error would tell you flat out that you don't have permissions to access the resource if that was the case.

[PedroSilva]

Hi,

I don't know if the machines are near eachother, but if they are, why don't you try to use on both machines a USB Infrared Adapter. Not a very fast solution ... but it works.

Very easy to use, no firewall or other similar network problems and cheap (aroud 30

[SirPoonga]

Actually, there are cheap wireless connectivity solutions out there that aren't IEEE standards.  You see them on ebay for like $10-$20.  They aren't as reliable but they get the job done.  They about as fast as 802.11b.  But it is still networking through IP.

[liquid8]

I would say if you got another nic pop it in there.. it could be a driver issue. I have seen some retarded things with different nics and drivers, at least if you don't have another network card, make sure you have the latest drivers..

LiQuiD8

[Salellron]

I have had the very same problem on several setups. Both when having win2k and xp machines on a network, as well as all win2k machines on a network. Now I know this will sound severly rigged, but it has worked for me EVERY time.

Change the workgroup that each machine is on to a DIFFERENT name, but make the same change on each machine. IE: if both of your machines are on a workgroup, say WORKGROUP, change it to something like HOME (or whatever you want.. ). Reboot both of them and then give it a try. For some weird reason, I have gotten this mysterious "one way" transmission on several occasions, and that fixed it. Of course, it may not work for you, but if you have everything else configured right....never know..

Sal

[grafixmonkey]

just had to say...  

Windows networking client blows!!  

ok got it out of my system.    


(I eventually had to burn all my Mame roms to 4 CDR's to transfer them from my workstation to my arcade cab pc...   because 4 out of 5 times I transferred a zip file, it would be corrupted when it reached the other end!  I never did solve the problem.  Not even putting all the files into one RAR and transferring the RAR worked, because after I transferred the 2-gig RAR it was corrupted too!)

To be fair to the MS client, it did it through the FTP protocol too.  I'm dumbfounded.  The cards are even brand new expensive Linksys gigabit cards, operating on 100 megabit.  No excuse for them not to be working right.

[Malachai]

Windows networking client blows!!

Ahhh, grafixmonkey speaks with much wisdom.