Cant see the tree

Hi,

We have a strange problem today. almost every clients can't connect because they dont find the tree. Some people have been able to connect after many reboot from their computer.

The client config is WinXp Sp3 and Novell client 4.91 SP4
some with the 6.5 agent and some with agent 10
they both have the problem.

We have many servers in different cities but they are all linked together on the same network. The problem was seen in all cities.

Any idea ?
  • Sounds like you have SLP problems. Have you checked that SLP is working? What happens if you enter the IP address of a server in the tree field of the Novell client?

    This thread should be logged under edirectory or Novell client not talk to a TSM too.
  • You were right. When entering the Tree IP Address instead of the tree name it works.

    Now, i'm just wondering why this just happended now since no changes have been made to the server....

    And for the topic move... Can i move the topic to the other section myself ?
  • Hmm something funny on your SLPDA probably.

    On a client check slpinfo /a and see if you are getting SLP delivered. Then check on your server too.

    DW a forum admin should be able to move it over.
  • Hmm something funny on your SLPDA probably.

    On a client check slpinfo /a and see if you are getting SLP delivered. Then check on your server too.

    DW a forum admin should be able to move it over.
  • With the SLPinfo /all command it seems i have no DA but i have been able to log in...

    here's what i have :

    *****************************************************
    *** Novell Client for Windows NT ***
    *** Service Location Diagnostics ***
    *****************************************************

    SLP Version: 4.91.3.0
    SLP Start Time: 11:11:07am 11/17/2010
    Last I/O: 11:12:01am 11/17/2010
    Total Packets: Out: 37 In:
    Total Bytes: Out: 1618 In:


    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>


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

    <No Directory Agents>



    Local Interface 10.148.3.168
    ---------------------------------
    Operational State: UP
    Operating Mode(s): MCAST
    SA/UA Scopes: <unscoped>
    Last I/O: 11:12:01am 11/17/2010
    Total Packets: Out: 18 In:
    Total Bytes: Out: 792 In:
    Last Addr Out: 224.0.1.35
    Last Addr In: 0.0.0.0


    Local Interface 198.168.56.1
    ---------------------------------
    Operational State: UP
    Operating Mode(s): MCAST
    SA/UA Scopes: <unscoped>
    Last I/O: 11:11:42am 11/17/2010
    Total Packets: Out: 19 In:
    Total Bytes: Out: 826 In:
    Last Addr Out: 224.0.1.35
    Last Addr In: 0.0.0.0

    *****************

    On our OES2 server we have the info entered in the SLP.conf for :
    net.slp.useScopes = XXX_SCOPE
    net.slp.DAAddresses = xxx.xxx.xxx.xxx

    but it is not configured in the dhcpd.conf.

    option slp-directory-agent true xxx.xxx.xxx.xxx;
    option slp-service-scope true "DEFAULT";

    Is the DA required for the SLP ?
  • Yes, SLP absolutely reequires there to be at least one DA.

    We don't move threads in these forums, sorry. Check out the documentation for your NOS re SLP, if you need more help post in the relevant server OS forum.