How to configure the Netware server in Linux

Source: Internet
Author: User

Netware is a Network File System of Novell. It used a lot of it before. It seems that it is not used much now. It is said that it can also support the TCP/IP protocol, however, earlier versions only support the IPX protocol, which has recently been forgotten.

In Linux, Netware server based on IPX protocol can be supported. It needs to be simulated using something called mars_nwe. However, this thing is very old and has not been updated since. From begin (now 3.13), the data structure has also been adjusted, so I am not sure if my modifications are OK, but at least the connection is okay, this part still needs to be tested.

Next I will briefly introduce how to configure (based on Asianux Server 3 ):

1. The core needs to be re-compiled to support ipx and ncpfs. Note that "Full internal ipx network" (that is, CONFIG_IPX_INTERN) in IPX must not be selected, otherwise, other machines won't be connected. I just don't know it at the beginning, and the results have been tossing for a long time.

2. ipxutils: a tool that supports ipx configuration. Asianux is included. Check whether the tool is installed.

3. ncpfs: ncpfs-Supported tools. Because the netware server uses ncpfs, you need to install this package.

4. mars_nwe. This is the package for simulating the netware Service. The configuration file is in the/etc/nwserv directory, and you can make slight modifications to nwserv. conf. The main changes are as follows:

(1) The CDROM path of Row 3 is still in the old format. The/mnt/cdrom directory does not exist in Asianux Server 3. You can change it to another directory, or you just need to create a/mnt/cdrom directory.

(2) Row 3: The name of the server. This is the name of your netware server. You can start with a number in the file, the number indicates what this line means. For example, the server name is 2, so this line is "2 servername". The number 2 is equivalent to a keyword similar to "ServerName" in some other configuration files.

(3) define the IPX device and frame in line 3. The corresponding number is 4, and the second column indicates the network. If there is no other netware service in your network, you can write it as you like. If there is, you can avoid conflict with it. The third column is the device, and you can write eth0. The fourth column is the frame. You can write 802.3 or ethernet_ii, the last column is to select whether Internal router processes RIP/SAP. I am not very clear about whether it is useful. Generally, you can write 1, and a number greater than 6 indicates processing.

(4) you can set a logon user in row 592. By default, there is only one guest. You can add users in linux to the system. The statement is as follows:

Logon username Linux username and password

The logon user name can be different from the Linux User name. The password is the password used to log on to Netware. Currently, only 0x1 is identified, indicating that the user cannot change the password. However, by default, the Linux User corresponding to this guest user is nobody, which seems to be okay, and the nobody user does not have any permissions, but because it does not have the HOME directory, so its HOME is changed to the root directory, so that the root directory of the entire Linux system is displayed on the Netware Client, so all the files can be viewed, when it feels insecure, it is best to remove this guest user.

Nothing else. You can use the default one.

Next, let's talk about my testing process. Because there is no diskless terminal on my side, I use two Linux machines for testing, one for the server and the other for the client:

Server Configuration:

1. Install the core of ipx and ncpfs. Install the ncpfs and mars_nwe packages and confirm that ipxutils has been installed;

2. Load the ipx and ncpfs modules;

3, modify the/etc/sysconfig/network-scripts/ifcfg-eth0 file, only keep the DEVICE = eth0 and ONBOOT = yes two lines, this is to make eth0 only support the IPX protocol, but not the TCP/IP protocol;

4. Restart the/etc/rc. d/init. d/network service and use ifconfig to view eth0;

5. Modify the/etc/nwserv. conf file;

6. Start the/etc/rc. d/init. d/nwserv service;

7. Run the ifconfig command to confirm that the IPX protocol is supported (you can see the line IPX/Ethernet 802.3). If you cannot see the line IPX, disable the nwserv service first, then run the command ipx_interface add eth0 802.3 and run the ifconfig command to check whether IPX is enabled and then enable the nwserv service;

8. Run the command slist to view the service name that you set in the/etc/nwserv. conf file;

OK. Now, the server is configured. If you are not at ease, you can mount yourself on the server first:

Ncpmount-S servername-U username-P password

Here, servername, username, and passwork must be replaced with your own. You can leave the-P Parameter Unspecified. In this case, you are required to enter the password and the user name. The user with guest is set by default, no Password. You can try it first. User settings are also in the/etc/nwserv. conf file.

It is the directory to be mounted. Note that if you set the CDROM path to/mnt/cdrom, do not mount it to the/mnt directory, because netware will share/mnt/cdrom, If you mount it to the/mnt directory, the ncpmount command will die because of a loop.

Client settings:

The settings in the first four steps are the same as those on the server;

5. Run the command ipx_interface add-p eth0 802.3 to add IPX support for eth0 and set the IPX address automatically. Note that a-p parameter must be added here, which indicates that the Primary mode is used, in the/proc/net/ipx/interface file, you can see that Primary writes Yes. Otherwise, the server is invisible on the client. I started to suspect that the switch does not support the IPX protocol for a long time because of this problem. Later, I changed the direct connection. Later, I accidentally saw this parameter and it was okay!

6. Run the ifconfig command to check whether eth0 has a line similar to IPX/Ethernet 802.3;

7. Run the command "slist" to view available servers. The following lines are displayed:

Known NetWare File Servers Network Node Address

---------------------------

MARS 7F000001 000000000001

8. If you see the server above, it means that the client can be connected to the server, and we can use the command (such as mount to the/opt directory ):

Ncpmount-s mars/opt-U guest

To connect to the server MARS. After running this command, you will be asked to enter the password. Press enter and you will be able to enter all of them at will. Then you can view the/opt directory to see many directories, these directories can be stored in/etc/nwserv. in the conf file, the HOME directory is the root directory of the server by default.

There are some ipx-related files in the/proc/net/ipx/directory. The interface file contains the configuration information of the IPX interface in the system; the route file contains the route list in the IPX route table. The socket file contains the list of IPX sockets in use.

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.