David Overton's Blog and Discussion Site
This site is my way to share my views and general business and IT information with you about Microsoft, IT solutions for ISVs, technologists and businesses, large and small
Forums » Microsoft Products » SBS 2003 » DHCP stopping

This blog is purely the personal opinions of David Overton. . If you can't find the information you were looking for e-mail me at admin@davidoverton.com. If you want to narrow down the content consider these links:

Wikio - Top Blogs - Technology

DHCP stopping

Previous | Next
Latest post Mon, Apr 7 2008 10:53 PM by David Overton. 1 replies.

  • Tue, Apr 1 2008 9:15 PM

    DHCP stopping

    Reply |Contact

    Hello All

    I am having a problem with DHCP it keeps stopping with the following error:

    Event Type: Error
    Event Source: DhcpServer
    Event Category: None
    Event ID: 1053
    Date:  02/03/2008
    Time:  16:57:56
    User:  N/A
    Computer: SERVER
    Description:
    The DHCP/BINL service on this computer running Windows Server 2003 for Small Business Server has encountered another server on this network with  IP Address, 192.168.100.1, belonging to the domain: .

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 00 00 00 00               ....   

    I have two NICs installed as follows:

    ISP Network connection: 192.168.1.3

    Server Local network connection:  192.168.100.1

    Ther are no other servers on the network ad the router has its DHCP disabled. It seems that it is seeing the other NIC as another server even though there is no connection between the two networks, other than the fact that the two NICs reside in the same machine.

    Any help is greatly appreciated.

     

    Paul

     
    • Post Points: 21

  • Mon, Apr 7 2008 10:53 PM In reply to

    Re: DHCP stopping

    Reply |Contact

    Paul,

     

    I would be tempted to load a network sniffer to be 110% sure, otherwise, if I was sure, log a call with MS - if there really is no other DHCP source anywhere and the 2 NICs are not plugged into the same network, for example, then it sounds like a bug.

    ttfn

    David
    • Post Points: 5
Page 1 of 1 (2 items) | RSS

(c)David Overton 2006-8