network controller [long]

az240zz

ASFN Lifer
Joined
Sep 11, 2002
Posts
3,314
Reaction score
542
I ran the network diagnostic to check my network connections as I can't get a computer to connect wirelessly

Network Adapters FAILED
[00000001] HP EN1207D-TX PCI 10/100 Fast Ethernet Adapter (FAILED)
Caption = [00000001] HP EN1207D-TX PCI 10/100 Fast Ethernet Adapter
DatabasePath = %SystemRoot%\System32\drivers\etc
DefaultIPGateway = 192.168.1.1(Same Subnet) (PASSED)
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=1
Reply from 192.168.1.1: bytes=32 time=1ms TTL=1
Reply from 192.168.1.1: bytes=32 time=1ms TTL=1
Reply from 192.168.1.1: bytes=32 time=1ms TTL=1
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
Description = NVIDIA nForce Networking Controller - Packet Scheduler Miniport
DHCPEnabled = TRUE
DHCPLeaseExpires = 10:16:28 PM 9/14/2005
DHCPLeaseObtained = 10:16:28 PM 8/30/2005
DHCPServer = 16.92.3.250 (FAILED)
Pinging 16.92.3.250 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 16.92.3.250:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
DNSDomain = americas.hpqcorp.net
DNSEnabledForWINSResolution = FALSE
DNSHostName = MINE
DNSServerSearchOrder (FAILED)
16.92.3.242 (FAILED)
Pinging 16.92.3.242 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 16.92.3.242:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
16.92.3.243 (FAILED)
Pinging 16.92.3.243 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 16.92.3.243:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
16.81.3.243 (FAILED)
Pinging 16.81.3.243 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 16.81.3.243:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
16.118.3.243 (FAILED)
Pinging 16.118.3.243 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 16.118.3.243:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
DomainDNSRegistrationEnabled = FALSE
FullDNSRegistrationEnabled = TRUE
GatewayCostMetric = 20
Index = 1
IPAddress = 192.168.1.2 (FAILED)
Pinging 192.168.1.2 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
IPConnectionMetric = 20
IPEnabled = TRUE
IPFilterSecurityEnabled = FALSE
IPSecPermitIPProtocols = 0
IPSecPermitTCPPorts = 0
IPSecPermitUDPPorts = 0
IPSubnet = 255.255.255.0
IPXEnabled = FALSE
MACAddress = 00:18:F3:28:79:29
ServiceName = RTL8139
SettingID = {892900FC-9814-4488-99C0-81491C1EE93D}
TcpipNetbiosOptions = 0
TcpMaxDataRetransmissions = 5
WINSEnableLMHostsLookup = TRUE
[00000011] NVIDIA nForce Networking Controller (FAILED)
Caption = [00000011] NVIDIA nForce Networking Controller
DatabasePath = %SystemRoot%\System32\drivers\etc
DefaultIPGateway = 192.168.1.1(Same Subnet) (PASSED)
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=1
Reply from 192.168.1.1: bytes=32 time=1ms TTL=1
Reply from 192.168.1.1: bytes=32 time=1ms TTL=1
Reply from 192.168.1.1: bytes=32 time=1ms TTL=1
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
Description = NVIDIA nForce Networking Controller - Packet Scheduler Miniport
DHCPEnabled = TRUE
DHCPLeaseExpires = 10:01:57 AM 12/23/2007
DHCPLeaseObtained = 10:01:57 AM 12/22/2007
DHCPServer = 192.168.1.1 (PASSED)
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=1
Reply from 192.168.1.1: bytes=32 time=1ms TTL=1
Reply from 192.168.1.1: bytes=32 time=1ms TTL=1
Reply from 192.168.1.1: bytes=32 time=1ms TTL=1
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
DNSEnabledForWINSResolution = FALSE
DNSHostName = MINE
DNSServerSearchOrder = 192.168.1.1 (PASSED)
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time=1ms TTL=1
Reply from 192.168.1.1: bytes=32 time=1ms TTL=1
Reply from 192.168.1.1: bytes=32 time=1ms TTL=1
Reply from 192.168.1.1: bytes=32 time=1ms TTL=1
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
DomainDNSRegistrationEnabled = FALSE
FullDNSRegistrationEnabled = TRUE
GatewayCostMetric = 20
Index = 11
IPAddress = 192.168.1.2 (FAILED)
Pinging 192.168.1.2 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.2:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss)
IPConnectionMetric = 20
IPEnabled = TRUE
IPFilterSecurityEnabled = FALSE
IPSecPermitIPProtocols = 0
IPSecPermitTCPPorts = 0
IPSecPermitUDPPorts = 0
IPSubnet = 255.255.255.0
IPXEnabled = FALSE
MACAddress = 00:18:F3:28:79:29
ServiceName = NVENETFD
SettingID = {E8431F4D-3FFD-482B-A205-DC424641B4BB}
TcpipNetbiosOptions = 0
TcpMaxDataRetransmissions = 5
WINSEnableLMHostsLookup = TRUE

Asa you can see the adapter failed. This is being controlled by a Nvidia network controller. Could this be the problem as to not allowing the laptop to receive packets. If so what do I do to fix it??

Thanks

az240
 

Darth Llama

Rise Up Red Sea!
Joined
Dec 9, 2007
Posts
2,360
Reaction score
0
Location
Section 444 Row 4
I went through some of that, and don't really see anything too telling in that report..

Let me ask you this.. are you trying to connect to a WEP encrypted network? or is your wireless network open for anyone?

I had a similar problem connecting to my Linksys router using a wireless card. When I turned off the encryption, it connected fine. Turned out the problem was that the encryption gave me 4 keys to use to access the network but only key #1 appeared to be valid.

If you're using encryption, try turning it off and seeing if you can connect. If you're not using encryption, do you know if any other computers have been able to connect to the router?
 
Top