Hi,

So, this following description is a real issue for us presently.

We are starting to see a rash of laptop users that have the same symptoms:

- The client will have been working for some time and then suddenly stop 
backing up.

- De-installing and re-installing the NBU 5.1MP3 client does not help.

- Sometimes it appears that uninstalling the XP patches to roll back to 
SP2 and then install the backup client and then the SP3 and 4 will work 
temporarily...but almost all of the laptops have reverted to stop 
working shortly thereafter once again.

- This only happens with laptops, and less than 2% of our Windows XP 
user-base...we have about 283 Windows and similar Mac and Unix amounts. 
No one has this problem but laptops, and only a select few of 
them....ironically, though, all of our division director and higher 
personnel. If that is not Murphy at work.

- Local to the laptops (all running XP SP4 with 5.1MP3 NBU client) 
everything looks normal
    * netstat -an shows 13782 in a LISTENING state.
    * firewall rules allow the ports (and work on the 200+ desktop 
Windows systems we back up).
    * we have uninstalled and disabled all other software for 
anti-virus, anti-spyware and any other network-based applications to no 
effect.
    * Adding 127.0.0.1 to the server list and then from the local box 
telneting to 127.0.0.1 13782 does get the proper hanging state we see on 
other systems.
    * Enabling logging brings out bpcd logs that look like this:
---------
16:04:32.302 [3576.3592] <2> logconnections: getsockname(-1) failed: 10038
16:04:32.302 [3576.3592] <16> bpcd setup_sockopts: setsockopt 1 failed: 
h_errno 10038
16:04:32.302 [3576.3592] <2> bpcd main: setup_sockopts complete
16:04:32.302 [3576.3592] <2> vauth_acceptor: 
..\libvlibs\vauth_comm.c.326: Function failed: 17 0x00000011
16:04:32.302 [3576.3592] <16> bpcd main: authentication failed: 17
16:04:36.117 [2624.2760] <2> bpcd main: offset to GMT 28800
16:04:36.117 [2624.2760] <2> bpcd main: Got socket for input -1
----------

- From the server we see a myriad of errors, ranging from 41 (net 
timeout) to 58 (auth issues) from these machines.
    * The client does not 'bpdir' from the server.
    * telnet $client 13782 does not hang and the connection is 
immediately closed.
    * The client does ping from the server.
    * The clientnames and servernames match on both client and server


Any thoughts would be most welcome. Anyone else seen this kind of behavior?


TIA!

--Chris