Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login

Maybe.
Also if it works from one location and not another you may have
different issues.

I would check your SLP configuration.

Try a "Display SLP Services" on your SLPDA server.
It should have a "Bindery" entry for every server.
(Note: This has nothing to do with NetWare 3.x type of Bindery Stuff)



--
Craig Wilson
Novell Product Support Forum Sysop
Master CNE, MCSE 2003, CCN
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login

> > craig wilson wrote:
> > This can be a second issue.
> >
> > Normally "Public" has at least browse [entry] rights to the tree and
> > inheritable.
> >
> > This is what lets you browse and find your context before you logon.
> > If this permission is removed or blocked, you will not be able to see
> > contexts until after you login to the tree and get permissions to

browse.
>
> We would still be able to see the tree?
>
> > I have worked at some places that disable these public rights for
> > security reasons. However hiding contexts from folks before they

logon
> > is not always a big concern.

>
> I have looked into it, there is a Novell TID, public has browse rights
> in root and we have never tried to block this. The reason I seem to
> link them is when I cannot find context the login script cannot run and
> find the remote server; when we find context the script runs perfectly
> everytime. Novell TIDs suggested scripting errors however, their fixes
> had no effect.
>
> Could this possibly be a replica / partition problem?
>
> Bill
>

Bill just a wild shot, does your tree and context have the same name?
Mine does and I am beginning to think that might be my problem. I have a
post here and in client. And still no answer to why we are having so
much trouble logging in all of a sudden.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login

By Context I presume you mean your top "O".
This is perfectly acceptable and not an issue.

There was an issue with a management tool at one point in time with
this, but has long since been fixed. The exact details escape me but
this is a fully supported configuration. (Not recommended - but should
not be a problem.)

> Bill just a wild shot, does your tree and context have the same name?
> Mine does and I am beginning to think that might be my problem. I have a
> post here and in client. And still no answer to why we are having so
> much trouble logging in all of a sudden.



--
Craig Wilson
Novell Product Support Forum Sysop
Master CNE, MCSE 2003, CCN
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login

On Wed, 11 Oct 2006 15:50:31 GMT, "Bill H" <bill@unxinc.com> wrote:

>I am having zero luck in finding that registry key to alter the timing.


Try 10086186, but also check 10095407.


---------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu

I'm tired of receiving rubbish in my mailbox, so the E-mail address is
munged to foil the junkmail bots. Humans will figure it out on their own.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login


pjam@do-no-spam-me-lorch.com wrote:

> Bill just a wild shot, does your tree and context have the same name?
> Mine does and I am beginning to think that might be my problem. I have a
> post here and in client. And still no answer to why we are having so
> much trouble logging in all of a sudden.


No our tree is 0=uns context ou=cns for the local server and ou=ans for
the remote server with the same 0=uns. The few other posts I have seen
they all have the new nwclient 4.91.

Bill

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login


craig wilson wrote:
> I would check your SLP configuration.
>
> Try a "Display SLP Services" on your SLPDA server.
> It should have a "Bindery" entry for every server.
> (Note: This has nothing to do with NetWare 3.x type of Bindery Stuff)



Looking at the slpda server I see the bindery
service:bindery.novell:///srv1 which is the remote server
service:bindery.novell:///srv2 the local and slpda server
I keep seeing IPX info also associated with srv1. IPX should be
removed totally however when client and server was running IPX we
didn't have this problem.

This is the slpinfo /all from the client
SLP Version: 4.91.0.1
SLP Start Time: 8:18:23am 10/12/2006
Last I/O: 8:49:42am 10/12/2006
Total Packets: Out: 163 In: 39
Total Bytes: Out: 13381 In: 3382


SLP Operational Parameters Values
------------------------------- ------------
Static Scopes NO
Static Directory Agents NO
Active Discovery YES
Use Broadcast for SLP Multicast NO
Use DHCP for SLP YES
SLP Maximum Transmission Unit 1400 bytes
SLP Multicast Radius 32 hops


SLP Timers Values
------------------------------------- ------------
Give Up on Requests to SAs 15 seconds
Close Idle TCP Connections 5 minutes
Cache SLP Replies 1 minutes
SLP Default Registration Lifetime 10800 seconds
Wait Before Giving Up on DA 5 seconds
Wait Before Registering on Passive DA 1-2 seconds


Scope List Source(s)
---------------------------------------- ------------
<unscoped>
DEFAULT DA


DA IP Address Source(s) State Version Local Interface
Scope(s)
--------------- --------- ----- ------- ---------------
---------------

192.168.10.200 CNFG UP SLPV2 192.168.10.14
DEFAULT
192.168.30.200 CNFG NORSP ? 192.168.10.14
<unknown>



