no ethernet connection via router nor cable modem

Greetings. Like a number of people have posted, I have the same problem of being unable to get a network connection when my nForce4 Asus A8N-E's integrated nic is connected to my Netgear WGT624 router. Knowing about the SPI issues (though mine's disabled, which people say hasn't always made a difference) and since I've not yet updated the firmware in desperation, I decided to bypass it and connect directly via my Comcast Thomson/RCA cable modem. As most people have been connecting fine via direct modem hookups, I figured it'd work fine, but nope. I get the same limited connection messages and inability to hit the internet at all like with the router. I couldn't even log into the router itself when it was connected, and my XP laptop confirmed via a wireless login that the router didn't see the Vista box as a connected device. The PPPoE option for building a new broadband connection is useless for me as I should just be fine with DHCP as in my XP Pro dual-boot. I'll be trying k600r's suggestion of diabling protected mode under internet, intranet, and trusted sites when I return home this evening, but since most people aren't having these issues with a direct-to-cablemodem connection, is there anything else I should attempt aside from this, disabling IPv6 & network seeking options, and perhaps entering the DNS info manually? I've already done an orderly shutdown and restart of the modem, router, and attached devices before. Thanks for any input. Hopefully some patches will be out soon to fix these TCP/IP stack issues.

I have the same router and nVidia LAN nForce4 Board. Had to go into the LAN controller properties and manually set the IP, SubNet and domain. You will need to ente 192.168.1.25 for the IP (or any # that isn't being used), the SubNet Mask of your router and the IP address of your router (Domain) probably 192.168.1.1
Good Luck
"cdburrus" wrote:

Greetings. Like a number of people have posted, I have the same problem of being unable to get a network connection when my nForce4 Asus A8N-E's integrated nic is connected to my Netgear WGT624 router. Knowing about the SPI issues (though mine's disabled, which people say hasn't always made a difference) and since I've not yet updated the firmware in desperation, I decided to bypass it and connect directly via my Comcast Thomson/RCA cable modem. As most people have been connecting fine via direct modem hookups, I figured it'd work fine, but nope. I get the same limited connection messages and inability to hit the internet at all like with the router. I couldn't even log into the router itself when it was connected, and my XP laptop confirmed via a wireless login that the router didn't see the Vista box as a connected device. The PPPoE option for building a new broadband connection is useless for me as I should just be fine with DHCP as in my XP Pro dual-boot. I'll be trying k600r's suggestion of diabling protected mode under internet, intranet, and trusted sites when I return home this evening, but since most people aren't having these issues with a direct-to-cablemodem connection, is there anything else I should attempt aside from this, disabling IPv6 & network seeking options, and perhaps entering the DNS info manually? I've already done an orderly shutdown and restart of the modem, router, and attached devices before. Thanks for any input. Hopefully some patches will be out soon to fix these TCP/IP stack issues.

Thanks a lot, jbiel, that did it. I'd seen your earlier posts and jotted that option down too, but wanted to cover all my bases, just in case. Thanks again. :)
"jbiel" wrote:

I have the same router and nVidia LAN nForce4 Board. Had to go into the LAN controller properties and manually set the IP, SubNet and domain. You will need to ente 192.168.1.25 for the IP (or any # that isn't being used), the SubNet Mask of your router and the IP address of your router (Domain) probably 192.168.1.1
Good Luck
"cdburrus" wrote:
Greetings. Like a number of people have posted, I have the same problem of being unable to get a network connection when my nForce4 Asus A8N-E's integrated nic is connected to my Netgear WGT624 router. Knowing about the SPI issues (though mine's disabled, which people say hasn't always made a difference) and since I've not yet updated the firmware in desperation, I decided to bypass it and connect directly via my Comcast Thomson/RCA cable modem. As most people have been connecting fine via direct modem hookups, I figured it'd work fine, but nope. I get the same limited connection messages and inability to hit the internet at all like with the router. I couldn't even log into the router itself when it was connected, and my XP laptop confirmed via a wireless login that the router didn't see the Vista box as a connected device. The PPPoE option for building a new broadband connection is useless for me as I should just be fine with DHCP as in my XP Pro dual-boot. I'll be trying k600r's suggestion of diabling protected mode under internet, intranet, and trusted sites when I return home this evening, but since most people aren't having these issues with a direct-to-cablemodem connection, is there anything else I should attempt aside from this, disabling IPv6 & network seeking options, and perhaps entering the DNS info manually? I've already done an orderly shutdown and restart of the modem, router, and attached devices before. Thanks for any input. Hopefully some patches will be out soon to fix these TCP/IP stack issues.

Hi -- same router, same problem! But I can't figure out where I enter the IP info, etc.. below. I went into the new-look network section, I think I ound a place to worl on LAN settings (it was called Local Network 5), but kept getting the feedback that my info -- the info below, and right for my router -- was invalid. SOOOOO frustrating. jbiel, or anyone, can would you mind giving me a bit of advice?
"jbiel" wrote:

I have the same router and nVidia LAN nForce4 Board. Had to go into the LAN controller properties and manually set the IP, SubNet and domain. You will need to ente 192.168.1.25 for the IP (or any # that isn't being used), the SubNet Mask of your router and the IP address of your router (Domain) probably 192.168.1.1
Good Luck
"cdburrus" wrote:
Greetings. Like a number of people have posted, I have the same problem of being unable to get a network connection when my nForce4 Asus A8N-E's integrated nic is connected to my Netgear WGT624 router. Knowing about the SPI issues (though mine's disabled, which people say hasn't always made a difference) and since I've not yet updated the firmware in desperation, I decided to bypass it and connect directly via my Comcast Thomson/RCA cable modem. As most people have been connecting fine via direct modem hookups, I figured it'd work fine, but nope. I get the same limited connection messages and inability to hit the internet at all like with the router. I couldn't even log into the router itself when it was connected, and my XP laptop confirmed via a wireless login that the router didn't see the Vista box as a connected device. The PPPoE option for building a new broadband connection is useless for me as I should just be fine with DHCP as in my XP Pro dual-boot. I'll be trying k600r's suggestion of diabling protected mode under internet, intranet, and trusted sites when I return home this evening, but since most people aren't having these issues with a direct-to-cablemodem connection, is there anything else I should attempt aside from this, disabling IPv6 & network seeking options, and perhaps entering the DNS info manually? I've already done an orderly shutdown and restart of the modem, router, and attached devices before. Thanks for any input. Hopefully some patches will be out soon to fix these TCP/IP stack issues.

Hi. Same router, same problem. Where do I enter the info below? I tried the new-look network center, couldn't find specific LAN setting (JUST LOCALNETOWK 5) but tried to enter the IP, etc. below but was told it's invalid. ANyone -- Help?
"jbiel" wrote:

I have the same router and nVidia LAN nForce4 Board. Had to go into the LAN controller properties and manually set the IP, SubNet and domain. You will need to ente 192.168.1.25 for the IP (or any # that isn't being used), the SubNet Mask of your router and the IP address of your router (Domain) probably 192.168.1.1
Good Luck
"cdburrus" wrote:
Greetings. Like a number of people have posted, I have the same problem of being unable to get a network connection when my nForce4 Asus A8N-E's integrated nic is connected to my Netgear WGT624 router. Knowing about the SPI issues (though mine's disabled, which people say hasn't always made a difference) and since I've not yet updated the firmware in desperation, I decided to bypass it and connect directly via my Comcast Thomson/RCA cable modem. As most people have been connecting fine via direct modem hookups, I figured it'd work fine, but nope. I get the same limited connection messages and inability to hit the internet at all like with the router. I couldn't even log into the router itself when it was connected, and my XP laptop confirmed via a wireless login that the router didn't see the Vista box as a connected device. The PPPoE option for building a new broadband connection is useless for me as I should just be fine with DHCP as in my XP Pro dual-boot. I'll be trying k600r's suggestion of diabling protected mode under internet, intranet, and trusted sites when I return home this evening, but since most people aren't having these issues with a direct-to-cablemodem connection, is there anything else I should attempt aside from this, disabling IPv6 & network seeking options, and perhaps entering the DNS info manually? I've already done an orderly shutdown and restart of the modem, router, and attached devices before. Thanks for any input. Hopefully some patches will be out soon to fix these TCP/IP stack issues.

Hi. Same router, same problem. Where do I enter the info below? I tried the new-look network center, couldn't find specific LAN setting but tried to enter the IP, etc. below but was told it's invalid. ANyone -- Help?
"cdburrus" wrote:

Thanks a lot, jbiel, that did it. I'd seen your earlier posts and jotted that option down too, but wanted to cover all my bases, just in case. Thanks again. :)
"jbiel" wrote:
I have the same router and nVidia LAN nForce4 Board. Had to go into the LAN controller properties and manually set the IP, SubNet and domain. You will need to ente 192.168.1.25 for the IP (or any # that isn't being used), the SubNet Mask of your router and the IP address of your router (Domain) probably 192.168.1.1
Good Luck
"cdburrus" wrote:
Greetings. Like a number of people have posted, I have the same problem of being unable to get a network connection when my nForce4 Asus A8N-E's integrated nic is connected to my Netgear WGT624 router. Knowing about the SPI issues (though mine's disabled, which people say hasn't always made a difference) and since I've not yet updated the firmware in desperation, I decided to bypass it and connect directly via my Comcast Thomson/RCA cable modem. As most people have been connecting fine via direct modem hookups, I figured it'd work fine, but nope. I get the same limited connection messages and inability to hit the internet at all like with the router. I couldn't even log into the router itself when it was connected, and my XP laptop confirmed via a wireless login that the router didn't see the Vista box as a connected device. The PPPoE option for building a new broadband connection is useless for me as I should just be fine with DHCP as in my XP Pro dual-boot. I'll be trying k600r's suggestion of diabling protected mode under internet, intranet, and trusted sites when I return home this evening, but since most people aren't having these issues with a direct-to-cablemodem connection, is there anything else I should attempt aside from this, disabling IPv6 & network seeking options, and perhaps entering the DNS info manually? I've already done an orderly shutdown and restart of the modem, router, and attached devices before. Thanks for any input. Hopefully some patches will be out soon to fix these TCP/IP stack issues.

Thanks jbiel. I was having the same problem, came here and did a search on "DHCP" and found this post. I still can't understand why I can't get the DHCP client in Vista to work properly. The autoconfig address in the network properties is something bizarre and it refuses to take a DHCP assignment from my router (D-Link 808HV). I set the IP address manually, along with the SubNet and domain (the router's address), and now I can connect to my network. However, I still can't get to the internet. Of course, this all works fine when I boot this machine into XP Pro. I know there is some little setting I'm missing.
Anyone have any ideas?
Thanks!
"jbiel" wrote:

I have the same router and nVidia LAN nForce4 Board. Had to go into the LAN controller properties and manually set the IP, SubNet and domain. You will need to ente 192.168.1.25 for the IP (or any # that isn't being used), the SubNet Mask of your router and the IP address of your router (Domain) probably 192.168.1.1
Good Luck
"cdburrus" wrote:
Greetings. Like a number of people have posted, I have the same problem of being unable to get a network connection when my nForce4 Asus A8N-E's integrated nic is connected to my Netgear WGT624 router. Knowing about the SPI issues (though mine's disabled, which people say hasn't always made a difference) and since I've not yet updated the firmware in desperation, I decided to bypass it and connect directly via my Comcast Thomson/RCA cable modem. As most people have been connecting fine via direct modem hookups, I figured it'd work fine, but nope. I get the same limited connection messages and inability to hit the internet at all like with the router. I couldn't even log into the router itself when it was connected, and my XP laptop confirmed via a wireless login that the router didn't see the Vista box as a connected device. The PPPoE option for building a new broadband connection is useless for me as I should just be fine with DHCP as in my XP Pro dual-boot. I'll be trying k600r's suggestion of diabling protected mode under internet, intranet, and trusted sites when I return home this evening, but since most people aren't having these issues with a direct-to-cablemodem connection, is there anything else I should attempt aside from this, disabling IPv6 & network seeking options, and perhaps entering the DNS info manually? I've already done an orderly shutdown and restart of the modem, router, and attached devices before. Thanks for any input. Hopefully some patches will be out soon to fix these TCP/IP stack issues.