Welcome guest. Before posting on our computer help forum, you must register. Click here it's easy and free.

Author Topic: getting online  (Read 11616 times)

0 Members and 1 Guest are viewing this topic.

Broni


    Mastermind
  • Kraków my love :)
  • Thanked: 614
    • Computer Help Forum
  • Computer: Specs
  • Experience: Experienced
  • OS: Windows 8
Re: getting online
« Reply #30 on: February 20, 2010, 05:05:06 PM »
Nice :)

dhatura1

    Topic Starter


    Rookie

    Re: getting online
    « Reply #31 on: February 20, 2010, 05:13:06 PM »
    thank you for all your help. i know it was a pain in the a#$. Did you ever get a chance to check out my other post?

    dahlarbear



      Specialist

      Thanked: 101
      Re: getting online
      « Reply #32 on: February 20, 2010, 05:39:50 PM »
      3.  Let's scale back the effort...  Can the computer communicate reliably with your local area network's gateway (home router)?

      Retest with the following commands (without the quotes and replace "<>" with the requested information):
           a.  "ping -n 20 127.0.0.1"
           b.  "ping -n 20 <your_computer's_IP_address>"
           c.  "ping -n 20 <your_local_gateway_address>"

      a.  "ping -n 20 127.0.0.1"                                                       0% loss
           b.  "ping -n 20 <your_computer's_IP_address>"              0% loss
           c.  "ping -n 20 <your_local_gateway_address>"              0% loss

      all 3  >>>>>>>>>>>>>     sent = 20, received = 20, lost = 0 (0% loss)

      i Got it. The problem was in a faulty ethernat card. i reconfigured my router to block the lan line and added a wireless connection. I then disabled the device and was then able to get on and browse no problem. The wierd thing is that my device manager says the ethernet card was functioning properly.

      The weird thing is the ethernet card (hardware) is probably "good". Communicates successfully to LAN gateway with zero packet loss (using "ping" with twenty echo requests).

      I'd look elsewhere for the problem...  Or at least take a closer look at the card (test more rigorously - maybe more ping requests with larger "buffer" size).

      Resource conflict?