[THIN] Re: Novell Contextless Logon and WI
- From: "Hutchinson, Alan" <Alan.Hutchinson@xxxxxxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Fri, 3 Feb 2006 15:39:00 -0000
Where - heeeeeelp - Can't find anything - tried everything I can think
of - I'd like to say I'm tearing my hair out but I've got so little left
that my fingernails are now full of splinters.
When logging in via a 'direct' connection i.e. not WI - login script
runs fine, contexless bit runs fine.
_____
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Andrew Wood
Sent: 03 February 2006 15:31
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Novell Contextless Logon and WI
wasn't this something in Novell where you could disable the novell logon
scripting from running?
_____
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Hutchinson, Alan
Sent: 03 February 2006 11:25
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Novell Contextless Logon and WI
Reposting - 'cos I'm still getting nowhere with this .......
_____
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Hutchinson, Alan
Sent: 31 January 2006 17:01
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Novell Contextless Logon and WI
Update - have installed 4.91 SP2 (4.91.2.20051209), disabled NMAS and
enabled LDAP and the contextless pasthrough authentication works a dream
(and I'll swear faster than the way I used to do it). The only caveat is
that the Novell logon scripts now don't run and as such users don't get
their mapped drives and making things like Word and Excel unusable. Any
other minor tweak I can make?
Regards,
Alan.
_____
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Hutchinson, Alan
Sent: 31 January 2006 12:29
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Novell Contextless Logon and WI
Rick,
Thanks for that - not using NMAS authentication so that bit's easy. Will
have a look at LDAP. This looks like it's part of CLAW (thanks for the
link Andrew), which for some reason I discounted yesterday ......
Regards,
Alan.
P.S. Will let you know how I get on ......
_____
From: Rick Mack [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Rick
Mack
Sent: 31 January 2006 10:16
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Novell Contextless Logon and WI
Hi Alan,
What I actually meant to say is if you want contextless passthrough
authentication to work through WI etc, disable NMAS authentication and
use ldap.
Sorry.
regards,
Rick
Ulrich Mack
Volante Systems
_____
From: thin-bounce@xxxxxxxxxxxxx on behalf of Rick Mack
Sent: Tue 31/01/2006 20:11
To: thin@xxxxxxxxxxxxx
Subject: RE: [THIN] Re: Novell Contextless Logon and WI
Hi Alan,
The main trick to getting contextless login to work is to disable NMAS
Authentication. Define your ldap servers and away you go ;-).
regards,
Rick
Ulrich Mack
Volante Systems
_____
From: thin-bounce@xxxxxxxxxxxxx on behalf of Hutchinson, Alan
Sent: Tue 31/01/2006 20:04
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Novell Contextless Logon and WI
Well - I was a bit surprised when I went and checked - I know that we
had severe problems late last year on our W2K farm. So bad in fact that
we got a 'pre-release' patch from Novell and have since discovered that
others have had the same problem. This patch was eventually released
into 'the wild' (and I think went into SP2) and the servers have been
very stable since but the client doesn't show any updates. I think I'm
going to upgrade to SP2 on this new build but don't believe that it will
resolve my issue below.
I've found several references to the 'tab event' to kick off the actual
contextless 'lookup' but no actual solutions.
Regards,
Alan.
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Rick Mack
Sent: 30 January 2006 20:36
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Novell Contextless Logon and WI
Hi,
4.91 lower than SP1 can bluescreen a server. That and other features
make 4.91 SP2 just about mandatory.
Regards,
Rikc
Ulrich Mack
Volante Systems
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Hutchinson, Alan
Sent: Tuesday, 31 January 2006 3:08 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Novell Contextless Logon and WI
4.91 (.0.20050216 - for completeness) which is the sam client as I've
got on my W2K farm which I know has been patched last year but can't
find details of patch.........
_____
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Andrew Wood
Sent: 30 January 2006 16:50
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Novell Contextless Logon and WI
whats the version of the Novell client that you're running?
_____
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On
Behalf Of Hutchinson, Alan
Sent: 30 January 2006 16:43
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Novell Contextless Logon and WI
I have a new pilot starting soon incorporating WI 4.2, CAG and AAC.
Servers are W2K3, PS4 and set up with Novell client for contextless
login. This part works fine when connecting directly to a server to a
published desktop - user enters credentials and contextless lookup takes
place and user is then logged in. Have been doing this for some years
now with W2K, MF1.8, and MF XP etc.
Problem arises when user accesses applications (or desktops) via WI.
User logs in and page is populated with available applications. This
tells me that authentication is taking place against the NT domain where
the user account exists and the correct applications are showing
(applcations published based on NT group membership). On selecting an
application a netware security message pops up saying that user can't
logon to the network. On o.k.ing this user is then presented with the
Novell logon box with username and password already populated but I can
tell that the 'contextless part' hasn't taken place as the id is still
in lowecase (selecting adavnced also shows that context is not correct).
Deleting the username and retyping it and then 'tabbing' to the next
field 'allows' the contextless lookup to take place and user can then
logon accordingly.
Not sure if I've explained that very well and can supply further details
if required. Anyone any pointers please.
Regards,
Alan.
########################################################################
#############
This e-mail, including all attachments, may be confidential or
privileged. Confidentiality or privilege is not waived or lost because
this e-mail has been sent to you in error. If you are not the intended
recipient any use, disclosure or copying of this e-mail is prohibited.
If you have received it in error please notify the sender immediately by
reply e-mail and destroy all copies of this e-mail and any attachments.
All liability for direct and indirect loss arising from this e-mail and
any attachments is hereby disclaimed to the extent permitted by law.
########################################################################
#############
************************************************
For Archives, RSS, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
//www.freelists.org/list/thin
************************************************
************************************************
For Archives, RSS, to Unsubscribe, Subscribe or
set Digest or Vacation mode use the below link:
//www.freelists.org/list/thin
************************************************
########################################################################
#############
This e-mail, including all attachments, may be confidential or
privileged. Confidentiality or privilege is not waived or lost because
this e-mail has been sent to you in error. If you are not the intended
recipient any use, disclosure or copying of this e-mail is prohibited.
If you have received it in error please notify the sender immediately by
reply e-mail and destroy all copies of this e-mail and any attachments.
All liability for direct and indirect loss arising from this e-mail and
any attachments is hereby disclaimed to the extent permitted by law.
########################################################################
#############
########################################################################
#############
This e-mail, including all attachments, may be confidential or
privileged. Confidentiality or privilege is not waived or lost because
this e-mail has been sent to you in error. If you are not the intended
recipient any use, disclosure or copying of this e-mail is prohibited.
If you have received it in error please notify the sender immediately by
reply e-mail and destroy all copies of this e-mail and any attachments.
All liability for direct and indirect loss arising from this e-mail and
any attachments is hereby disclaimed to the extent permitted by law.
########################################################################
#############
Other related posts:
