IP Office 3.2 and DHCP SBS 2003 1

[realestategod]

HELP! Please, anyone?

We just upgraded our IP office to 3.2 and now for some reason our network server (win Small Bisiness 2003) is thinking that the voicemail server or the phone system is acting as a DHCP server. This is shutting down our DHCP server for the network.

Has anyone experienced this? AVAYA is telling our service company that it is not an AVAYA issue even though our server says different. The DHCP server is not running on the Voicemail server and according to Manager, it is disabled on the phone modules.

The only way for me to restart the DHCP server on our network is to unplug the voicemail server from the switch. It then will eventually stop DHCP services again. So it is abviously an AVAYA issue, hardware or software.

Help Please!!!!!


Chris

 

[Markee2171]

SBS2003 has a very weak DHCP server, it basically bows down in the presence of anything it can't argue with

check again that you have in fact disabled the DHCP options in the system, completely of, not just set to different range or dial in only - also make sure that the system has reooted then do a power cycle

HTH

Mark

 

[jml2665]

check in manager, under the System >> LAN1 tab, make sure DHCP Mode is ticked "disabled

 

[realestategod]

:-(

Thanks for responding so quickly. I have check the above, and still nothing.

 

[Markee2171]

check your sbs event logs, see where the other dhcp server is coming from

it is physically possible to have more than one dhcp server on a network ( for resiliency )

use the advanced logging in dhcp on the server to assist in this

Mark

 

[kurthansen]

If you unplug the voicemail server and then it works it sounds like you have DHCP turned on on that server, not the IPO.

Also make sure you don't have internet connection sharing turned on the VM server.

 

[mattKnight]

As Kurthansen says ICS can cause this.

There is a rumour (from the distributor we use) that this issue is caused by Manager, expecially in the 3.2 software. I have seen similar behaviour from our SBS 2003 server. If you look in the event log it will list the IP address of the "rogue" DHCP server.

<standard registry disclaimer applies i.e. if you break it, you get to keep both bits....>

this is supposed to "fix" (and I use fix loosely) the issue

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DHCPServer\Parameters] "DisableRogueDetection"=dword:00000001

Take Care

Matt
If at first you don't succeed, skydiving is not for you.

 

[realestategod]

Thanks Matt.

 

[realestategod]

Matt,

It worked I think! I will know more in a few days to see if it happens again. If you do not hear from me, then it did the trick. I wish Avaya could have figured it out rather than saying it was not their issue. Maybe there is a fix in 4.0.

Thanks again to all who replied! I love this site.

 

[VTTony]

Just another note on the issue, I found that disabling the BootP option in Manager did the trick on my system. Checking the IP Address as mentioned before on the thread is definitely a great suggestion, since the problem may be caused by a Manager workstation and not the IP Office unit itself.

 

[tlpeter]

so the manager application is the problem ?
that is very very strange


ACA - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[realestategod]

Well, so far, so good. I have not had the DHCP services shut down since the reg fix. Thanks. Were there any side effects I should be looking out for after the fix?

Chris

 

[mattKnight]

>Were there any side effects I should be looking out for after the fix?

Yep - Rogue DHCP servers....

>I found that disabling the BootP option in Manager did the trick on my system.

No great suprise there! DHCP and BOOTP are very closely related. It may be that the manager produces a malformed bootp packet undefr certain conditions???


Take Care

Matt
If at first you don't succeed, skydiving is not for you.

 

[VTTony]

> so the manager application is the problem ?

Well, it can be. BOOTP was the predecessor to DHCP, so they are closely related as Matt mentioned. Checking the logs for an IP address will give you the offender for sure.

 

[etherbadger]

I too have had to disable bootp on a single manager installation. It was on a laptop and everytime it came back to our network it would take out the w2k3 dhcp service. We've got 4 or 5 people who run manager, plus it stays up full time on the VM server but its only 1 laptop that causes issues.

 

[jamie77]

Manager 4.0.7 also does this.

We've just rolled in a new W2K3 SBS and Manager 4.0.7 causes this.

Don't really fancy playing with reg hacks on our new Server though, so will just have to cope with shutting down Manager when I reboot the server!!!!!!!!

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Fooball is not a matter of life and death-It is far more important!!!!

 

[intrigrant]

It is because Manager sends BOOTP requests to the broadcast address during startup.
The SBS DHCP service then think there is another DHCP server in the network and the service stops with event ID 1053.
This maybe a problem caused by Manager ( says Microsoft ) but in my opinion it is a problem in the DHCP service of Microsoft as other versions of DHCP servers do not have this problem ( yet? ).

You could raise a case by Avaya and ask them to change the Manager so it will not send the broadcasts during startup, or ask Microsoft to change the SBS DHCP service.

I think asking Avaya will be the best option.

 

[jamie77]

It never caused a problem with our old NT4 server.

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

http://www.alliedcom.co.uk

Fooball is not a matter of life and death-It is far more important!!!!

 

[intrigrant]

It is only a problem with a MS2003 SmallBusinessServer

 

[realestategod]

I would think Avaya would do something about this since more and more business are going with SBS from what I have seen. SBS may have its limitations, but it is a very powerful all in one package for those who are on a budget.

The problem for us was not just on reboot, but randomly throughout the day or night. I would have to unplug the vmserver from the switch, restart DHCP server and then plug the VM server back in. It may be ok for a few hours, then I would get the e-mail that the DHCP services has stoped. We no longer have the issue since the fix. What is the difference in 3.2 to have this all start up. why did the older versions not have this issue?

I guess my biggest question is why is this information (warning) not know to Avaya or on their site? The tech who came out to "fix" our issue, said that after hours of looking into the issue, the issue had nothing to due with the Avaya system at all. So we got this huge bill from them for them doing nothing at all. They even tried to add a service call charge and tried to charge for intalling something. The nerve of some people. Here I ask a question and get a response and fix the issue in one hour. Amazing. I do not mind paying for something that makes sense, even if the guy did what I did so I didn't have to, I would have gladly paid him for an hour or so, but I had to research and fix it myself when he failed. I think I mught just bill him for wasting my time. I heard a person ended up billing his doctor for the lengthy wait in the waiting room. The doctor refused to pay, the guy took him to court and won. The lesson from that is that everyone's time is valuable.

Thanks again for the comments. I think I would go crazy not to mention broke without this service.