Jochen, such problems should normally be reported to our bugtracker.
On Tuesday 05 August 2008, Jochen Roderburg wrote: > 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 Your WinXP guest is reading a share from another machine running WinXP as well, is that right? > > 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. What network card did you select, the default one (PCNet)? > > 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". Sounds like related to the first problem. > > 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. We normally don't see such kind of problems. I assume your WinXP guest is well patched? Do you experience some other instabilities apart from the network problems? Do you have a firewall running at the host (I know, Ubuntu normally doesn't setup iptables, but ... If so, try to disable the firewall. Kind regards, Frank -- Dr.-Ing. Frank Mehnert Sun Microsystems http://www.sun.com/
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ vbox-users mailing list vbox-users@virtualbox.org http://vbox.innotek.de/mailman/listinfo/vbox-users
