DHCP - Specific User Can't obtain IP address. 1

[theripper]

I have something interesting going on.

Client running 3.2 - connects to 5.1 sbe sp2.

Yesterday, my user reported she had lost all her network drives. After trouble shooting the TCP/IP settings, Network config, etc. . . it appears as though 1/2 of the NIC may be fried.

I can manually enter an IP address. Can at least see my network. Can not ping outside the building. Can not tracert. No DNS numbers have changed. All other PC's obtain an IP address via DHCP just fine & all are working normally. No errors reported. Dropped down an image via Ghost from the network - still same problems (can't grab an IP address via DHCP)

Before I switch the NIC - has anyone ever heard of burning out 1/2 a NIC? We did have a blackout (unscheduled) over the weekend.

Thanks~

 

[DrGreen26]

Well, blackouts and computers don't mix. I have had a modem (actually 2) that lightening did a number on. They would pick theline, I would hear the dialtone, but the modem would not detect a dial tone and thus fail.

So in the sense of power, blackouts, brownout, surges, spikes, lightening, static, can all damage components on circuit boards.

I would say that it is probably damaged...one in a million, just replace it and see what happens...or move the current NIC into another slot on the motherboard and see if that remedies it.

Mark C. Greenwood, CNE
m_jgreenwood@yahoo.com

CNE 4.11 and CNE 5 certified. BS Degree in MIS. Working in the industry for 8 years.

I work with NT servers, NDS for NT as well.

 

[KenB]

I've had this problem on several of my workstations under Win98. It seems to be caused to a corrupt tcp stack in the network section. I tried doing an uninstall/reinstall and also copied files from another system but it didn't fix the problem. I finally had to remove all networking, remove the nic and reboot to clean out all the files and settings. Then I reinstalled the nic, loaded the drivers and set up everything from scratch. The next reboot and I had the IP address back.
I use the 3com 3c905b nics and they seem to be a little bit picky at times.

Ken

 

[TheBoySmith]

If you run winipcfg on the dodgy workdstations does it show the info or come up with Fatal IP Config. If you get fatal ip then there is a TID that tells you about ws2bakup.

Check to see if you have a directory called c:\windows\ws2bakup.

If you have then
1. Goto a command prompt and cd into c:\windows\ws2bakup.
2. then run ws2bakup.bat
You will get lots of errors but keep running it. The last couple of commands do a registry edit.
3. Restart your pc in ms-dos mode.
4. again cd to c:\windows\ws2bakup
5. Run ws2bakup.bat, this should now copy all the files needed.
6. restart pc and try running winipcfg. If it runs your IP is fixed. Lee Smith
Xenon Network Services
Snr. Technical Support
LSmith@xenon-uk.co.uk