We actually had this happen before several times while installing DCPs, it is very common. It is a Ethernet connectivity issue of some kind imho. Please confirm the Ethernet connection between your DCP and the TA server is using the ENET port. Check speed and duplex settings match or use auto/auto. You should be able to login to the associated Linux TA server using putty and ping the DCP over this link. (Assuming your TA server is running, which may be a problem..) Use a traceroute to confirm you are pinging the DCP over the right TA server interface. Make sure the TA server's firewall or SE Linux isn't blocking the connection. Confirm the ATNET interface is also connected to an Ethernet switch. ATNET is like the voice vlan. ENET is a private network with two hosts, the TA and the DCP. The DCP obtains its ENET IP address from the TA via a DHCP discover message. Depending on your system version, the TA handles its DHCP server a little differently. Once the DCP gets it's ENET IP, it downloads its config from the TA. Much of the DCP config info exists in the TA's HOSTS file. If layer 2 connectivity looks OK, check the layer 3 addresses assigned in the HOSTS file of the TA. Be very careful making changes if you aren't comfortable hacking Linux. You can really cause a disaster here if you make a mistake. Sound like your DCP is down anyway, so I hope this helps somewhat.