Mark Nienberg schrieb: > Tomasz Chmielewski wrote: >> 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. > > OK, at least that would reduce the complaints. In 1.3.x, you can also schedule software installation on reboot/shutdown. >> 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. > > Yes, but this didn't happen with the old 0.9 series of wpkg and I kind of think it > doesn't happen on my WinXP SP2 clients, and it happens sometimes even when I test at > night with no other activity on the network, and all of the workstations are just > fine after login, so I'm not convinced that it is a network problem. Maybe some sort > of timing issue like you suggest. The machines have fixed IP addresses so it isn't Do you use server name or IP address to reach it? If you use a name, does it change anything if you use IP? Nevertheless, try if the issue is not fixed in 1.3.x. -- Tomasz Chmielewski http://wpkg.org |