Nforce Network Controller Issue with Windows 7? cannot connect to the internet
This is my first post here
I connect to the internet Via a Verxxx highspeed internet connection DSL I just installed Vindows 7 from a clean instal from vindows Wista Ultimate x64 my ethernet connection via the Nforce network controller built in my board worked just fine under Wista and after i installed Vindows sleven suddenly my network adapter wont connect to the internet I tried installing old vista 64 drivers after disabling driver enforcement and signing and I reinstalled Sleven drivers and even gave my network adapter my own made up mac address and my router either dosnt see my Nforce adapter or Vindows Sleven drivers will not point my Nic to the router which is an Actiontec gt704wg wireless gateway/router i reset the modem/ router to defaults went through the whole spill with Verizon and they said it was a Network card issue i.e. my Nforce adapter was bad , I called ASUS and went through their tech support they said it was a Vindows Sleven driver issue. Now I am not sure what to do but Device driver says NIC is working properly here are the IPCONFIG STATS WHICH LOOK VERY PECULUAR:

I am desperate to figure out , what is going on here so if anyone has any help please do so an RMA takes months and i dont have that kind of time......

Windows IP Configuration

Host Name . . . . . . . . . . . . : Joshua-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domain_not_set.invalid

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : domain_not_set.invalid
Description . . . . . . . . . . . : TE100-PCIWN 10/100Mbps PCI Adapter #2
Physical Address. . . . . . . . . : 00-14-D1-1A-29-C1
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::d4a4:ec53:3a4d:d6e2%23(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.64(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Sunday, November 08, 2009 10:39:41 AM
Lease Expires . . . . . . . . . . : Monday, November 09, 2009 10:39:41 AM
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 385881297
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-7F-29-F5-00-23-54-2C-37-54
DNS Servers . . . . . . . . . . . : 192.168.1.1
68.238.96.12
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce Networking Controller
Physical Address. . . . . . . . . : 00-23-54-2C-37-54
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::49fd:26db:df90:f890%17(Preferred)
Autoconfiguration IPv4 Address. . : 169.254.248.144(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : (theres nothing here which there should be) "weird"
DHCPv6 IAID . . . . . . . . . . . : 318776148
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-7F-29-F5-00-23-54-2C-37-54
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.domain_not_set.invalid:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : domain_not_set.invalid
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No "weird"
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No ?????????????????? "weird"
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:24fc:3286:b89f:b730(Preferred)
Link-local IPv6 Address . . . . . : fe80::24fc:3286:b89f:b730%13(Preferred)
Default Gateway . . . . . . . . . : :: (nothing here either)?????????????? "weird"
NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter isatap.{4449CD6F-8EDE-4636-9A03-F5A2FD61EC5E}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes




I have an ASUS M3NHT-Deluxe edition motherboard here are my specs:

Field Value

CPU Properties
CPU Type DualCore AMD Athlon 64 X2
CPU Alias Windsor
CPU Stepping JH-F3
Engineering Sample YES
CPUID CPU Name AMD Athlon(tm) 64 X2 Dual Core Processor 5600+
CPUID Revision ADA6500IAA6CZ CCBVF
CPU Speed
CPU Clock 3126.7 MHz (original: 2800 MHz, overclock: 12%)
CPU Multiplier 14x
CPU FSB 223.3 MHz (original: 200 MHz, overclock: 12%)
HyperTransport Clock 1116.7 MHz
Memory Bus 446.7 MHz
DRAM:FSB Ratio CPU/7

CPU Cache
L1 Code Cache 64 KB per core (Parity)
L1 Data Cache 64 KB per core (ECC)
L2 Cache 1 MB per core (On-Die, ECC, Full-Speed)

Motherboard Properties
Motherboard ID 07/16/2009-MCP72XE-M3N-HT-D-00
Motherboard Name Asus M3N-HT Deluxe (2 PCI, 1 PCI-E x1, 3 PCI-E x16, 4 DDR2 DIMM, Audio, Video, Gigabit LAN, IEEE-1394)

Chipset Properties
Motherboard Chipset nVIDIA nForce 780a SLI, AMD Hammer
Memory Timings 5-5-5-15 (CL-RCD-RP-RAS)
Command Rate (CR) 2T
DIMM1: Samsung M3 78T2863QZS-CF7 1 GB DDR2-800 DDR2 SDRAM (6-6-6-18 @ 400 MHz) (5-5-5-15 @ 333 MHz) (4-4-4-12 @ 266 MHz)
DIMM2: Samsung M3 78T2863QZS-CF7 1 GB DDR2-800 DDR2 SDRAM (6-6-6-18 @ 400 MHz) (5-5-5-15 @ 333 MHz) (4-4-4-12 @ 266 MHz)
DIMM3: Samsung M3 78T2863QZS-CF7 1 GB DDR2-800 DDR2 SDRAM (6-6-6-18 @ 400 MHz) (5-5-5-15 @ 333 MHz) (4-4-4-12 @ 266 MHz)
DIMM4: Samsung M3 78T2863QZS-CF7 1 GB DDR2-800 DDR2 SDRAM (5-5-5-18 @ 400 MHz) (4-4-4-12 @ 266 MHz) (3-3-3-9 @ 200 MHz)

BIOS Properties
System BIOS Date 07/16/09
Video BIOS Date 02/26/08
Award BIOS Type Phoenix - AwardBIOS v6.00PG
Award BIOS Message ASUS M3N-HT Deluxe ACPI BIOS Revision 2704
DMI BIOS Version ASUS M3N-HT Deluxe ACPI BIOS Revision 2704

Graphics Processor Properties

Video Adapter XFX GeForce 9600 GT 512MB
GPU Code Name G94GT (PCI Express 2.0 x16 10DE / 0622, Rev A1)
GPU Clock (Geometric Domain) 650 MHz (original: 650 MHz)
GPU Clock (Shader Domain) 1600 MHz (original: 1625 MHz)
Memory Clock 900 MHz (original: 900 MHz)


Field Value
Operating System Properties
OS Name Microsoft Windows 7 Ultimate
OS Language English (United States)
OS Kernel Type Multiprocessor Free (64-bit)
OS Version 6.1.7600
OS Service Pack -
OS Installation Date 11/1/2009
OS Root C:\Windows

License Information
Registered Owner xxxxxxxxxxxxxxxxxxxxxxx
Registered Organization
Product ID xxxxxxxxxxxxxxxxxxxxxxx
Product Key xxxxxxxxxxxxxxxxxxxxxxx
Product Activation (WPA) xxxxxxxxxxxxxxxxxxxxxxx
Current Session
Computer Name xxxxxxxxxx
User Name Joshua
Logon Domain xxxxxxxxxx
UpTime 5225 sec (0 days, 1 hours, 27 min, 5 sec)

Components Version
Common Controls 6.16
Internet Explorer 8.0.7600.16385
Windows Mail 6.1.7600.16385 (win7_rtm.090713-1255)
Windows Media Player 12.0.7600.16385 (win7_rtm.090713-1255)
Windows Messenger -
MSN Messenger 14.0.8089.0726
Internet Information Services (IIS) 7.5
.NET Framework 2.0.50727.4927 built by: NetFXspW7
Novell Client -
DirectX DirectX 10.1
OpenGL 6.1.7600.16385 (win7_rtm.090713-1255)
ASPI -

Operating System Features
Debug Version No
DBCS Version No
Domain Controller No
Security Present No
Network Present Yes
Remote Session No
Safe Mode No
Slow Processor No
Terminal Services Yes
This is my first post here

I connect to the internet Via a Verxxx highspeed internet connection DSL I just installed Vindows 7 from a clean instal from vindows Wista Ultimate x64 my ethernet connection via the Nforce network controller built in my board worked just fine under Wista and after i installed Vindows sleven suddenly my network adapter wont connect to the internet I tried installing old vista 64 drivers after disabling driver enforcement and signing and I reinstalled Sleven drivers and even gave my network adapter my own made up mac address and my router either dosnt see my Nforce adapter or Vindows Sleven drivers will not point my Nic to the router which is an Actiontec gt704wg wireless gateway/router i reset the modem/ router to defaults went through the whole spill with Verizon and they said it was a Network card issue i.e. my Nforce adapter was bad , I called ASUS and went through their tech support they said it was a Vindows Sleven driver issue. Now I am not sure what to do but Device driver says NIC is working properly here are the IPCONFIG STATS WHICH LOOK VERY PECULUAR:



I am desperate to figure out , what is going on here so if anyone has any help please do so an RMA takes months and i dont have that kind of time......



Windows IP Configuration



Host Name . . . . . . . . . . . . : Joshua-PC

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : domain_not_set.invalid



Ethernet adapter Local Area Connection:



Connection-specific DNS Suffix . : domain_not_set.invalid

Description . . . . . . . . . . . : TE100-PCIWN 10/100Mbps PCI Adapter #2

Physical Address. . . . . . . . . : 00-14-D1-1A-29-C1

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . : fe80::d4a4:ec53:3a4d:d6e2%23(Preferred)

IPv4 Address. . . . . . . . . . . : 192.168.1.64(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Lease Obtained. . . . . . . . . . : Sunday, November 08, 2009 10:39:41 AM

Lease Expires . . . . . . . . . . : Monday, November 09, 2009 10:39:41 AM

Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.1

DHCPv6 IAID . . . . . . . . . . . : 385881297

DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-7F-29-F5-00-23-54-2C-37-54

DNS Servers . . . . . . . . . . . : 192.168.1.1

68.238.96.12

NetBIOS over Tcpip. . . . . . . . : Enabled



Ethernet adapter Local Area Connection 2:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : NVIDIA nForce Networking Controller

Physical Address. . . . . . . . . : 00-23-54-2C-37-54

DHCP Enabled. . . . . . . . . . . : Yes

Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . : fe80::49fd:26db:df90:f890%17(Preferred)

Autoconfiguration IPv4 Address. . : 169.254.248.144(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.0.0

Default Gateway . . . . . . . . . : (theres nothing here which there should be) "weird"

DHCPv6 IAID . . . . . . . . . . . : 318776148

DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-7F-29-F5-00-23-54-2C-37-54

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS over Tcpip. . . . . . . . : Enabled



Tunnel adapter isatap.domain_not_set.invalid:



Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . : domain_not_set.invalid

Description . . . . . . . . . . . : Microsoft ISATAP Adapter

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No "weird"

Autoconfiguration Enabled . . . . : Yes



Tunnel adapter Teredo Tunneling Pseudo-Interface:



Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No ?????????????????? "weird"

Autoconfiguration Enabled . . . . : Yes

IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:24fc:3286:b89f:b730(Preferred)

Link-local IPv6 Address . . . . . : fe80::24fc:3286:b89f:b730%13(Preferred)

Default Gateway . . . . . . . . . : :: (nothing here either)?????????????? "weird"

NetBIOS over Tcpip. . . . . . . . : Disabled



Tunnel adapter isatap.{4449CD6F-8EDE-4636-9A03-F5A2FD61EC5E}:



Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes









I have an ASUS M3NHT-Deluxe edition motherboard here are my specs:



Field Value



CPU Properties

CPU Type DualCore AMD Athlon 64 X2

CPU Alias Windsor

CPU Stepping JH-F3

Engineering Sample YES

CPUID CPU Name AMD Athlon(tm) 64 X2 Dual Core Processor 5600+

CPUID Revision ADA6500IAA6CZ CCBVF

CPU Speed

CPU Clock 3126.7 MHz (original: 2800 MHz, overclock: 12%)

CPU Multiplier 14x

CPU FSB 223.3 MHz (original: 200 MHz, overclock: 12%)

HyperTransport Clock 1116.7 MHz

Memory Bus 446.7 MHz

DRAM:FSB Ratio CPU/7



CPU Cache

L1 Code Cache 64 KB per core (Parity)

L1 Data Cache 64 KB per core (ECC)

L2 Cache 1 MB per core (On-Die, ECC, Full-Speed)



Motherboard Properties

Motherboard ID 07/16/2009-MCP72XE-M3N-HT-D-00

Motherboard Name Asus M3N-HT Deluxe (2 PCI, 1 PCI-E x1, 3 PCI-E x16, 4 DDR2 DIMM, Audio, Video, Gigabit LAN, IEEE-1394)



Chipset Properties

Motherboard Chipset nVIDIA nForce 780a SLI, AMD Hammer

Memory Timings 5-5-5-15 (CL-RCD-RP-RAS)

Command Rate (CR) 2T

DIMM1: Samsung M3 78T2863QZS-CF7 1 GB DDR2-800 DDR2 SDRAM (6-6-6-18 @ 400 MHz) (5-5-5-15 @ 333 MHz) (4-4-4-12 @ 266 MHz)

DIMM2: Samsung M3 78T2863QZS-CF7 1 GB DDR2-800 DDR2 SDRAM (6-6-6-18 @ 400 MHz) (5-5-5-15 @ 333 MHz) (4-4-4-12 @ 266 MHz)

DIMM3: Samsung M3 78T2863QZS-CF7 1 GB DDR2-800 DDR2 SDRAM (6-6-6-18 @ 400 MHz) (5-5-5-15 @ 333 MHz) (4-4-4-12 @ 266 MHz)

DIMM4: Samsung M3 78T2863QZS-CF7 1 GB DDR2-800 DDR2 SDRAM (5-5-5-18 @ 400 MHz) (4-4-4-12 @ 266 MHz) (3-3-3-9 @ 200 MHz)



BIOS Properties

System BIOS Date 07/16/09

Video BIOS Date 02/26/08

Award BIOS Type Phoenix - AwardBIOS v6.00PG

Award BIOS Message ASUS M3N-HT Deluxe ACPI BIOS Revision 2704

DMI BIOS Version ASUS M3N-HT Deluxe ACPI BIOS Revision 2704



Graphics Processor Properties



Video Adapter XFX GeForce 9600 GT 512MB

GPU Code Name G94GT (PCI Express 2.0 x16 10DE / 0622, Rev A1)

GPU Clock (Geometric Domain) 650 MHz (original: 650 MHz)

GPU Clock (Shader Domain) 1600 MHz (original: 1625 MHz)

Memory Clock 900 MHz (original: 900 MHz)





Field Value

Operating System Properties

OS Name Microsoft Windows 7 Ultimate

OS Language English (United States)

OS Kernel Type Multiprocessor Free (64-bit)

OS Version 6.1.7600

OS Service Pack -

OS Installation Date 11/1/2009

OS Root C:\Windows



License Information

Registered Owner xxxxxxxxxxxxxxxxxxxxxxx

Registered Organization

Product ID xxxxxxxxxxxxxxxxxxxxxxx

Product Key xxxxxxxxxxxxxxxxxxxxxxx

Product Activation (WPA) xxxxxxxxxxxxxxxxxxxxxxx

Current Session

Computer Name xxxxxxxxxx

User Name Joshua

Logon Domain xxxxxxxxxx

UpTime 5225 sec (0 days, 1 hours, 27 min, 5 sec)



Components Version

Common Controls 6.16

Internet Explorer 8.0.7600.16385

Windows Mail 6.1.7600.16385 (win7_rtm.090713-1255)

Windows Media Player 12.0.7600.16385 (win7_rtm.090713-1255)

Windows Messenger -

MSN Messenger 14.0.8089.0726

Internet Information Services (IIS) 7.5

.NET Framework 2.0.50727.4927 built by: NetFXspW7

Novell Client -

DirectX DirectX 10.1

OpenGL 6.1.7600.16385 (win7_rtm.090713-1255)

ASPI -



Operating System Features

Debug Version No

DBCS Version No

Domain Controller No

Security Present No

Network Present Yes

Remote Session No

Safe Mode No

Slow Processor No

Terminal Services Yes

#1
Posted 11/08/2009 05:57 PM   
Well, that alot of stuff I know nothing about....

What Id like you to do is stop mickeying the Mac addies and default it.

[quote]Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1[/quote]

This is generally the DEFAULT for the router, which I would assume means it sees the router.

Check for FIREWALL software like Win 7's or something you installed.


But that DOMAIN NOT SET VALID looks odd to me.
Well, that alot of stuff I know nothing about....



What Id like you to do is stop mickeying the Mac addies and default it.



Default Gateway . . . . . . . . . : 192.168.1.1

DHCP Server . . . . . . . . . . . : 192.168.1.1




This is generally the DEFAULT for the router, which I would assume means it sees the router.



Check for FIREWALL software like Win 7's or something you installed.





But that DOMAIN NOT SET VALID looks odd to me.

My Opinion is no more important or right than yours. But if your using the LATEST drivers, go back to the prior set.

Piss Poor tech support blame all issues on drivers and assumes that your an idiot. Find a set that you know worked and see if the problem exists still.

""Don't f with it if it ain't broken!""

Constantly updating drivers is a good way to F'up the whole system.

#2
Posted 11/08/2009 09:43 PM   
[quote name='Greybear' post='947641' date='Nov 8 2009, 03:43 PM']Well, that alot of stuff I know nothing about....

What Id like you to do is stop mickeying the Mac addies and default it.



This is generally the DEFAULT for the router, which I would assume means it sees the router.

Check for FIREWALL software like Win 7's or something you installed.


But that DOMAIN NOT SET VALID looks odd to me.[/quote]


I have tried to set it to not assigned and it seems like the router cannot actually see my Nic card to properly assign the network address
[quote name='Greybear' post='947641' date='Nov 8 2009, 03:43 PM']Well, that alot of stuff I know nothing about....



What Id like you to do is stop mickeying the Mac addies and default it.







This is generally the DEFAULT for the router, which I would assume means it sees the router.



Check for FIREWALL software like Win 7's or something you installed.





But that DOMAIN NOT SET VALID looks odd to me.





I have tried to set it to not assigned and it seems like the router cannot actually see my Nic card to properly assign the network address

#3
Posted 11/09/2009 02:11 AM   
You should not need to change anything.

What happened to the NIC prior to installing the Nvidia Drivers? Did it work before that?
Roll it back.
You should not need to change anything.



What happened to the NIC prior to installing the Nvidia Drivers? Did it work before that?

Roll it back.

My Opinion is no more important or right than yours. But if your using the LATEST drivers, go back to the prior set.

Piss Poor tech support blame all issues on drivers and assumes that your an idiot. Find a set that you know worked and see if the problem exists still.

""Don't f with it if it ain't broken!""

Constantly updating drivers is a good way to F'up the whole system.

#4
Posted 11/09/2009 02:39 AM   
[quote name='Greybear' post='947749' date='Nov 8 2009, 08:39 PM']You should not need to change anything.

What happened to the NIC prior to installing the Nvidia Drivers? Did it work before that?
Roll it back.[/quote]


Absoloutly nothing has happened to the NIC just upgraded to Windows 7 its baffeling
[quote name='Greybear' post='947749' date='Nov 8 2009, 08:39 PM']You should not need to change anything.



What happened to the NIC prior to installing the Nvidia Drivers? Did it work before that?

Roll it back.





Absoloutly nothing has happened to the NIC just upgraded to Windows 7 its baffeling

#5
Posted 11/09/2009 09:53 AM   
What I meant was did you try the NIC or did you just turn around and install the latest drivers first?

Check the Windows Firewall is off also.
What I meant was did you try the NIC or did you just turn around and install the latest drivers first?



Check the Windows Firewall is off also.

My Opinion is no more important or right than yours. But if your using the LATEST drivers, go back to the prior set.

Piss Poor tech support blame all issues on drivers and assumes that your an idiot. Find a set that you know worked and see if the problem exists still.

""Don't f with it if it ain't broken!""

Constantly updating drivers is a good way to F'up the whole system.

#6
Posted 11/09/2009 01:05 PM   
I just thought I would share my recent experience.

I updated my machine this September with a 750i Motherboard which has the built in NIC. I was running XP and everything ran pretty well but, firefox was crashing a lot.
Then I got a free copy of Windows 7 ultimate at a conference in early October, put a brand new formatted drive in and ran the install, installed my apps.

Each time I restarted the machine, Windows 7 warned me that the was no connection to the Internet. The network diagram shwed a successful path the the router but, not beyond.
After some fiddling I found that if I disabled the network card, and then re-enabled it, the connection to the internet would succeed. This is with the latest 74.19 (I think) drivers. I never did find any other fix.. I played with auto-detect settings and just about anything else I could find both on the NIC and the router.

Meanwhile, Firefox was crashing nearly every 60 seconds on random pages, then succeed, then crash. I installed Chrome which never started once.

After 4 weeks of this I dug a little deeper into the Firefox crash logs and the ALL referred to[b] NVlsp.dll [/b](I think.. I'm not at my home machine now). Who does this dll belong to? NVidia onboard NIC of course.

So I hit the local PC store, bought a Neatgear GB NIC for 20 bucks, disabled the NVidia and: BING! no more firefix crashes, no more startup NIC failures.

So in my opinion[b] YES the NVidia NIC has serious issues[/b].. generally I blame the driver but I couldn't find a standalone driver to roll back to. I don't think it was limited to Windows 7, Firefox was crashing in XP as well on a completely different build.
20 bucks was well spent.
I just thought I would share my recent experience.



I updated my machine this September with a 750i Motherboard which has the built in NIC. I was running XP and everything ran pretty well but, firefox was crashing a lot.

Then I got a free copy of Windows 7 ultimate at a conference in early October, put a brand new formatted drive in and ran the install, installed my apps.



Each time I restarted the machine, Windows 7 warned me that the was no connection to the Internet. The network diagram shwed a successful path the the router but, not beyond.

After some fiddling I found that if I disabled the network card, and then re-enabled it, the connection to the internet would succeed. This is with the latest 74.19 (I think) drivers. I never did find any other fix.. I played with auto-detect settings and just about anything else I could find both on the NIC and the router.



Meanwhile, Firefox was crashing nearly every 60 seconds on random pages, then succeed, then crash. I installed Chrome which never started once.



After 4 weeks of this I dug a little deeper into the Firefox crash logs and the ALL referred to NVlsp.dll (I think.. I'm not at my home machine now). Who does this dll belong to? NVidia onboard NIC of course.



So I hit the local PC store, bought a Neatgear GB NIC for 20 bucks, disabled the NVidia and: BING! no more firefix crashes, no more startup NIC failures.



So in my opinion YES the NVidia NIC has serious issues.. generally I blame the driver but I couldn't find a standalone driver to roll back to. I don't think it was limited to Windows 7, Firefox was crashing in XP as well on a completely different build.

20 bucks was well spent.

#7
Posted 11/09/2009 02:25 PM   
[quote name='Denver_80203' post='947968' date='Nov 9 2009, 08:25 AM']I just thought I would share my recent experience.

I updated my machine this September with a 750i Motherboard which has the built in NIC. I was running XP and everything ran pretty well but, firefox was crashing a lot.
Then I got a free copy of Windows 7 ultimate at a conference in early October, put a brand new formatted drive in and ran the install, installed my apps.

Each time I restarted the machine, Windows 7 warned me that the was no connection to the Internet. The network diagram shwed a successful path the the router but, not beyond.
After some fiddling I found that if I disabled the network card, and then re-enabled it, the connection to the internet would succeed. This is with the latest 74.19 (I think) drivers. I never did find any other fix.. I played with auto-detect settings and just about anything else I could find both on the NIC and the router.

Meanwhile, Firefox was crashing nearly every 60 seconds on random pages, then succeed, then crash. I installed Chrome which never started once.

After 4 weeks of this I dug a little deeper into the Firefox crash logs and the ALL referred to[b] NVlsp.dll [/b](I think.. I'm not at my home machine now). Who does this dll belong to? NVidia onboard NIC of course.

So I hit the local PC store, bought a Neatgear GB NIC for 20 bucks, disabled the NVidia and: BING! no more firefix crashes, no more startup NIC failures.

So in my opinion[b] YES the NVidia NIC has serious issues[/b].. generally I blame the driver but I couldn't find a standalone driver to roll back to. I don't think it was limited to Windows 7, Firefox was crashing in XP as well on a completely different build.
20 bucks was well spent.[/quote]


I came to the same conclusion I bought a gigabit NIC card I just wanted to try to get my onboard card to work since i am running two video cards in SLI and I only have two PCI slots and its all a tight fit havng to put a card in either of the two PCI slots. Im going to call ASUS back today and try this all again......Hopefully with some luck I really think Nvidia should limit themselves to building Ghraphical Processors.....
[quote name='Denver_80203' post='947968' date='Nov 9 2009, 08:25 AM']I just thought I would share my recent experience.



I updated my machine this September with a 750i Motherboard which has the built in NIC. I was running XP and everything ran pretty well but, firefox was crashing a lot.

Then I got a free copy of Windows 7 ultimate at a conference in early October, put a brand new formatted drive in and ran the install, installed my apps.



Each time I restarted the machine, Windows 7 warned me that the was no connection to the Internet. The network diagram shwed a successful path the the router but, not beyond.

After some fiddling I found that if I disabled the network card, and then re-enabled it, the connection to the internet would succeed. This is with the latest 74.19 (I think) drivers. I never did find any other fix.. I played with auto-detect settings and just about anything else I could find both on the NIC and the router.



Meanwhile, Firefox was crashing nearly every 60 seconds on random pages, then succeed, then crash. I installed Chrome which never started once.



After 4 weeks of this I dug a little deeper into the Firefox crash logs and the ALL referred to NVlsp.dll (I think.. I'm not at my home machine now). Who does this dll belong to? NVidia onboard NIC of course.



So I hit the local PC store, bought a Neatgear GB NIC for 20 bucks, disabled the NVidia and: BING! no more firefix crashes, no more startup NIC failures.



So in my opinion YES the NVidia NIC has serious issues.. generally I blame the driver but I couldn't find a standalone driver to roll back to. I don't think it was limited to Windows 7, Firefox was crashing in XP as well on a completely different build.

20 bucks was well spent.





I came to the same conclusion I bought a gigabit NIC card I just wanted to try to get my onboard card to work since i am running two video cards in SLI and I only have two PCI slots and its all a tight fit havng to put a card in either of the two PCI slots. Im going to call ASUS back today and try this all again......Hopefully with some luck I really think Nvidia should limit themselves to building Ghraphical Processors.....

#8
Posted 11/09/2009 05:17 PM   
OK, Sorry to bump an old thread but I have the same issue and searching around the web there seems to be a major issue with the nForce Network Controller and Windows 7.

I have a Gigabyte GA-M57SLI-S4 board that has served me very well through Windows XP Pro and Windows Vista Ultimate. Never a problem at all. Now I have upgraded my PC to Windows 7 Ultimate suddenly I get network disconnects. It can always be successfully fixed by using the troubleshooter which resets the NIC but it only stays connected for a few minutes before disconnecting again. Like I said, It worked fine in WinXP and Vista but in Win7, no go.

Checked Gigabyte's website for fresh Win7 drivers but there's none available. Updated the BIOS but the problem remains. Posted a support request with Gigabyte support but so far I have had no reply. Looks like my trusty old WinXP Pro is going to make a comeback /blarg.gif' class='bbc_emoticon' alt=':/' />
OK, Sorry to bump an old thread but I have the same issue and searching around the web there seems to be a major issue with the nForce Network Controller and Windows 7.



I have a Gigabyte GA-M57SLI-S4 board that has served me very well through Windows XP Pro and Windows Vista Ultimate. Never a problem at all. Now I have upgraded my PC to Windows 7 Ultimate suddenly I get network disconnects. It can always be successfully fixed by using the troubleshooter which resets the NIC but it only stays connected for a few minutes before disconnecting again. Like I said, It worked fine in WinXP and Vista but in Win7, no go.



Checked Gigabyte's website for fresh Win7 drivers but there's none available. Updated the BIOS but the problem remains. Posted a support request with Gigabyte support but so far I have had no reply. Looks like my trusty old WinXP Pro is going to make a comeback /blarg.gif' class='bbc_emoticon' alt=':/' />

#9
Posted 04/14/2010 12:50 AM   
HI Hope this reply finds you all well .

I had similar problem with Windows 7 and the Nic’s on the 680i Striker extreme, That is frequent drop outs and disconnections
The fix /Work around I found that cure4ed my problem was to disable Receive Side scaling on the network adaptor Though I can’t say for sure it will cure your problem.

To disable Receive Side scaling: Click Start, type ‘Device Manager’ (no quotes) into Search programs and files and click the ‘Device Manager’ entry. Expand Network adapters and right click the adapter entry and choose properties.

From the Advance tab Locate Receive Side scaling property and select Disabled from the value field for that property. Click ok to close the Properties dialogue.

As I said I can’t be sure if this with work for your MB but it may.

Tony
HI Hope this reply finds you all well .



I had similar problem with Windows 7 and the Nic’s on the 680i Striker extreme, That is frequent drop outs and disconnections

The fix /Work around I found that cure4ed my problem was to disable Receive Side scaling on the network adaptor Though I can’t say for sure it will cure your problem.



To disable Receive Side scaling: Click Start, type ‘Device Manager’ (no quotes) into Search programs and files and click the ‘Device Manager’ entry. Expand Network adapters and right click the adapter entry and choose properties.



From the Advance tab Locate Receive Side scaling property and select Disabled from the value field for that property. Click ok to close the Properties dialogue.



As I said I can’t be sure if this with work for your MB but it may.



Tony

#10
Posted 04/14/2010 07:45 PM   
Scroll To Top