DHCP Issue

[Guest]

I have several laptop users in the office. Everything works fine until they
return from a trip. For some reason there network adapter will not pull an
IP from my DHCP server. It will default to the generic adapter address. The
only way to get it to work is to uninstall the adapter and scan for hardware
changes. Once I do that it will pull the proper address. This happens every
time. None of the IPCONFIG commands work either. Does anyone know what
might cause this or a solution to the problem?

All users are using XP fully patched and I use a juniper router (old
netscreen 10) as my DHCP server.

 

[Guest]

hi JT, I have the same problem & I think I have traced the source back to
IPSEC not loading. Although i am unsure as to where to go from here.

 

[Guest]

What do you use as your DHCP server? I am wondering if it is my router?

 

[GTS]

Sometimes this happens because certain public access points may change the
network node type to peer-to-peer. If you are able to run IPCONFIG /all,
check the node type (I'm inferring this ipconfig function does work.) If
it shows "Peer-to-Peer" go to at the
HLM\System\CurrentControlSet\Services\Netbt\Parameters and delete these
values if they're present:
NodeType
DhcpNodeType
(Usual warnings re. registry editing..... be careful). Reboot, then try
network again.

 

[Guest]

I've tried the PC on two seperate networks:
1) Windows network with SBS2003 server running DCHP Server - won't pick
up IP
2) Home network with Router acting as DHCP Server - won't pickup IP
either
yet my laptop will pickup IP Address - no problem, using the same Network
Point & Cable.

If I set the PC's IP as a Static then I can see the network, browse, even
access the Servers shared folders, yet I cannot access the internet

it's a strange problem

 

[Guest]

tried your suggestgion GTS - it still refuses to pickup a DHCP IP

I've run through everything again this morning, just to make sure that
yesterday, it wasn't just me being an idiot.
I've double checked everything - Workgroup, firewalls, services etc
everything looks to be set as it should - if I specify IP - i can even
access the servers shared folders.

the only problem that I can see is - IPSEC Services (which is set to
Automatic) refuses to start & gives error: 10106 The requested service
provider could not be loaded or initialised.

I tried kicking the pc aswell - but this doesn't work either

 

[Guest]

I was messing around with it yesterday and change the DHCP service recovery
on the first and second failure to restart the service. I tried it once and
it appeared to work. Not sure if it was just a fluke. I will test it more
today. Give it a shot and let me know if it works for you.

 

[Guest]

That is the DHCP Client service.

I was messing around with it yesterday and change the DHCP service recovery
on the first and second failure to restart the service. I tried it once and
it appeared to work. Not sure if it was just a fluke. I will test it more
today. Give it a shot and let me know if it works for you.

 

[Guest]

It didn't work, but when you restart the DHCP client service. the IPCONFIG
/RELEASE and /RENEW work. There has got to be something out there to fix
this problem.

 

[GTS]

I'm puzzled but have a few thoughts particularly given AW's earlier info re.
being able to network except Internet with a static IP.

1. Check Internet Options / Connections to make sure no proxy server or
other oddity is present.
2. Try running this command >netsh winsock reset catalog Any
difference?
--

 

[Guest]

I am not really having the same problem as AW. I can get it to work. I just
have to go to there machine and unistall the network adapter, scan for
hardware changes and it will pull the proper IP. The problem is I have to do
this for every user that leaves the office and connects to another wired or
wireless connection. (ie. hotels). I can get it to work, but it is a pain.
I am looking for a solution so I can automate the process. I have been
playing around restarting the DHCP client and doing ipconig /release and the
/renew. That seems to work without having to uninstall the adapter
everytime. I was trying to find a way to restart that service and do the
ipconfig in a login script or something like that. Any suggestions.

 

[GTS]

I'm bothered by the underlying problem of why using another network would
cause this, but don't know the answer. I have many clients with laptops
used this way without this problem except for the occasional issue with the
node type I mentioned earlier. In any case, to answer the script question,
these would be the basic commands for a batch file. There could be a timing
issue with the commands, but you could give it a try.

net stop dhcp
net start dhcp
ipconfig /release
ipconfig /renew

--

 

[GTS]

Correction - See Dynamic DNS updates do not work if the DHCP client service
stops
http://support.microsoft.com/default.aspx?scid=kb;en-us;264539

net stop dhcp
net start dhcp
ipconfig /registerdns
ipconfig /release
ipconfig /renew

Please let us know the result if you try this.
Thanks.


--

 

[Guest]

Thanks for the suggestgions, i'll have to wait till Monday to try them now
& sorry for hijacking your thread JT

GTS - I have tried those already, normally in win98 I would have removed
TCP/IP and then re-installed it, but this doesn't seem possible in XP

is there a way of restoring e.g. the original Local Area Connection registry
keys?

btw O/S was WinXP Home SP1 but have installed SP2 since - did not fix DHCP
Problem

PC was infected with a version of About:Blank IE Hijack, which I had
sucessfully removed using an excellent how-to (will post the link here when i
find it) - which enabled me to identify the hidden dll file that the
About:Blank Hijack uses to restore the se.dll file whenever it gets deleted.
I deleted the dll - which was not a Microsoft dll, since then i've been left
with this DHCP problem.

any help will be greatly appreciated.

 

[GTS]

I recommend trying the solutions below in the order shown if the first
fails. Problems in the Layered Service Provider chain are not uncommon
after removing malware and one of these usually works to resolve them.

(Run in a command prompt. See KB Below for explanation) netsh winsock
reset catalog
LSP-fix- http://www.cexx.org/lspfix.htm
WinSock XP Fix http://www.spychecker.com/program/winsockxpfix.html

