DHCP Address Assignment Delay

I am noticing an initial delay upon logging in with Windows XP trying to
acquire a DHCP assigned IP address when my network interface is setup to
automatically obtain one. In the Event Viewer, it is giving an Error ID of
1003 from the source DHCP. Windows XP seems to attempt to acquire an IP
address but times out, assigns me the auto-configured IP, and then contacts
my router (setup as a DHCP server) for an IP address. The initial attempt
causes a 5-10 second delay upon logging into Windows till it finally talks to
my router. I have been able to speed this up considerably and remove the
Event Warning by configuring my network interface with a static IP.

It seems that Windows XP is initially trying to contact some other DHCP
server source other than the DHCP on my router. How can I configure Windows
with my own DHCP Server IP to initially connect to?

I am using a freshly installed Windows. I am full up to date with SP3 and
additional updates. My external networking hardware is a ADSL 6Mbit bridged
with a Linksys BEFSR41. My internal network is a nForce 680i SLI motherboard
networking interface.

Hi
The BEFSR41 is an old Router and it does not do IP reservation, so leave it
with a static IP if it works. Performance wise it does not make a difference
if it connected.
Otherwise, borrow an Other Router from a friend to rule out Router, or
computer problem.
Jack (MS, MVP-Networking).

"redsolarmoon" wrote in message
...
I am noticing an initial delay upon logging in with Windows XP trying to
acquire a DHCP assigned IP address when my network interface is setup to
automatically obtain one. In the Event Viewer, it is giving an Error ID of
1003 from the source DHCP. Windows XP seems to attempt to acquire an IP
address but times out, assigns me the auto-configured IP, and then
contacts
my router (setup as a DHCP server) for an IP address. The initial attempt
causes a 5-10 second delay upon logging into Windows till it finally talks
to
my router. I have been able to speed this up considerably and remove the
Event Warning by configuring my network interface with a static IP.

It seems that Windows XP is initially trying to contact some other DHCP
server source other than the DHCP on my router. How can I configure
Windows
with my own DHCP Server IP to initially connect to?

I am using a freshly installed Windows. I am full up to date with SP3 and
additional updates. My external networking hardware is a ADSL 6Mbit
bridged
with a Linksys BEFSR41. My internal network is a nForce 680i SLI
motherboard
networking interface.

Hi
The BEFSR41 is an old Router and it does not do IP reservation, so leave it
with a static IP if it works. Performance wise it does not make a difference
if it connected.
Otherwise, borrow an Other Router from a friend to rule out Router, or
computer problem.
Jack (MS, MVP-Networking).

"redsolarmoon" wrote in message
...
I am noticing an initial delay upon logging in with Windows XP trying to
acquire a DHCP assigned IP address when my network interface is setup to
automatically obtain one. In the Event Viewer, it is giving an Error ID of
1003 from the source DHCP. Windows XP seems to attempt to acquire an IP
address but times out, assigns me the auto-configured IP, and then
contacts
my router (setup as a DHCP server) for an IP address. The initial attempt
causes a 5-10 second delay upon logging into Windows till it finally talks
to
my router. I have been able to speed this up considerably and remove the
Event Warning by configuring my network interface with a static IP.

It seems that Windows XP is initially trying to contact some other DHCP
server source other than the DHCP on my router. How can I configure
Windows
with my own DHCP Server IP to initially connect to?

I am using a freshly installed Windows. I am full up to date with SP3 and
additional updates. My external networking hardware is a ADSL 6Mbit
bridged
with a Linksys BEFSR41. My internal network is a nForce 680i SLI
motherboard
networking interface.