Anonymous_User Absent Member.
Absent Member.
993 views

Client 4.91 SP3 Not Attaching to Specified Server

Have a current network of users with Win2K PCs logging in with Netware
client 4.83. This all works fine. No user has an individual login script.
They all use the root script which has a number of map commands; some
based up login name (MAP S3:=sys:test, etc.). The client also logs in to a
specific server in the tree.

Am now setting up all new Windows XP PCs with Netware client 4.91 SP3. It
sees the tree and the servers. I set it up to log in to the same specific
server. When I log in, it does not log in to that server, even though I
picked it out of the list in the client advanced screen (and does none of
the mapping in the script). In fact, if I manually try to map a drive to
that server I get a "path not found" error. It does attach to one of the
servers on the network, but not the one specified.

Thank You

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

Re: Client 4.91 SP3 Not Attaching to Specified Server

Delete the treename, context and server name fields in the gui login,
and put the desired server's IP address in the server name field. If you
can then connect to it, you have an SLP issue; if not it's something
else. Are the new PCs in a new subnet perhaps?

First step would be to disable the bad address cache and bad name cache
temporarily, see if that helps.
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Client 4.91 SP3 Not Attaching to Specified Server

This server (and most others in tree) do not have IP addresses. They are
just plain Netware 4.11 IPX/SPX. The one the client attached to is the
only one that happens to use IP.

Thanks,


> Delete the treename, context and server name fields in the gui login,
> and put the desired server's IP address in the server name field. If you
> can then connect to it, you have an SLP issue; if not it's something
> else. Are the new PCs in a new subnet perhaps?
>
> First step would be to disable the bad address cache and bad name cache
> temporarily, see if that helps.
> --
> Andrew C Taubman
> Novell Support Forums Volunteer SysOp
> http://support.novell.com/forums
> (Sorry, support is not provided via e-mail)
>
> Opinions expressed above are not
> necessarily those of Novell Inc.


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Client 4.91 SP3 Not Attaching to Specified Server

That would have been useful to know in the OP ... so did you install the
client with both IP and IPX?
--
Andrew C Taubman
Novell Support Forums Volunteer SysOp
http://support.novell.com/forums
(Sorry, support is not provided via e-mail)

Opinions expressed above are not
necessarily those of Novell Inc.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Client 4.91 SP3 Not Attaching to Specified Server

1) Make sure each user has the "default server" attribute set in NDS

2) Make sure you remove the NMAS client from your workstations. Having the
NMAs client installed will force your workstations to do their login
through a server with NMAS support installed (typically a NetWare 6.0 or
later server).

3) With 4.11 servers in your tree, maybe it's best to stick with a fully
patched 4.83 client. The 4.9x clients have many new features that are
specific to NetWare 6.x and that might cause problems on 4.11 servers.
Beside, the new clients have not tested with such old NetWare versions.

--
Marcel Cox (using XanaNews 1.18.1.6)
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.