Re: Lost Packets

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Kristofer Gafvert (kgafvert_at_NEWSilopia.com)
Date: 03/31/04


Date: Wed, 31 Mar 2004 11:40:36 +0200

The easiest to do, and many times solves problems like this, is to update
the NIC driver on both computers. If this does not fix your problem, i would
recommend you to try to connect the computer using a cross over cable. That
will tell you if you have a problem with a switch/hub/other device, that
connects these two computers together.

I have seen this before, and in that case, the problem was a switch that did
not work properly (fast in one direction, very slow in the other direction).
Furthermore, only two computers were affected. It is possible that you have
a similar problem, and a cross over cable will tell you if this is the case.

Also, worth to check is if you have any firewall on any of the PCs involved.
This can also slow down the traffic. AV software with real time checking,
can also cause slow downs.

-- 
Regards,
Kristofer Gafvert - IIS MVP
Reply to newsgroup only. Remove NEWS if you must reply by email, but please
do not.
www.ilopia.com - FAQ and Tutorials for Windows Server 2003
"Jansen Barbara" <jansen@maltanet.net> wrote in message
news:7c51b5e2.0403310123.28228e17@posting.google.com...
> I just installed a P1 with win xp.Everything seemed ok until I found
> out that transfering a 340Mb file from my P3 win xp to this P1 winxp
> was going to take ages.In fact windows said that it will be transfered
> at 131hrs.After some minutes transfering the first part of the file, I
> had a message stating somethign like "the resource is not anymore
> available"
>
> I started troubleshooting the problem by pinging from my host computer
> (P3) to this Pc (P1) and had request timed outs like the following:
>
> Pinging testpc [192.168.0.235] with 32 bytes of data:
>
> Reply from 192.168.0.235: bytes=32 time<1ms TTL=128
> Reply from 192.168.0.235: bytes=32 time<1ms TTL=128
> Request timed out.
> Request timed out.
>
> Ping statistics for 192.168.0.235:
>     Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
> Approximate round trip times in milli-seconds:
>     Minimum = 0ms, Maximum = 0ms, Average = 0ms
>
> To keep this note short,trying from the testpc I also had same loss of
> packets.On the other hand I tried pinging the other P3 pc (win xp)
> however I never received any loss of packets.I also tried transfering
> the same file from this host pc to the other P3 pc.The last only took
> around 5minutes or less.
>
> then I checked the mac addresses:
>
> P1 - 00-30-4F-04-9F-61
> P3 - 00-30-4F-04-9F-52
> P3 - 00-50-FC-80-5C-8A
> P3 - 00-E0-06-09-55-66
>
> No mac conflict.
> I just went from another P3 to try the transfer. I started pinging the
> P1 pc from the other PC and had no request timed outs until I started
> again transfering the file.I've noticed that when there is any network
> operation on this P1 Pc packets are being lost.Just displaying the
> drive contents will give request timed out.Is this problem related to
> a P1 with xp? or Is this problem coming since the P1 can't handle this
> speed. I am connected 100Mbps on all computers! Can I slow something
> from the P1 so that transfer at least can be done.
>
> Small note:
>
> On this P1 pc I have Internet browsing,which is quit normal speed for
> this P1.Pages load in few seconds.
>
> Is it a problem of bottle neck?Can I increase time outs
>
> Regards
> Jansen


Relevant Pages

  • Re: Lost Packets
    ... I agree - drivers or cables. ... > connects these two computers together. ... >> at 131hrs.After some minutes transfering the first part of the file, ...
    (microsoft.public.windowsxp.general)
  • Re: Performance Issue - NT Kernel & System using 50% CPU
    ... I run a bandwidth monitor program so that I can watch how ... much ISP bandwidth is being used since my ISP degrades my bandwidth rate ... in my house and is actively transfering data between the computers. ...
    (microsoft.public.windows.server.general)
  • Re: Wired Network with XP
    ... Yes on Both computers ... Pinging 4.232.42.159 with 32 bytes of data: ... Ping statistics for 209.244.0.3: ... Ethernet adapter Desk Top: ...
    (microsoft.public.windowsxp.network_web)
  • Re: Wired Network with XP
    ... Yes on Both computers ... Pinging 4.232.42.159 with 32 bytes of data: ... Ping statistics for 209.244.0.3: ... Ethernet adapter Desk Top: ...
    (microsoft.public.windowsxp.network_web)
  • Re: Wired Network with XP
    ... Yes on Both computers ... WAN Miniport ... Pinging 4.232.42.159 with 32 bytes of data: ... Ping statistics for 209.244.0.3: ...
    (microsoft.public.windowsxp.network_web)