>> I suspect a network issue. IIRC Firefox tries to connect to some >> (Mozilla related?) sites on startup. So as long as you miss a proper >> network setup (with gateway 10.0.0.1, see manual) it'll be like >> experienced. You could try Chromium w/ https://10.0.2.2/gosa instead; >> you'll need to accept an unsecure connection, though.
Hi Wolfgang, I have added a second network card to my Debian Edu Server and connected it to a temporal router on 10.0.0.1. I realized that the new network card took over eth0 so I edited /etc/network/interfaces switching eth0 and eth1. The DHCP service was kind of confused after this not allowing the thin clients to start anymore but rebooting the server fixed this. However, I think ip forwarding is not working yet. Pings to/from the router dont work. I think, this causes the firefox issue to still occur. What am I missing here? Kind regards, Roman
