Data Transfer Interruptions

When transferring large folders with multiple files I receive the following error message. Any and all help will be highly appreciated. Thanks



Error Copying File or Folder (Red circle with white X here)
"Cannot copy (file name here) - The specified network resource or device is no longer available. "

Things I have tried:

1. Reinstalled drivers.
2. Disabled "Detect connection to media type "
3. Set Browse Master to Automatic on both PCs
4. Disabled Browse Master on one PC.
5. Set Media Type to from AutoSense to 100base TX_Full Duplex
6. Move NIC to a different PCI slot.
7. Checked CAT 5 Cable and made sure connections were secure and away from
electrical lines.
8. Moved switch away from all electrical devices.
9. Changed CAT5 cables.

2 PC LAN consisting of:

P-III 1000 P-II 400 running Windows Me w/ Intel chips and chips sets
Linksys LNE100TX v.5 NICS (both)
384Mb RAM (both)
Linksys 8 port switch
ICS enabled on P-III
Longest cable run = 45 ft

 

Do you have good data lights at all points?
On a linksys card you should have 3 solid greens for 100Mb full duplex.
Have you run a packet test?
From a comand promp
C:\ping 192.168.1.? -n 1000 -L 1000
Start with your own IP address and work your way out.
Try the switch next my guess is it's IP is 192.168.1.1
C:\ping 192.168.1.1 -n 1000 -L 1000

You should have zero packet loss and a latency of around 1ms inside your network.
The cheapest insurance you could buy is have someone come in and test the cables unless they are all factory cables, which the jury is still out on that.

 

I did this from a windows DOS prompt and received the following.

bytes=1000 time<10ms TTL=128

When I tried to do the switch it stated " L" was a bad command.

I did not see anything about latency or packet loss. I do not have broadband, just dial-up. Sorry, but this ping stuff is new to me.

 

Try changing the /L to a /l since ping switches are case sensitive and it wants the lower case one.

Also, add a -t to the string right after the word "ping" which will cause the test to go until you stop it (with a ctrl-break or something). Let it run for a few screens full and check mainly for consistency. You should get the same values (or nearly) returned each time.

The idea to force large packet and buffer sizes is a good one since the defaults are pretty small and polite and may work fine even if you have a problem.

Try ping /? to see the options available and then maybe read up on ping some. Very useful troubleshooting tool for TCP/IP networks.

 

Sorry I wasn't clearer on that

 

Ping statistics for 192.168.0.1:
Packets: Sent = 209, Received = 209, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 14ms, Average = 0ms

Ping Statistics for 192.168.1.:
Packets: Sent = 156, Received = 155, Lost = 1 ( 0% loss), Approximate round times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms

The test for 192.168.1 would only run while I was connected to the Internet and showed "Reply from (address I did not include) Destination host unreachable."

So, what do these test tell you/me?

 

Did you ping the other machine?
To determine the IP address of the other machine, go to that machine and from a command prompt type at the C:\
C:\ipconfig

should look something like this:
IP Address. . . . . . . . . . . . : 192.168.1.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1

packet test should look something like this:

C:\>ping 192.168.1.101 -n 1000 -l 500

Pinging 192.168.1.101 with 500 bytes of data:

Reply from 192.168.1.101: bytes=500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=500 time<1ms TTL=128

-l 500 equals the size of the packets
-n 1000 equals the number of packets
you can make those numbers anything you like:

C:\>ping 192.168.1.101 -n 25 -l 1500

Pinging 192.168.1.101 with 1500 bytes of data:

Request timed out.
Reply from 192.168.1.101: bytes=1500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=1500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=1500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=1500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=1500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=1500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=1500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=1500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=1500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=1500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=1500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=1500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=1500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=1500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=1500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=1500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=1500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=1500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=1500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=1500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=1500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=1500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=1500 time<1ms TTL=128
Reply from 192.168.1.101: bytes=1500 time<1ms TTL=128

Ping statistics for 192.168.1.101:
Packets: Sent = 25, Received = 24, Lost = 1 (4% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\>

I lost the first packet on that string but Im not concerned with that because that machine was asleep.

 

I checked both cards with the Linksys diagnostic program all passed. With System Monitor I get 2.4 - 2.5 M (I think that means Mega Bytes not bits) read a second. When I copy those 250Mb directories I see that my unused physical memory all but goes away and it quits w/ error at about 100Mb. I beginning to wonder if software i.e. NAV might have something to do with this, anyone?

 

that has to mean bits.
a 10/100 network is 10Mb/100Mb (megabit per second)
I not sure about that diagnostic program but it may be checking communication between the motherboard bus and the card.
Did you ever look at the display lights on the card and on the router?

 

v.5 of the LNE100TX has only two lights.

Light one (100 LED) illuminates when operating at 100Mps, or off for 10Mps. Light two (Link/ACT) stays green and flickers when there is data transfer.

All lights on the cards and switch show that I'm in 100Mbps with no collisions.

 

Cool. Don't know what to tell you from there. How is that cat 5 routed through the house? Are the cables near any electrical wires or florescent lights?
Do you have any data cable buddies that can come test your cables? I know I'm hammering on the cable issue but I don't know what else it could be. Bad cables or interference will drive you nuts. That's why cable testing rules that out of the puzzle.

 

Hmm, my switch is about 3' away from a fluorescent light, but it's usually off. I've moved all the cables as far away from all possible sources of interference as I possibly can. I’ve replaced the shorter or the two cables, so I guess I'll have the 40' run in the crawl space tested. What gizmo do I need to test it with? I'm sure a good multipurpose meter won't do.

 

That's why I asked you if you had a buddy in the data cable biz because a good tester is 7000.00!
Maybe go buy a factory crimped 50' patch cable and string it through the house to see if that fixes it.

 

I know someone who might be able to help me out with that. Thankx for all your help.

 

ssmith10pn,

Your suggestion to replace my existing cable with a factory-crimped cable seems to have worked, so far I’ve not had any interruptions. It’s amazing how a cable can mess with your network. There sure was a lot of hair pulling for one stinking cable.

Here’s a stupid question:
Why can’t they come up with a simpler wiring method...like a shielded duel coax or something? Will we see fiber optic cable in the near future?

 

Spend some time here, you will learn a lot. http://www.lanshack.com/highlights/cat5notes.htm

 

George -

192.168.1 (from your post above) shouldn't ping as it isn't a complete IP address.

You should absolutely be able to ping your switch as long as you are connected to it. Internet would make no difference whatever.

We did use shielded coax back in the dark ages. 10base2 it was (I think - been a while) rather than 10baseT. And no way to push it to 100baseT (100Mbs). And ... well, sufice it to say we got it better these days with twisted pair cables. Performance from good UPT cable is lots better.

Fiber is out there now. You just gotta pay a bunch for it.

 

Yea Newt we are showing our age. Remember the BNC connectors?
Bus systems?
Terminators?
A break in the segment kills everybody.