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


craig wilson wrote:
> try .wgh.chs.unx (leading dot)
> I presume that unx is your O and not tree name.


Tried it with the (dot) first and without tree name and context as
before and I was able to login normally using either srv2 or its IP.

Bill

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login

Something with SLP is likely not working properly.

1)Ensure that the SLP.CFG file on each server points to the SLPDA
server. (The SLPDA server does not need to point to itself, but should
point to other SLPDA servers)
(Issue "Set SLP RESET=ON" if you fix this on a server)


2) Ensure that "SET SLP SCOPE NAME" is set to the correct scope name on
each server. (Server Reboot is needed if this is wrong.)

Thinking back that you only have two servers and both show up in the
"DISPLAY SLP SERVICES" request confuses me to what the issue could be.
-------------------------------------------------------------------------




Bill H wrote:
> craig wilson wrote:
>> try .wgh.chs.unx (leading dot)
>> I presume that unx is your O and not tree name.

>
> Tried it with the (dot) first and without tree name and context as
> before and I was able to login normally using either srv2 or its IP.
>
> Bill
>



--
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:
> Something with SLP is likely not working properly.
>
> 1)Ensure that the SLP.CFG file on each server points to the SLPDA
> server. (The SLPDA server does not need to point to itself, but should
> point to other SLPDA servers)
> (Issue "Set SLP RESET=ON" if you fix this on a server)
>
>
> 2) Ensure that "SET SLP SCOPE NAME" is set to the correct scope name on
> each server. (Server Reboot is needed if this is wrong.)
>
> Thinking back that you only have two servers and both show up in the
> "DISPLAY SLP SERVICES" request confuses me to what the issue could be.
> ------------------------------------------------------------------------

There are only 2 netware servers involved in this, should be simple
huh, I wish it was.

The SLP.CFG file in srv1 has only one line:
DA IPV4, 192.168.10.200

192.168.10.200 (srv2) is the DA and everything else is a comment.

What is ment by "The last line must contain a line feed and char
return. A semi-colon specifies a comment." spacifically the first
sentence.

The SLP.CFG file in srv2, the DA server, is empty except for comments.

Our network has fixed IP addresses and does not use DHCP at all. There
are no scope names and none are configured.

The client has one IP address in the directory agent list box,
192.168.10.200, nothing in scope list box, and I have had static box
both checked and unchecked.

Display SLP Services on both servers show binds to srv1 and srv2.

I have noticed IPXS.nlm, IPXSPX.nlm. IPXRTR.nlm still loading on both
servers. IPX in no longer being used, could these nlms cause problems
with SLP?

Bill

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login


I should of added Multicast is disabled on both servers.
Enabled on both is Static configuration SLP.cfg, Disable Multicast
After DHCP, Static.

The srv1 in norm shows 192.168.10.200 as discovered DA and active.

Bill

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Context appears only after login


There is a happy ending for those of you who like me who read through
these long posts looking for answers.

Mr. Wilson was right, it was 2 problems.

1. Not seeing the tree or not seeing the context, depending on your
remote location in our network was a replica issue. Master [root]
replica was gone only a read write remained.
I used dsrepair to upgrade it to master replica and made sure my
partitions had their replicas placed properly on our servers. Problem
Solved.

2. login script giving me the unkown server (890) connecting to remote
server, srv1, was fixed by pushing down some route adds to our clients
"route -p add 192.168.20.0 mask 255.255.255.0 192.168.10.255" -p makes
it persistent. Now the login script has no problem seeing servers.

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.