Hi all,
Some background first.
VLAN 100 - Data. Windows SBS2011 (Windows 2008 Server) DHCP server, giving out ip in range 192.168.100.x
VLAN 200 - Voice, MITEL 3300 giving out ip in range 192.168.200.x to 5330 phones.
Option 125 set as below. Option 43 also the same (but in hex)
id:ipphone.mitel.com;sw_tftp=192.168.200.253;call_srv=192.168.200.253;vlan=200;l2p=6;dscp=46v46s26
The issue :-
Since changing the Windows server from Windows 2003 to 2008, each morning, most computers that plug into the back of the 5330 phones pick up an ip from the MITEL unit instead of the windows server. If I do a release/renew on the computer, it gets the correct ip from the windows server.
It's as if the phone is tagging the DHCP request from the computer with VLAN 200 tag, when it should not be tagging it at all. This only happens when the computer is either first plugged in to the phone OR if the computer is plugged in but the phone is disconnected/reconnected to the switch/power cycled.
I know the switch tagging is correct.
The weird bit I can;t get my head around is that this did not happen on Windows 2003 and has only happened since the 2008 DHCP has been installed. The option 43 has been added in order to try to fix this issue - I gather this is normal now anyway.
I can only think it is a bug in the phone firmware that is not now compatible 100% with the new Windows DHCP?? The phones say Main ver 01.05.00.41 from 2009.
Any one got any ideas on this?
THe only thing I can think of as a workaround is to set the "Client's class ID must match Name" to true. Can you please review my two DHCP pics and see if I am coorect in the assumption that the DHCP "Name" on the MITEL must match the scope option of ipphone.mitel.com as shown in the Windows scope option 125? Or am I looking at this wrong.
Thank you
Graham