-----Original Message-----
From: mdw [mailto:mdw]On Behalf Of Mark Weaver
Sent: Monday, August 14, 2000 6:11 AM
To: Jose M. Sanchez; '[EMAIL PROTECTED]'
Subject: almost there: ref - novell servers


Hi there,

I hope you don't mind me emailing you directly. I got your message from
the list this morning concerning connecting a linux box to a Novell
server. I was the one that started that thread and after reading your
resonse I was thrilled. At last, I thought, I would be able to connect
to the servers. Well, I uninstalled the nwclient that I was trying to
use, and installed ncpfs.

I followed your instructions to the letter. Everything was working just
fine and I thought I was going to make it, but when I attempted to log
on to the servers I recieved a message that goes something like this:
----

The first thing you have to establish is whether or not IPX is installed and
running.

ifconfig should give you results similiar to this...

eth0      Link encap:Ethernet  HWaddr 00:10:5A:04:36:65
          inet addr:10.0.0.1  Bcast:10.255.255.255  Mask:255.0.0.0
          IPX/Ethernet II addr:000000A3:00105A043665
          IPX/Ethernet SNAP addr:00000032:00105A043665
          IPX/Ethernet 802.2 addr:0000003C:00105A043665
          IPX/Ethernet 802.3 addr:000000A2:00105A043665
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:39848620 errors:0 dropped:0 overruns:0 frame:0
          TX packets:22944038 errors:0 dropped:0 overruns:0 carrier:6
          collisions:70244 txqueuelen:100
          Interrupt:9 Base address:0xe400

There is quite a lot of information here. Notice the IPX/Ethernet and the
PROTOCOLS... I.E. 802.3, 802.2, SNAP, ETHERNET II. On my Linux box all are
active.

Your Linux box -MUST- have enabled the SAME protocol(s) that your Novell
server is using. If it doesn't your Linux box will never see them.

How do you do this?

Via Linuxconf...

Normally you can enable ALL the protocols and select AUTODETECTION of NET
Addresses/Protocols, in Linuxconf. This works.

Once done, try rebooting your machine, just in case. Then perform a ifconfig
command and see if you see the protocols.

If you do, the next step is to issue the "slist" command.

Do you see the server?

If so try logging in again...

Now here's the trick...

THE SERVER NAME -MUST- be entered in upper case. The username and password
is usually lower case.

The error you report, indicates that the server cannot be found on the LAN.
This in turn normally indicates a basic problem with IPX configuration
itself.

Try "slist". Does it work?

If not, try going into Linuxconf.


+------------------------------+
|------------Config------------|
|[X] IPX networking            |
|(o) primary                   |
|[X] interfaces frame types    |
|----------Adaptor 1-----------|
|[X] 802.2                     |
|( ) is the primary interface  |
|(o) Probe __________          |
|----------                    |
+---------------v--------------+

+---------------^--------------+
|[X] 802.3                     |
|( ) is the primary interface  |
|(o) Probe __________          |
|----------__________          |
|[X] EtherII                   |
|( ) is the primary interface  |
|(o) Probe __________          |
|----------__________          |
|[X] snap                      |
+---------------v--------------+

+---------------^--------------+
|[X] snap                      |
|( ) is the primary interface  |
|(o) Probe __________          |
|----------Adaptor 2-----------|
|[ ] 802.2                     |
|( ) is the primary interface  |
|(o) Probe __________          |
|----------__________          |
|[ ] 802.3                     |
+---------------v--------------+

Are the above values set?

Are you SURE that you are not enabling IPX on the wrong interface (if you
have a multi-homed, or multiple ethernet card, system...)

----

I was wondering if you could shed some light on why it's not working. I
looked in /etc and I didn't find a trace of the file nwserv.conf that
you made mention of. Although, to the best of my knowledge I do have
everything configured correctly in Linuxconf. I get favorable return
from ifconfig which shows IPX active.

---

/etc/nwserv.conf is part of the MARS package, which you need as well.

# rpm -qa | grep mars -
mars-nwe-0.99pl17-2mdk

Make sure it's installed or else you'll be missing some utilities. Then edit
the /etc/nwserv.conf file to set up Linux as a Novell Server. You need to do
this as bringing up MARS forces the configuration if the IPX routines in the
kernel...

Included is a copy of mine.

Get it installed, reboot (sorry but it's easier than doing things manually)
and manually start mars-nwe... /etc/rc.d/init.d/mars-nwe start

Now try slist again. See anything?

If you do, you are all set, you should be able to mount the directory -IF-
you can log in (make  sure you do this as root...)

Oh yes, one more "gotcha" which I almost forgot. BINDERY EMULATION -MUST- be
on in the server. NCPFS doesn't know about NDIS yet. ugh... As a result
you'll not see servers running anything greater than 3.12 unless they have
bindery emulation turned on and the account you are trying to use is a
BINDERY account (though you can have accounts which exists in "both
worlds".).

Another thing to do to...

Create a /root/.nwclient file which looks like this...

#
server/username password
#

Now try "nwuserlist".

#
# nwuserlist

Conn  User name            Login time
---------------------------------------------------
   1: LAN.LAN              Wed 26 Apr 2000 04:04:48 PM EDT
   2: LAN.LAN              Mon 14 Aug 2000 04:06:41 PM EDT
   3: ADMIN                Mon 14 Aug 2000 02:53:52 AM EDT
   4: ADMIN                Mon 17 Jul 2000 06:28:21 AM EDT
   5: NOT_LOGGED_IN        Wed 26 Apr 2000 04:06:34 PM EDT
   6: PS-LAN               Wed 26 Apr 2000 04:06:36 PM EDT
   7: PS-LAN               Wed 26 Apr 2000 04:06:41 PM EDT
   8: NOT_LOGGED_IN        Mon 14 Aug 2000 04:06:41 PM EDT
   9: JULIE                Sat 29 Jul 2000 05:22:30 PM EDT
  10: HP1200C              Fri 28 Jul 2000 08:09:55 PM EDT
  11: AS_BACKUP_SERVER.LAN Wed 17 May 2000 05:07:48 PM EDT

---

Good luck.

If you get it working you can have some real fun with Linux...

I.E. Round Robin mounts...

Mount your nwserver under a samba share which the Novell server can itself
mount...

Mount your nwserver under FTP or HTTP and make files available via NFS in
Linux, etc.

Use the Linux box as a gateway to Novell, circumventing the user
limitations... all Linux users appear to be only one user to Novell...

Use Samba to share your Novell Print Queues for Winblows machines which do
not have the Netware client installed, or turn all of your non-Postscript
printers into "ghostscript" printers via Linux... etc.

I've gotten some pretty weird arrangements to work this way.

BTW: "man nwauth"

-JMS
[EMAIL PROTECTED]

nwserv.conf

Reply via email to