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.

Network adapter problems

Discussion in 'Networking (Hardware & Software)' started by FitzDawg, 2007/06/18.

  1. 2007/06/18
    FitzDawg

    FitzDawg Inactive Thread Starter

    Joined:
    2006/05/15
    Messages:
    21
    Likes Received:
    0
    I have a small home network, consisting of a Windows Server 2003 and Windows 2000 workstation. I have DHCP installed on the server and enabled. On the Windows workstation I have "Obtain IP Address Automatically" checked and when I do a IPCONFIG /RENEW, I get the error "The following error occurred when renewing adapter Local Area Connection: Unexpected network failure or insufficient access." But, when I enter a static IP Address I can access my network.

    I am logged in as the Administrator. How can I fix this error so I can get an IP address from my DHCP server?
     
  2. 2007/06/19
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    OK - lets start with the basics.

    A surprising number of DHCP problems are caused by faults on the cable - especially an intermittent Rx connection. Or rather, a DHCP problem is the most obvious symptom of cable problems because it is one of the first services that a system uses on the network. Try swapping the network cable. I don't think that is the problem, but it is a simple thing to check and rule out.

    Next try doing a IPCONFIG /RELEASE before doing the renew. Again, something to try but probably not the solution.

    Do you have any other PC on the network that is picking up IP settings from the server DHCP service? If not I wonder if you have activated the DHCP scope. You can create a new scope and configure it all perfectly, but until you activate the scope, it will not be active on your network.

    To activate the DHCP scope: go into the DHCP tool on the server; drill down to the scope and right click on it; select the option to "Activate ". I think it is quite likely that this is the problem.

    If that doesn't work its time to install Wireshark (used to be Ethereal) on the 2000 pro PC and check to see if the DHCP/BOOTP packets are getting to the computer.

    By the way, when you say you are logged on as Administrator, is that the local admin account or the domain admin account: the local admin account has no special privileges on the network and in fact has less rights at the server than a normal domain user.
     

  3. to hide this advert.

  4. 2007/06/19
    FitzDawg

    FitzDawg Inactive Thread Starter

    Joined:
    2006/05/15
    Messages:
    21
    Likes Received:
    0
    I can check the cables, but I don't think that's the problem since I can ping the other workstations and server.
    I do have other computers that need to obtain an IP address from the DHCP server. The DHCP server is activated.
    I might be loggin in as the local admin. I will check this out and let you know.
     
  5. 2007/06/20
    FitzDawg

    FitzDawg Inactive Thread Starter

    Joined:
    2006/05/15
    Messages:
    21
    Likes Received:
    0
    Problem solved! There was a DHCP conflict between my server and my gateway. This is the first time I ever had to deal with this kind of issue.
    The simplest things are overlooked.
     
  6. 2007/06/21
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    Switch one of them off. You only need one DHCP server on the network. In almost all cases the DHCP service on the 2003 server is the one to use. Turn off DHCP on the router!
     

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.