What system are these installed on? is your tftp server up? If these are new phones, they will no doubt need to be updated....and if the tftp server IP isnt set, they wont know where to get the files from.
a 6ya Technician can help you resolve that issue over the phone in a minute or two.
Best thing about this new service is that you are never placed on hold and get to talk to real repair professionals here in the US. click here to Talk to a Technician (only for users in the US for now) and get all the help you need. Goodluck!
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
Your phone needs an IP address in order to communicate. Normally, it asks a "host" for that IP. You need to be connected to the internet for it to connect to the normal host, and your router should be willing to give it that IP address. "DHCP" is how devices ask for and get an IP address.
Put 'Hard Drive C:' before 'Network' in the boot order
(If the hard drive does not appear in the boot order, that's why the PXE network boot agents start)
Note : Check that the hard drive is seen in the BIOS setup
PXE (pronounce Pixie) is an agent used to boot on to the network
It's using the DHCP protocol to localise a server where the image of the OS is located
In order to PXE boot press F12 at startup or configure the boot order in BIOS to display 'Network' before 'Hard Drive C:'
If, for any reason, the hard drive is not seen the computer will attempt to boot on the network controller.
That is caused by the hard drive is missing, unplugged or failed
If your computer is working fine then, disable PXE boot in BIOS or remove from 1st boot option. This is a LAN (network) boot option. It can't find a DHCP server, and is usually used to load an OS image.
For the most part not a real problem. More of a warning. Some corporate models use PXE to mass image.
If both phones are showing the same symptoms then it probably means that your DHCP server is down or not configured properly. If the phones are on a separate VLAN and you have recently upgraded or replaced your network switch then it could be misconfigured as well - specifically it may require you to configure a DHCP helper address.
I don't have any experience with this product but I am 99.9% sure your problem is with Option 67. This path is from the root as defined for the TFTP server, i.e. root for the TFTP service is not the same as root for the server proper.
You didn't provide any information about your network which is ALWAYS required to provide any type of help, not to mention a solution.
"Failed to get boot parameters via DHCP, xxx seconds until reboot" simply means that the computer isn't getting an IP address from your router. Setting up your router is another entirely separate topic.
This is pretty simple though, one of three things is happening:
1. Your router is not properly configured to provide DHCP to the phone.
2. Your network cable is bad.
3. Your phone is bad (most likely the RJ45 port since the phone seems to work otherwise).
You can check for bad ports or cables by checking the port status within the router. If the port is lit up, most likely the cable and phone port are fine. This is not 100% though, replacing the cable should always be a consideration even with a lit port.
It is trying to boot from a network. You need to get it to boot from the optical drive (CD/DVD drive), there's no other way of installing the os, unless you can get another identical machine to load it with. If it doesn't recognize the optical in the boot menu, then you may have been more than a hard drive crash.