Re: How to test a nic card?
From: John McVea [MSFT] (jmcvea_at_online.microsoft.com)
Date: 04/19/04
- Next message: Sergio Moreno: "RE: can send but not receive"
- Previous message: Sergio Moreno: "RE: No Logon Servers"
- In reply to: Steven Robillard: "Re: How to test a nic card?"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 19 Apr 2004 13:30:06 -0700
Steven,
here is the link to linksys site win2k driver for the lne100tx
http://www.linksys.com/download/driver.asp?dlid=2&osid=5
there were many chipsets generically identified as "lne100tx" so double
check yours against the photos on the download page for the proper driver
correct me if I'm wrong here:
win 98 box in which both cards function
win 2000 box in which neither card will work
you can't check number of packets sent/recieved in win98-98 didn't have this
feature, don't really need to if the box has an IP address & is functioning
I would try 1 other thing on the win2k box if indeed this is the bad one
even though the 98 box connects thru cable, hub I would changes the speed
settings on the 2k box before going to the new driver (use the lne100tx
card in the 2k box)
Change link speed settings of nic
start/run/devmgmt.msc R click
nic/properties/advanced/link speed; default value is usually Auto try
changing this value alternately between 10 half duplex & 100 half & see if
it resolves the problem- some nics have trouble negotiating link speed with
various hubs/switches/OSs
-- John McVea [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. "Steven Robillard" <steven.robillard@verizon.net> wrote in message news:4084106a.9463573@news.verizon.net... > I have switched the nic and confirmed that it is not the problem. The > good compyuter still works and the bad computer still cannot connect. > I then moved the nic to another slot and reinstalled the drivers but > still no luck. I tried to find updated drivers on the internet but > was unsuccessful. > > Does anyone know where the linksys website is? > > > > > On Mon, 19 Apr 2004 14:54:35 GMT, steven.robillard@verizon.net (Steven > Robillard) wrote: > > >Here is the results from my testing: > > > >***** > >On the working computer The setup of these two computers is both > >computers go to a hub and the hub is connected to a DSL modem. > > > > Host Name . . . . . . . . . : GIRLS.dsl-verizon.net > > DNS Servers . . . . . . . . : 4.2.2.4 > > 4.2.2.5 > > 4.2.2.6 > > Node Type . . . . . . . . . : Broadcast > > NetBIOS Scope ID. . . . . . : > > IP Routing Enabled. . . . . : No > > WINS Proxy Enabled. . . . . : No > > NetBIOS Resolution Uses DNS : No > > > >0 Ethernet adapter : > > > > Description . . . . . . . . : Linksys LNE100TX Fast Ethernet > >Adapter > > Physical Address. . . . . . : 00-A0-CC-33-59-45 > > DHCP Enabled. . . . . . . . : Yes > > IP Address. . . . . . . . . : 4.13.156.186 > > Subnet Mask . . . . . . . . : 255.255.248.0 > > Default Gateway . . . . . . : 4.13.152.1 > > DHCP Server . . . . . . . . : 209.244.126.42 > > Primary WINS Server . . . . : > > Secondary WINS Server . . . : > > Lease Obtained. . . . . . . : 04 19 04 7:49:47 AM > > Lease Expires . . . . . . . : 04 19 04 11:49:47 AM > > > > > >****** > >On the non-working computer > > > > > >With suspect cable attached to nic > > > > > > > >C:\>ipconfig/all > > > >Windows 2000 IP Configuration > > > > Host Name . . . . . . . . . . . . : Main > > Primary DNS Suffix . . . . . . . : > > Node Type . . . . . . . . . . . . : Broadcast > > IP Routing Enabled. . . . . . . . : No > > WINS Proxy Enabled. . . . . . . . : No > > > >Ethernet adapter Local Area Connection: > > > > Connection-specific DNS Suffix . : > > Description . . . . . . . . . . . : Linksys LNE100TX(v5) Fast > >Ethernet A > >dapter > > Physical Address. . . . . . . . . : 00-A0-CC-33-98-92 > > DHCP Enabled. . . . . . . . . . . : Yes > > Autoconfiguration Enabled . . . . : Yes > > Autoconfiguration IP Address. . . : 169.254.30.101 > > Subnet Mask . . . . . . . . . . . : 255.255.0.0 > > Default Gateway . . . . . . . . . : > > DNS Servers . . . . . . . . . . . : > > > > > >With proven cable attached to nic > > > > > >C:\>ipconfig/all > > > >Windows 2000 IP Configuration > > > > Host Name . . . . . . . . . . . . : Main > > Primary DNS Suffix . . . . . . . : > > Node Type . . . . . . . . . . . . : Broadcast > > IP Routing Enabled. . . . . . . . : No > > WINS Proxy Enabled. . . . . . . . : No > > > >Ethernet adapter Local Area Connection: > > > > Connection-specific DNS Suffix . : > > Description . . . . . . . . . . . : Linksys LNE100TX(v5) Fast > >Ethernet A > >dapter > > Physical Address. . . . . . . . . : 00-A0-CC-33-98-92 > > DHCP Enabled. . . . . . . . . . . : Yes > > Autoconfiguration Enabled . . . . : Yes > > Autoconfiguration IP Address. . . : 169.254.30.101 > > Subnet Mask . . . . . . . . . . . : 255.255.0.0 > > Default Gateway . . . . . . . . . : > > DNS Servers . . . . . . . . . . . : > > > > > >With proven cable to release all. (This is using no hub going > >straight to the DSL modem from the computer > > > > > >C:\>ipconfig/release all > > > >Windows 2000 IP Configuration > > > >All adapters bound to DHCP do not have DHCP addresses. The addresses > >were autom > >atically configured and can not be released. > > > > > >Same setup and try to renew. > > > > > >C:\>ipconfig/renew > > > >Windows 2000 IP Configuration > > > >(I wait about a minute and then) > > > >The following error occurred when renewing adapter Local Area > >Connection: DHCP S > >erver unreachable > > > > > >Ping 127.0.0.1 > > > > > >C:\>ping 127.0.0.1 > > > >Pinging 127.0.0.1 with 32 bytes of data: > > > >Reply from 127.0.0.1: bytes=32 time<10ms TTL=128 > >Reply from 127.0.0.1: bytes=32 time<10ms TTL=128 > >Reply from 127.0.0.1: bytes=32 time<10ms TTL=128 > >Reply from 127.0.0.1: bytes=32 time<10ms TTL=128 > > > >Ping statistics for 127.0.0.1: > > Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), > >Approximate round trip times in milli-seconds: > > Minimum = 0ms, Maximum = 0ms, Average = 0ms > > > > > >Even after this the Local Area Connection Status shows no packets sent > >or received. > > > > > >I will swap out the nic and then test again. If packets are sent I > >will have my answer. > > > >BTW how do I check for packets recieved and sent on my Win 98 > >computer? > > > >John, thank you very much with detail and the reasoning behind your > >answers. It has helped very much. > > > >Steve > > > >On Fri, 16 Apr 2004 13:45:02 -0700, "John McVea [MSFT]" > ><jmcvea@online.microsoft.com> wrote: > > > >>I am able to ping myself > >>this tells us only that the network card is installed but tells us nothing about the cabling > >>we don't at this point acutally know if packets are making it out on the wire, or if the cable is good-easy check would be to swap cabling with the known good nic setup & see if good machine still works > >> the device manager says everything is working fine. > >>this tells us the driver is installed, most times, the hardware will be good here but not 100% > >> This would seem to tell me my nic is not the problem. > >>most likely in a general sort of way-could still be link speed issues if on hub/switch > >> > >>can you do start/run/cmd ipconfig /all from suspect machine send output labeled "suspect" for nic in question (please include the part that identifies the adapter) > >> > >>do start/run/cmd ipconfig /all from good machine send output labeled "good" for good nic in working machine (please include the part that identifies the adapter) > >> > >>then we can check these to make sure they both have IPs on the same subnetwork > >> > >>how are the 2 computers "bad/good" connected to each other? crossover cable, hub, switch? > >> > >>Thanks >
- Next message: Sergio Moreno: "RE: can send but not receive"
- Previous message: Sergio Moreno: "RE: No Logon Servers"
- In reply to: Steven Robillard: "Re: How to test a nic card?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
