Thanks for the reply,
With V3.3rc2 i'm able to backup, but i can't download packages. (maybe there is no repo for the release candidate??)
But i noticed that V3.3rc2 tries to get an ip address from the dhcp3-server my tftp-server is running on, wile 3.2 does not, it probably gets it's ip from the dhcp server on my isp-router and connects.
I tried static ip configuration but this also didn't work with 3.3rc2 (did not tried 3.2)
I also changed the ip-range in the dhcp3-config, because otherwise the nfs server is rejecting the mount request.
The server gives 192.168.1.11, tiny-core takes 192.168.1.8 and is unknown with the same mac address. (don't know which version) For those who think it's strange that i could save before without out changing the ip range, that's probably because i'm using my laptop now.
I'm really a network noob, but is there a way to make tiny core takes the same ip address as when its getting downloaded, from the tftpserver (like other disto's do)? Or do i really need to chance my whole setup to the needs of v3.2?