Clients can not find the tree 1

[phart]

My problem is my workstations have trouble finding the tree. I have SLP configured (not sure if it is right). I have the DA set up in the workstation client. I will log into the tree just fine, but then I will restart the workstation and will not be able to find the tree. The only way I have found around this is to manually put the server IP in the client login. I thought the correct way to login now was to just login to the tree and not the server.

 

[terry712]

ok - it's slp most likely

it's very simple

check the server first - the slpda is running - yes
ie display slpda - should say yeeha - and say it's working and a scope

distribute the scope and da through dhcp
option 78 and 79
if it's a dhcp from shall we say another vendor - you need to create these options

on the client
drop to dos
type slpinfo /all

it will say it's found da and scope etc - or it should i suspect it doesnt

on each server they should all point to the da
it's in the sys:etc/slp.cfg line da 10x.x.x

now in slp parameters in monitor or think you can imanage it?
look at options - set the scope and also one line that say slp da discovery or something like that - defaults to 15
i dont like this i prefer 4 as i know my slp.cfg is correct and there

DONT point the DA to itself - it's bad - it will lookback

there are lots of tids on this - but it is worth fixing
as the real preference and some may disagree but i like to see the server left blank in the advanced login

 

[marvhuffaker]

The fact that you have to enter the ServerID in the login screen confirms that SLP is not setup correctly. You should not need to do this.

How is your scope defined. Have you configured SLP services on the server? Do you have a DA defined and is it running?

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[Pauzotah]

I have also had an issue identical to this which was caused when i upgraded my 4.11 Server to 6.5. As the 4.11 server was running IPX, it stills runs IPX as 6.5.

I needed to run SLP because wireless laptops dont usually like communicating via IPX as some network printers dont either.

What worked for me was reinstalling clients and making sure if they were wired enabling IPX if they were laptops that wouldnt work through IPX, setting them to IP only.

As for the SLP, these guys above are spot on with what they say, i have done the same.

All this only applies, in my opinion, if you have upgraded from an older version of netware, if yours is a fresh install then it defualts to IP in the setup.

Hope this helps

 

[phart]

terry712,

yes slpda is running.

I had option 78 set but the Ip number was not showing up. I remove it and re added it is now showing the value. I had not set option 79 but now it is.

I have my slp discovery set to 5, I read some where that this was a good value. Should I change it to 4?

C:\>slpinfo /all


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

SLP Version: 4.91.0.0
SLP Start Time: 8:34:52am 7/18/2006
Last I/O: 8:37:11am 7/21/2006
Total Packets: Out: 10250 In: 11
Total Bytes: Out: 451061 In: 322


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>
eoc_slp DA


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

xx.x.x.xxx CNFG NORSP ? xx.xx.x.xx <unknown>

xx.x.x.xxx DHCP UP SLPV2 xx.x.x.xxx eoc_slp


Local Interface xx.x.x.xxx
---------------------------------
Operational State: UP
Operating Mode(s): MCAST,STATIC-DA
SA/UA Scopes: <unscoped>,eoc_slp
Last I/O: 8:37:11am 7/21/2006
Total Packets: Out: 10250 In: 11
Total Bytes: Out: 451061 In: 322
Last Addr Out: xx.x.x.xxx
Last Addr In: xx.x.x.xxx

Leaving the server blank in advanced login is what I have read is the best method and that is what I am trying to get done.

Since I changed option 78 and 79 I will let you know how that worked. Please let me know if you see anything wrong in the SLP /info listing.

Thanks for your help.

 

[phart]

Sorry that I have not replied as to the results. I wanted to make sure that everything was working. Thank you Terry712, I think the major problem was in my DHCP configuration. It was not giving out the corrcet info. I am still getting told, very seldom, that slp is down. This is not happending often and I can live with it.

 

[terry712]

good to here

it may flush it's self out once all the leases have been reapplied for