Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[war59312]

Hi,

Here is what I see on my Windows XP Pro. SP3 x86 PC:



Earlier today I saw it pass 4 million errors. Crazy! Sent errors is always a small number. Though it should be zero too?

Yet everything seems to be working just fine. Even when it hit 4 million errors nothing appears to be broke.

Even getting my full 300Mbps to the router and maxing out my bandwidth of 16Mbps (downloaded a 85 GB file to be sure).

Crazy Windows and/or Driver bug? Is the network card bad? Should I send it back to Newegg for replacement? Just got it Tuesday.

Last time I checked, it should always be 0 errors, for both sent and received.

I just now checked my old PC which is using a USB wireless adapter and no errors at all, and that's after 3 months of being online 24/7.

Just for kicks, I tried same adapter in my PC and no errors after a few hours so seems nothing on my PC causing it.

Something odd is going on for sure then.

And of course, I'm running the latest driver from the dlink site.

Any thoughts,

Will

Update:



Still, everything seems to be functioning correctly.

[arod]

war59312,

Can you open up a command prompt and type in ipconfig /all and list what you see here.. Also ensure the adapter is properly seated in your PC or try another slot.

[war59312]

As requested:

Windows IP Configuration

        Host Name . . . . . . . . . . . . : Will
        Primary Dns Suffix  . . . . . . . :
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : No
        WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 8:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : D-Link DWA-552 XtremeN Desktop Adapter
        Physical Address. . . . . . . . . : 00-1E-58-39-C1-E8
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 192.168.1.105
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.1.1
        DNS Servers . . . . . . . . . . . : 208.67.222.222
                                            208.67.220.220
        NetBIOS over Tcpip. . . . . . . . : Disabled

Tired all three PCI lots on my motherboard and same. Many errors reported by windows when used in either one.

I know all three lots are good as one has had my sound card in it and still works just for over a year. The other two before getting this one and raid card adapters in them. No longer needed since using External Raid connection now. So I know all the lots are good.

So do you think the unit is defective?

[war59312]

Still need help on this d-link, pls. Any ideas?

[funchords]

Ignore it or go to HKLM\CurrentControlSet\Control\Network\Connections\StatMon\ShowLanErrors and delete the ShowLanErrors key.

What this does -- to this day I've never seen a clear explanation, but here is what I've gather --

Every IP packet that the stack can't decode or disposition is an RX error. This includes packets and partial packets that aren't for your hardware or IP or even your WLAN (remember, these are shared frequencies).

Every IP packet the stack can't send out is a TX error. These will be a lot more rare because your stack will only get TX packets its supposed to handle.  It could be that the card was in the wrong state. This isn't a problem because TCPIP.SYS simply does it again.  It could be that an ICMP was blocked, which are optional anyway. The error, and the right response to the error, caused no hiccup at all. 

So when using these counters, they're relative over time.  They ought to be graphed, the counters are useless alone and disabled (hidden) by default. 

