Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Computing > Windows 64bit > Network issues - DHCP client?

Reply
Thread Tools

Network issues - DHCP client?

 
 
adamomitcheney@kiwis.co.uk
Guest
Posts: n/a
 
      03-01-2007
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...

 
Reply With Quote
 
 
 
 
Kue2
Guest
Posts: n/a
 
      03-01-2007
Do you have the latest Marvel drivers?
I would try that first

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


<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> 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...
>


 
Reply With Quote
 
 
 
 
Aaron Kelley
Guest
Posts: n/a
 
      03-01-2007
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

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> 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...
>


 
Reply With Quote
 
Charlie Russel - MVP
Guest
Posts: n/a
 
      03-02-2007
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


<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> 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...
>


 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Need help setting up a wireless DHCP behind a wired non-DHCP network? sonicgravy Hardware 0 11-13-2006 07:45 PM
Dhcp Relay Agent And Acl On Sw 3750, DHCP Relay Agent and ACL on Sw 3750 Vimokh Cisco 3 09-06-2006 02:16 AM
Wireless DHCP clients cannot obtain an IP address from the DHCP se =?Utf-8?B?SGVpbkQ=?= Wireless Networking 0 01-08-2006 03:41 PM
run > ipconfig > net stop dhcp then > net start dhcp Fayza Computer Support 3 05-12-2004 07:10 PM
if Active Directory no DHCP? or: Where ist my DHCP Ingo Hauf Computer Support 2 10-18-2003 02:25 PM



Advertisments