Christian Thurow schrieb:
Tomasz Chmielewski wrote:
Christian Thurow schrieb:
unfortunately the cmd only appears, when a user is logged in, and the
wpkgservice starts, but not at the boot.
Yes, you will see cmd.exe window (or any other window started by WPKG
Client service) only after you log in.
So this is expected behaviour.
Now, can you browse files on your network share from that cmd.exe window?
And did you check the Windows Event Log to see what WPKG Client logs?
This is where you should have began with.
other idea: where can i see, which version of wpkg i installed? the
client is 1.2.1
start wpkginst.exe - About.
but i dont know the server version, maybe i use an old
wpkg-version (over apt-get).
You mean wpkg.js? See the beginning of this file in any editor.
And I don't think you installed it using apt-get (unless you made your
own package).
OK, im wondering how i get the cmd on my screen last time after logon..
now i only get the following messages in the eventlog of windows under
application:
WPKG Service trying start...
WPKG Service- RegisterServiceCtrlHandler: successfully done
WPKG Service- SERVICE_START_PENDING: successfuly done
Service Start
Set script security context: successfuly done.
and at last the error (ca. 9 seconds later):
WNetAddConnection2- Zugriff Verweigert (english: access denied)
So you gave invalid credentials.
See http://wpkg.org/FAQ - last question.
i use the same user for testing settings, as i fill in the fields in
wpkginst.exe for accessing the server. with logged in user and then
starting the service all works fine..
Read this sentence carefully, it was in my first answer to your post:
If you're already connected to a password-protected network share (i.e.
as Administrator) Test settings may not show errors when trying to
connect to that share.
Do you know why? Because you're probably already connected to that share
(as Administrator).
the samba-server doesnt show any log-entrys before a user logged into
the client, so there must be a right issue for accessing the samba
server for the wpkg-service on the client.. but the user fpr wpkg has
the required rights, where is the failure?
Samba *must* log something - otherwise, you wouldn't have Access
denied error.
It probably logs that you used an invalid user or invalid password.
the service wpkg is startet AFTER netlogon, afd, openvpn and tcpip.. so
it should work, but it didnt..
the version of wpkg.js is 1.0 - could this be a problem?
No, at this stage we don't even have access to wpkg.js.
--
Tomasz Chmielewski
-
Reporting bugs, all WPKG mailing lists http://wpkg.org/Support
___
wpkg-users mailing list
wpkg-users@lists.wpkg.org
http://lists.wpkg.org/mailman/listinfo/wpkg-users
