What is generating that log?
Interesting that you have a 0.0.0.0 IP unless you’ve removed it?
TFTPD32 is giving it, I was copying the instructions on the link above and it said to leave WIN/DNS as 0.0.0.0
Slightly confused how it is receiving a DHCP request for an IP that doesn’t exist and is outside your subnet…
This is what it said:
Under DHCP server within the tftp32 program, enter the following and click SAVE.
IP pool starting address as 192.168.1.2
Size of pool as 250 (If your doing multiple phones, this just makes sure your phones are able to receive an IP address.)
Default router as 192.168.1.1
Mask as 255.255.255.0
Additional option, enter 150 in the first box, then 0x0101A8C0 in the second box (This number is 192.168.1.1 in Hexadecimal format).
I assume you already have a DHCP on your network and you’re probably having clashes 
It’s plugged directly into my PC
Ah. Change your address pool to 192.168.0.2 and increase the pool to 150 not 50 addresses
It’s not uncommon for a device to request the last IP it had… the DHCP server is just supposed to reject that and offer a new one, so that log shouldn’t be an error unless TFTPD32 is slightly broken…
1 Like
And the option to 0x0100A8C0 as well in that case.
1 Like
PC is set to
192.168.1.1
255.255.255.0
DNS
192.168.1.1
Power is coming from POE switch so could be that?
Yup, you’ll need to change the address range otherwise the client is requesting an address completely out of the range. It is easier to just move the range so the DHCP can offer that address rather than hoping negotiation will prove successful.
Handset doesn’t do anything other than a mute speaker line 1 flash then screen stays blank.
the cisco images up top no longer show
I think it’s a brick now 
Yeah sounds like it unfortunately 
If you want a less official approach to test it, boot up an appropriate IOS image on a Cisco Router on GNS3 and find a configuration guide.
Start reading? https://www.cisco.com/c/en/us/support/collaboration-endpoints/unified-ip-phone-7941g/model.html
I think I will config one of my switches to have 192.168.1 instead of .0 and pull if from the network and then see what happens
1 Like
That’s done it’s uploading now, so that’s sorted the connection etc let’s see if I got the right image lol
1 Like
It’s working I have access but there is a padlock next to config so I can’t change the IP
1 Like
It’s been provisioned by DHCP so I assume it’s preventing the end-user from screwing up the config. Either leave it like that and just rely on your DHCP server to give it the correct IP or see if you can restart it without DHCP & TFTP (in standalone mode if such thing exists) and see if that unlocks the option - you might need to reset it one more time.
**# should unlock the padlock… when in the settings menu
Jason
2 Likes
Cheers mate, literally just googled and found that.
Changed it now.
1 Like