0 is perfect, however 0 is never going to happen in real life.  (You may see 0 but that's a diagnostic thing -- some network cards handle errors in hardware.)  Networks have collisions and noise and these alone are not signs of trouble. 

Myself, here's what I've racked up in 16 hours.. (some are errors, some are just counts -- also my wireless card is Intel which handles some errors on card rather than in the OS, as you observe some hardware offloads most all error checking and handling). 

Code: [Select]

robb@topol015:~$ nstat
#kernel
IpInReceives                    166872             0.0
IpInAddrErrors                  173                0.0
IpInDelivers                    157059             0.0
IpOutRequests                   138615             0.0
IpOutNoRoutes                   39                 0.0
IcmpInErrors                    8898               0.0
IcmpInDestUnreachs              3                  0.0
IcmpInTimeExcds                 36                 0.0
IcmpInParmProbs                 25                 0.0
IcmpInEchoReps                  46                 0.0
IcmpInTimestamps                8791               0.0
IcmpOutErrors                   8914               0.0
IcmpOutTimeExcds                36                 0.0
IcmpOutTimestamps               46                 0.0
IcmpMsgInType0                  8791               0.0
IcmpMsgInType3                  36                 0.0
IcmpMsgInType8                  46                 0.0
IcmpMsgInType11                 25                 0.0
IcmpMsgOutType0                 46                 0.0
IcmpMsgOutType3                 36                 0.0
IcmpMsgOutType69                8832               0.0
TcpActiveOpens                  6191               0.0
TcpPassiveOpens                 92                 0.0
TcpAttemptFails                 14                 0.0
TcpEstabResets                  159                0.0
TcpInSegs                       143059             0.0
TcpOutSegs                      126463             0.0
TcpRetransSegs                  907                0.0
TcpInErrs                       26                 0.0
TcpOutRsts                      904                0.0
UdpInDatagrams                  5052               0.0
UdpInErrors                     1                  0.0
UdpOutDatagrams                 2356               0.0
UdpRcvbufErrors                 1                  0.0
Ip6InReceives                   2                  0.0
Ip6InDelivers                   2                  0.0
Ip6OutRequests                  20                 0.0
Ip6OutMcastPkts                 24                 0.0
Icmp6OutMsgs                    18                 0.0
Icmp6OutRouterSolicits          9                  0.0
Icmp6OutNeighborSolicits        3                  0.0
Icmp6OutMLDv2Reports            6                  0.0
Icmp6OutType133                 9                  0.0
Icmp6OutType135                 3                  0.0
Icmp6OutType143                 6                  0.0
TcpExtPruneCalled               176                0.0
TcpExtTW                        1450               0.0
TcpExtTWRecycled                1                  0.0
TcpExtPAWSEstab                 70                 0.0
TcpExtDelayedACKs               5415               0.0
TcpExtDelayedACKLost            432                0.0
TcpExtTCPPrequeued              6                  0.0
TcpExtTCPDirectCopyFromPrequeue 1858               0.0
TcpExtTCPHPHits                 76920              0.0
TcpExtTCPHPHitsToUser           2                  0.0
TcpExtTCPPureAcks               16079              0.0
TcpExtTCPHPAcks                 1607               0.0
TcpExtTCPSackRecovery           2                  0.0
TcpExtTCPTSReorder              1                  0.0
TcpExtTCPFullUndo               1                  0.0
TcpExtTCPPartialUndo            2                  0.0
TcpExtTCPDSACKUndo              1                  0.0
TcpExtTCPLossUndo               51                 0.0
TcpExtTCPSackFailures           1                  0.0
TcpExtTCPFastRetrans            5                  0.0
TcpExtTCPForwardRetrans         1                  0.0
TcpExtTCPSlowStartRetrans       3                  0.0
TcpExtTCPTimeouts               680                0.0
TcpExtTCPRcvCollapsed           3842               0.0
TcpExtTCPDSACKOldSent           416                0.0
TcpExtTCPDSACKOfoSent           8                  0.0
TcpExtTCPDSACKRecv              55                 0.0
TcpExtTCPAbortOnData            70                 0.0
TcpExtTCPAbortOnClose           28                 0.0
TcpExtTCPAbortOnTimeout         5                  0.0
TcpExtTCPDSACKIgnoredOld        5                  0.0
TcpExtTCPDSACKIgnoredNoUndo     21                 0.0
TcpExtTCPSpuriousRTOs           1                  0.0
IpExtInMcastPkts                192                0.0
IpExtOutMcastPkts               152                0.0
IpExtInBcastPkts                2985               0.0
IpExtOutBcastPkts               375                0.0
robb@topol015:~$ uptime
 01:56:45 up 16:21,  2 users,  load average: 0.37, 0.31, 0.27
robb@topol015:~$

HTH. 

You can ignore that display -- pretty much forever.  The command "netstat -s" has similarly useful statistics if you are experiencing a real performance or integrity problem and want to troubleshoot it.  The error display is not needed. 

[war59312]

Yeah been ignoring since it seems fine, just wondering if anyone else is seeing same thing, and yeah I knew about the reg key, I turned it on..

Anyhow, After less than 8 hours (17 million errors and 930,000 packets reported in wireless connection):

IPv4 Statistics

  Packets Received                  = 8199853 (wow and yet wireless connections shows less than 1 million)
  Received Header Errors             = 0
  Received Address Errors            = 845
  Datagrams Forwarded                = 0
  Unknown Protocols Received         = 0
  Received Packets Discarded         = 0
  Received Packets Delivered         = 8199853
  Output Requests                    = 8837568
  Routing Discards                   = 0
  Discarded Output Packets           = 0
  Output Packet No Route             = 0
  Reassembly Required                = 0
  Reassembly Successful              = 0
  Reassembly Failures                = 0
  Datagrams Successfully Fragmented  = 0
  Datagrams Failing Fragmentation    = 0
  Fragments Created                  = 0

ICMPv4 Statistics

                            Received    Sent
  Messages                  1118        27
  Errors                    0           0
  Destination Unreachable   625         24
  Time Exceeded             1           0
  Parameter Problems        0           0
  Source Quenches           490         0
  Redirects                 0           0
  Echos                     0           3
  Echo Replies              2           0
  Timestamps                0           0
  Timestamp Replies         0           0
  Address Masks             0           0
  Address Mask Replies      0           0

TCP Statistics for IPv4

  Active Opens                        = 29835
  Passive Opens                       = 8085
  Failed Connection Attempts          = 16089
  Reset Connections                   = 825
  Current Connections                 = 56
  Segments Received                   = 7885186
  Segments Sent                       = 8384181
  Segments Retransmitted              = 91050

UDP Statistics for IPv4

  Datagrams Received    = 314611
  No Ports              = 74
  Receive Errors        = 13
  Datagrams Sent        = 363052

[thecreator]

Hi war59312,

Remove IPv4 or Microsoft TCP/IP version 6 protocol from the adapter. Just go with the Internet Protocol (TCP/IP) instead.

Perhaps your ISProvider is not using Microsoft TCP/IP version 6 protocol, particularly when relaying information.

Or the places you are communicating with aren't using the same protocol as you are. Therefore the errors.

[funchords]

He's behind a home gateway, so any errors from the ISP side would be filtered by it.

This is actually normal.  See my message from December 2.

[war59312]

It's cool. I'm ignoring it, all seems well. Thanks anyhow. Tried removing ipv4 and adding back just to see, still errors.

I just thought it was odd since every other adapter I've tried never reported any errors..