Local Interface 192.168.10.14
---------------------------------
Operational State: UP
Operating Mode(s): MCAST
SA/UA Scopes: <unscoped>,DEFAULT
Last I/O: 8:49:42am 10/12/2006
Total Packets: Out: 163 In: 39
Total Bytes: Out: 13381 In: 3382
Last Addr Out: 192.168.30.200
Last Addr In: 192.168.30.200

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login

On Thu, 12 Oct 2006 13:08:34 GMT, "Bill H" <bill@unxinc.com> wrote:

>DA IP Address Source(s) State Version Local Interface
>Scope(s)
>--------------- --------- ----- ------- ---------------
>---------------
>
>192.168.10.200 CNFG UP SLPV2 192.168.10.14
>DEFAULT
>192.168.30.200 CNFG NORSP ? 192.168.10.14
><unknown>



You have two DAs configured, one of which is either not running, or not
reachable on the network. You might want to get that fixed.



---------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu

I'm tired of receiving rubbish in my mailbox, so the E-mail address is
munged to foil the junkmail bots. Humans will figure it out on their own.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login

On Wed, 11 Oct 2006 20:28:14 GMT, pjam@do-no-spam-me-lorch.com wrote:

>Bill just a wild shot, does your tree and context have the same name?


Doesn't matter. I've had that here since 1996. Only a few buggy products have
ever had trouble with it, and those have long since been resolved.


---------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu

I'm tired of receiving rubbish in my mailbox, so the E-mail address is
munged to foil the junkmail bots. Humans will figure it out on their own.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login

But do you have any other servers in your tree - especially ones holding
replicas. This list should be exhaustive. If IPX fixes things, it is
looking like an SLP configuration issue.

You may also try doing a trace at startup to see if we can see a source
of an error.

At least we have started to limit problems.
Hopefully somebody here can help you nail this 2ne issue.

Bill H wrote:
> craig wilson wrote:
>> I would check your SLP configuration.
>>
>> Try a "Display SLP Services" on your SLPDA server.
>> It should have a "Bindery" entry for every server.
>> (Note: This has nothing to do with NetWare 3.x type of Bindery Stuff)

>
>
> Looking at the slpda server I see the bindery
> service:bindery.novell:///srv1 which is the remote server
> service:bindery.novell:///srv2 the local and slpda server
> I keep seeing IPX info also associated with srv1. IPX should be
> removed totally however when client and server was running IPX we
> didn't have this problem.



--
Craig Wilson
Novell Product Support Forum Sysop
Master CNE, MCSE 2003, CCN
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login


craig wilson wrote:
> But do you have any other servers in your tree - especially ones holding
> replicas. This list should be exhaustive. If IPX fixes things, it is
> looking like an SLP configuration issue.


I fixed that second slpda issue It was configured that way in the
client, 192.168.10.200 is the only slpda. No improvement on the
problem though.

We have only two servers in this tree, and three contexts. Our company
is spread across the city in three locations only 2 have netware
servers but each location has its own context under the same tree
(o=unx).

I am thinking more of a replica / partition problem. The location
that does not have a server (ou=plt) at intial boot cannot see the tree
but can see context and servers their prefered server is srv2. When plt
users login (IP only) the script runs perfectly they find both servers.


The original location (ou=chs) that cant see context or server but can
see tree also has srv2 as prefered server. When chs users login (IP
only) they get the unknown server error. The scripts are the same for
everyone.

The second netware server srv1 at the 3rd location (ou=arl) users dont
have any problems that I am aware of (I need to verify this) there
prefered server is srv1.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login


Bill H wrote:
> craig wilson wrote:
> > But do you have any other servers in your tree - especially ones holding
> > replicas. This list should be exhaustive. If IPX fixes things, it is
> > looking like an SLP configuration issue.

>
> I fixed that second slpda issue It was configured that way in the
> client, 192.168.10.200 is the only slpda. No improvement on the
> problem though.
>
> We have only two servers in this tree, and three contexts. Our company
> is spread across the city in three locations only 2 have netware
> servers but each location has its own context under the same tree
> (o=unx).
>
> I am thinking more of a replica / partition problem. The location
> that does not have a server (ou=plt) at intial boot cannot see the tree
> but can see context and servers their prefered server is srv2. When plt
> users login (IP only) the script runs perfectly they find both servers.
>
>
> The original location (ou=chs) that cant see context or server but can
> see tree also has srv2 as prefered server. When chs users login (IP
> only) they get the unknown server error. The scripts are the same for
> everyone.
>
> The second netware server srv1 at the 3rd location (ou=arl) users dont
> have any problems that I am aware of (I need to verify this) there
> prefered server is srv1.


I made sure about our third location ou=arl. At intial novell login
they can see tree context and server also script runs perfectly.

This is really beginning to make my head hurt 🙂

I'll try and run a trace on startup.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login

