Re: DHCP Issue

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...b;en-us;299357
--

"AW" <AW@discussions.microsoft.com> wrote in message
news:6DABBA87-690E-4CAC-A011-B15312E9C6CE@microsoft.com...
> 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.
>
> "JT" wrote:
>
>> 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.

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.

"GTS" wrote:

> 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...b;en-us;299357
> --
>
> "AW" <AW@discussions.microsoft.com> wrote in message
> news:6DABBA87-690E-4CAC-A011-B15312E9C6CE@microsoft.com...
> > 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.
> >
> > "JT" wrote:
> >
> >> 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.
>
>
>

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" wrote:

> 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...b;en-us;299357
> --
>
> "AW" <AW@discussions.microsoft.com> wrote in message
> news:6DABBA87-690E-4CAC-A011-B15312E9C6CE@microsoft.com...
> > 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.
> >
> > "JT" wrote:
> >
> >> 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.
>
>
>

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

"AW" <AW@discussions.microsoft.com> wrote in message
news:EB7E29F8-67FD-4BBB-9FB7-3028BF805C1F@microsoft.com...
> 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" wrote:
>
>> 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...b;en-us;299357
>> --
>>
>> "AW" <AW@discussions.microsoft.com> wrote in message
>> news:6DABBA87-690E-4CAC-A011-B15312E9C6CE@microsoft.com...
>> > 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.
>> >
>> > "JT" wrote:
>> >
>> >> 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.
>>
>>
>>

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.
--

"JT" <JT@discussions.microsoft.com> wrote in message
newsF9DA849-EE00-42BA-8924-F81F12DB543D@microsoft.com...
> 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.