Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
On Tue, 24 Oct 2006 14:17:06 +0200, David Somers <dsomers at omz13.com> wrote: >Bo Berglund wrote: > >> More tests done from client PC: >> >> cvs status -q file1 WORKS >> cvs status -q file1 file2 WORKS >> cvs status -v file1 WORKS >> cvs status file1 WORKS >> >> but >> cvs status -v file1 file2 HANGS >> cvs status file1 file2 HANGS >> >> and >> cvs -ttt status <whatever> HANGS >> >> All of the above work when executed in a command window on the server >> itself. >> >> We have rebooted the server but it changes nothing. >> Server is build 2151, client is build 2382 > >Its not some kind of networking problem is it... when the ghosted your >machine into vmware, did update all the network drivers to the VMware ones? >Was Microsoft Update run and some hotfixes applied (which could have >screwed your system)? I also think that a networking problem is at large here, but I can't figure out what.... It looks strange that some commands ooperate OK (cvs log or cvs status on a single file for example) whereas others do not (like the cvs status -v file1 file2 type). Anyways the virtual machine has a VMWare virtual network adapter and the IT person today tried to clean out all of the drivers for now nonexisting hardware. But so far it has not helped. The VMWare network adapter is connected to a virtual network switch on the server and the output of that is in turn connected to the physical network adapter on the server PC. According to the IT person the virtual switch is a beast to configure and whatever they do will affect all servers sunning on the same hardware PC, so they are reluctant to change the defaults.... Sigh! HTH /Bo (Bo Berglund, developer in Sweden)