Martyn
Well-Known Member
- Reaction score
- 116
- Location
- Bedfordshire UK
Cant acquire an IP Address - Please Help!
- Thread starter jdsbellis
- Start date
Martyn
Well-Known Member
- Reaction score
- 116
- Location
- Bedfordshire UK
I'm lost because of his quote. If he sets a static ip then it should work
TriadPCSolutions
Member
- Reaction score
- 0
I'm lost because of his quote. If he sets a static ip then it should work
Agreed static IP should absolutely work, for the home network anyway. However the practicallity of that solution depends largely on the users intentions with it. (IE taking the laptop out on a regular basis to multiple AP's, or only using the home network). Is the DHCP set to automatic or manual? (which is still strange, if I recall manual is the standard and it should start the service when the user tries to connect to a network, but for the heck of it try automatic). Otherwise check event log and see if anything odd is going on related to DHCP.
ATTech
New Member
- Reaction score
- 3
- Location
- Sacramento Area, CA
Do you understand what DHCP is? A static IP address doesn't require a dhcp service, because it doesn't use DHCP...
Xander
Banned
- Reaction score
- 66
- Location
- Niagara region, Ontario
Workaround?
Give him a desktop shortcut with: net start dhcp in it, OR just put that shortcut into the Startup folder. Or, as I said a few days ago, go with a static IP.
Give him a desktop shortcut with: net start dhcp in it, OR just put that shortcut into the Startup folder. Or, as I said a few days ago, go with a static IP.
Or just give to computer to someone who knows what they are doing. If the OP doesn't understand the basics he shouldn't be taking on paid work.
It's a paying customer, not a college project.
Xander
Banned
- Reaction score
- 66
- Location
- Niagara region, Ontario
Not arguing but there have been times where I've said to a customer, "I could spend another hour trying to find what's causing the problem, or I can give a workaround that you'd have to use each time manually." Sometimes, based on cost, they opt for the latter, especially for older machines that the know won't last another year.
I recently had a similar problem for one of my clients on a Dell vostro machine.
I had:
* Checked that DHCP was running fine on the network
* Statically assigned an IP. It would work for a few mins then stop.
* Updated network card drivers (from Dell and then straight from manufacturer)
* Tried a different network cable
* Tried a different patch port
* Tried a different switch port.
All to no avail! In the end, I figured it must have either been a hardware fault or something wrong with the OS. Decided to go with hardware fault... and I was right. Dell replaced the motherboard and the problem went away!
I was just glad that the system was still under warranty
I had:
* Checked that DHCP was running fine on the network
* Statically assigned an IP. It would work for a few mins then stop.
* Updated network card drivers (from Dell and then straight from manufacturer)
* Tried a different network cable
* Tried a different patch port
* Tried a different switch port.
All to no avail! In the end, I figured it must have either been a hardware fault or something wrong with the OS. Decided to go with hardware fault... and I was right. Dell replaced the motherboard and the problem went away!
I was just glad that the system was still under warranty
Which is a fair indication this wasn't a hardware fault. In replacing the mainboard the OS would have been nuked'n' paved which is why it appeared to be the fix.
As I suggested earlier, this is a common fault on Dell machines and is often caused by their network management software. Anything the intercept/interfaces with the network protocol stack should be regarded as a possible suspect when dealing with this type of problem - anti-virus, firewall, network management tools, virus/malware and so forth should all be eliminated before you reach out for the screwdriver. Network components can also be a cause, but can be quickly eliminated or separated from the problem PC if you plug in your own netbook or laptop - if that has a problem picking-up an IP address via DHCP then start with the patch lead and work backwards towards the DHCP server.
If you suspect the device NIC to be suspect, this can usually be tested with a pre-boot environment such as UBCD Win, this includes drivers for most NICs and a DHCP client. If this picks up a DHCP address then the fault will lie with the client OS or installed software.
Last edited:
atlanticjim
Well-Known Member
- Reaction score
- 36
- Location
- Long Island, New York
Am I missing something here?
*MSCONFIG
*Services Tab
*Scroll to DHCP Client
*tic the box
*reboot
edit:
Of course DHCP Client has dependencies.
Tcpip
Afd
NetBt
*MSCONFIG
*Services Tab
*Scroll to DHCP Client
*tic the box
*reboot
edit:
Of course DHCP Client has dependencies.
Tcpip
Afd
NetBt
Last edited:
Fraid not! No Dell network management software installed. Operating system wasn't touched either. They just did a pure swap of the motherboard.
Either way, solution was found!
K007
Member
- Reaction score
- 0
There are 30 replies, and I didn't read through all of them.
If my suggestion is a repeat, the please ignore it.
Did you actually check to see this 2 things:
1. Is there a manual switch on the laptop that swithches WiFi on/off? If it is, is it on or off?
2. Some laptops are by default set on WiFi = Bluetooth. Did you check that?
Nakin
Member
- Reaction score
- 2
- Location
- Paris, France
It happened to me once... Finally, I just have unistalled the wifi card driver, and rebooted the machine. Of course, Windows reinstalled it, and, guess what? It worked perfectly!!
I don't think that could help, but: desperate situations, desperate ways.
I don't think that could help, but: desperate situations, desperate ways.
10 years as a tech and this is a stumped issue? Multiple pages?
If computer does not pull IP in windows on multiple adapters, boot to live cd (linux ..etc).
If it gets IP, then the hardware is fine.
If it doesn't, then the hardware is bad.
If it gets IP, then move onto software diagnostics.
Does it get IP in safe mode... etc etc etc
Basic methodology here, no need to get all complicated.
If computer does not pull IP in windows on multiple adapters, boot to live cd (linux ..etc).
If it gets IP, then the hardware is fine.
If it doesn't, then the hardware is bad.
If it gets IP, then move onto software diagnostics.
Does it get IP in safe mode... etc etc etc
Basic methodology here, no need to get all complicated.
I'm not sure why people are still trying to help him troubleshoot this when he has isolated the problem. The issue is with the "DHCP Client" service not starting automatically. Hard coding is hardly a solution, more of a bandaid.
I'm going to assume you already made sure the Service startup type was set to: Automatic correct?
In this situation i'd most likely do the following
1. Verify service startup type is set to automatic
2. Check dependencies(CMD /K SC QC DHCP)
3. Run TDSSKiller
4. See if afd.sys, tcpip.sys, or netbt.sys are corrupted, replace and do a winsock tcp/ip fix
5. Repair install
I'd be willing to bet TDSSKiller will find something and resolve your issue.
Last edited:
Sounds like you're trying to help him.
IMHO, I very much doubt it's malware, most malware & virus writers want to keep the connection alive. This type of problem is typical of malfunctioning security software and/or a corrupted protocol stack.
Sounds like you're trying to help him.
What i was meaning was there is no reason to keep offering general troubleshooting advice that is not related to the DHCP Client service. He already confirmed that this was the issue because it was not starting automatically.
I disagree, there is a good chance it is malware, a rootkit in particular. TDSS is known for causing the exact symptoms the OP is describing which is why I recommended TDSSKiller. I would say it's actually very likely this is the cause.
Did you read the entire thread? Malfunctioning security software or a corrupted protocol stack will not cause the DHCP Client service to not start automatically.
Read my previous post before we knew it was the DHCP Client service and you will see I already recommended he check those very two things.
OP please let us know
Last edited:
Ccomp5950
Member
- Reaction score
- 13
- Location
- Marshall, Texas
I realizes this is a slightly dated thread but I figure this needs to be said...
TDSSKiller will fix your issue. What is going on:
The customer had a virus spyware issue and it partially removed it. The rootkit is telling your computer "look over here for ${System_File}" at boot up. Afterwards it quits redirecting your computer to that file once the service starts up. The problem is an antivirus scan or something removed that file already so it can't redirect to it. So you are getting a "File not found" error at boot up but not when you manually do it.
Next time you are in this situation take a good look at the system error logs it would have hinted that a lot of services weren't able to start, which would have been an easy tip off for an experience tech here or at least given you a place to start googling.
Good luck.
Ccomp5950
Member
- Reaction score
- 13
- Location
- Marshall, Texas
Do I hear an echo?????????
Perhaps
We have a shop down the street that got about 8 of these same problems and instead of using TDSSkiller they made a startup script that waited and then started up the services.
I recognized their service tag stickers when they all came to my shop about a week later, I had figured out TDSS being the problem about 2 weeks prior though I did have one stump me for a couple days while I was swamped with service calls. Was a real light bulb moment the day I figured it out, and I made 8 new customers the next week when their scripts failed.
Similar threads
