![]() |
![]() |
![]() |
|||||
![]() |
![]() |
![]() |
![]() |
![]() |
|||
| Welcome
to Tech Support Forum home to more then 136,000 problems solved. Issues
have included: Spyware, Malware, Virus Issues, Windows, Microsoft,
Linux, Networking, Security, Hardware, and Gaming Getting your
problem solved is as easy as: 1. Registering for a free account 2. Asking your question 3. Receiving an answer Registered members: * See fewer ads. * And much more..
|
| Want to know how to post a question? click here | Having problems with spyware and pop-ups? First Steps |
|
|||||||
| Cabling and Network Cards cable and nic support forum; D-Link, Netgear, Linksys, Cisco, Sun |
![]() |
|
|
LinkBack | Thread Tools |
|
|
#1 (permalink) |
|
Registered User
|
Nvidia Networking Controller shows Connected but will not receive packets.
Hello All,
I am sorry if there is already a solution to this out there but I have been searching and can not find a post that matches my symptoms. I recently put my new PC together and everything is working fine... That is of course with the exception of my Ethernet connection which is controlled by an Gigabyte NVIDIA Network controller. This is an onboard network controller on my Foxconn-M7PMX-S motherboard. When I connect the ethernet cable to the port, the status goes from aquiring network address, to limited/no connectivity then a second later it flashes up with Connected. During the Aquiring and limited stages there is no ip address listed when I run ipconfig. However when I run ipconfig after it says connected I have a valid ip. The connection doesn't work however as it sends data but never receives any packets back. The status of the ethernet port has never shown 1 packet received. Following a couple of threads I have tried changing the TCP/IP settings to give static address variables but this did not fix. I have tried taking it of Full Autonegotiation and tried some of the slower settings - no fix. Motherboard: Foxconn M7PMX-S / Processor: Intel Pentium Dual CPU E2200 @2.20GHz / RAM: 2GB I am able to connect to the internet using my Wireless card and also using a USB connection to my router. I have also used the same ethernet cable in my laptop and it connnects up fine so it is not the cable or the connection to the router? Can you help? |
|
|
|
| Important Information |
|
Join the #1 Tech Support Forum Today - It's Totally Free!
TechSupportForum.com is a leading support website for your computer needs. We offer free, friendly and personalized computer support. Why pay to have your computer fixed when you can do it for free. Join TechSupportforum.com Today - Click Here |
|
|
#2 (permalink) |
|
Registered User
|
Re: Nvidia Networking Controller shows Connected but will not receive packets.
I have carried on reading some other posts and found some information that might be required:
------------------------------------------------------------------------ Check your Services are Started on all PCs: Computer Browser DHCP Client DNS Client Network Connections Network Location Awareness Remote Procedure Call (RPC) Server TCP/IP Netbios helper Workstation ----------------------------------------------------------------------- These are all enabled/started ----------------------------------------------------------------------- TCP/IP stack repair options for use with Windows XP with SP2/SP3. Start, Run, CMD to open a command prompt: In the command prompt window that opens, type type the following commands: Note: Type only the text in bold for the following commands. Reset TCP/IP stack to installation defaults, type: netsh int ip reset reset.log Reset WINSOCK entries to installation defaults, type: netsh winsock reset catalog Reboot the machine. ----------------------------------------------------------------------- I have run this but it has not solved my issue. ----------------------------------------------------------------------- Try these simple tests. Hold the Windows key and press R, then type CMD (COMMAND for W98/WME) to open a command prompt: In the command prompt window that opens, type type the following commands one at a time, followed by the Enter key: IPCONFIG PING <computer_IP_address> PING <default_gateway_address> PING 206.190.60.37 PING yahoo.com Right click in the command window and choose Select All, then hit Enter. Paste the results in a message here. ---------------------------------------------------------------------- C:\Documents and Settings\Aidan>ipconfig Windows IP Configuration Ethernet adapter Local Area Connection 5: Connection-specific DNS Suffix . : home IP Address. . . . . . . . . . . . : 192.168.1.65 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.254 C:\Documents and Settings\Aidan>ping 192.168.1.65 Pinging 192.168.1.65 with 32 bytes of data: Reply from 192.168.1.65: bytes=32 time<1ms TTL=128 Reply from 192.168.1.65: bytes=32 time<1ms TTL=128 Reply from 192.168.1.65: bytes=32 time<1ms TTL=128 Reply from 192.168.1.65: bytes=32 time<1ms TTL=128 Ping statistics for 192.168.1.65: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\Documents and Settings\Aidan>ping 192.168.1.254 Pinging 192.168.1.254 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 192.168.1.254: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\Documents and Settings\Aidan>ping 206.190.60.37 Pinging 206.190.60.37 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 206.190.60.37: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\Documents and Settings\Aidan>ping yahoo.com Ping request could not find host yahoo.com. Please check the name and try again. |
|
|
|
|
|
#3 (permalink) |
|
Manager, Networking Forums
Join Date: Sep 2002
Location: S.E. Pennsylvania, US
Posts: 41,623
OS: Windows 7, XP-Pro, Vista, Linux
Blog Entries: 1
|
Re: Nvidia Networking Controller shows Connected but will not receive packets.
With the cable connected, let's see this.
Hold the Windows key and press R, then type CMD to open a command prompt: In the command prompt window that opens, type type the following command: Note that there is a space before the /ALL, but there is NOT a space after the / in the following command. IPCONFIG /ALL Right click in the command window and choose Select All, then hit Enter. Paste the results in a message here. If you are on a machine with no network connection, use a floppy, USB disk, or a CD-RW disk to transfer a text file with the information to allow pasting it here.
__________________
If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience |
|
|
|
|
|
#4 (permalink) |
|
Registered User
|
Re: Nvidia Networking Controller shows Connected but will not receive packets.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Aidan>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : aidans Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : home Ethernet adapter Local Area Connection 5: Connection-specific DNS Suffix . : home Description . . . . . . . . . . . : NVIDIA nForce Networking Controller Physical Address. . . . . . . . . : 67-5E-66-5F-66-55 Dhcp Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes IP Address. . . . . . . . . . . . : 192.168.1.65 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.254 DHCP Server . . . . . . . . . . . : 192.168.1.254 DNS Servers . . . . . . . . . . . : 192.168.1.254 Lease Obtained. . . . . . . . . . : 22 October 2008 14:25:52 Lease Expires . . . . . . . . . . : 23 October 2008 14:25:52 C:\Documents and Settings\Aidan> |
|
|
|
|
|
#8 (permalink) |
|
Manager, Networking Forums
Join Date: Sep 2002
Location: S.E. Pennsylvania, US
Posts: 41,623
OS: Windows 7, XP-Pro, Vista, Linux
Blog Entries: 1
|
Re: Nvidia Networking Controller shows Connected but will not receive packets.
If you still can't ping the 192.168.1.254 address, I'm thinking it's a firewall configuration issue. There's no reason you should not be able to ping the default gateway. Disable ALL firewalls and see if that helps.
__________________
If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience |
|
|
|
|
|
#9 (permalink) |
|
Registered User
|
Re: Nvidia Networking Controller shows Connected but will not receive packets.
Ok, I have tried the reboot attempt, switching off my router and my computer for over 5 mins. Same issue on start up. Connection goes to limited connectivity and then a second later says connected 100mbs, IP address is then configured but still no received packets and am unable to ping default gateway.
Rebooted again and then tried with norton firewall disabled. Same results. Its worth mentioning that I tried this connection before even installing Norton Internet security 2009 and it didn't work before installing the firewall. Any more thoughts would be greatly appreciated?
|
|
|
|
|
|
#13 (permalink) |
|
Manager, Networking Forums
Join Date: Sep 2002
Location: S.E. Pennsylvania, US
Posts: 41,623
OS: Windows 7, XP-Pro, Vista, Linux
Blog Entries: 1
|
Re: Nvidia Networking Controller shows Connected but will not receive packets.
This almost has to be a firewall. Try booting in Safe Mode with Networking, see if you can ping the default gateway in that mode.
__________________
If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience |
|
|
|
|
|
#14 (permalink) |
|
Registered User
|
Re: Nvidia Networking Controller shows Connected but will not receive packets.
Thanks for the response John,
Unfortunately I found the same results. Boot up in Safe Mode with Networking Enabled the NVIDIA network controller. Aquiring network address... then connected. Ipconfig shows the computer has been configured with IP, Subnet and Default gateway. There is still no packets being received and when I try to ping the default gateway it just gets: Request timed out. Request timed out. Request timed out. Request timed out. I know this is a tough one but if you have any more thoughts or tests I could do it would be appreciated? |
|
|
|
|
|
#15 (permalink) |
|
Manager, Networking Forums
Join Date: Sep 2002
Location: S.E. Pennsylvania, US
Posts: 41,623
OS: Windows 7, XP-Pro, Vista, Linux
Blog Entries: 1
|
Re: Nvidia Networking Controller shows Connected but will not receive packets.
I'd have to test the machine in a different environment at this point.
What happens if you type 192.168.1.254 into the address bar of IE and hit Enter?
__________________
If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience |
|
|
|
|
|
#17 (permalink) |
|
Manager, Networking Forums
Join Date: Sep 2002
Location: S.E. Pennsylvania, US
Posts: 41,623
OS: Windows 7, XP-Pro, Vista, Linux
Blog Entries: 1
|
Re: Nvidia Networking Controller shows Connected but will not receive packets.
Well, this makes very little sense, but it appears that the router is doing something very odd.
I'd test the machine elsewhere and see if you can pin it down. You could also bring in another machine to test in this environment and see how it reacts.
__________________
If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience |
|
|
|
|
|
#18 (permalink) |
|
Registered User
|
Re: Nvidia Networking Controller shows Connected but will not receive packets.
Its not the router that has the issue. When I take that ethernet cable out of the PC and put it into my Laptop the laptop works fine.
Are all my settings correct? Flow Control=Disable Low Power State Link Speed=Disable Network Address=Not Present Optimize for= CPU Reset PHY if not in use=Disable Speed/Duplex Settings=Full Autonegotiation VLAN & Priority=Disable VLAN&Priority VLAN id=1 Wake on Magic Packet=Enable Wake on Pattern= Enable WakeOnLAN from PowerOff=Disable Last edited by Leo_5878; 10-27-2008 at 10:22 AM. |
|
|
|
|
|
#19 (permalink) |
|
Manager, Networking Forums
Join Date: Sep 2002
Location: S.E. Pennsylvania, US
Posts: 41,623
OS: Windows 7, XP-Pro, Vista, Linux
Blog Entries: 1
|
Re: Nvidia Networking Controller shows Connected but will not receive packets.
There is no reason in the world you should have to tinker with those settings.
Normally, I see Flow Control enabled, the others look fine.
__________________
If TSF has helped you, Tell us about it! or Donate to help keep the site up! Microsoft MVP - Windows Desktop Experience |
|
|
|
|
|
#20 (permalink) |
|
Registered User
|
Re: Nvidia Networking Controller shows Connected but will not receive packets.
Same issues with Flow Control Enabled:
tried ipconfig /renew: Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\Aidan>ipconfig Windows IP Configuration Ethernet adapter Local Area Connection 5: Connection-specific DNS Suffix . : home IP Address. . . . . . . . . . . . : 192.168.1.67 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.254 C:\Documents and Settings\Aidan>ipconfig /renew Windows IP Configuration An error occurred while renewing interface Local Area Connection 5 : unable to c ontact your DHCP server. Request has timed out. C:\Documents and Settings\Aidan> |
|
|
|
![]() |
| Thread Tools | |
|
|