Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
More truble after upgrade to R5 4
- Thread starter keke6608
- Start date
-
2
- #2
If I understand correctly. you have an SBS2k3. turn off BOOTP server in Manager. This is well known with SBS2k3
Jamie Green
ACA:Implement - IP Office
ACS:Implement - IP Office
Football is not a matter of life and death-It is far more important!!!!
Jamie Green
ACA:Implement - IP Office
ACS:Implement - IP Office
Football is not a matter of life and death-It is far more important!!!!
- Thread starter
- #4
Yes, we're running Server 2003, thanks for your advice Jamie.
The System Event Log shows that the DHCP service was stopped. I tried restarting the service but stopped straight away saying that another Server was on the network, pointing to the PC that has IPO installed on it.
So, is there a particular way to turn off the BOOTP service in Manager? I can untick the boxes in BOOTP for our system here onsite, but have a few other connections for other sites, do they need to be unticked too, or am I looking in the wrong direction altogether?
Thanks very much for your help Jamie
The System Event Log shows that the DHCP service was stopped. I tried restarting the service but stopped straight away saying that another Server was on the network, pointing to the PC that has IPO installed on it.
So, is there a particular way to turn off the BOOTP service in Manager? I can untick the boxes in BOOTP for our system here onsite, but have a few other connections for other sites, do they need to be unticked too, or am I looking in the wrong direction altogether?
Thanks very much for your help Jamie
-
1
- #5
Put this in your registry:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DHCPServer\Parameters] "DisableRogueDetection"=dword:00000001
This will prevent the SBS2003 to stop the dhcp service by bootp or another dhcp server
ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DHCPServer\Parameters] "DisableRogueDetection"=dword:00000001
This will prevent the SBS2003 to stop the dhcp service by bootp or another dhcp server
ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
-
1
- #6
You can add this in the registry of the DHCP server and restart the service to disable the rogue detection that makes it shutdown.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DHCPServer\Parameters]
"DisableRogueDetection"=dword:00000001
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DHCPServer\Parameters]
"DisableRogueDetection"=dword:00000001
Same thoughts and the same solution
ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
mattKnight
Programmer
please can you confirm if this is a DELL pc?
FWIW, I'd turn off BOOTP on the manager PC, rather than turn off rogue detection on the DHCP server - rogue detection is doing it's job correctly, it is the IPO manager that causes the issue. I suspect that the BOOTP server responds incorrectly to DHCPDISCOVER packets and this is what causes the issue
Take Care
Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
FWIW, I'd turn off BOOTP on the manager PC, rather than turn off rogue detection on the DHCP server - rogue detection is doing it's job correctly, it is the IPO manager that causes the issue. I suspect that the BOOTP server responds incorrectly to DHCPDISCOVER packets and this is what causes the issue
Take Care
Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
I do not agree with this !
Only the SBS2003 has this problem
Very often this is the only server used in an office
Why ? because it is complete and there is no need for another server
Turning off rogue detection does the job
If you have turned off bootp then it is all alright untill your college comes in has it not turned off and the dhcp server stops working
I had this even yesterday, no more dhcp !
It happens every time
By turning the rogue detection of on the server will prevent stopping the dhcp service
ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
Only the SBS2003 has this problem
Very often this is the only server used in an office
Why ? because it is complete and there is no need for another server
Turning off rogue detection does the job
If you have turned off bootp then it is all alright untill your college comes in has it not turned off and the dhcp server stops working
I had this even yesterday, no more dhcp !
It happens every time
By turning the rogue detection of on the server will prevent stopping the dhcp service
ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
mattKnight
Programmer
>Only the SBS2003 has this problem
Correct, because only the SBS2003 DHCP server has rogue detection built-in. 2003 Std, Enterprise and web editions do not.
>Since BOOTP originally was used as an DHCP server before DHCP was around it doesn't do anything wrong by answering to the requests.
Wrong, the BOOTP protocol uses the same ports and a very similar packet structure. It has the same layout, but the BOOTP can have zero vendor options, the DHCP packet must have at least 1 option field. This mandatory field is called MessageType and can contain the following values.
[ul]
[li]DHCPDISCOVER[/li]
[li]DHCPOFFER[/li]
[li]DHCPREQUEST[/li]
[li]DHCPACK[/li]
[li]DHCPNAK[/li]
[li]DHCPDECLINE[/li]
[li]DHCPRELEASE[/li]
[li]DHCPINFORM[/li]
[/ul]
So, the BOOTP packets can be differentiated from the DHCP packets. That is if they have an option called MessageType they are a DHCP packet, if not BOOTP.
So if the manager BOOTP server responds to a DHCP packet - it is doing so incorrectly
I go back to my statement, that the DHCP server is responding to this situation correctly. The cause of the error is a bug in the BOOTP server in manager.
by turning of DHCP rogue detection, you are fixing the symptom, not the cause. If you are aware of that and are willing to accept that then that is OK, however, blindly disabling something without understanding what you are doing is foolish.
<done ranting now>
Take Care
Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
Correct, because only the SBS2003 DHCP server has rogue detection built-in. 2003 Std, Enterprise and web editions do not.
>Since BOOTP originally was used as an DHCP server before DHCP was around it doesn't do anything wrong by answering to the requests.
Wrong, the BOOTP protocol uses the same ports and a very similar packet structure. It has the same layout, but the BOOTP can have zero vendor options, the DHCP packet must have at least 1 option field. This mandatory field is called MessageType and can contain the following values.
[ul]
[li]DHCPDISCOVER[/li]
[li]DHCPOFFER[/li]
[li]DHCPREQUEST[/li]
[li]DHCPACK[/li]
[li]DHCPNAK[/li]
[li]DHCPDECLINE[/li]
[li]DHCPRELEASE[/li]
[li]DHCPINFORM[/li]
[/ul]
So, the BOOTP packets can be differentiated from the DHCP packets. That is if they have an option called MessageType they are a DHCP packet, if not BOOTP.
So if the manager BOOTP server responds to a DHCP packet - it is doing so incorrectly
I go back to my statement, that the DHCP server is responding to this situation correctly. The cause of the error is a bug in the BOOTP server in manager.
by turning of DHCP rogue detection, you are fixing the symptom, not the cause. If you are aware of that and are willing to accept that then that is OK, however, blindly disabling something without understanding what you are doing is foolish.
<done ranting now>
Take Care
Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
mattKnight
Programmer
No
Take Care
Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
Take Care
Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
Does the same happen with SBS2008 ?
I agree it is not the best solution but it works well
ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
I agree it is not the best solution but it works well
ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
mattKnight
Programmer
>Does the same happen with SBS2008
I don't know, we haven't got that
>I agree it is not the best solution but it works well
Indeed it does hide the problem.
Take Care
Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
I don't know, we haven't got that
>I agree it is not the best solution but it works well
Indeed it does hide the problem.
Take Care
Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
It does not hide it
It solves the problem.
Microsoft should make this an option to turn rogue detection on or of
Like i said, most SBS2003 server are used in a situation where only one server is used
Very rare there is a SBS2003 used in a situation where also another domain controller is used
ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
It solves the problem.
Microsoft should make this an option to turn rogue detection on or of
Like i said, most SBS2003 server are used in a situation where only one server is used
Very rare there is a SBS2003 used in a situation where also another domain controller is used
ACS - Implement IP Office
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!
mattKnight
Programmer
>It does not hide it
>It solves the problem.
<grrrr>
>Microsoft should make this an option to turn rogue detection on or of
They have done... Through the registry.
> Like i said, most SBS2003 server are used in a situation where only one server is used.
Windows Servers are not the only device that can act as DHCP servers
>Very rare there is a SBS2003 used in a situation where also another domain controller is used
Umm. but you can still do that...
Take Care
Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
>It solves the problem.
<grrrr>
>Microsoft should make this an option to turn rogue detection on or of
They have done... Through the registry.
> Like i said, most SBS2003 server are used in a situation where only one server is used.
Windows Servers are not the only device that can act as DHCP servers
>Very rare there is a SBS2003 used in a situation where also another domain controller is used
Umm. but you can still do that...
Take Care
Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.
Just tested MS RogueDetection and got a response in my Manager, looking at the packet in Wireshark it seems like it should be considered posible to be a bootp packet.
Guess one could argue that not getting an optional 64 byte vendor field should make you understand that it's not a bootp packet since I only get 20 byte from the Rogue Detector.
Guess one could argue that not getting an optional 64 byte vendor field should make you understand that it's not a bootp packet since I only get 20 byte from the Rogue Detector.
- Thread starter
- #20
Thanks everyone for your advice. I understand what MattKnight is saying - the registry addition will only fix the symtom... is there a way of sorting out the BOOTP issue then with IPO?
I'll get the registry changed on the Server soon enough
Thanks very much for the help, much appreciated!
I'll get the registry changed on the Server soon enough
Thanks very much for the help, much appreciated!
- Status
Similar threads
