Big DUH!! programing IPO DHCP

[jml2665]

just a heads up if you ever run into this, I programed my IPO static IP using xxx.xxx.xxx.48 and my VMPro/KeyServer xxx.xxx.xxx.49, started having problems when using IP phones (DHCP) and eventually my VMPro system was crashing occasionally. Come to find out the phones were grabbing the .49 address which killed the KeyServer and eventually I had to reboot. IP Phones continued to work but I was getting IP conflicts on the VMPro/KeyServer. I finally changed the IP's on VMPro to .30 and IPO to .31, and allocated enough addresses for the amount of IP phones and now all works fine. Moral to this story, if you are using static IP's and IP Phones with DHCP (IPO Controlled), setup your VPPro/KeyServer with an IP lower then your IPO

 

[IPGuru]

or set the IP off the VM PC above the range allocated by the IPO, This is why the IPO in default only allocates 200 DHPC addresses, leaving 202-254 free for static IP's

a bigger word of warning DO NOT use the IPO as a DHCP server if you have more than about 5 IP Phones!
the DHCP server can get confused if it recieves multiple requests(IP Phones re-requesting IP after a config change) & can issue duplicate IP Addresses.

 

[MrIPO]

This would be common practice, to NOT get the issue you are having.

Remember as well the IPO can only manage 5 concurrent DHCP requests, which is why it is not recomended as a DHCP server in a large enviroment.

Umm anotherprivatebuild !!!