Jeg er ked af at mit forslag kun gjorde situationen værre for dig :-(
Det følgende er sakset direkte fra
www.michna.com og omhandler netværksproblemer i forbindelse med sp2 opdatering. Prøv . . .
IP address 169.254...—Winsock corruption
If the computer cannot obtain an IP address from a DHCP (Dynamic Host Configuration Protocol) server, like a router using NAT (Network Address Translation), Windows will automatically assign an APIPA (Automatic Private IP Address) in the range:
Class B: 169.254.0.0 - 169.254.255.255
(Subnet mask: 255.255.0.0)
One likely cause is Winsock corruption, caused by adware or a virus. Service Pack 2 adds a new command to repair this Winsock corruption problem.
netsh winsock reset catalog
Using this command should normally not do any harm, so if you have unsolvable connection problems or spurious disconnections, try it. It does remove all nonstandard LSP (Layered Service Provider) entries from the Winsock catalog, which are usually adware or spyware entries, but if you happened to have a legitimate one installed, it would also be removed and would have to be reinstalled.
If you're really curious, you can use the command:
netsh winsock show catalog
before and after resetting the catalog to find out whether any entries were in fact removed and which ones these were. Another way to get at the same information is to run
winmsd
and select Components, Network, Protocol. The Layered Service Providers in the list should be of the MSAFD or RSVP ... Service Provider type. All others are likely malevolent and should disappear after the reset command shown above.
If this is not enough, you can reset the entire IP stack with the command:
netsh int ip reset
or
netsh int ip reset c:\resetlog.txt
where you can replace c:\resetlog.txt with a path and filename of your choice, to get a log file of the process. If the path contains a space, add double quotes. Example (type all in one line):
netsh int ip reset "C:\Documents and Settings\Administrator\My Documents\resetlog.txt"