Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

How to configure Novell Win98 client to log on to NT domain

1 view
Skip to first unread message

pea...@attglobal.net

unread,
Jan 23, 2004, 10:35:49 AM1/23/04
to
My network is an NT domain and I have individuals who are traveling to a
client that has a Novell network. I have been told that I can setup the
Novell Client on my boxes and when they are at our client's office they
could log on to the Novell network and when they are back at our office the
Novell Client will allow them to logon to our NT domain. Is this true and
how do I set it up so that I use the Novell Client to logon to either of the
networks? I have win98SE, win2k, and winxp boxes that would require this
ability. Thank you for any help that can be provided in this matter.
Thaddeus Corrigan, corri...@pearldc.com, 303.838.8090.

I have rec'd feedback from the win2k forum concerning the Novell 2k and xp
client configuration. I tried to do the same config with the Novell win98
client. At the login screen when I switch the location to the domain I
enter the username and password but the "OK" button is still grey. There
must be something different in the configuration of the win98 Novell client
vs the Novell win2k/xp client in order to logon to a NT domain. What am I
missing.

This is response from win2k/xp forum:
For the 2K/XP boxes, you can setup location profiles.

Go into the client properties, Location profiles. In the "New Location
Profile"
enter "Domain", hit Add, then "NetWare" hit Add (feel free to change the
names),
then configure each of the profiles.

Highlight the Domain profile, hit Properties, put a "Domain" entry into the
"Service Instance" field, hit Add. On the next screen ensure that "Active
Authenticator" is NOT ticked on both the NDS and Bindery tabs. On the
Windows
TAB enter the user name and domain. Hit OK.If prompted that there is no
active
authenticator enabled, hit OK or yes. Hit OK on when you're back on the
"Services" screen.

Repeat for the "NDS" profile - Highlight the NDS profile, hit Properties,
put a
"NDS" entry into the "Service Instance" field, hit Add. On the next screen
ensure that "Active Authenticator" IS ticked on the NDS tab. Enter the
relevant
tree/context/server information. Hit OK.

Finally, when you back at the client properties screen, go to the Advanced
Login
tab, enable the "Location List Feature" under "Show on Login".

From then on when you get to the login screen you can select the appropriate
location from the dropdown.

It may be the same process for the Win9x boxes - but haven't touched one of
those in a looooooong time. <g> If it looks different, ask over in the
Client9x
forum

--
Hamish Speirs
Novell Support Forums Volunteer Sysop


Edison Ortiz

unread,
Jan 23, 2004, 11:25:22 AM1/23/04
to

You need to change your Initial Login Client order by going into
Control Panel | Network and set the Microsoft Client to have the
initial login. In Windows9x, you need to authenticate to MS first
then Novell. If the credentials in MS are the same as Novell, the
MS Client will transfer the information over to the Novell Client
and a single login will occur.

--
Edison Ortiz
Novell Product Support Forum SysOp
(No Email Support, Thanks !)

Gerald Reynolds

unread,
Jan 27, 2004, 11:26:16 AM1/27/04
to
Here's what we do for Win 9x clients. A similar approach may work for
W2K and XP clients. (See particularly the WINS tab off the Advanced
button of the NIC's IP properties.)

The NetWare client is the primary login. The Client for Microsoft
Networks must be installed. On its properties sheet (it has only a
General tab) check Log on to Windows NT domain and provide the domain
name. The client must be able to find the domain server. We use
lmhosts for that. In the Windows folder of the client we place an
lmhosts file that reads:
#begin_alternate
#include \\servername\lmhosts
#end_alternate
where servername is the NetBIOS name of the domain server.

The domain server must also have an lmhosts file that the above file
references. At this writing ours is down and I don't have a ready copy
of that file, but it should look as follows:
123.45.67.89 servername #PRE #DOM:domainname
In other words, the server's own IP address, its own NetBIOS name, and
the domain name by which it is known to other systems. Read Microsoft's
documentation on lmhosts for more information.

Gerald Reynolds

pea...@attglobal.net

unread,
Jan 28, 2004, 5:52:13 PM1/28/04
to
Gerald, thank you for your help. I am assuming that the Novell win98 Client
does not acknowledge the lmhosts files, that is why you suggest using the MS
Client for Netware? Is this a true statement? I have set it up like you
have suggested, with the exception that I am using the Novell win98 client
rather thatn the MS Client. My lmhost file is working fine but the Novell
win98 client fails to recognize a "Netware" server, so the logon client
never is presented for logon. Again, I am assuming that this client does
not acknowledge the lmhost file and thereofre you suggest using the MS
Client? Is this the reason for using the MS client?

If I use the MS client for Netware, to complete your suggestions, do I have
the choice of using IP only or does this client use only IPX?


"Gerald Reynolds" <grey...@cccsda.org> wrote in message
news:IiwRb.843$Wh....@prv-forum2.provo.novell.com...

Donald Albury

unread,
Jan 28, 2004, 7:10:48 PM1/28/04
to
On Wed, 28 Jan 2004 22:52:13 GMT, <pea...@attglobal.net> wrote:

>Gerald, thank you for your help. I am assuming that the Novell win98 Client
>does not acknowledge the lmhosts files, that is why you suggest using the MS
>Client for Netware?

The Novell Client for NetWare for Win 9x can use a NWHOST file. See
the client documentation for more information.

>If I use the MS client for Netware, to complete your suggestions, do I have
>the choice of using IP only or does this client use only IPX?

The Microsoft Client for NetWare is IPX only.

Donald Albury
Novell Product Support Volunteer SysOp
Sorry, no replies to e-mail responses

0 new messages