While troubleshooting some more, when I try to log in using wgh.chs.unx
as a user and removing the tree and context, using only the servers IP
or name. I get user not found in current context -100: access has been
denied. I go back to wgh with tree and context supplied to nwlogin no
problem. This was all done after intial login.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login

try .wgh.chs.unx (leading dot)
I presume that unx is your O and not tree name.


Bill H wrote:
> While troubleshooting some more, when I try to log in using wgh.chs.unx
> as a user and removing the tree and context, using only the servers IP
> or name. I get user not found in current context -100: access has been
> denied. I go back to wgh with tree and context supplied to nwlogin no
> problem. This was all done after intial login.
>



--
Craig Wilson
Novell Product Support Forum Sysop
Master CNE, MCSE 2003, CCN
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login

This is the result of the trace:

14:07:29 91B5E080 Agent: DSARead failed, no such attribute (-603).
14:07:29 91B5E080 Agent: Calling DSARead conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: DSARead failed, no such attribute (-603).
14:07:29 91B5E080 Agent: Calling DSARead conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: DSARead failed, no such attribute (-603).
14:07:29 91B5E080 Agent: Calling DSARead conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: DSARead failed, no such attribute (-603).
14:07:29 91B5E080 Agent: Calling DSAResolveName conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: Calling DSAReadObjectInfo conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: Calling DSAResolveName conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: Calling DSAReadObjectInfo conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: Calling DSARead conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: DSARead failed, no such attribute (-603).
14:07:29 91B5E080 Agent: Calling DSARead conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: DSARead failed, no such attribute (-603).
14:07:29 91B5E080 Agent: Calling DSARead conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: DSARead failed, no such attribute (-603).
14:07:29 91B5E080 Agent: Calling DSARead conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: DSARead failed, no such attribute (-603).
14:07:29 91B5E080 Agent: Calling DSARead conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: DSARead failed, no such attribute (-603).
14:07:29 91B5E080 Agent: Calling DSARead conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: DSARead failed, no such attribute (-603).
14:07:29 91B5E080 Agent: Calling DSARead conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: DSARead failed, no such attribute (-603).
14:07:29 91B5E080 Agent: Calling DSAResolveName conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: Calling DSAReadObjectInfo conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: Calling DSAResolveName conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: Calling DSAReadObjectInfo conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: Calling DSARead conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: DSARead failed, no such attribute (-603).
14:07:29 91B5E080 Agent: Calling DSARead conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: DSARead failed, no such attribute (-603).
14:07:29 91B5E080 Agent: Calling DSARead conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: DSARead failed, no such attribute (-603).
14:07:29 91B5E080 Agent: Calling DSARead conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: DSARead failed, no such attribute (-603).
14:07:29 91B5E080 Agent: Calling DSARead conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: DSARead failed, no such attribute (-603).
14:07:29 91B5E080 Agent: Calling DSARead conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: DSARead failed, no such attribute (-603).
14:07:29 91B5E080 Agent: Calling DSARead conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: DSARead failed, no such attribute (-603).
14:07:29 91B5E080 Agent: Calling DSAResolveName conn:63 for client
..WGH.CHS.UNX.UNX.
14:07:29 91B5E080 Agent: Calling DSAResolveName conn:65 for client
..[Public].
14:07:36 8E705440 Agent: Calling DSARead conn:16 for client
..NFAUUser.CHS.UNX.UNX.
14:07:36 8E705440 Agent: DSARead failed, no such attribute (-603).
14:08:01 94055200 Agent: Calling DSAGetServerNetAddress conn:65 for
client .[Public].
14:08:01 94055200 Agent: Calling DSAResolveName conn:65 for client
..[Public].
14:08:01 94055200 Agent: Calling DSARead conn:19 for client
..SRV2.CHS.UNX.UNX.
14:08:01 94055200 Agent: Calling DSAResolveName conn:19 for client
..SRV2.CHS.UNX.UNX.
14:08:01 94055200 Agent: Calling DSARead conn:19 for client
..SRV2.CHS.UNX.UNX.
14:08:01 94055200 Agent: Calling DSARead conn:19 for client
..SRV2.CHS.UNX.UNX.
14:08:01 94055200 Agent: DSARead failed, no such attribute (-603).
14:10:13 8AD1D3E0 Agent: Calling DSAGetServerNetAddress conn:62 for
client .WGH.CHS.UNX.UNX.
14:10:13 8AD1D3E0 Agent: Calling DSAGetServerNetAddress conn:62 for
client .WGH.CHS.UNX.UNX.
14:10:13 8AD1D3E0 Agent: Calling DS Ping conn:62 for client
..WGH.CHS.UNX.UNX.
14:10:13 8AD1D3E0 Agent: Calling DS Ping conn:62 for client
..WGH.CHS.UNX.UNX.
14:10:13 8AD1D3E0 Agent: Calling DSAGetServerNetAddress conn:65 for
client .[Public].
14:10:13 8AD1D3E0 Agent: Calling DSAGetServerNetAddress conn:65 for
client .[Public].
14:10:13 8AD1D3E0 Agent: Calling DSAGetServerNetAddress conn:62 for
client .WGH.CHS.UNX.UNX.
14:10:13 8AD1D3E0 Agent: Calling DSAGetServerNetAddress conn:62 for
client .WGH.CHS.UNX.UNX.
14:10:19 838F0480 Conn: Process Watchdog reply on remote inconn 6,
udp:192.168.30.200:524, succeeded
14:11:12 8D6AB260 Agent: Calling DSAResolveName conn:65 for client
..[Public].
14:11:12 8D6AB260 Agent: Calling DSARead conn:2 for client
..SRV2.CHS.UNX.UNX.
14:11:12 8D6AB260 Agent: DSARead failed, no such attribute (-603).
14:12:13 8AD1D3E0 Agent: Calling DSAGetServerNetAddress conn:62 for
client .WGH.CHS.UNX.UNX.
14:12:13 8AD1D3E0 Agent: Calling DSAGetServerNetAddress conn:62 for
client .WGH.CHS.UNX.UNX.
14:12:13 8AD1D3E0 Agent: Calling DS Ping conn:62 for client
..WGH.CHS.UNX.UNX.
14:12:13 8AD1D3E0 Agent: Calling DS Ping conn:62 for client
..WGH.CHS.UNX.UNX.
14:12:13 8AD1D3E0 Agent: Calling DSAGetServerNetAddress conn:65 for
client .[Public].
14:12:13 8AD1D3E0 Agent: Calling DSAGetServerNetAddress conn:65 for
client .[Public].
14:12:13 8AD1D3E0 Agent: Calling DSAGetServerNetAddress conn:62 for
client .WGH.CHS.UNX.UNX.
14:12:13 8AD1D3E0 Agent: Calling DSAGetServerNetAddress conn:62 for
client .WGH.CHS.UNX.UNX.
14:12:22 8A43C120 Agent: Calling DSAGetServerNetAddress conn:65 for
client .[Public].
14:12:23 8A43C120 Agent: Calling DSAGetServerNetAddress conn:65 for
client .[Public].
14:12:23 8A43C120 Agent: Calling DSAGetServerNetAddress conn:65 for
client .[Public].
14:12:23 8A43C120 Agent: Calling DSAGetServerNetAddress conn:65 for
client .[Public].
14:12:23 8A43C120 Agent: Calling DSAGetServerNetAddress conn:65 for
client .[Public].
14:12:24 8A43C120 Agent: Calling DSAGetServerNetAddress conn:65 for
client .[Public].
14:12:24 8A43C120 Agent: Calling DSAGetServerNetAddress conn:65 for
client .[Public].
14:12:24 8A43C120 Agent: Calling DSAGetServerNetAddress conn:65 for
client .[Public].
14:12:45 838F0480 Agent: Calling DSAResolveName conn:65 for client
..[Public].
14:12:45 838F0480 Agent: Calling DSARead conn:19 for client
..SRV2.CHS.UNX.UNX.
14:12:56 83A143A0 Agent: Calling DS Ping conn:65 for client .[Public].
14:12:56 83A143A0 Agent: Calling DSAResolveName conn:65 for client
..[Public].
14:12:56 83A143A0 Agent: Calling DSAReadObjectInfo conn:2 for client
..SRV2.CHS.UNX.UNX.
14:12:56 83A143A0 Agent: Calling DSARead conn:2 for client
..SRV2.CHS.UNX.UNX.
14:12:56 83A143A0 Agent: DSARead failed, no such attribute (-603).
14:12:56 83A143A0 Agent: Calling DSAResolveName conn:2 for client
..SRV2.CHS.UNX.UNX.
14:12:56 83A143A0 Agent: Calling DS Ping conn:65 for client .[Public].
14:12:56 83A143A0 Agent: Calling DSAResolveName conn:65 for client
..[Public].
14:12:56 83A143A0 Agent: Calling DSAReadObjectInfo conn:2 for client
..SRV2.CHS.UNX.UNX.
14:12:56 83A143A0 Agent: Calling DSARead conn:2 for client
..SRV2.CHS.UNX.UNX.
14:12:56 83A143A0 Agent: DSARead failed, no such attribute (-603).
14:12:56 83A143A0 Agent: Calling DSAResolveName conn:2 for client
..SRV2.CHS.UNX.UNX.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login

This was at the beginning of the first trace but got cut off.

14:18:19 8AA742C0 Agent: Calling DSAResolveName conn:63 for client
..WGH.CHS.UNX.UNX.
14:18:19 8AA742C0 Agent: DSAResolveName failed, no such entry (-601).

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.