Anonymous_User Absent Member.
Absent Member.
1109 views

Simplest client installation for XP Pro and NW 5.0 SP6

 
Labels (1)
0 Likes
8 Replies
Anonymous_User Absent Member.
Absent Member.

Simplest client installation for XP Pro and NW 5.0 SP6A

Oops; somehow I posted the message without text.

At any rate, I'd like to accomplish the simplest installation possible of
the Novell Client for XP Pro and a NW5.0SP6A server. We're converting to
IP, which is already bound in the server, and the XP Pro clients already
have TCP/IP installed, as they access the 'net thru a premises DHCP router.

We've had lots of problems with the latest Client (4.91 SP2), and it looks
like way more than we need. I'm installing 4.83 SP3, but we've still had
problems like the dreaded "Tree or server not found" error.

What's the minimum Client configuration to access a NW5.0SP6A server (no
NMAS or NICI) via NDS? In reading the 4.91 app note, it suggests that LDAP
contextless login must be enabled; but why? Isn't locating the server
using its NDS name much simpler than that?

Help us to wade thru this swamp. Much obliged.

André
San Jose, CA.


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Simplest client installation for XP Pro and NW 5.0 SP6A

André,

Assuming IP is bound to NetWare and SLP is adequately configured,
install the client manually or via ACU to install IP-only with no other
components checked.

Contextless login is not required. Just a nice to have.
Which app not are you speaking of?

Many of the other components are usually used in more developed
OES/NetWare 6.x environments.

--
Tony Pedretti
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Simplest client installation for XP Pro and NW 5.0 SP6A

Thanks for your note, Tony.

IP is bound to NetWare, and that's working correctly as the server
maintains its clock using an Internet time service.

Installing the 4.83SP3 client works correctly, and no other components are
selected. We don't use NDPS or NMAS, or any other features.

When you say "SLP is adequately configured," that might be a clue. To my
knowledge, the server's SLP configuration has not been tested. Maybe
therein lies the problem. I'll look into it.

The App Note that I was referring to is here:
www.novell.com/coolsolutions/appnote/620.html

Any other thoughts? We've been spinning our wheels on this one, and we'd
like to get it working ASAP. Thanks again.

André
San Jose, CA.

> André,
>
> Assuming IP is bound to NetWare and SLP is adequately configured,
> install the client manually or via ACU to install IP-only with no other
> components checked.
>
> Contextless login is not required. Just a nice to have.
> Which app not are you speaking of?
>
> Many of the other components are usually used in more developed
> OES/NetWare 6.x environments.
>
> --
> Tony Pedretti


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Simplest client installation for XP Pro and NW 5.0 SP6A

What error(s) are you experiencing with the 4.91 SP2 client?

Masking any info. you might consider a security hazard please post the
results of SLPINFO /A run from the command-prompt on Windows.

Windows Event logs showing anything unusual?

Security or any other driver-based software like firewall, VPN, remote
management, antivirus, etc. installed and running?

--
Tony Pedretti
0 Likes
Highlighted
Anonymous_User Absent Member.
Absent Member.

Re: Simplest client installation for XP Pro and NW 5.0 SP6A

Thanks for your note, Tony.

The only error is the "Tree or server not found" message when attempting
to log in (XP Pro SP2 PC running Client 4.83 SP3). Nothing appears in the
event logs that's connected with authentication to the NW server. NAV 2006
is running, and a firewall is built into our subnet router, so no software
involved.

Here's the SLPINFO /A output:
*****************************************************
*** Novell Client for Windows NT ***
*** Service Location Diagnostics ***
*****************************************************

SLP Version: 1.0
SLP Start Time: 7:39:11pm 4/3/2006
Last I/O: 7:39:23pm 4/3/2006
Total Packets: Out: 10 In:
Total Bytes: Out: 340 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 2 hops


SLP Timers Values
------------------------------------- ------------
Give Up on Requests to SAs 3 seconds
Close Idle TCP Connections 5 minutes
Cache SLP Replies 5 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 Local Interface Scope(s)
--------------- --------- ----- --------------- -------------------
----
<No Directory Agents>



Local Interface 192.168.5.106
---------------------------------
Operational State: UP
Operating Mode(s): MCAST
SA/UA Scopes: <unscoped>
Last I/O: 7:39:23pm 4/3/2006
Total Packets: Out: 10 In:
Total Bytes: Out: 340 In:
Last Addr Out: 224.0.1.35
Last Addr In: 0.0.0.0

We're still coming up to speed on SLP, so it's most likely incorrectly
configured. I'm reading all of the app notes and TIDs that apply. The
SLPINFO dump doesn't mean a great deal to us (yet).

Hope this helps.

André
San Jose, CA.

> What error(s) are you experiencing with the 4.91 SP2 client?
>
> Masking any info. you might consider a security hazard please post the
> results of SLPINFO /A run from the command-prompt on Windows.
>
> Windows Event logs showing anything unusual?
>
> Security or any other driver-based software like firewall, VPN, remote
> management, antivirus, etc. installed and running?
>
> --
> Tony Pedretti


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Simplest client installation for XP Pro and NW 5.0 SP6A

SLP is the default and preferred name/service resolver for NetWare 5.0 and
above over IP. Its like a combination of WINS and DNS the IETF
first released in 1997. If your servers and workstations are on separate
VLANs or subnets, you'll want to have SLPDA setup and configured for your
clients. Consider having one setup or 2 for redundancy. Unless your
environment is huge or distributed over slow WAN links, a single scope works
best.

These TIDs will give you some additional SLP background, the steps to
configure a DA, and links to others for more detail...

SLP Terms and Configuration Reference
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10014396.htm

Configuring SLP with a SCOPED directory agent (DA)
http://support.novell.com/cgi-bin/search/searchtid.cgi?10059981.htm

4.91 SP2 is current and therefore has the best support. Even with a base
install you would also be able to configure the client with Group Policy...

CLIENT 4.9x ADM
Administrative Template for Novell Client 4.9x
http://www.novell.com/coolsolutions/tools/1903.html

Then consider any applicable post-updates...

Production patches for 4.91
http://support.novell.com/filefinder/20609/index.html

Beta patches for 4.91 (beta in most cases has the most fixes but hasn't been
baked as thoroughly)
http://support.novell.com/filefinder/20609/beta.html

--
Tony Pedretti
TransUnion Corporation


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Simplest client installation for XP Pro and NW 5.0 SP6A

I had one client with over 500 sites and relatively slow WAN Links.
Novell Consulting even recommended a single scope for them. ( Yeah, it
took a few tweaks, but even in their case Novell designed a single scope.)

> environment is huge or distributed over slow WAN links, a single scope works
> best.


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

Re: Simplest client installation for XP Pro and NW 5.0 SP6A

I agree you would really need to be at wits end or otherwise have a specific
need to split it up.
As we've seen around here with enough tweaks you can get away with just
about anything.

--
Tony Pedretti
TransUnion Corporation


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.