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

Dave Ewart davee at ceu.ox.ac.uk
Mon May 21 18:12:30 CEST 2007

On Monday, 30.04.2007 at 15:37 +0100, Dave Ewart wrote:

> > >>> On a WPKG 'problem' PC:
> > >>>
> > >>> - WPKGService: Set script security context: successfully done
> > >>> - WPKGService: Multiple connections to a server or shared resource by
> > >>>   the same user, using more than one user name, are not allowed.
> > >>>   Disconnect all previous connections to the server or shared resource and
> > >>>   try again..
> > >> It's a limitation and message coming from Windows. Google for it.
> > >>
> > >> Basically, you can't connect from a Windows machine more than once, and 
> > >> use different credentials (more or less).
> > > 
> > > Yeah, that's how I interpreted it; and I found some discussion about
> > > people who were actively trying to do things with multiple shares, but
> > > that's not what I'm doing...
> > > 
> > >> This means: probably you have some other script or program that uses 
> > >> network shares, and starts before WPKG (or WPKG starts scripts which 
> > >> mount shares using different credentials etc.?).
> > > 
> > > Yes, "some other script or program uses network shares" makes sense as
> > > an explanation but doesn't apply here.  There's nothing else running.
> > > All the 'working' PCs and 'non-working' PCs were deployed from the same
> > > Windows XP disk image and are, aside from minor hardware differences,
> > > identical.
> > 
> > Some 3rd party worm/virus? :)
> > 
> > Try that: log into a problematic machine.
> > 
> > Open cmd.exe.
> > 
> > Use "net use" to show current open connections.
> > 
> > Try net stop "wpkg service", net stop "wpkg service", netstat, net 
> > use... There must be something which blocks a connection.
> On one of the 'problem' PCs, logged-in as local Administrator:
>   net use
>   New connections will not be remembered
>   There are no entries in the list.
> Not that then.
> And, for what it's worth, running:
> net stop "wpkg service"
> net start "wpkg service"
> works fine, for a local Administrator session, started immediately after
> boot-up.

I still haven't solved the above issue :-(

I'm focusing on the message in the Event Log ("Multiple connections to a
server or shared resource by the same user, using more than one user
name, are not allowed.") - there is nothing running as any other user
that I am aware of.  Is there any way to make this message more verbose
and say which shares/users it believes are in use?

Taking this further, I have three PCs, all imaged from the same sysprep
image for WinXP:

- A : WPKG always runs at boot-up;

- B : WPKG *sometimes* runs at boot-up, other times the "Multiple
  connections" error appears;

- C : WPKG *never* runs, always giving the "Multiple connections" error
  at boot-up.

If I reimage the above PCs, the same behaviour with regard to WPKG
running at bootup persists: A still works, B sometimes works and C never
works.  The WinXP sysprep image includes a correctly-configure WPKG
client-side setup.

Therefore, the only difference in the above systems is (a) their
hardware and (b) their WPKG behaviour at bootup.

Note that even for PCs B and C, it is *always* possible to perform a
domain login immediately after the login prompt appears (i.e. just after
the WPKG splash goes away).

Any more ideas, folks? ;-)

Dave Ewart
davee at ceu.ox.ac.uk
Computing Manager, Cancer Epidemiology Unit
Cancer Research UK / Oxford University
PGP: CC70 1883 BD92 E665 B840 118B 6E94 2CFD 694D E370
Get key from http://www.ceu.ox.ac.uk/~davee/davee-ceu-ox-ac-uk.asc
N 51.7518, W 1.2016

wpkg-users mailing list
wpkg-users at lists.wpkg.org

More information about the wpkg-users mailing list