|
Question : PC with 3c905c-tx NIC returns 110ms ping, but rest on same hop <10ms.
|
|
Their are three computers in our 10.10.20.0 segment, the two intel pro 100 NIC return constant <10ms ping, but the 3com 3c905c-tx is steady with 110. I intermittantly loose connectivity too. But I appears to be the T1 is unstable. I'm using needTEXT and freeping to monitor connectivity.
Maybe I have a incorrect device setting on the 3c905c-tx. Here is a list of the device settings. 802.1p Support Disabled DoubleNego Enabled Down Poll Rate 8 Eng LAN Power Mgmt On Flow Control Enable InitDelayCount 0 LnkChk Enable Media Type 100 MB, Full Duplex PHYCompat Enable RWU ARP Disable RWU Magic Pkt Enable RWU Ping Disable Rx Checksum Offload Enable Software Cable Detect Off Stdby RWU Magic Pkt Enable Stdby RWU Pattern Enable Tx Checksum Offload Enable
What is: RWU stand for? (Restart/WakeUp?) PHYCompat ? What does it do.
Well anyway any ideas appreciated.
Unfortuatly BestBuy, CircuityCity, MicroCenter don't carry Intel pro 100 NIC and CompUSA's has them for delivery only. Or I'd just go get one today.
500 pts is for urgency.
|
Answer : PC with 3c905c-tx NIC returns 110ms ping, but rest on same hop <10ms.
|
|
Try the following config :
802.1p Support Disabled DoubleNego Disabled Down Poll Rate 8 Eng LAN Power Mgmt Off Flow Control Enable InitDelayCount 0 LnkChk Enable Media Type Auto PHYCompat Disable RWU ARP Disable RWU Magic Pkt Disable RWU Ping Disable Rx Checksum Offload Disable Software Cable Detect Off Stdby RWU Magic Pkt Disable Stdby RWU Pattern Disable Tx Checksum Offload Disable
This is a FailSafe configuration . In the same time, update all drivers from 3COM . If you are usind W2K or XP try PATHPING <targetIP> to see some statistics. From another point of view, check cable and conectivity. A ... question: if you change the connection point ( INTEL <-->3COM), the response is the same ?! If NO, you ave some collisons or other connectivity problem. Try another test : FTP , the same file from the same server . If the result is the same time, don't lose time to fix a PING response. :-) C.U.
|
|
|
|