Event Viewer: System Error Dhcp or Ipnathlp

  • Thread starter Thread starter Helob
  • Start date Start date
H

Helob

I have 2 PCs home networked and hard wired to a DSL Router (D-Link
DSL-504T) for shared file/folder & ADSL connection. Both running
Windows XP Pro SP2.
What is the correct sequence of turning on the system?
1. Power supply>Router>PCs.
The Event viewer show a Dhcp Error event:1002. Is it necessary to wait
for the Router to establish the ADSL connection before turning on the
PCs? or
2. Power supply>PCs>Router.
The Event Viewer show a Ipnathlp error event:32003.
Router DHCP is enabled. In both cases, both PCs can connect
to the Internet.
Which is the correct way? 1 or 2. In either case, what is the cause of
the system error?
qTIA
 
I have 2 PCs home networked and hard wired to a DSL Router (D-Link
DSL-504T) for shared file/folder & ADSL connection. Both running
Windows XP Pro SP2.
What is the correct sequence of turning on the system?
1. Power supply>Router>PCs.
The Event viewer show a Dhcp Error event:1002. Is it necessary to wait
for the Router to establish the ADSL connection before turning on the
PCs? or
2. Power supply>PCs>Router.
The Event Viewer show a Ipnathlp error event:32003.
Router DHCP is enabled. In both cases, both PCs can connect
to the Internet.
Which is the correct way? 1 or 2. In either case, what is the cause of
the system error?
qTIA

See if this article is of any interest to you:
<http://support.microsoft.com/kb/293497>
 
Chuck,
Thanks for the prompt advise. I have read the article but
nothing is mentioned on the sequence of startup i.e. router or pc
first.

The article discusses the error message that you're seeing. You would have to
consider each startup sequence, and decide if it's advice is relevant. The
article is to answer your second question "what is the cause of the system
error?".

Your first question is a little vague. What is the power supply? Are the
computers setup as DHCP clients? What is the problem that you're seeing?
<http://nitecruzr.blogspot.com/2005/06/background-information-useful-in.html>

Without those answers, I must overburden you with details, and you have to fit
my details into the context of your problem.

In a normal installation, if the computers are running as DHCP clients, you need
to have the router powered on, and operational, before starting the computers.
If you do not, the computers (if they are Windows XP) will self assign APIPA
addresses, and they will not get connectivity with the Internet, when the router
comes online.
<http://support.microsoft.com/?id=220874>

In other words, it is not necessary to have the router establish the ADSL
connection before the computers are powered on. It is, however, necessary to
have the router online, to issue IP addresses, etc, to the computers when they
are powered on. With APIPA addresses, the computers will be able to communicate
to each other (all others that get APIPA addresses), but not to the router or to
the Internet.
 
Chuck,
Thanks for the prompt advise. I have read the article but
nothing is mentioned on the sequence of startup i.e. router or pc
first.

If the computers are running as DHCP clients, you need to have the router
powered on, and operational, before starting the computers. If you do not, the
computers (if they are Windows XP) will self assign APIPA addresses, and they
will not get connectivity with the Internet, when the router comes online.
<http://support.microsoft.com/?id=220874>

In other words, it is not necessary to have the router establish the ADSL
connection before the computers are powered on. It is, however, necessary to
have the router itself online, to issue IP addresses, etc, to the computers when
they are powered on. With APIPA addresses, the computers will be able to
communicate to each other (all others that get APIPA addresses), but not to the
router or to the Internet.
 
Back
Top