1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Unable to connect to DHCP server

Discussion in 'Networking (Hardware & Software)' started by spacetoker, 2009/03/19.

  1. 2009/03/19
    spacetoker

    spacetoker Inactive Thread Starter

    Joined:
    2009/03/19
    Messages:
    3
    Likes Received:
    0
    Hello, I've recently replaced the motherboard, cpu and ram in my computer and done a fresh install of windows xp sp2.

    The motherboard is an ASUS M4A79 with an onboard realtek RTL8168/8111 ethernet port, running the latest (and only) driver.

    I am using a router connected to a cable modem, but I have also connected the computer directly to the modem with the same results.

    I am able to ping the localhost, and ASUS tech support feels the mobo isn't damaged.

    About the best I can get is a partial connection, with the device status reporting "Limited or no connectivity." The Ipconfig /renew command returns the error: "An error occurred while renewing interface Local Area Connection 3: unable to contact your DHCP server. Request has timed out. "

    Was able to ping yahoo once using IP #s instead of ping www.yahoo.com, but it only returned 1 of 4 pings then timed out.

    Things I have tried so far:
    - Different cables
    - Uninstalling/Reinstalling network card driver
    - netsh command
    - ipconfig release/renew
    - manually inputting IP, gateway, etc, no joy


    I have also installed a spare wireless NIC to troubleshoot and was unable to get any connectivity there as well, even in totally unsecured mode. I'm able to detect multiple wireless networks in range, too.

    I've never had this much difficulty with networking before outside of linux. Any help would be sincerely appreciated!

    Here's my ipconfig return:



    Windows IP Configuration



    Host Name . . . . . . . . . . . . : m5000

    Primary Dns Suffix . . . . . . . :

    Node Type . . . . . . . . . . . . : Unknown

    IP Routing Enabled. . . . . . . . : No

    WINS Proxy Enabled. . . . . . . . : No



    Ethernet adapter Local Area Connection 3:



    Connection-specific DNS Suffix . :

    Description . . . . . . . . . . . : Realtek RTL8168/8111 PCI-E Gigabit Ethernet NIC

    Physical Address. . . . . . . . . : 00-24-8C-40-C1-60

    Dhcp Enabled. . . . . . . . . . . : Yes

    Autoconfiguration Enabled . . . . : Yes

    Autoconfiguration IP Address. . . : 169.254.76.119

    Subnet Mask . . . . . . . . . . . : 255.255.0.0

    Default Gateway . . . . . . . . . :
     
  2. 2009/03/19
    TonyT

    TonyT SuperGeek Staff

    Joined:
    2002/01/18
    Messages:
    9,072
    Likes Received:
    400
    1. turn off comp, unplug modem, unplug router.
    2. plugin modem, wait until it synches with isp headend.
    3. plugin router & wait until synches w/ modem.
    4. turn on comp.
     

  3. to hide this advert.

  4. 2009/03/19
    spacetoker

    spacetoker Inactive Thread Starter

    Joined:
    2009/03/19
    Messages:
    3
    Likes Received:
    0
    Hi Tony, tried that but exact same ipconfig output and limited connectivity.

    I tried manual settings again, specifying everything I could including DNS suffixes etc. This enabled me to ping the other machine on my router, but still no internet connectivity.

    I'm really not sure what's holding it back here...
     
  5. 2009/03/19
    spacetoker

    spacetoker Inactive Thread Starter

    Joined:
    2009/03/19
    Messages:
    3
    Likes Received:
    0
    Well I'm posting from the new computer, so something must have clicked.

    One thing I did was go thru the D-Link router's setup, and manually input the MAC address for my new motherboard. I'm pretty sure this is what was blocking the system from talking to the router properly.

    :D
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.