Network issues - DHCP client?

Discussion in 'Windows 64bit' started by adamomitcheney@kiwis.co.uk, Mar 1, 2007.

  1. Guest

    Hi there,

    I've got a slightly weird problem with networking - at the moment I
    suspect the problem lies with the operating system - XP64 - but I'm
    still diagnosing. I'm just hoping someone might have an insight...

    System:
    Windows XP64
    AMD dual-core 3800+ on Asus A8N-SLI Premium
    Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller
    (onboard)
    LinkSys WRT54G Router

    Basically, I've seen my network drop intermittently in the past, but
    today it started doing it pretty consistently after around 6 hours
    working today (up to that point is had apparently been OK). To start
    with, going to 'Repair' in Network Connections resolved the problem,
    but after a few attempts that stopped working. I found that restarting
    the DHCP client appeared to resolve the problem, but sometimes for
    only a few minutes. This appears to be an issue on this machine's side
    of the network, as I could not even ping the gateway at 192.168.1.1.
    Interestingly, bittorrent *appeared* to keep working all through these
    outages, although I do have the ports forwarded at the router.

    I've since rebooted the machine and the problem is back. When I first
    brought it up I ran ipconfig -all and everything appeared to be
    normal. I tried pinging 192.168.1.1 and got 100% of packets returned
    in less that 1ms; on the second attempt I lost one packet; on the
    third and fourth attempts I lost two packets each; next time it
    appeared to be OK. As I type this I have no network - I'll restart the
    DHCP client before posting.

    There don't appear to be any messages in the event logs relating to
    this, although the system logs have recorded a few warning messages
    about the "Aegis Protocol (IEEE 802.1x_ v2.3.1.9 service" failing to
    start (this machine is not using wireless - good old cat5e). There are
    also some warnings about TCP/IP reaching the security limit imposed on
    the number of concurrent TCP connect attempts. None of these
    correspond exactly with when I have problems. If I repair the network
    without restarting the DHCP client, I get a warning saying:
    "Your computer was not able to renew its address from the network
    (from the DHCP Server) for the Network Card with network address
    0015F2D346AB. The following error occurred:
    The semaphore timeout period has expired. . Your computer will
    continue to try and obtain an address on its own from the network
    address (DHCP) server."
    There was also a warning earlier today that read:
    "The server could not bind to the transport \Device
    \NetBT_Tcpip_{3CEC7C87-EFF1-4E16-980A-4004499DEE28}."

    This does not appear to be a NIC problem - I've tried the second
    onboard NIC and get exactly the same symptoms.

    Can anyone help me?

    One last thing to note - it appears that I can only keep the network
    up and running for a few moments at a time right now.

    Here's hoping - Adam...
    , Mar 1, 2007
    #1
    1. Advertising

  2. Kue2 Guest

    Do you have the latest Marvel drivers?
    I would try that first

    http://www.marvell.com/drivers/search.do


    <> wrote in message
    news:...
    > Hi there,
    >
    > I've got a slightly weird problem with networking - at the moment I
    > suspect the problem lies with the operating system - XP64 - but I'm
    > still diagnosing. I'm just hoping someone might have an insight...
    >
    > System:
    > Windows XP64
    > AMD dual-core 3800+ on Asus A8N-SLI Premium
    > Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller
    > (onboard)
    > LinkSys WRT54G Router
    >
    > Basically, I've seen my network drop intermittently in the past, but
    > today it started doing it pretty consistently after around 6 hours
    > working today (up to that point is had apparently been OK). To start
    > with, going to 'Repair' in Network Connections resolved the problem,
    > but after a few attempts that stopped working. I found that restarting
    > the DHCP client appeared to resolve the problem, but sometimes for
    > only a few minutes. This appears to be an issue on this machine's side
    > of the network, as I could not even ping the gateway at 192.168.1.1.
    > Interestingly, bittorrent *appeared* to keep working all through these
    > outages, although I do have the ports forwarded at the router.
    >
    > I've since rebooted the machine and the problem is back. When I first
    > brought it up I ran ipconfig -all and everything appeared to be
    > normal. I tried pinging 192.168.1.1 and got 100% of packets returned
    > in less that 1ms; on the second attempt I lost one packet; on the
    > third and fourth attempts I lost two packets each; next time it
    > appeared to be OK. As I type this I have no network - I'll restart the
    > DHCP client before posting.
    >
    > There don't appear to be any messages in the event logs relating to
    > this, although the system logs have recorded a few warning messages
    > about the "Aegis Protocol (IEEE 802.1x_ v2.3.1.9 service" failing to
    > start (this machine is not using wireless - good old cat5e). There are
    > also some warnings about TCP/IP reaching the security limit imposed on
    > the number of concurrent TCP connect attempts. None of these
    > correspond exactly with when I have problems. If I repair the network
    > without restarting the DHCP client, I get a warning saying:
    > "Your computer was not able to renew its address from the network
    > (from the DHCP Server) for the Network Card with network address
    > 0015F2D346AB. The following error occurred:
    > The semaphore timeout period has expired. . Your computer will
    > continue to try and obtain an address on its own from the network
    > address (DHCP) server."
    > There was also a warning earlier today that read:
    > "The server could not bind to the transport \Device
    > \NetBT_Tcpip_{3CEC7C87-EFF1-4E16-980A-4004499DEE28}."
    >
    > This does not appear to be a NIC problem - I've tried the second
    > onboard NIC and get exactly the same symptoms.
    >
    > Can anyone help me?
    >
    > One last thing to note - it appears that I can only keep the network
    > up and running for a few moments at a time right now.
    >
    > Here's hoping - Adam...
    >
    Kue2, Mar 1, 2007
    #2
    1. Advertising

  3. Aaron Kelley Guest

    If it really is a DHCP problem...
    You could try just assigning your machine a static address and seeing if the
    problem goes away.

    - Aaron

    <> wrote in message
    news:...
    > Hi there,
    >
    > I've got a slightly weird problem with networking - at the moment I
    > suspect the problem lies with the operating system - XP64 - but I'm
    > still diagnosing. I'm just hoping someone might have an insight...
    >
    > System:
    > Windows XP64
    > AMD dual-core 3800+ on Asus A8N-SLI Premium
    > Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller
    > (onboard)
    > LinkSys WRT54G Router
    >
    > Basically, I've seen my network drop intermittently in the past, but
    > today it started doing it pretty consistently after around 6 hours
    > working today (up to that point is had apparently been OK). To start
    > with, going to 'Repair' in Network Connections resolved the problem,
    > but after a few attempts that stopped working. I found that restarting
    > the DHCP client appeared to resolve the problem, but sometimes for
    > only a few minutes. This appears to be an issue on this machine's side
    > of the network, as I could not even ping the gateway at 192.168.1.1.
    > Interestingly, bittorrent *appeared* to keep working all through these
    > outages, although I do have the ports forwarded at the router.
    >
    > I've since rebooted the machine and the problem is back. When I first
    > brought it up I ran ipconfig -all and everything appeared to be
    > normal. I tried pinging 192.168.1.1 and got 100% of packets returned
    > in less that 1ms; on the second attempt I lost one packet; on the
    > third and fourth attempts I lost two packets each; next time it
    > appeared to be OK. As I type this I have no network - I'll restart the
    > DHCP client before posting.
    >
    > There don't appear to be any messages in the event logs relating to
    > this, although the system logs have recorded a few warning messages
    > about the "Aegis Protocol (IEEE 802.1x_ v2.3.1.9 service" failing to
    > start (this machine is not using wireless - good old cat5e). There are
    > also some warnings about TCP/IP reaching the security limit imposed on
    > the number of concurrent TCP connect attempts. None of these
    > correspond exactly with when I have problems. If I repair the network
    > without restarting the DHCP client, I get a warning saying:
    > "Your computer was not able to renew its address from the network
    > (from the DHCP Server) for the Network Card with network address
    > 0015F2D346AB. The following error occurred:
    > The semaphore timeout period has expired. . Your computer will
    > continue to try and obtain an address on its own from the network
    > address (DHCP) server."
    > There was also a warning earlier today that read:
    > "The server could not bind to the transport \Device
    > \NetBT_Tcpip_{3CEC7C87-EFF1-4E16-980A-4004499DEE28}."
    >
    > This does not appear to be a NIC problem - I've tried the second
    > onboard NIC and get exactly the same symptoms.
    >
    > Can anyone help me?
    >
    > One last thing to note - it appears that I can only keep the network
    > up and running for a few moments at a time right now.
    >
    > Here's hoping - Adam...
    >
    Aaron Kelley, Mar 1, 2007
    #3
  4. nVidia (or is that nvidious?) motherboard. Therefore:
    Known problem:
    Unfortunately, the built in nVidia firewall product appears to install at
    least some portion of itself even if you've never chosen to install it. And
    this appears to interfere with 32-bit programs. The solution is to install
    the firewall program if it isn't already installed, and then uninstall it.

    --
    Charlie.
    http://msmvps.com/xperts64


    <> wrote in message
    news:...
    > Hi there,
    >
    > I've got a slightly weird problem with networking - at the moment I
    > suspect the problem lies with the operating system - XP64 - but I'm
    > still diagnosing. I'm just hoping someone might have an insight...
    >
    > System:
    > Windows XP64
    > AMD dual-core 3800+ on Asus A8N-SLI Premium
    > Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller
    > (onboard)
    > LinkSys WRT54G Router
    >
    > Basically, I've seen my network drop intermittently in the past, but
    > today it started doing it pretty consistently after around 6 hours
    > working today (up to that point is had apparently been OK). To start
    > with, going to 'Repair' in Network Connections resolved the problem,
    > but after a few attempts that stopped working. I found that restarting
    > the DHCP client appeared to resolve the problem, but sometimes for
    > only a few minutes. This appears to be an issue on this machine's side
    > of the network, as I could not even ping the gateway at 192.168.1.1.
    > Interestingly, bittorrent *appeared* to keep working all through these
    > outages, although I do have the ports forwarded at the router.
    >
    > I've since rebooted the machine and the problem is back. When I first
    > brought it up I ran ipconfig -all and everything appeared to be
    > normal. I tried pinging 192.168.1.1 and got 100% of packets returned
    > in less that 1ms; on the second attempt I lost one packet; on the
    > third and fourth attempts I lost two packets each; next time it
    > appeared to be OK. As I type this I have no network - I'll restart the
    > DHCP client before posting.
    >
    > There don't appear to be any messages in the event logs relating to
    > this, although the system logs have recorded a few warning messages
    > about the "Aegis Protocol (IEEE 802.1x_ v2.3.1.9 service" failing to
    > start (this machine is not using wireless - good old cat5e). There are
    > also some warnings about TCP/IP reaching the security limit imposed on
    > the number of concurrent TCP connect attempts. None of these
    > correspond exactly with when I have problems. If I repair the network
    > without restarting the DHCP client, I get a warning saying:
    > "Your computer was not able to renew its address from the network
    > (from the DHCP Server) for the Network Card with network address
    > 0015F2D346AB. The following error occurred:
    > The semaphore timeout period has expired. . Your computer will
    > continue to try and obtain an address on its own from the network
    > address (DHCP) server."
    > There was also a warning earlier today that read:
    > "The server could not bind to the transport \Device
    > \NetBT_Tcpip_{3CEC7C87-EFF1-4E16-980A-4004499DEE28}."
    >
    > This does not appear to be a NIC problem - I've tried the second
    > onboard NIC and get exactly the same symptoms.
    >
    > Can anyone help me?
    >
    > One last thing to note - it appears that I can only keep the network
    > up and running for a few moments at a time right now.
    >
    > Here's hoping - Adam...
    >
    Charlie Russel - MVP, Mar 2, 2007
    #4
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. =?Utf-8?B?SGVpbkQ=?=

    Wireless DHCP clients cannot obtain an IP address from the DHCP se

    =?Utf-8?B?SGVpbkQ=?=, Jan 8, 2006, in forum: Wireless Networking
    Replies:
    0
    Views:
    2,812
    =?Utf-8?B?SGVpbkQ=?=
    Jan 8, 2006
  2. vigi98
    Replies:
    0
    Views:
    4,235
    vigi98
    Jul 15, 2003
  3. =?Utf-8?B?V1NuaXBlcw==?=

    Setting up WDS network with Static, but still need DHCP on client

    =?Utf-8?B?V1NuaXBlcw==?=, May 26, 2006, in forum: Wireless Networking
    Replies:
    3
    Views:
    4,370
    =?Utf-8?B?V1NuaXBlcw==?=
    May 26, 2006
  4. sonicgravy
    Replies:
    0
    Views:
    1,416
    sonicgravy
    Nov 13, 2006
  5. dantheterpsfan

    DHCP Client issues

    dantheterpsfan, Jun 1, 2010, in forum: General Computer Support
    Replies:
    0
    Views:
    1,199
    dantheterpsfan
    Jun 1, 2010
Loading...

Share This Page