Results 1 to 10 of 11

Thread: Ideas please

Hybrid View

  1. #1
    Li'l Abner Guest

    Ideas please

    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 :-)

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

  2. #2
    David H. Lipman Guest

    Re: Ideas please

    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.



    --
    Dave
    Multi-AV Scanning Tool - http://multi-av.thespykiller.co.uk
    http://www.pctipp.ch/downloads/dl/35905.asp



  3. #3
    Li'l Abner Guest

    Re: Ideas please

    "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-***** ---

  4. #4
    David H. Lipman Guest

    Re: Ideas please

    From: "Li'l Abner" <blvstk@dogpatch.com>

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


    What about fixing the media connection state instead auto-detection ?

    --
    Dave
    Multi-AV Scanning Tool - http://multi-av.thespykiller.co.uk
    http://www.pctipp.ch/downloads/dl/35905.asp



  5. #5
    David H. Lipman Guest

    Re: Ideas please

    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 :-)
    >


    Anther idea...

    Try a USB or PCMCIA Ethernet adapter and bypass the internal NIC.



    --
    Dave
    Multi-AV Scanning Tool - http://multi-av.thespykiller.co.uk
    http://www.pctipp.ch/downloads/dl/35905.asp


  6. #6
    Li'l Abner Guest

    Re: Ideas please

    "David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in
    news:yfidnbamJPtaG1zSnZ2dnUVZ_qKdnZ2d@giganews.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 :-)
    >>

    >
    > Anther idea...
    >
    > Try a USB or PCMCIA Ethernet adapter and bypass the internal NIC.


    OK. I have one. Now if I can just find the driver for it. I'll try that
    next.


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

  7. #7
    Li'l Abner Guest

    Re: Ideas please

    "David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in
    news:yfidnbamJPtaG1zSnZ2dnUVZ_qKdnZ2d@giganews.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 :-)
    >>

    >
    > Anther idea...
    >
    > Try a USB or PCMCIA Ethernet adapter and bypass the internal NIC.


    I finally found one of those and the drivers for it. Tried using it and
    same thing... 169.254.200.30.
    Found a Microsoft Fixit that *didn't* fixit.
    The DHCP service is set to Automatic and it's started.
    However, the details of the connection in Network & Sharing Center says:
    Connection specific DNS Suffix
    Description Broadcom802.11b/g WLAN
    Physical address 00-21-00-70-78-4B
    DHCP Enabled NO <------------------Why "NO"?
    IPv4 IP Address 169.254.200.30
    IPv4 Subnet Mask 255.255.0.0
    Lease
    Lease
    IPv4 Default gateway 192.168.1.1
    IPv4 DHCP Server 192.168.1.1
    Still striking out.

    Did I mention that they had Webroot Internet Security installed in it?
    Well, just for ****s and giggles I disabled the firewall.
    Voila! Everything started working. DHCP Enabled became YES, and IP address
    became proper, 192.168.1.100 and connected.
    I also tried assigning a static IP and that worked too.
    Next I totally uninstalled Webroot. Never was very impressed with it
    anyway, unfortunately, they paid a pretty good chucnk of money for it.

    Anyway, I appear to be out of the woods, Now it's just a mtter of getting
    rid of iWon toolbar, Webroot toolbar (it didn't uninstall), Shop at Home
    toolbar, Something about rebates, blah, blah, you name it, I also intend to
    Bang Bing in the process, Then I'll go with MSE and see how it likes that!
    It's 2:50 AM. I'm shooting for daylight!



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

  8. #8
    David H. Lipman Guest

    Re: Ideas please

    From: "Li'l Abner" <blvstk@dogpatch.com>

    > "David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in
    > news:yfidnbamJPtaG1zSnZ2dnUVZ_qKdnZ2d@giganews.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 :-)
    >>>

    >>
    >> Anther idea...
    >>
    >> Try a USB or PCMCIA Ethernet adapter and bypass the internal NIC.

    >
    > I finally found one of those and the drivers for it. Tried using it and
    > same thing... 169.254.200.30.
    > Found a Microsoft Fixit that *didn't* fixit.
    > The DHCP service is set to Automatic and it's started.
    > However, the details of the connection in Network & Sharing Center says:
    > Connection specific DNS Suffix
    > Description Broadcom802.11b/g WLAN
    > Physical address 00-21-00-70-78-4B
    > DHCP Enabled NO <------------------Why "NO"?
    > IPv4 IP Address 169.254.200.30
    > IPv4 Subnet Mask 255.255.0.0
    > Lease
    > Lease
    > IPv4 Default gateway 192.168.1.1
    > IPv4 DHCP Server 192.168.1.1
    > Still striking out.
    >
    > Did I mention that they had Webroot Internet Security installed in it?
    > Well, just for ****s and giggles I disabled the firewall.
    > Voila! Everything started working. DHCP Enabled became YES, and IP address
    > became proper, 192.168.1.100 and connected.
    > I also tried assigning a static IP and that worked too.
    > Next I totally uninstalled Webroot. Never was very impressed with it
    > anyway, unfortunately, they paid a pretty good chucnk of money for it.
    >
    > Anyway, I appear to be out of the woods, Now it's just a mtter of getting
    > rid of iWon toolbar, Webroot toolbar (it didn't uninstall), Shop at Home
    > toolbar, Something about rebates, blah, blah, you name it, I also intend to
    > Bang Bing in the process, Then I'll go with MSE and see how it likes that!
    > It's 2:50 AM. I'm shooting for daylight!
    >
    >


    The Firewall must be blocking TCP/UDP port 67 & 68



    --
    Dave
    Multi-AV Scanning Tool - http://multi-av.thespykiller.co.uk
    http://www.pctipp.ch/downloads/dl/35905.asp



  9. #9
    Li'l Abner Guest

    Re: Ideas please

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

    > From: "Li'l Abner" <blvstk@dogpatch.com>
    >
    >> "David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in
    >> news:yfidnbamJPtaG1zSnZ2dnUVZ_qKdnZ2d@giganews.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 :-)
    >>>>
    >>>
    >>> Anther idea...
    >>>
    >>> Try a USB or PCMCIA Ethernet adapter and bypass the internal NIC.

    >>
    >> I finally found one of those and the drivers for it. Tried using it
    >> and same thing... 169.254.200.30.
    >> Found a Microsoft Fixit that *didn't* fixit.
    >> The DHCP service is set to Automatic and it's started.
    >> However, the details of the connection in Network & Sharing Center
    >> says: Connection specific DNS Suffix
    >> Description Broadcom802.11b/g WLAN
    >> Physical address 00-21-00-70-78-4B
    >> DHCP Enabled NO <------------------Why "NO"?
    >> IPv4 IP Address 169.254.200.30
    >> IPv4 Subnet Mask 255.255.0.0
    >> Lease
    >> Lease
    >> IPv4 Default gateway 192.168.1.1
    >> IPv4 DHCP Server 192.168.1.1
    >> Still striking out.
    >>
    >> Did I mention that they had Webroot Internet Security installed in
    >> it? Well, just for ****s and giggles I disabled the firewall.
    >> Voila! Everything started working. DHCP Enabled became YES, and IP
    >> address became proper, 192.168.1.100 and connected.
    >> I also tried assigning a static IP and that worked too.
    >> Next I totally uninstalled Webroot. Never was very impressed with it
    >> anyway, unfortunately, they paid a pretty good chucnk of money for
    >> it.
    >>
    >> Anyway, I appear to be out of the woods, Now it's just a mtter of
    >> getting rid of iWon toolbar, Webroot toolbar (it didn't uninstall),
    >> Shop at Home toolbar, Something about rebates, blah, blah, you name
    >> it, I also intend to Bang Bing in the process, Then I'll go with MSE
    >> and see how it likes that! It's 2:50 AM. I'm shooting for daylight!
    >>
    >>

    >
    > The Firewall must be blocking TCP/UDP port 67 & 68


    I'm gaining but I'm still not out of the woods. I put MSE on it last
    night and it seemed to be working but this morning it went back to the no
    internet connection thing. So I uninstalled it again and it is
    connecting. If he didn't have so much stuff installed on here I'd wipe it
    in a heartbeat.


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

  10. #10
    Dustin Guest

    Re: Ideas please

    "Li'l Abner" <blvstk@dogpatch.com> wrote in
    news:XnsA0607D8D6AF2Ebutter@wefb973cbe498:

    > "David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in
    > news:jpsvvo01s7s@news7.newsguy.com:
    >
    >> From: "Li'l Abner" <blvstk@dogpatch.com>
    >>
    >>> "David H. Lipman" <DLipman~nospam~@Verizon.Net> wrote in
    >>> news:yfidnbamJPtaG1zSnZ2dnUVZ_qKdnZ2d@giganews.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 :-)
    >>>>>
    >>>>
    >>>> Anther idea...
    >>>>
    >>>> Try a USB or PCMCIA Ethernet adapter and bypass the internal NIC.
    >>>
    >>> I finally found one of those and the drivers for it. Tried using it
    >>> and same thing... 169.254.200.30.
    >>> Found a Microsoft Fixit that *didn't* fixit.
    >>> The DHCP service is set to Automatic and it's started.
    >>> However, the details of the connection in Network & Sharing Center
    >>> says: Connection specific DNS Suffix
    >>> Description Broadcom802.11b/g WLAN
    >>> Physical address 00-21-00-70-78-4B
    >>> DHCP Enabled NO <------------------Why "NO"?
    >>> IPv4 IP Address 169.254.200.30
    >>> IPv4 Subnet Mask 255.255.0.0
    >>> Lease
    >>> Lease
    >>> IPv4 Default gateway 192.168.1.1
    >>> IPv4 DHCP Server 192.168.1.1
    >>> Still striking out.
    >>>
    >>> Did I mention that they had Webroot Internet Security installed in
    >>> it? Well, just for ****s and giggles I disabled the firewall.
    >>> Voila! Everything started working. DHCP Enabled became YES, and IP
    >>> address became proper, 192.168.1.100 and connected.
    >>> I also tried assigning a static IP and that worked too.
    >>> Next I totally uninstalled Webroot. Never was very impressed with
    >>> it anyway, unfortunately, they paid a pretty good chucnk of money
    >>> for it.
    >>>
    >>> Anyway, I appear to be out of the woods, Now it's just a mtter of
    >>> getting rid of iWon toolbar, Webroot toolbar (it didn't uninstall),
    >>> Shop at Home toolbar, Something about rebates, blah, blah, you name
    >>> it, I also intend to Bang Bing in the process, Then I'll go with
    >>> MSE and see how it likes that! It's 2:50 AM. I'm shooting for
    >>> daylight!
    >>>
    >>>

    >>
    >> The Firewall must be blocking TCP/UDP port 67 & 68

    >
    > I'm gaining but I'm still not out of the woods. I put MSE on it last
    > night and it seemed to be working but this morning it went back to
    > the no internet connection thing. So I uninstalled it again and it is
    > connecting. If he didn't have so much stuff installed on here I'd
    > wipe it in a heartbeat.
    >
    >


    uninstall the 3rd party firewall and filtering software programs, reset
    windows firewall back to defaults, reset winsock IP configuration. See
    if it holds up. It's important to do this in the order I listed.



    --
    Character is doing the right thing when nobody's looking. There are too
    many people who think that the only thing that's right is to get by, and
    the only thing that's wrong is to get caught. - J.C. Watts

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •