• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1223
  • Last Modified:

Using Netware over different Subnet

Hi.. hopefully simple question.

We have a single subnet network and are about to take on another office that i want to place onto a different subnet. In advance of this i have created a test network on a different subnet and connected up a PC to it.

ie.. main network sits on a 10.0.0.0/16 network  (yes i know its too big but thats the history of this place)
and my new test network now sits on 10.5.0.0/16

i have placed an XP machine on there that used to work fine on the previous network and reconfigured IP etc.. (using DNS servers from 10.0 subnet) I then logged in locally  and tested some pings.. by Ip and DNS name to both windows and netware servers (all ok)

I then logged off and tried a proper logon through the netware client and it cant see the tree.. the only way i can get it to log on is by manually typing in a server name in the server name drop down (which we normally leave blank) and it will eventually log on - although it takes ages and ages.

any ideas.. what i am missing here? why do i need to type in a server name and why cant i see the tree?! and why does it take so long!

thanks

We are using a mix of Netware 6.0 Sp5 and Netware 6.5 sp2 servers.. all IP settings are set correctly on these machines.. (as proved with the pings)

0
huziy
Asked:
huziy
  • 10
  • 8
  • 3
  • +1
2 Solutions
 
PsiCopCommented:
Is Service Location Protocol (SLP) configured correctly on NetWare?

How does the XP box get its IP address information? If via DHCP, does it get SLP or eDirectory Options in its DHCP reply?

If not, does the routing setup allow broadcast or multicast traffic? Client 32 will fall back to that if it can't get SLP info any other way.

Sounds like this is an SLP issue.
0
 
huziyAuthor Commented:
thanks for the reply..

I have just assigned a static IP to the XP box.

and i havent allowed any broadcast through the router..

I believe you are correct as i can remember someone talking about this in the past.. forgive my Netware ignorance with this.. but how can i ensure SLP is setup correctly?

thanks
0
 
ShineOnCommented:
SLP doesn't do broadcast by default - it's multicast by nature.  It can also be unicast, which is what you probably want to do.

So, if you're disallowing multicast, then that's why.  You have to specify the DA server IP via a) DHCP or b) the Service Location configuration tab in the Novell client properties.

If the other subnet will have a server, its SA should reference the DA on the other subnet, directly, through SYS:\ETC\SLP.CFG.

If you don't have a DA server, you need to re-configure your SLP to use a DA.  There are several PAQs in this TA that discuss SLP configuration and implementation.
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
huziyAuthor Commented:
Id look this up my self bokut the Novell Site has been down all afternoon..... makes a change!
0
 
huziyAuthor Commented:
ok.. i think that SLP has not been setup on this network. So i need to create the Scopes and DA's etc..

although console one keeps telling me i dont have the snapins for it... will go find the CD and see if i can install them...

many thanks
0
 
ShineOnCommented:
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10062474.htm

is a TID called "SLP Design and Implementation Guidelines."  It should help a lot figuring out how to do it.  

Also do a search on E-E in this TA for "SLP Configuration" for even more help.
0
 
PsiCopCommented:
Yes, many of Novell's sites are having connectivity problems today. Note sure if its an intervening peering point or what.
0
 
PsiCopCommented:
Seems like whatever issue it was cleared up yesterday.
0
 
huziyAuthor Commented:
When i try and add SLP objects in my console one it indicates i dont have the snapins.. any ideas where i can get hold of these?
0
 
huziyAuthor Commented:
i have been trying to follow this... http://www.novell.com/documentation/ndsedir86/index.html?page=/documentation/ndsedir86/taoenu/data/a5eyqkl.html

but when i type slpda i just get "Module initialization failed" - not getting very far here!
0
 
ShineOnCommented:
Are you doing this on a NW6 or NW6.5 server?  Are there any messages in the logger screen?  Are there any SLP objects already configured, and if so, are there any SLPDA server objects configured?

Re: ConsoleOne and snapins - what version of C1 are you using, and where are you running it from - is it a local copy, copied from a server, a locally-installed copy, directly from a server, or what?

Try running it directly from the SYS:/PUBLIC/MGMT location, from a NW6.5 server, just for kicks.
0
 
ShineOnCommented:
Are you doing this on a NW6 or NW6.5 server?  Are there any messages in the logger screen?  Are there any SLP objects already configured, and if so, are there any SLPDA server objects configured?

Re: ConsoleOne and snapins - what version of C1 are you using, and where are you running it from - is it a local copy, copied from a server, a locally-installed copy, directly from a server, or what?

Try running it directly from the SYS:/PUBLIC/MGMT location, from a NW6.5 server, just for kicks.
0
 
huziyAuthor Commented:
hiya

tried running this on both NW6 and NW6.5 server.. get the following on the NW6.5 machine..
-------------
Service location NDS Directory Agent
Version 2.12

SLP Directory agent has not been configured.

note:if this machine does not hold a replica, NWADMIN configuration is reccomended becuase the server object does not have rights to setup the default container.

Directory agent not configured.

error: DA has not been configured for any scopes or containers Server -5.70-1553: Module initialization failed.
Module SLPDA.NLM not loaded.

