Failure to Obtain IP Address Via DHCP (Error 1003)

[Karl Hennermann]

Hi,
I have Windows NT 4.0 with Service Pack 6 in an Ethernet (NT/Netware)
and configured as a DHCP client.
When I start one of the NT systems, I see the following message :

The DHCP client could not obtain an IP address.

If you want to see DHCP messages in the future,
choose YES, otherwise choose NO.

The Event log shows an Error ID 1003:

DHCP failed to obtain a lease for the card with
network address <12-digit hexadecimal media access
control address of the local network adapter>. The
following error occurred: The semaphore timeout
period had expired.

According to the MS Knowledge Base this happens in Token Ring
Environments with NT4/SP2 (Article Q163383) and is caused "by the way
that Tcpip.sys read the registry value that indicates that source
routing should be used." (MS)

MS suggests to change a RegKey
(HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\
Tcpip\Parameters\ArpAlwaysSourceRoute) to 1.
As I said, I have neither Token Ring or SP2, I tried anyway, but it
didn't help.

The NIC is working, I can access Netware Services via IPX/SPX and I can
also see the other NT Workstations, I just don't get an IP address. I
also cant't PING any Server.

Any ideas??

Thanks a lot!

Karl
______________________________
henne...@bwl.uni-muenchen.de

[Markus Fischer]

[fu'2 comp.os.ms-windows.nt.admin.networking]

In article <3950C844...@bwl.uni-muenchen.de>,

Karl Hennermann <henne...@bwl.uni-muenchen.de> wrote:
>I have Windows NT 4.0 with Service Pack 6 in an Ethernet (NT/Netware)
>and configured as a DHCP client.
>When I start one of the NT systems, I see the following message :
>
> The DHCP client could not obtain an IP address.
>
> If you want to see DHCP messages in the future,
> choose YES, otherwise choose NO.

Just curious: Have you properly set up an dhcp server ?
Does any other dhcp client work without problems ? Does your
network work on the NT machine if you statically enter the
network configuration ?

kind regards,
Markus

--
Markus Fischer, http://josefine.ben.tuwien.ac.at/~mfischer/
EMail: mfis...@josefine.ben.tuwien.ac.at
PGP Public Key: http://josefine.ben.tuwien.ac.at/~mfischer/C2272BD0.asc
PGP Fingerprint: D3B0 DD4F E12B F911 3CE1 C2B5 D674 B445 C227 2BD0
- Free Software For A Free World -

[Ralf Horn]

Karl,

DHCP uses broadcasts which are usually not forwarded by a router.
Is the DHCP-Server in the same segment as the clients ??
Also you are writing that you cannot ping the server ???
I guess, you are just using IPX/SPX for the communication and you
have a general problem with IP.

First you should be able to ping the servers (check router, client-settings
etc....)
Next, for a test I would put a client in the same physical segment as the
DHCP-Server.
If this works, the DHCP-Server is configured right.
If the Server and Client are in a different IP-Subnet, use the
DHCP-Relay-Service. This converts
broadcasts in directed IP-Datagrams to the DHCP-Server which are forwarded
by the IP-Routers.
It is also possible to use IP-Helper-addresses on routers.

Hope this helps

Ralf Horn
Wertheim

"Karl Hennermann" <henne...@bwl.uni-muenchen.de> schrieb im Newsbeitrag
news:3950C844...@bwl.uni-muenchen.de...
> Hi,

> I have Windows NT 4.0 with Service Pack 6 in an Ethernet (NT/Netware)
> and configured as a DHCP client.
> When I start one of the NT systems, I see the following message :
>
> The DHCP client could not obtain an IP address.
>
> If you want to see DHCP messages in the future,
> choose YES, otherwise choose NO.
>