• Creator
  • #2150412



    by honkd ·

    I’m having trouble getting on the net with a new dell insperion at work. I am the amatuer network admin. It’s not seeing our network and we’ve tried different connections plus wireless.

All Answers

  • Author
    • #2922893


      by honkd ·

      In reply to recognize


    • #2922888

      Try this for your problem network connection.

      by Anonymous ·

      In reply to recognize

      Fix your DNS problems
      If you’re having problems Web surfing, you may have a DNS problem. Here are quick ways to fix it.
      DNS, though, can be your foe as well as your friend. DNS problems may stop you from being able to visit Web sites. If you’re having problems connecting, it doesn’t take much work to see if DNS is the cause, and if it is, to try to fix it.
      To find out whether DNS is a potential culprit when you’re having trouble connecting to a site, first ping the site to which you can’t connect by issuing the ping command at the command prompt, like this:
      If the site is live, you’ll get an answer like this
      [] with 32 bytes of data:

      Reply from bytes=32
      time=22ms TTL=235
      Reply from bytes=32
      time=23ms TTL=235
      Reply from bytes=32
      time=23ms TTL=235
      Reply from bytes=32
      time=24ms TTL=235

      Ping statistics for
      Packets: Sent = 4, Received = 4,
      Lost = 0 (0% loss),
      Approximate round trip times in
      Minimum = 22ms, Maximum = 24ms,
      Average = 23ms
      If it’s not, you’ll get a response like this:
      Ping request could not find host.
      Please check the name and try again.
      If you ping a site and it’s live but you can’t connect to it with your browser, a DNS problem might be the reason. If you suspect you’re having a DNS problem, take the following actions:
      Check your HOSTS file
      If your HOSTS file contains an incorrect or outdated listing, you won’t be able to connect. Even if you don’t recall adding listings to a HOSTS file, it still might contain listings, because some Internet accelerator utilities edit them without telling you. Open your HOSTS file with Notepad and see if the site you can’t connect to is listed there. If it is, delete the entry, and you should be able to connect.
      For details about editing a HOSTS file, see “Hack DNS for lightning-fast Web browsing.”
      Check your DNS settings
      Make sure your DNS settings are correct for your ISP or network. If you’ve changed your DNS settings to use a service such as OpenDNS, for example, you might have entered them incorrectly.
      Find out from your ISP or network administrator what your DNS settings are supposed to be, or check the OpenDNS site (or another DNS service) for their server settings. Once you’ve done that, you’ll need to make sure that you’ve entered the DNS settings properly.
      Check the article “Hack DNS for lightning-fast Web browsing” for details about how to change your DNS settings. Then change the DNS servers to the proper ones, or choose “Obtain DNS server address automatically” if your ISP or network administrator tells you to use that setting.
      Flush your DNS cache
      The problem might be related to your DNS cache, so flush it out. To flush the cache, type ipconfig /flushdns at a command prompt.
      Find out if your ISP is having DNS problems
      Your ISP could be the source of the problem. One possibility is that one of its DNS servers is down and you’re trying to access the downed server. If you know the addresses of the DNS servers, ping each of your ISP’s DNS servers, and if any of them don’t respond, remove them from your DNS list.
      If you don’t know the address of the DNS servers and you’re supposed to use the choose “Obtain DNS server address automatically” setting, you’ll have to call your ISP to see whether its DNS servers are having problems. Alternately, you can use the OpenDNS servers instead of your ISP’s DNS servers. For details, see “Hack DNS for lightning-fast Web browsing.”

      Please post back if you have any more problems or questions.

    • #2922884

      A simplified approach

      by nepenthe0 ·

      In reply to recognize

      Network Magic has been favorably reviewed in this Forum:

      Also, check out this Microsoft [i]Knowledge Base[/i] bulletin:

      • #2922882

        You have here made a recommendation…

        by boxfiddler ·

        In reply to A simplified approach

        that is more than likely against company policy for security reasons. You have also recommended a product geared for the home user, inappropriate to the business network.

        “I’m having trouble getting on the net with a new dell insperion [b][i]at work[/i][/b]. I am the amatuer network admin. It’s not seeing our network and we’ve tried different connections plus wireless.”

        Pay attention to what the OP asks if you wish to be rid of me. And stop answering questions about which you know nothing from personal experience if you wish to be rid of me.

    • #2922870

      Can you give a little more detail?

      by dumphrey ·

      In reply to recognize

      When you say trouble, do you mean “Page not found” errors?
      Are you able to ping other machines on the network, but just not reach the internet?
      When you do ipconfig /all, do you see the correct gateway and DNS server listed?
      Are you only using wireed OR wireless at any one time?
      If its a laptop, is the power cord plugged in befor booting? Many Dell laptops disable the wired net interface if on battery.
      What results do you get from an nslookup of google?
      Are you sure of the computers IP settings?

      I know I am asking a lot of questions, but these are the (I have found) common places and tools to trouble shoot physical connections and net connections.

      In your situation I would: (not in strict order)
      1) IPconfig /all (compare output with expectations, right IP, subnet, gatewy, DNS?)
      2) Ping a local network machine.
      3) Ping an internet address.
      4) nslookup a local machine, internet machine
      5)check the firewall for ip restrictions

Viewing 3 reply threads