DHCP Event ID 1053

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi

DHCP Service starts and immediately stops because of event id 1053 "The DHCP/BINL Service on this Small Business Server has encountered another Server on this network with IP Address, 192.168.70.1, belonging to the Domain:". I'm running a 10.1.1.x network with DHCP Server being 10.1.1.2 and I've checked the ip of every machine in the network and i can't find one with 192.168.70.1. I have no clue what 192.168.70.1 is but its servicing my client's DHCP requests. How can I go about finding and eliminating this rogue DHCP Server

Thank
 
Hi

Is BOOTP enabled?
Maybe this will help

Problem:
========
event id 1053 "The DHCP/BINL Service on this Small Business Server has
encountered another Server on this network with IP Address, 192.168.70.1,
belonging to the Domain:"

Resolution:
==========
CAUSE:
======

This can occur if the BOOTP relay agent forwards the DHCP Offer frame from
the DHCP
server to the broadcast address (255.255.255.255) instead of forwarding the
Offer
frame directly to the client computer that requested the IP address. The
DHCP
server sees this traffic and interprets it as another DHCP server on the
same
network, which causes the DhcpServer service to fail.

A network monitor capture of this DHCP traffic will show a pattern similar
to the
following:

Frame 1 (Discover frame forwarded from the BOOTP relay agent to the DHCP
server):

DHCP Discover Source: Cisco router Destination: SBS server
Frame: Base frame properties
ETHERNET: ETYPE = 0x0800 : Protocol = IP: DOD Internet Protocol
IP: ID = 0x2543; Proto = UDP; Len: 272
UDP: Src Port: BOOTP Server, (67); Dst Port: BOOTP Server (67); Length =
252
(0xFC)
DHCP: Discover (xid=00000000)

Frame 2 (Offer frame from the DHCP server back to the BOOTP relay agent):

DHCP Offer Source: SBS server Destination: Cisco router
Frame: Base frame properties
ETHERNET: ETYPE = 0x0800 : Protocol = IP: DOD Internet Protocol
IP: ID = 0x63A3; Proto = UDP; Len: 328
UDP: Src Port: BOOTP Server, (67); Dst Port: BOOTP Server (67); Length =
308
(0x134)
DHCP: Offer (xid=00000000)

Frame 3 (Offer frame from the BOOTP relay agent to the broadcast address):

DHCP Offer Source: Cisco router Destination: 255.255.255.255
Frame: Base frame properties
ETHERNET: ETYPE = 0x0800 : Protocol = IP: DOD Internet Protocol
IP: ID = 0x2544; Proto = UDP; Len: 328
UDP: IP Multicast: Src Port: BOOTP Server, (67); Dst Port: BOOTP Client
(68);
Length = 308 (0x134)
DHCP: Offer (xid=00000000)

The DHCP server interprets Frame 3 from the BOOTP relay agent to the
broadcast
address as an offer from another DHCP server on the network, which causes
the DhcpServer service to fail.

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
<>
*** Resolution *** Jun 3 2003 8:07AM msadoff

RESOLUTION:
===========

Configure the BOOTP relay agent to forward the Offer frame directly to the
requesting DHCP client instead of to the broadcast address. For help
configuring
the router, contact the manufacturer.

For additional information about BOOTP relay, see the following article:

120932 DHCP: Spanning Multiple Subnets
http://support.microsoft.com/?id=120932


Shilpa Sinha
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Thanks. Can you elaborate further? How do i configure the bootp relay agent? Is it something i have to do on every workstation? Also, is the network monitor tool available for download? If so, where? Appreciate it

Thank yo

----- Shilpa Sinha [MSFT] wrote: ----

Hi

Is BOOTP enabled
Maybe this will hel

Problem
=======
event id 1053 "The DHCP/BINL Service on this Small Business Server has
encountered another Server on this network with IP Address, 192.168.70.1,
belonging to the Domain:

Resolution
=========
CAUSE
=====

This can occur if the BOOTP relay agent forwards the DHCP Offer frame from
the DHCP
server to the broadcast address (255.255.255.255) instead of forwarding the
Offer
frame directly to the client computer that requested the IP address. The
DHCP
server sees this traffic and interprets it as another DHCP server on the
same
network, which causes the DhcpServer service to fail

A network monitor capture of this DHCP traffic will show a pattern similar
to the
following

Frame 1 (Discover frame forwarded from the BOOTP relay agent to the DHCP
server)

DHCP Discover Source: Cisco router Destination: SBS serve
Frame: Base frame propertie
ETHERNET: ETYPE = 0x0800 : Protocol = IP: DOD Internet Protoco
IP: ID = 0x2543; Proto = UDP; Len: 27
UDP: Src Port: BOOTP Server, (67); Dst Port: BOOTP Server (67); Length =
252
(0xFC
DHCP: Discover (xid=00000000

Frame 2 (Offer frame from the DHCP server back to the BOOTP relay agent)

DHCP Offer Source: SBS server Destination: Cisco route
Frame: Base frame propertie
ETHERNET: ETYPE = 0x0800 : Protocol = IP: DOD Internet Protoco
IP: ID = 0x63A3; Proto = UDP; Len: 32
UDP: Src Port: BOOTP Server, (67); Dst Port: BOOTP Server (67); Length =
308
(0x134
DHCP: Offer (xid=00000000

Frame 3 (Offer frame from the BOOTP relay agent to the broadcast address)

DHCP Offer Source: Cisco router Destination: 255.255.255.25
Frame: Base frame propertie
ETHERNET: ETYPE = 0x0800 : Protocol = IP: DOD Internet Protoco
IP: ID = 0x2544; Proto = UDP; Len: 328
UDP: IP Multicast: Src Port: BOOTP Server, (67); Dst Port: BOOTP Client
(68);
Length = 308 (0x134
DHCP: Offer (xid=00000000

The DHCP server interprets Frame 3 from the BOOTP relay agent to the
broadcast
address as an offer from another DHCP server on the network, which causes
the DhcpServer service to fail

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
*** Resolution *** Jun 3 2003 8:07AM msadof

RESOLUTION
==========

Configure the BOOTP relay agent to forward the Offer frame directly to the
requesting DHCP client instead of to the broadcast address. For help
configuring
the router, contact the manufacturer

For additional information about BOOTP relay, see the following article

120932 DHCP: Spanning Multiple Subnet
http://support.microsoft.com/?id=12093


Shilpa Sinh
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Hi

That solution was in case BOOTP is enabled.
Can you elaborate on the type of network you have. It will lead to better
understanding of your problem.

Shilpa Sinha
This posting is provided "AS IS" with no warranties, and confers no rights.
 
Back
Top