OK. You have a number of problems. First issue is you put the wrong addresses in the first problem pc. The working one has 192.168.1.1 for gateway yet the nonworking one has 192.168.0.1 You need to re-enter the correct ips into the nonworking workstation or BETTER yet set to obtain ip automatically [ so dhcp is set to yes] Now in the second ipconfig post these entries are not correct. Node Type . . . . . . . . . . . . : Broadcast IP Routing Enabled. . . . . . . . : Yes WINS Proxy Enabled. . . . . . . . : Yes They should say something like this Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No I am assuming you have all of these connecting to a router which is at 192.168.1.1

0

Once again, thank you for helping me with this. Well, the working PC is connecting to the internet via a wireless connection, while my older desktop PC (the non-working one) is connected via a NETGEAR router. Do you need the IP config of the host computer or anything? Because unfortunately my desktop is the only one connected this way not using a wireless connection. I'll try changing what you suggested. [edit] I changed the gateway number to what you suggested. However, a bubble recently popped up notifying that 'Local Area Connection 4' has little or no connectivity. You might not be able to access the internet or some network resources etc. etc. [edit II] After doing some searching, it seems I have the sme problem as this person here: http://www.computing.net/answers/ne... Including the problem with renewing and releasing ipconfig. I tried disabling my firewall as well. Any suggestions?

0

Please? Is there anyone left that would be wiling to help me with this? It's been over a week! Or am I just too impatient?

0

Wait so...on the problem computer - the internet does work SOMETIMES, but randomly drops - or it never works?? And regarding the other post - have you seen the IP address change to the 169.254.xx.xx address?? Also - you've said the wireless computers work ok, but the wired computer on the netgear router does not - are there any OTHER computers connected to the NETGEAR that have this problem? (Or any other computers connected to the netgear AT ALL?) You should try setting the static IP on the problem computer to something in the 192.168.0 subnet, like 192.168.0.2 w/ gateway: 192.168.0.1, nameservers: 4.2.2.1 and 4.2.2.2 - do not use the 'obtain IP address automatically' setting.... see if that fixes the drops... my guess is - you have two DHCP servers, the one on the wireless router, and one on the netgear. When your wired computer requests an address, a 'race-condition' happens - DHCP broadcasts to everybody - when the netgear is first to respond, your internet works as you have a correct IP in the 0 subnet, but when the wireless router 'wins the race', you get an IP in the 192.168.1 network, which your netgear might not be routing...your other computers don't see the problem because they're getting their address via the wireless interface & not being forwarded to the netgear...so try hard setting the address & don't let it auto configure... of course, in that scenario - all the computers connected to the netgear w/ DHCP would have that problem...so do they? Sorry about the long post, try to answer the first 3 questions and post back.

0

Thank you for the reply, by the way. The internet had been functioning fine for about the last one & a half years on the problem computer. And one day, it just randomly dropped, and since then there is yet to be an internet connection on it. Yes, the problem computer has a 169.254 etc. as the IP addess and default gateway. The problem computer is the only one set up via a NETGEAR router, the rest either have direct access to the ISP or are connected via wireless access that was built into the machine. (The three laptops not connected to the NETGEAR router work flawlessly on wireless.) I changed the IP's and such to what you suggested. The "!" triangle icon over the connection has dissapeared, but there still isn't internet. Thank you for such an in-depth description....and how might I go about hard setting the address? Forgive this computer - illiterate poster. Nope, as the problem computer is the only one set up VIA a NETGEAR router.

0

Well, the working PC is connecting to the internet via a wireless connection, while my older desktop PC (the non-working one) is connected via a NETGEAR router. Is the wireless router the same Netgear router, or is it a different router altogether? If they're separate router's, what does the router that has the PC that isn't working plug into for internet?

0

The wireless connection and the one that should be sent to my desktop are both broadcast by the same router. It's sending out a wireless connection fine to the PCs that have the thing to receive it built in, while my desktop pc doesn't have this. Does that make sense? Haha.

0

Well, if you see a 169.254 address, that kind of invalidates my theory...169.254 means your computer was never able to reach the router - it normally indicates a problem from Layer2 downwards (so, NIC drivers, cabling, or the router itself) Can you try to verify connectivity here, from your problem computer, give it the 192.168.0.2 address, as I'd mentioned earlier, then from a Command Prompt window (CMD), try this: ping 192.168.0.1 Do you get a REPLY FROM 192.168.0.1? If so, then it's reaching the netgear Next try: ping 192.168.1.1 Do you get a REPLY? If so, you're reaching the wireless modem (Everything should work if you can get this step working) Lastly - how is your network physically wired exactly? Where is the Uplink to the internet? I assume it's something like: [wired computer]---[netgear]---[wireless router]---[cable modem]---(INTERNET) is that right? Also on the netgear - is the uplink (to the wireless) connected via the LAN or the WAN port?? (Try moving it to the LAN port) Try to post back w/ the answers to the above - if you can't reach 192.168.0.1 from your problem computer, then it's Layer 2 or 1 related from the host to the netgear (check the link lights on the netgear, try a differnet computer on the netgear, replace the cabling, reinstall your drivers, replace the nic, replace the netgear router) But, if you can HIT 192.168.0.1, but not 192.168.1.1, then the problem lies between the netgear and the wireless router link.

0

After pinging 192.168.0.1, and the request timed out four times with 100% loss. I also tried pinging 192.168.1.1, and the request timed out 4 times with a 100% loss. Basically, the same thing. The setup you described is correct. Unfortunatly, I don't know whether it's connected via a LAN or WAN port. I also tried reinstalling the drivers, still nothing. I recently plugged in a wireless connector also, into the problem computer. I regained internet access for abut a minute before it disappeared again. If that helps.

0

Hello, thanks to everyone that tried to help me resolve this problem. I really appreciate your time and knowledge. I recently bought a wireless connection card thing, and I now have access to the internet. 8] (Basically gave up on the NETGEAR thing, haha.) Once again, thank you everyone. If I had the money, I would pay you with a million dollars. :)

0