[wpkg-users] WPKG cannot reach Samba at boot-up (was Re: Where is WPKG client config stored?) [SEC=UNCLASSIFIED]

[Michael Chinn]

Would it be worthwhile changing the wpkg service to a script that tries 
to access the share or port 139 on the server every 5 seconds before 
launching wpkg. You could even put in place detection of dialup and 
abort wpkg at this point.

-- 
Michael Chinn
User Support Officer - Information Technology

Great Barrier Reef Marine Park Authority
PO Box 1379
TOWNSVILLE, QLD 4810

Ph 07 47500874 Fax 07 4772 6093
michaelc at gbrmpa.gov.au 

================================================================================
If you have received this transmission in error please notify us immediately
by return email and delete all copies. Any unauthorised use, disclosure or
distribution of this email is prohibited.
================================================================================



Tomasz Chmielewski wrote, On 23/05/2007 06:07:
> Dave Ewart schrieb:
>   
>> On Monday, 21.05.2007 at 19:03 +0100, Dave Ewart wrote:
>>
>>     
>>> On Monday, 21.05.2007 at 12:02 -0500, Adam Williams wrote:
>>>
>>>       
>>>> Is the erroring PC using a wireless NIC?  I've found that wireless
>>>> NICs don't start their software and connect to the wireless
>>>> connection until a few seconds after the login screen comes up (or
>>>> after the start menu loads if not in a domain), however in both
>>>> cases, WPKG service has already ran and errored out since there
>>>> wasn't a network connection yet.
>>>>         
>>> No, all the PCs I mention use wired NICs.  In fact, the PC hardware is
>>> all pretty similar, really; different, but very similar.
>>>       
>> Working on this basis, though, I was wondering if there was any way to
>> make WPKG launch later in the boot process.  I even tried hacking the
>> registry to make "WPKG Service" dependent on some other services such as
>> TCP/IP and NetBIOS, to see if that made a difference, but no luck.
>>
>> I am assuming that the problem I'm seeing is essentially a race
>> condition at boot-up and WPKG sometimes loses :-(
>>     
>
> Hi,
>
> I could add it to the TODO list (delay startup of WPKG service) - but: 
> how should we handle the so called "delayed logon" in that case (user 
> not allowed to logon when WPKG client operate, for 10 or 15 minutes or so)?
>
> Somehow I feel, these two exclude each other?
>
>
>
>   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wpkg.org/pipermail/wpkg-users/attachments/20070523/b570e7cc/attachment-0002.html>