Jump to content
XPEnology Community

HP thin client T5745 cannot acquire IP adsress .


Datinhkhach

Recommended Posts

According HP website for your T5745 you should have one of these network card:

 

Allied Telesis PCIe x1 Fast Ethernet Fiber Network Interface Card (AT-2711FX)

Allied Telesis PCI-e x1 Gigabit Fiber Network Interface Card (AT-2972SX)

 

Both use the broadcom tg3 driver which I think is included in nanoboot release.

Unfortunately the CPU inside this little thing is a Intel Atom N280 which do not support 64bits so you can't use XPEnoboot :sad:

Link to comment
Share on other sites

Hi

 

Have you tried to navigate to ip address 192.168.1.42 as shown in image?

 

Can you ping this address?

 

Please post more info about nanoboot (exact file name) and hardware....

 

192.168.1.42 address not work and can't ping this address too . My DHCP seting is from 192.168.2.10 to 192.168.2.100 , not "192.168.1.xx"

I use HP T5745 thin PC to setup , Atom n280 , Nic Broadcom Bcm57780 , ram 2Gb . Try all nanoboot version and not work .

nanoboot.jpg

Edited by Guest
Link to comment
Share on other sites

According HP website for your T5745 you should have one of these network card:

 

Allied Telesis PCIe x1 Fast Ethernet Fiber Network Interface Card (AT-2711FX)

Allied Telesis PCI-e x1 Gigabit Fiber Network Interface Card (AT-2972SX)

 

Both use the broadcom tg3 driver which I think is included in nanoboot release.

Unfortunately the CPU inside this little thing is a Intel Atom N280 which do not support 64bits so you can't use XPEnoboot :sad:

 

Can use Nanoboot instead XPEnoboot ?

Link to comment
Share on other sites

it looks like your network adapter is not getting an ip address in your scope, most likely because the nic hardware is not supported (even if the driver is part of the boot image, it might not be loading). I would try another nic, I think there is a PCI slot on the mobo could take one?

 

you could also look at the dhcp server (router?) logs to see if its getting a DHCP request and replying, or maybe use some packet sniffing software to look for DHCP requests?

also if the thin client bios has options for how it gets its IP address eg boottp, dhcp etc. Some thin clients can get a config from a tftp server too, so maybe check that thats not enabled

Link to comment
Share on other sites

×
×
  • Create New...