Computer wont acquire a network address

[TheoPetro]

I have a netgear WGR614v6 wireless router with one comp on wireless and 3 others hard wired. I was having zero problems with this computer before but I changed some stuff to make it a bit more secure because my fam wanted file/print sharing on.

Stuff I changed: I put all of the MAC addresses and the computer discriptions into the reserved IP list. I gave each comp a different IP address in the range that I set.

The computer that isnt working is . . .3 The ones that are working are . . .2 - . . .5

This computer worked fine untill I uninstalled McAfee anti virus and rebooted. I put kaspersky on allong with comodo firewall on each of the computers. I then tried to repair the connection (ipconfig /release then /renew) and on 3 of the computers it worked fine. On the last comp (IP . . .3) it kept telling me that it failed to acquire an address and windows gave it one. When I tried to do it in the cmd prompt I got the message that it cant connect to the DHCP server. The comp can not access the router

Things I tried:
In IP/TCP properties I set the comp to get an IP automatically and get a DNS automatically.

In WINS tab I set netBIOS to enable.

Tried restarting comp.

Tried giving it a static IP and still nothing.

Tried the repair program for winsocks and all of the above again and still nothing.

Tried the windows network setup wizzard and it tells me theres an error and to try it again.

EDIT: Thanks c3p0 for reminding me. I tried setting the firewall to allow all too and it still doesnt work.

Im a tad confused about this one. The NIC is integrated into the mobo and worked fine for ~ a year.

 

[c3p0]

Have you tried disabling the comodo firewall on the pc with the connection problem? Just an idea!!!

c3p0

 

[RebateMonger]

There's five things likely to cause this:

1) Physical connection to your router (cabling or router port failure).
2) Router has run out of IP addresses to assign.
3) NIC failure.
4) Firewall.
5) Windows TCP/IP stack damage.

You can troubleshoot the first by swapping cables and router ports.
Cause #2 is unlikely in your situation.
You can troubleshoot the third by installing a $10 PCI network card. It never hurts to have a spare.
You can troubleshoot the fourth by UNINSTALLING any software that has a firewall built in. Yeah, you can try disabling it, but uninstalling is "for sure".
It sounds like you've already tried to repair the TCP/IP stack.

 

[TheoPetro]

1) I already changed the port on the router the cable plugs into and the cable has been running perfectly untill I took down the old network and put this new one up.

2) It should only be assigning 4 IP addresses to the ones that are reserved in the router. I have it set to give out a range of 50 addresses (the max) with 4 reserved for the 4 comps on the network.

3) I have no empty PCI slots in the comp and the same with the cable I doubt it is this because it worked perfectly for ~1year untill I changed the network yesterday.

4) Ill give that a try.

5) Are there any other ways to repair the tcp/ip stack other than the winsocks app?

 

[JackMDS]

It is quite interesting how much of OP?s effort goes to describing the past and trying to fix thier system with the "Best" technical tool: ""It works for a year and now it is not working"".

The only way to "Fix" the trouble id to find out what is wrong and correct it.

If the WINSocket is corrupted, you need a Winsock application, since it is Not possible to repair it with a screwdriver.

 

[TheoPetro]

I have tried to fix the problem with a winsocks app and it hasnt worked. I have tried a bunch of things to fix it already and none of it is working so I figured I would come here and get some other ideas on what to try. If you have any actual advice to fix this I would appreciate it