Early Tues. AM, a machine this pc that was functioning fine on the network stopped seeing the network. I ran ipconfig /all and found that the ip address and subnet mask information had gone back to the default ip address (169.254.0.0 & 255.255.0.0). We are using DHCP thru our 2003 server, so I am trying to figure out why the nic won't pick up the dhcp lease information from the server. I have deleted the lease info that was on dhcp for this pc and I have uninstalled and reinstalled the network card. I am new to working with Dhcp so I am not sure if there is something I should be doing on the server to try and get the nic to pick the information back up. Anyone have any ideas?

have u tried the .. flushdns , then release all , then renew .. ?

i would suggest changing the network card and see what happens...if you remove the computer from the server AD (active directory) and reboot, does the see the computer name? (which i bet it probably doesn't) if you get a new network card and put it in, and it still doesn't work, i would look at the cable, or possible what connects the server to the machine (router, switch) possibly having a bad port...if you have a router or switch also you might want to check the port lights on it, to see if that machine is actually connected to the switch...my money is on the network card...if you still have issues, i would even place the network card in a different PCI slots and see what happens...hope that helps Complete Computer Service Inc. NW Indiana

check in services and be sure DHCP is set to automatic. Please post back within 24 hours or I will delete the post from my follow up list. Thanks. It would be a courtesy if you would post back and let us know if the fix worked or not.

Cheryl, First things first... Try hooking up another system (laptop) to that Network connnection, or hook that system up to a different network connection to see if it will connect. The 169 address it is picking up is the APIPA (windows automatic ip addressing) address. If Windows can not detect a DHCP, usually due to no network connection, it will assign the APIPA address. If the current connection is dead, I would try changing the port on the switch. Also, did this system every have spyware on it? Specifically Shop At Home? If it did and you removed it with a spyware removal tool, well, you are in for a world of fun getting it working. let us know if the network jack is live or not first... before changing out any hardward. good luck Scootr

Ok, yes, I have tried /release & /renew without any luck. I went ahead and tried hooking up a laptop to the same port w/same cord and I was able to get onto the network with no problems, so it is workstation specific. I did go to our switch and try switching ports with the problem pc hooked up and each time I put it on a working (lit up) port, it went out as soon as I tried the cable. So, I am thinking it is the nic then? As far as spyware goes, there is a HUGE possibility that there was some on there. I just don't know specifically if it was "Shop at Home". Oh, Also, Dhcp was set to Automatic on the pc. Is there anything else I should try other than a new nic?

Cheryl, OK, now we know it is machine specific. Check in the Hardware manager and ensure the device is not disabled. If everything is as it should be, try a seperate nic. that would be the easiest solution right now. If it still does not funciton, we'll have to try something else. g/l scootr