This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C1EC78.B2F732A0
Content-Type: text/plain;
charset="iso-8859-1"
Hi Bob,
at this time I think it may be bug 319388 from Axiant 2, details below,
Problem # : 319388
Title : Users in a trusted domain cannot run application
----------------------------------------------------------------------
Problem Description
If users in a trusted domain try to run axiant client but receive the
following message:
50: COMM-E-M_LOGIN, Login incorrect
Axiant is unable to start this application
If the client stops the NETD service and runs the NETD from console, the
users in the trusted domain do not have problems.
The netd service is running in the PGOC domain and clients are running in
the PGOC and NTBSCO domain. The clients in the PGOC domain work with no
problems. The clients in the NTBSCO domain cannot connect and receive the
error message.
Currently, the client can either...
1) run 2 netd's (ie, one for the PGOC domain, and one for the NTBSCO
domain).
or
2) run netd from the console
or
2) run netd with these startup parameters:
-dgx -s -fnetd.log
However, this is not what the client wants.
Is this working as designed ? Should you be able to run Axiant client
successfully if the netd is running as a service in another domain ?
-------------------------------------------------------------
The comment below was found in the bug details, I suspect this is a
description of what must be done to fix the problem. And if it is now fixed
in Axiant 3, the syntax for invoking the functionality.
-------------------------------------------------------------
Client passed a login string of format <domain>\<userid>, but the netd has
never taken this format. The change was added to netd to take the format of
<domain>\<userid> login string. Netd will verify a user against the
specified <domain>. If netd cannot login the user against this specified
domain, it will return an error. If the login string is <userid> only,
netd will try to verify a user against the entire trusted system ( i.e.
local machine, then primary domain, and then any trusted domains ).
-----Original Message-----
From: Edis, Bob [mailto:BEdis@usbnc.org]
Sent: 25 April 2002 17:32
To: PowerHouse List (E-mail)
Subject: RE: Logon error in Axiant for Windows NT
Did anyone come up with an answer to this? I'm curious as to the cause and
solution as I couldn't see anything in the knowledgebase relating to it.
Blue
-----Original Message-----
From: Egil Oldevik [mailto:Egil.Oldevik@cappelen.no]
Sent: Tuesday, April 23, 2002 2:39 AM
To: powerh-l@lists.swau.edu
Subject: Logon error in Axiant for Windows NT
Dear Members,
We have been struggling a while to enforce security when logging on to an
Axiant (PowerHouse) application on Windows NT. When we do not enforce
security (ie. use the -s switch on either the NETD console or the NETD
service) we can logon, but are not prompted for passwords. This renders the
use of logons useless as a method of restricting users' access to parts of
the application. When we remove the -s switch, however, the user gets the
message "50: COMM-E-M_LOGIN, Login incorrect". In the NETD log file, the
message is "CREATETASK: LogonUser() return error 259".
The service is running as user Administrator (ie. the domain administrator
for the domain where the server and the users belong). We have also tried to
use the local Administrator, as well as specifying the domain when logging
on (ie. domain\user in the username field). Neither works, and we are still
not able to enforce authentication.
As we have been spending a lot of man hours trying to solve this, we see
ourselves running out of ideas about new things to try. Therefore we would
highly appreciate any new ideas as to how we can locate the error, and find
a fix for this problem.
Best Regards,
Egil Oldevik
Cappelen
Norway
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.swau.edu
Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu
Unsubscribe: "unsubscribe" in message body to
powerh-l-request@lists.swau.edu
http://lists.swau.edu/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.swau.edu
Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu
Unsubscribe: "unsubscribe" in message body to
powerh-l-request@lists.swau.edu
http://lists.swau.edu/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.
This message may contain privileged and/or confidential information. If you
have received this e-mail in error or are not the intended recipient, you
may not use, copy, disseminate or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so. Thank you.
------_=_NextPart_001_01C1EC78.B2F732A0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
RE: Logon error in Axiant for Windows NT
Hi Bob,
at this time I think it may be bug 319388 from Axiant =
2, details below,
Problem # : =
319388
Title : =
Users in a trusted domain cannot run application
---------------------------------------------------------------=
-------
Problem Description
If users in a trusted domain try to run axiant client =
but receive the following message:
50: COMM-E-M_LOGIN, Login incorrect
Axiant is unable to start this application
If the client stops the NETD service and runs the =
NETD from console, the users in the trusted domain do not have =
problems.
The netd service is running in the PGOC domain and =
clients are running in the PGOC and NTBSCO domain. The clients in =
the PGOC domain work with no problems. The clients in the NTBSCO =
domain cannot connect and receive the error message.
Currently, the client can either...
1) run 2 netd's (ie, one for the PGOC domain, and one =
for the NTBSCO domain).
or
2) run netd from the console
or
2) run netd with these startup parameters:
-dgx -s -fnetd.log
However, this is not what the client wants.
Is this working as designed ? Should you be able to =
run Axiant client successfully if the netd is running as a service in =
another domain ?
-------------------------------------------------------------
The comment below was found in the bug details, I =
suspect this is a description of what must be done to fix the problem. =
And if it is now fixed in Axiant 3, the syntax for invoking the =
functionality.
&nb=
sp;
-------------------------------------------------------------
Client passed a login string of format =
<domain>\<userid>, but the netd has never taken this =
format. The change was added to netd to take the format of =
<domain>\<userid> login string. Netd will verify a =
user against the specified <domain>. If netd cannot login =
the user against this specified domain, it will return an =
error. If the login string is <userid> only, netd =
will try to verify a user against the entire trusted system ( i.e. =
local machine, then primary domain, and then any trusted domains =
).
-----Original Message-----
From: Edis, Bob [mailto:BEdis@usbnc.org]
Sent: 25 April 2002 17:32
To: PowerHouse List (E-mail)
Subject: RE: Logon error in Axiant for Windows =
NT
Did anyone come up with an answer to this? I'm =
curious as to the cause and
solution as I couldn't see anything in the =
knowledgebase relating to it.
Blue
-----Original Message-----
From: Egil Oldevik [mailto:Egil.Oldevik@cappelen.no=
]
Sent: Tuesday, April 23, 2002 2:39 AM
To: powerh-l@lists.swau.edu
Subject: Logon error in Axiant for Windows NT
Dear Members,
We have been struggling a while to enforce security =
when logging on to an
Axiant (PowerHouse) application on Windows NT. When =
we do not enforce
security (ie. use the -s switch on either the NETD =
console or the NETD
service) we can logon, but are not prompted for =
passwords. This renders the
use of logons useless as a method of restricting =
users' access to parts of
the application. When we remove the -s switch, =
however, the user gets the
message "50: COMM-E-M_LOGIN, Login =
incorrect". In the NETD log file, the
message is "CREATETASK: LogonUser() return =
error 259".
The service is running as user Administrator (ie. the =
domain administrator
for the domain where the server and the users =
belong). We have also tried to
use the local Administrator, as well as specifying =
the domain when logging
on (ie. domain\user in the username field). Neither =
works, and we are still
not able to enforce authentication.
As we have been spending a lot of man hours trying to =
solve this, we see
ourselves running out of ideas about new things to =
try. Therefore we would
highly appreciate any new ideas as to how we can =
locate the error, and find
a fix for this problem.
Best Regards,
Egil Oldevik
Cappelen
Norway
=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =
=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D
Mailing list: powerh-l@lists.swau.edu
Subscribe: "subscribe" in message body to =
powerh-l-request@lists.swau.edu
Unsubscribe: "unsubscribe" in message body =
to
powerh-l-request@lists.swau.edu
http://lists.swau.edu/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you =
must be a subscriber.
=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =
=3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D
Mailing list: powerh-l@lists.swau.edu
Subscribe: "subscribe" in message body to =
powerh-l-request@lists.swau.edu
Unsubscribe: "unsubscribe" in message body =
to powerh-l-request@lists.swau.edu
http://lists.swau.edu/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you =
must be a subscriber.
This message may contain privileged and/or =
confidential information. If you have received this e-mail in =
error or are not the intended recipient, you may not use, copy, =
disseminate or distribute it; do not open any attachments, delete it =
immediately from your system and notify the sender promptly by e-mail =
that you have done so. Thank you.
------_=_NextPart_001_01C1EC78.B2F732A0--