The following problems survived an update to the new VirtualBox 1.6.4: > I have various networking problens which could all be related but I am > not really sure. > > Current situation: > VirtualBox 1.6.2 on a Linux host, Windows 2000 guest, host interface > networking. > > 1) In general the network works (after it stopped working in 1.6.0 and > after a massive update problem which I will report in a separate > thread). Normal TCP/IP functions seem to be ok, in my local net and > with systems all over the world. > Windows networking works also with Samba shares on Linux systems (the > VM host and another one), I can read and write there without problems. > But I have a strange problem with shares on another (non-virtual) > Windows XP machine. Reading from the shares is ok, but when I try to > write, it hangs a while, then I get either an error message (not all > data could be written ....) or it just seems to succeed. In both cases > I have then a file on the destination with correct attributes (size, > date, ...), but the file contains only zero-bytes. > > 2) I cannot print to a network printer on my local net. My printer is > connected to a little print-server box by D-Link. the box can be used > with UNIX-LPD or Windows-SMB protocols and both ways work from the > non-VM Linux and Windows machines. > When I make some experiments with command-line programs in the Windows > VM I see the following: > > lpq printserver succeeds. > lpr printserver printfile hangs a while and eventually gives an > error message that it cannot write to the printserver. > > net view \\printserver shows the print share. > cp printfile \\printserver\printshare works. > > But both acceess methods do not work when I define them for a "normal" > Windows print queue. When I try to print a file they just hang there > in the queues "for ever". > > 3) Last not least: Automatic Windows Updates do not work, in the log > file I see a number of those cryptic Windows error message which all > seem to mean that it somehow could not connect to the MS updates > servers. > > Another strange thing is that there had been a short time-frame when > all these errors disappeared, but I can't remember if this was > correlated to a particular VBox version or to some other change in my > system or was purely random. > > > Jochen Roderburg > ZAIK/RRZK > University of Cologne > Robert-Koch-Str. 10 Tel.: +49-221/478-7024 > D-50931 Koeln E-Mail: [EMAIL PROTECTED] > Germany >
_______________________________________________ vbox-users mailing list vbox-users@virtualbox.org http://vbox.innotek.de/mailman/listinfo/vbox-users
