Possible solution for DHCP (ip address) and SP2

1)
on a cmd window type
netsh int ip reset [log_file_name]

as explained here
http://support.microsoft.com/default...b;en-us;299357

and /or

2) The registry key that must be added is as follows (without the
brackets):

[HKLM\System\CurrentControlSet\Services\IPSec\Assum eUDPEncapsulationContextOnSendRule
= REG_DWORD].
The value data should be set to equal 2.
You can reset the behavior to Default SP2 by changing the Value to "0". A
value of "1" will only enable a Client
with a public (i.e.non-NAT'd) address to connect to a NAT'd server.
The value of "2" enables both public and NAT'd clients to connect to
a NAT'd server. The value of "2" is equal to the pre-SP2 behavior.
The key can be entered into the registry by a system's user.

I had the problem of not getting ip address from my cable modem (direct,
without any router) upon installing sp2.
changing of any network properties settings like "QoS packet scheduler" or
any others would crash my internet client log -in software (BSOD) , on
uninstalling that client software i would get ip address and all, but no
internet connection (since the client software was not installed)

previosly i was using sp1 without any problems for the last 2 yrs or so (
not a single crash / BSOD of any kind)

tried the above two in sequence without rebooting so do not know which one
helped, an hour back, now i can get ip address and can log to the net.
(Still keeping fingers crossed)

here is the logfile from the netsh utility (if it helps any of you technical
people)

reset
SYSTEM\CurrentControlSet\Services\Dhcp\Parameters\ Options\15\RegLocation
old REG_MULTI_SZ =
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\?\DhcpDomain
SYSTEM\CurrentControlSet\Services\TcpIp\Parameters \DhcpDomain

reset
SYSTEM\CurrentControlSet\Services\Netbt\Parameters \Interfaces\Tcpip_{93B180D8-0530-423E-8D36-5D08D24CD7D5}\NameServerList
old REG_MULTI_SZ =
empty

added
SYSTEM\CurrentControlSet\Services\Netbt\Parameters \Interfaces\Tcpip_{93B180D8-0530-423E-8D36-5D08D24CD7D5}\NetbiosOptions
added
SYSTEM\CurrentControlSet\Services\Netbt\Parameters \Interfaces\Tcpip_{9FB47FB7-1E62-4404-AFB6-1E5883C8F48D}\NetbiosOptions
reset
SYSTEM\CurrentControlSet\Services\Netbt\Parameters \Interfaces\Tcpip_{AFB66625-4F55-4289-AB3A-E1187E37D7C8}\NameServerList
old REG_MULTI_SZ =
empty

added
SYSTEM\CurrentControlSet\Services\Netbt\Parameters \Interfaces\Tcpip_{AFB66625-4F55-4289-AB3A-E1187E37D7C8}\NetbiosOptions
added
SYSTEM\CurrentControlSet\Services\Netbt\Parameters \Interfaces\Tcpip_{EAEE51B4-9DD0-42B2-8B39-E077DF7CD532}\NetbiosOptions
deleted SYSTEM\CurrentControlSet\Services\Netbt\Parameters \EnableLmhosts
added
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{04FBE11B-019E-422F-A960-8B00774F492C}\AddressType
added
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{04FBE11B-019E-422F-A960-8B00774F492C}\DisableDynamicUpdate
reset
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{04FBE11B-019E-422F-A960-8B00774F492C}\RawIpAllowedProtocols
old REG_MULTI_SZ =
0

reset
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{04FBE11B-019E-422F-A960-8B00774F492C}\TcpAllowedPorts
old REG_MULTI_SZ =
0

reset
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{04FBE11B-019E-422F-A960-8B00774F492C}\UdpAllowedPorts
old REG_MULTI_SZ =
0

added
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{53C357D5-2E02-4E16-96E0-FB42EFD99584}\AddressType
added
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{53C357D5-2E02-4E16-96E0-FB42EFD99584}\DisableDynamicUpdate
reset
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{53C357D5-2E02-4E16-96E0-FB42EFD99584}\RawIpAllowedProtocols
old REG_MULTI_SZ =
0

reset
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{53C357D5-2E02-4E16-96E0-FB42EFD99584}\TcpAllowedPorts
old REG_MULTI_SZ =
0

reset
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{53C357D5-2E02-4E16-96E0-FB42EFD99584}\UdpAllowedPorts
old REG_MULTI_SZ =
0

deleted
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{93B180D8-0530-423E-8D36-5D08D24CD7D5}\NameServer
added
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{A77E6EF1-393C-462F-9F69-CEDEAC72A0A7}\DisableDynamicUpdate
deleted
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{A77E6EF1-393C-462F-9F69-CEDEAC72A0A7}\IpAutoconfigurationAddress
deleted
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{A77E6EF1-393C-462F-9F69-CEDEAC72A0A7}\IpAutoconfigurationMask
deleted
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{A77E6EF1-393C-462F-9F69-CEDEAC72A0A7}\IpAutoconfigurationSeed
reset
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{A77E6EF1-393C-462F-9F69-CEDEAC72A0A7}\RawIpAllowedProtocols
old REG_MULTI_SZ =
0

reset
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{A77E6EF1-393C-462F-9F69-CEDEAC72A0A7}\TcpAllowedPorts
old REG_MULTI_SZ =
0

reset
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{A77E6EF1-393C-462F-9F69-CEDEAC72A0A7}\UdpAllowedPorts
old REG_MULTI_SZ =
0

deleted
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \Interfaces\{AFB66625-4F55-4289-AB3A-E1187E37D7C8}\NameServer
deleted
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \DontAddDefaultGatewayDefault
deleted
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \EnableIcmpRedirect
deleted
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \EnableSecurityFilters
deleted SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \SearchList
deleted
SYSTEM\CurrentControlSet\Services\Tcpip\Parameters \UseDomainNameDevolution
reset Linkage\UpperBind for
PCI\VEN_10B7&DEV_1700&SUBSYS_1015147B&REV_12\4&1F7 DBC9F&0&10F0. bad value
was:
REG_MULTI_SZ =
PSched

reset Linkage\UpperBind for ROOT\MS_NDISWANIP\0000. bad value was:
REG_MULTI_SZ =
PSched

completed

On Tue, 31 Aug 2004 10:43:44 +0530, "deejay"
wrote:

tried the above two in sequence without rebooting so do not know which one
helped, an hour back, now i can get ip address and can log to the net.
(Still keeping fingers crossed)

Deejay,

thanks for the report!

The second change could fairly quickly be undone and later
redone for a test. It would be helpful to know. So if you find
the time ...

You may have to reboot though to make the change effective.

Hans-Georg

--
No mail, please.

Changed the second option back to sp2 default, i.e. changed the value back
to 0 (zero). rebooted
and it is working fine.
so i guess it was the first option which did it.
and the "packet scheduler" ( psched) was the cause of the problem, which was
reset / repaired by the net shell utility as stated above.
This could be m/c specific, i.e. it could be for my particular m/c and not a
general fix. but it solved my problem thats what matters to me.
now ..... SP2 is superb, well done microsoft and the development team.

"Hans-Georg Michna" wrote in message
...
On Tue, 31 Aug 2004 10:43:44 +0530, "deejay"
wrote:

tried the above two in sequence without rebooting so do not know which
one
helped, an hour back, now i can get ip address and can log to the net.
(Still keeping fingers crossed)

Deejay,

thanks for the report!

The second change could fairly quickly be undone and later
redone for a test. It would be helpful to know. So if you find
the time ...

You may have to reboot though to make the change effective.

Hans-Georg

--
No mail, please.

On Wed, 1 Sep 2004 06:43:36 +0530, "deejay"
wrote:

Changed the second option back to sp2 default, i.e. changed the value back
to 0 (zero). rebooted
and it is working fine.
so i guess it was the first option which did it.
and the "packet scheduler" ( psched) was the cause of the problem, which was
reset / repaired by the net shell utility as stated above.
This could be m/c specific, i.e. it could be for my particular m/c and not a
general fix. but it solved my problem thats what matters to me.
now ..... SP2 is superb, well done microsoft and the development team.

Deejay,

thanks a lot for your second test. I will ad this information to
the document http://www.michna.com/kb/WxSP2.htm.

Hans-Georg

--
No mail, please.

Nice going deejay :)

-----Original Message-----
On Wed, 1 Sep 2004 06:43:36 +0530, "deejay"

wrote:

Changed the second option back to sp2 default, i.e.
changed the value back
to 0 (zero). rebooted
and it is working fine.
so i guess it was the first option which did it.
and the "packet scheduler" ( psched) was the cause of
the problem, which was
reset / repaired by the net shell utility as stated
above.
This could be m/c specific, i.e. it could be for my
particular m/c and not a
general fix. but it solved my problem thats what matters
to me.
now ..... SP2 is superb, well done microsoft and the
development team.

Deejay,

thanks a lot for your second test. I will ad this
information to
the document http://www.michna.com/kb/WxSP2.htm.

Hans-Georg

--
No mail, please.
.