This is hearsay, and I have not tested it.
I am told that the 169.x.x.x is what gets assigned if the box cannot find a DHCP server to give it an address.
In any case, try this line of testing:
(Note that if you are not the system admin, youwill have to have the system admin do most of this.)
Check that the DHCP server is not out of addresses. If it is, it needs more.
If there were enough addresses, next suspect the cables. Try physically swapping the "bad" machine with another in the room, and see if it gets an address when you turn it on. If so, the cables between the computer and the hub are bad somewhere, or the hub port is bad. First try moving to another port on the hub. If that does not work, check and possibly replace the cables. (Check that wires did not pull out of the RJ-45 plugs -- this is common when the plugs were not crimped down hard enough.)
If it still does not get an address, get an address from the DHCP pool and manually exclude it from the pool.Put in the static address (and subnet mask) and reboot. See if you can ping the rest of the network. If not, the ethernet port of the machine is probably bad.
If you can ping around, if the machine can have the address long term, you are done. If the address needs to go back to the DHCP pool, you will need to look at the tcp/ip controls and try to figure what is wrong with DHCP.
Good luck.