How to reset Internet Protocol (TCP/IP) in Windows XP (Note Shows pre SP2
command syntax)
http://support.microsoft.com/default.aspx?scid=kb;en-us;299357
--

 

[Guest]

Thanks for your help GTS. As am I bother by this issue. I will keep trying
some things to see if I can get some work arounds. I read a couple of
articles about the autoconfiguration to turn it off on one network card if
you have two. all the laptops have 1 lan and 1 wireless. Do you think this
might be the cause of it.

I already tried the net stop DHCP and realize that doesn't work. Thanks
again for all you help.

I was talking with another user and he gets around it by doing ipconfig
/release prior to getting off the out of office network. If he does that, it
will work fine when he returns. Unfortunately, most of my users are not
really computer savvy.

 

[Guest]

Thankyou, Thankyou Thankyou GTS..

After using the LSP Fix & the Winsock Fix, the system will now pick up a
DHCP IP Address.
As promised the about:blank fix I used which apart from this DHCP issue is
so easy.

------------------------------------------------------------------------------------------------

Is your browser always defaulting to homepage about:blank? If so then
follow these steps to eliminate this spyware

Steps to take to remove the about:blank spyware

1) First, you need to get the about:blank page displayed, so open your
Internet Explorer web browser.

2) If you have this spyware on your computer, then your browser will open to
about:blank as expected.

3) Click "View" on the toolbar at the top, then click the "View Source"
option.

4) Look for something like the following: res://%43%3a%5c%57%49%..... (or
something like this). Copy the entire string, make sure you copy the ENTIRE
string from start to end.

5) Now you need to translate this to the actual name. Many sites will do
this for you. Go to http://www.simplelogic.com/Developer/URLDecode.asp and
paste the string you copied into the box and press the "clean" button.

6) You will see a string and dll file name (that ends with dll). Go to that
folder, its most likely located in your windows\system32 folder. Make sure
you have your explorer set to show hidden files. Now simply rename the dll
file. Reboot immediately. Problem solved.

NOTE: For experienced users, if you cannot find the file in your browser as
listed in #3, this may be because there are several different about:blank
spyware versions floating around, and you possibly may have gotten a
different adware or spyware version of about blank. In this case, if you are
familiar with the windows registry, go to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows and
then view AppInit_DLLs. Get the value from that key and this is your dll file
that you need to rename, as specified in the removal instructions above. It
basically allows you to skip the first 5 steps and go right to the rename
step. You have to be a little more technical to use this method, as you need
to be a little familiar with the registry and what that is, but you can find
the about blank spyware dll module by going directly to this registry key.
Make sure you have explorer set to show all hidden files, otherwise you may
not see this when you look for it, but it should be in your
c:\windows\system32 folder.

-------------------------------------------------------------------------------------------------

After completing the above, you may need to run the LSP Fix & the
Winsock Fix listed below.

thanks again GTS & LT

 

[GTS]

You're welcome. Glad it worked out.
--

Thankyou, Thankyou Thankyou GTS..

After using the LSP Fix & the Winsock Fix, the system will now pick up a
DHCP IP Address.
As promised the about:blank fix I used which apart from this DHCP issue
is
so easy.

------------------------------------------------------------------------------------------------

Is your browser always defaulting to homepage about:blank? If so then
follow these steps to eliminate this spyware

Steps to take to remove the about:blank spyware

1) First, you need to get the about:blank page displayed, so open your
Internet Explorer web browser.

2) If you have this spyware on your computer, then your browser will open
to
about:blank as expected.

3) Click "View" on the toolbar at the top, then click the "View Source"
option.

4) Look for something like the following: res://%43%3a%5c%57%49%..... (or
something like this). Copy the entire string, make sure you copy the
ENTIRE
string from start to end.

5) Now you need to translate this to the actual name. Many sites will do
this for you. Go to http://www.simplelogic.com/Developer/URLDecode.asp and
paste the string you copied into the box and press the "clean" button.

6) You will see a string and dll file name (that ends with dll). Go to
that
folder, its most likely located in your windows\system32 folder. Make sure
you have your explorer set to show hidden files. Now simply rename the dll
file. Reboot immediately. Problem solved.

NOTE: For experienced users, if you cannot find the file in your browser
as
listed in #3, this may be because there are several different about:blank
spyware versions floating around, and you possibly may have gotten a
different adware or spyware version of about blank. In this case, if you
are
familiar with the windows registry, go to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows
and
then view AppInit_DLLs. Get the value from that key and this is your dll
file
that you need to rename, as specified in the removal instructions above.
It
basically allows you to skip the first 5 steps and go right to the rename
step. You have to be a little more technical to use this method, as you
need
to be a little familiar with the registry and what that is, but you can
find
the about blank spyware dll module by going directly to this registry key.
Make sure you have explorer set to show all hidden files, otherwise you
may
not see this when you look for it, but it should be in your
c:\windows\system32 folder.

-------------------------------------------------------------------------------------------------

After completing the above, you may need to run the LSP Fix & the
Winsock Fix listed below.

thanks again GTS & LT

 

[GTS]

You're welcome. I'm about out of ideas on this one though I think it might
be worth trying the items I noted for AW.

I see a lot of laptops with wired and wireless NICs without this kind of
problem, so I have some doubt the idea you mentioned would help. What the
other user told you is interesting, and should give some clue, but I don't
know what to make of it at this point. If anything more comes to mind, I'll
let you know.