Your interface is up but got no IP. Crazy!
Can you please try command "/sbin/udhcpc -q -t 5 -n -i eth0"?
Are you sure, that your dhcp server is well configured?
Regards, Jörn
Am 09.03.2016 um 16:31 schrieb Florian Berzl:
> "IP a s"
>
> 1: lo: mtu 65536 qdisc noqueue
>
Hi,
i think the dhcp works well. The DHCP send the boot image to the thinclient.
All other workstations and thinclients work without problems. So I think the
dhcp server is ok.
After the error "(DEBUGSHELL) : No LDAP connection possible, please debug." I
do a ping to my LDAP server with ping
Hi Florian,
nope, you sure have some different problem. Module r8169 is loaded - so
you should have a working network interface.
Can you please try commands "ip a s" and "ping IP.of.your.OTC-Server".
Regards, Jörn
Am 09.03.2016 um 15:41 schrieb Florian Berzl:
> Hello,
>
> i have exactly the
"IP a s"
1: lo: mtu 65536 qdisc noqueue
Link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
Inet 127.0.0.1/8 scope host lo
Valid_lft forever preferred_lft forever
Inet6 ::1/128 scope host
Valid_lft forever
I hope, you assigned the "device" "smartcard" to the thinclient?
Alexander Stecher
--
Dipl.-Ing. (BA)
Telefon: +49 711 1378636-1
Handy: +49 151 2761 2961
mailto:a.stec...@openthinclient.com
openthinclient gmbh
Heilbronner Str. 150, 70191 Stuttgart, Deutschland
Telefon: +49 711 1378636-0
Hallo Herr Mayer,
das liegt vermutlich an der Treiber-Unterstützung für VMware.
Das Betriebssystem Ihrer Testmaschine ist unwichtig, da dies ja eh zur
Laufzeit per PXE geladen wird.
Ändern Sie die virtuelle Netzwerkkarte.
Oder testen Sie bitte einen physikalischen Client.
Gruß
Alexander