----------
no SLP objects configured as yet as far as i am aware.

tried running console one directly from the server but unfortunatley get the same issue.

I assume from the above i need to do this on a server that holds a replica??


0
 
huziyAuthor Commented:
Tried it on one with a replica... get the same error!
0
 
ShineOnCommented:
Yes, you must do it on a server that holds at least a read/write replica of the partition where the SLP objects will be created.  In a simple setup, that would probably be the O container, which is usually, in a simple setup, in the [Root] partition.

Regarding the snapins, try downloading C1 1.3.6e fresh, from http://download.novell.com/index.jsp?product_id=&search=Search&build_type=SDBuildBean&families=2647&version=&date_range=&keywords=&x=18&y=14

Install it locally, not to a server.  It should install all of the common snapins.   If it does, then you can probably install it to your servers.  If any specialty snapins are missing, copy their \resources\ and \snapins\ folders from another working ConsoleOne installation and test 'em in your new locally-installed C1.

The SLP snapins should be in <path>\ConsoleOne\1.2\resources\slpda and <path>\ConsoleOne\1.2\snapins\slpda.

The other common C1 snapins would be in subdirectories of resources and snapins, as well, and those directories would include: core, ice, ldap, nss and security.  

 
0
 
huziyAuthor Commented:
Downloaded that version of console one and same error.. telling me i dont have the snapins..

Also the dir slpda does not exist in the resources dir.

0
 
ShineOnCommented:
Download the eDirectory 8.7 snapin pack for C1: http://download.novell.com/Download?buildid=FCT5LqrhcGI~

Install it - it includes the snapins for SLPDA, LDAP and WAN traffic manager.
0
 
pspencer53Commented:
You shouldn't need to use ConsoleOne to create an SLP DA definition.   Simply load SLPDA.NLM /A on the NetWare server to create a nice default configuration.  
See http://support.novell.com/cgi-bin/search/searchtid.cgi?/10100796.htm and
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10098246.htm

Next, you need to set the SLPDA IP address in the client.   This is best done as part of the DHCP ticket.  
See http://support.novell.com/cgi-bin/search/searchtid.cgi?/10054413.htm  or
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q285019& depending on you DHCP server platform.

Or you could hard code the SLPDA in the Novell client.  
0
 
ShineOnCommented:
He's getting an error trying to load SLPDA, so it'd be nice to know if there's any configuration already there, hence the desire to see what  kind of SLP objects might already be there...

Hard-coding SLPDA doesn't help if you don't have a DA server.
0
 
pspencer53Commented:
In my travels, an SLP DA is not a product that needs much tuning, at least in a simple configuration like what he has.  The only time I would need to examine an existing SLP configuration is if there was a multi-site, multi-campus, multi-company kind of thing where you don' want users at one campus to browse servers at the other campus.   This is beyond the scope of any sites that I have worked at.

Anyway, in a single server environment, I would have no hesitation in creating a default set of SLP objects.  There is no value in seeign what the previous configuration was.  The command LOAD SLPDA /A will create what it needs to do the job.  In addition, you can then edit the new SLP objects to convert them to whatever configuration that you need.  (chage the scope, etc)

I just tested this on a NW65 server and it will create exactly what it needs, regardless of what objects pre-existed, so I am certain that this will fix any issues that are causing the SLPDA to not load.  

My advice?  Go for it and let the system create what it needs.  

0
 
ShineOnCommented:
We're not talking about tuning SLP, but making sure it's configured correctly to work across different subnets, which requires you to know how it's configured, if it is.  Apparently it's not, based on the error message the Asker posted, but I'm not talking about creating an SLPDA object in C1, either.  The plugins are necessary if you need to create a scope other than the default.  The asker says he can't see any SLP objects 'cause he doesn't have the snapins.  That's still an issue that should be addressed, although it may or may not be germane to getting things working.

This isn't a single system environment, by the way, and they're complicating SLP communications by adding another subnet.

The asker's getting an error message when attempting to load SLPDA saying it hasn't been configured, and in a multi-system environment that has to go across subnets, I suppose you might be able to get away with using the default scope that gets created but it'd be good to be able to configure your scope manually if the default's not good enough.

Configuration has to be done on a server holding a read/write replica of [Root], too, so it can create the service objects that get reported to it.  I'd also recommend sticking with a 6.5 server.  What you say may be true, in a quick-and-dirty sense, but IMHO doesn't fully address the issue, because it ignores the snapin issue, which precludes any use of the Novell-recommended SLP configuration guidelines.
0
 
huziyAuthor Commented:
I have a consultant with me on Tuesday and we plan to look over this.. I havent tried the SLPDA with the /A switch yet but i agree we should get the replica's on the 6.5 servers as some are currently on 6.0 servers.

So might tidy that up before configuring the SLP?

Will feed back the info gained here to the consultant and let you know how we get on and how/if we solved the error!

thanks
0
 
huziyAuthor Commented:
I ended up adding some replicas on to our 6.5 servers and running.. SLDA A from there... this setup the default configuration.. I then updated all the SLP.CFG files on all the servers and configured DHCP to hand out the SLP information...

Many thanks for all your help
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

  • 10
  • 8
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now