Mark Nienberg schrieb: > Some of the clients on my network occasionally start up wpkg at boot and then have > the error (in the event viewer): > > "WNetAddConnection2-> The network location cannot be reached. For information..." > > And the user must wait for the full maximum logon delay. After that, the user logs > on fine and all network services are available. It doesn't happen every time. I > need to do more research, but I think it may only be happening to Windows XP clients > that have Service Pack 3 installed. > > The clients are 1.2.1. > wpkg.js is 1.0.2 > > Any ideas appreciated. Try installing WPKG Client 1.3.x - it shouldn't unnecessary delay the user if the network is unavailable. And why can't WPKG Client access network and logs "The network location cannot be reached"? It's because... it can't access the network. We are using standard Windows APIs, and if the system reports it, it can be the network card driver which takes some more time to bring up the network card, slow DHCP etc. You can also play with "offline mode" settings. -- Tomasz Chmielewski http://wpkg.org |