"David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in
news:jps0cg01kar@news6.newsguy.com:

> From: "Li'l Abner" <blvstk@dogpatch.com>
>
>> Someone brought me a HP laptop with Vista on it. The described
>> problem was that it said "connected" but still no internet access.
>> I booted in Safe Mode with Networking. In Network and Sharing Center
>> the line over to the router is OK, but the one to "internet" is X-ed
>> out. IPv4 connectivity is "limited". Icon in tray says "connected to
>> (router), signal strength excellent. I can disable wireless and go
>> direct and get the limited connectivity.
>>
>> In either case, it's assigning an IP of 169.254.*.*. (should be
>> 192.168.1.something).
>>
>> I tried netsh winsock reset. Nothing.
>>
>> Installed MBam from a memory stick. And copied the latest
>> definitions. I ran that and the worst thing it found was 4 or 5
>> Trojan.Vundo. And a couple hundred MyWebSearch items.
>>
>> Rebooted. No joy. Still getting the 169.254 IP's. If I go into IP
>> properties and assign it a valid IP, the the "line" between the
>> computer and the router is even broken.
>>
>> I've just copied all the guy's stuff off onto a portable drive. I
>> have ComboFix copied onto it and am about ready to run that..
>>
>> But since I have a date with the local bar, I will hold off for a
>> while. When I come back, I expect one of you will have replied "Oh I
>> know what that is! Just do this!"
>>
>> TIA :-)
>>
>
> 169.25.x.y means Auto IP Configuration. That usually occurs when the
> NIC sees it has an Ethernet connection but can't obtain an IP lease
> via DHCP.
>
> If you are on a 192.168.1.x subnet, try statically setting an IP.
>
> IP: 192.168.1.100
> Net Mask: 255.255.255.0
> Gateway: 192.168.1.1
> DNS: 4.2.2.3 & 8.8.8.4
>
> See if that gets you out in the Internet.
>
> You may also want to try fixing the connection at 10 or 100mb/s half
> duplex.

I guess I forgot to mention. I had done that too. I had gone with
192.168.1.44. I set the DNS to 192.168.1.1 and the other one of my ISP.
When I did that, and rebooted, it still showed an IPv4 address of
169.254.200.20 (or something close).

--
--- My mother never saw the irony in calling me a son-of-a-***** ---