<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
> Date: Thu, 11 Mar 2010 14:21:35 -0500<BR>> From: brinegar@physics.unc.edu<BR>> To: subscription@kkeane.com<BR>> CC: wpkg-users@lists.wpkg.org<BR>> Subject: Re: [wpkg-users] "The network path was not found." - Windows 7, wireless connection.<BR>> <BR>> This does not seem to be true for Windows XP. I have not tested this on <BR>> Windows 7, but if I had to guess I would think it is <BR>> connection-dependent. The user is asked to configure the Wireless <BR>> Connection (if applicable) in the OOBE when setting up Windows - which <BR>> occurs before a login occurs. This deserves some more investigation <BR>> with multiple wireless authentication schemes.<BR>> <BR>> To the original poster:<BR>> <BR>> I would investigate forcing the WPKG service to depend on the Wireless <BR>> Connection. It will not start until the service or system component <BR>> becomes available. You should be careful with what you select, because <BR>> you may run into situations that won't let WPKG start. I've only worked <BR>> with service dependencies on Windows XP, but I'm sure there's <BR>> documentation out on the net that will help you. Note that the service <BR>> depends on AFD and TCP/IP by default. That should be a start, in any case.<BR>> <BR>> Justin<BR>> <BR>> Kevin Keane wrote:<BR>> > I believe Windows establishes the wireless connection only at login. This is because with some types of wireless authentication (Enterprise/RADIUS-based), the Windows user name and password actually doubles as wireless user name and password.<BR>> > <BR>> >> -----Original Message-----<BR>> >> From: wpkg-users-bounces@lists.wpkg.org [mailto:wpkg-users-<BR>> >> bounces@lists.wpkg.org] On Behalf Of jetshopit@o2.co.uk<BR>> >> Sent: Thursday, March 11, 2010 8:11 AM<BR>> >> To: wpkg-users@lists.wpkg.org<BR>> >> Subject: [wpkg-users] "The network path was not found." - Windows 7,<BR>> >> wireless connection.<BR>> >><BR>> >> I have Windows 7 machines which are connected only by wireless. WPKG is<BR>> >> set to run at startup. However, no packages are installed, instead the<BR>> >> Event Viewer has an error entry<BR>> >><BR>> >> WNetAddConnection2-> The network path was not found.<BR>> >><BR>> >> from WPKGService.<BR>> >><BR>> >> If I manually start the service, all is well. So I think the problem<BR>> >> is that WPKG is running before the wireless connection is established.<BR>> >> I'm not actually sure when Windows 7 establishes the wireless<BR>> >> connection - at startup or at login.<BR>> >><BR>> >> How can I make wpkg wait until the connection is established, then<BR>> >> run, rather than quitting as is currently the case? Possibly something<BR>> >> with the 'Execute Before' option?<BR>
<BR>
This isn't a Win7 issue per-se, I've seen it recently on some XP Home netbooks too. The current Beta of wpkg client has an option to restart the service up to 10 times if it fails. I found this was enough to ensure the wireless connection was made during up to these 10 restarts.<BR>
<BR>
wpkg already depends on the tcp/ip service but this doesn't seem enough to handle some slow wireless connectivity issues.<BR>
<BR>
Chris<BR> <br /><hr />Got a cool Hotmail story? <a href='http://clk.atdmt.com/UKM/go/195013117/direct/01/' target='_new'>Tell us now</a></body>
</html>