Applies to: Version #
address-suppressed

General

Configuration

Volumes

Users / Groups

Master / Slave

Installation

Upgrade and Repair

Backup / Restore

Files Manager / Hotlinks

Alerts

Printing

Console / X Server

FTP / Mail / Time Services

WebServer

Browsers

Hardware

File Sharing

News / LDAP Services

Advanced Configuration

DNS / DHCP Services

Routing / Fire Wall / Proxy Cache

Non-NetMAX Application Hints

SSL / SSH

NetMAX VPN Server Suite (Virtual Private Networking)

Security Updates

Licensing

New / Updated / Top 10 FAQs

Certified NetMAX Addon Packages

NetMAX OEM Toshiba Products

NetMAX Instructional Materials

Answers in this category:
restore backup floppy
DSL/Modems and NetMAX
Enabling Wireless Access Point in L2.4Pv5.02

Answers in this category:
I forgot my password.
My NetMAX will not boot, even though it has booted correctly many times before.
The NetMAX is up and running. Now what do I do?
Is there any reason I should reboot the NetMAX once it is up and running correctly?
The NetMAX does not seem to respond.
The NetMAX does not show up in my Network Neighborhood or my AppleTalk zone.
The "lnc 1" (PCNet/PCI NE2100 compatible) PCI Ethernet device seems to have a problem sending "large packets" (more than 1000 bytes).
I am unable to use the FreeBSD user utilities vipw, adduser, and rmuser.
How do I add a FreeBSD port to the NetMAX system?
Users are Unable to Change Passwords
How do I make a new boot floppy?
Why do NetMAX exports to AppleShare disappear during COMMIT?
Why aren't my administrative web pages coming up?
I can't get backspace to work during an X-Session. What's wrong?
How do I change the volume for my modem?
Does NetMAX Fire Wall and Professional support Port Forwarding?
Does NetMAX Fire Wall support DMZ?
Does NetMAX Fire Wall detect and thwart Denial of Service (DoS) attacks such as Ping of Death, SYN Flood, LAND Attack, and IP Spoofing?
Does NetMAX Fire Wall perform Stateful Packet Inspection?
I have multiple archive devices, can I use NTFS's ability to stream to multiple files to increase the speed of my backups?
Does NetMAX WebServer and Professional support virtual hosting?
When I click on help in NetMAX, why does it mention options that my NetMAX product doesn't have?
Why doesn't my web browser continue past "Currently Processing Request" when installing new packages?
Can I administer my NetMAX remotely from an AOL account?
Why can't I login as root?
Does the NetMAX support PPPoE?
Do NetMAX's WebServer products support PHP & MySQL?
Can NetMAX FireWall and Web Server run on the same machine?
How do I access your anonymous FTP site?
Why do I see "***truncation***" in my log files?
What version of Red Hat/Linux/FreeBSD "comes with" NetMAX?
How do I get rid of an alert from 2069?
Does NetMAX Fire Wall support VPN tunneling?
When I try to access the NetMAX web interface, I get an internal server error : "Unable to write (store) SDB file /var/conf/userprefs/…."

Applies to: NetMAX Free BSD Bld475
            NetMAX Linux 2.0.37 - 4.0x

Applies to: All versions of NetMAX

Applies to: NetMAX Free BSD Bld475
            NetMAX Linux 2.0.37 - 4.0x

Applies to: All versions of NetMAX

Applies to: NetMAX Free BSD Bld475
            NetMAX Linux 2.0.37 - 4.0x

Applies to: NetMAX Free BSD Bld475
            NetMAX Linux 2.0.37

To make this a permanent change, add "/sbin/ifconfig lnc1 mtu 1000" to the boot script/etc/re.local after the comment line in the file "# put your local stuff here".

Note: lnc1 (el-en-cee-one)
address-suppressed

Applies to: NetMAX Free BSD only

Applies to: NetMAX Free BSD

Because NetMAX runs on a fully-functional open-source operating system, advanced users may feel competent to compile and install ports, packages and source manually - at their own risk, of course.
address-suppressed

Applies to: NetMAX Free BSD Bld475
            NetMAX Linux 2.0.37 - 3.x

Some package installations execute programs which set up users and/or groups. Technically, they are executing the 'pw' program for updating the user/group databases. In a NetMAX installation, the files /etc/pwd.db and /etc/spwd.db are symbolic links to var/conf/etc/pwd.db and /var/conf/etc/spwd.db. Executing the 'pw' program removes these symbolic links, thus circumventing the NetMAX committers' ability to update users and groups.

The known packages which execute 'pw' are gnats-3.104b, ifmail-2.14 and ircd-hybrid-5.3

If you must install one of these packages, first determine what the package has added (gnats adds a 'gnats' user, ircd adds an 'ircd' group, for example). You should then telnet to the NetMAX and log in as the 'root' user. From the shell prompt, enter the following commands

     ln -sf /var/conf/etc/pwd.db /etc/pwd.db
     ln -sf /var/conf/etc/spwd.db /etc/spwd.db

Applies to: NetMAX Free BSD Bld475
            NetMAX Linux 2.0.37 - 3.x

Windows: Insert a new blank 1.44MB 3.5" floppy disk in Floppy Drive A:. Open up a command prompt and change directory to the 'Floppies' folder on the NetMAX CD-ROM disk. There you will find a batch file called 'makeboot.bat'. Run this batch file by typing "makeboot" to create a NetMAX boot floppy in drive A.

Macintosh: Currently, Cybernet does not support the creation of boot floppies using Macintosh computers. However, using the above procedure with Connectix's Virtual PC does work.

Unix: Insert a new blank 1.44MB 3.5" floppy disk in the floppy drive. Use 'dd' to copy the boot image 'boot.flp' from the 'Floppies' folder on the NetMAX CD-ROM to your floppy drive. For example, under FreeBSD the command would be:

fdformat /dev/rfd0

dd if=/CDROM/Floppies/boot.flp of=/dev/rfd0
address-suppressed

Applies to: NetMAX Free BSD Bld475
            NetMAX Linux 2.0.37

                  All NetMAX versions 

address-suppressed

  #!/bin/sh
  # $XConsortium: xinitrc.cpp,v 1.4 91/08/22 11:41:34 rws Exp $

  userresources=$HOME/.Xresources
  usermodmap=$HOME/.Xmodmap
  sysresources=/usr/X11R6/lib/X11/xinit/.Xresources
 sysmodmap=/usr/X11R6/lib/X11/xinit/.Xmodmap

  # merge in defaults and keymaps

  if [ -f $sysresources ]; then
    xrdb -merge $sysresources
  fi

  if [ -f $sysmodmap ]; then
    xmodmap $sysmodmap
  fi

  if [ -f $userresources ]; then
    xrdb -merge $userresources
  fi

  if [ -f $usermodmap ]; then
    xmodmap $usermodmap
  fi

  # start some nice programs
  #Fix backspace

  xmodmap -e "keysym Delete = 0xFF08"

  geo=`/usr/X11R6/bin/xdpyinfo -display :0.0 | grep dimensions: | awk '{print $2}'`

  geo=`echo $geo | awk '{split($1, a, /x/); a[1]=a[1] - 8; a[2]=a[2] - 98; printf("%dx%d", a[1], a[2])}'`

  netscape -geometry $geo+0+25 &
  startkde

NOTE: You can not test port forwarding from your internal network. It only works from an external network.
address-suppressed

L22Pv2.x

With the proper network appliances, it is possible to have a DMZ, as long as your NetMAX is not the router for your NAT'd network and the connection to the DMZ.

This limitation is caused by the inability to specify between which NICs to apply IP Masquerading (NAT) to.

L22Pv3.x

The current version of the NetMAX FireWall products allow you to enable IP Masquerading between specific NICs, which should allow you to use your NetMAX as the router for your NAT'd network and the connection to the DMZ.

To do this, create a custom firewall rule on the external NIC. The custom rule should have a Category of Forward, an Action of masquerade, and you'll want to specify your Internal NIC's IP address for the source address. Leave every other field at its default setting. This will create an IP NAT between the external NIC and internal NIC involved.
address-suppressed

NetMAX 2.2 - 3.x

NetMAX 4.x

The current version (L2.2Pv3.0 under its new name "Internet Server Suite") supports virtual hosting more than one domain name on a single IP address.
address-suppressed

Only NetMAX Professional comes with LDAP and news service.

NetMAX Fire Wall only comes with one administrative user, and does not have mail or ftp services.
address-suppressed

AOL's proxy server insists on cacheing pages, even when it shouldn't which results in you being served the login page instead of being served the dynamically generated web page at the same URL.

In general, you should set your web browser to:

1. Access the internet directly (not through a proxy server).
2. Disable cacheing (retrieve document from remote site each time as opposed to once per session).
3. Enable cookies.
   
   address-suppressed

If you are unable to login at the console as root, you may need to enable login access by going to Home|Users|Login Access, checking the box that says "Root console and 'su' access enabled", entering a root password, confirming the password, and commiting these changes.
address-suppressed

www.roaringpenguin.com (PPPoE client script).

This is completely third party software and is in no way supported through technical support. PPPoE support in the interface may be added in later releases.
address-suppressed

NetMAX is not distributed with MySQL because of licensing issues. For that reason, PHP is not compiled with MySQL support (in version 3.2 and earlier). As of version 4.0, PHP is compiled with MySQL support, although you will still need to enable MySQL. If you are running NetMAX 3.x or older, you can still use PHP to access a MySQL database with your NetMAX product. However, you will want to visit php.net and mysql.com for information on installing PHP with MySQL support.

Note: Until, L2.2Pv2.2 of NetMAX, although PHP 3.0 was installed, no mime type was created. You will need to create it from Home|Services|WWW| MIME TYPES tab.

To install MySQL on L2.2Pv4.0x, please see: How do I get started using MySQL?

If you are using an upgraded version and need to create the MIME types, they will look like this:

1. Extension: php
   MIME Type: application/x-httpd-php
   Select Local Execuation Method: None
   
2. Extension: php3
   MIME Type: application/x-httpd-php
   Select Local Execuation Method: None
   
3. Extension: php4
   MIME Type: application/x-httpd-php
   Select Local Execuation Method: None
   
4. Extension: phps
   MIME Type: application/x-httpd-php-source
   Select Local Execuation Method: None
   
5. Extension: phtml
   MIME Type: application/x-httpd-php
   Select Local Execuation Method: None

Truncation simply marks off a day or other time period.

Truncation lines with nothing between them signify that there 
was nothing to log during the period between truncations.

NetMAX version 4.0x for Linux is based on the Linux 2.4 kernel.

NetMAX Professional (FreeBSD version) is based on the FreeBSD 3.3 kernel.

If you get an alert from 2069 that won't go away you will need to remove the alerts log.

To do this you must login to the command line interface as root user and type:

rm -f /var/log/alerts
address-suppressed

If you are not doing NAT, NetMAX is capable of routing VPN traffic (including PPTP), as long as you are not denying it with the firewall.

There is a VPN patch available for ipmasq (the IP NAT that NetMAX uses) that should allow some VPN clients to be behind the NAT.

You may read up on it at:

http://www.impsec.org/linux/masquerade/ip_masq_vpn.html.

Please note that we can't support your installation of this patch.

For more information about Microsoft VPN and NAT, please see their knowledge base article at:

http://www.microsoft.com/windows2000/techinfo/reskit/samplechapters/inbe/inbe_vpn_ymsi.asp.

address-suppressed

Answers in this category:
"Insert disk and press any key" error message appeared on my NetMAX console when I installed NetMAX on my SCSI disk.
I see the "Welcome to the NetMAX Installer" screen again.
I have gotten past the template page, but nothing happens.
"Missing operating system" error message appears.
"Unable to connect to server browser" error message.
I cannot find the city for my time zone on the clock tab.
Are the user name and password case sensitive?
How do I know which templates to select during setup?
How long does it take for the NetMAX to perform its first commit?
If I see red progress bars after the initial commit, what should I do?
I got an alert "AppleTalk services failed to start". What shall I do?
Can I use Unix utilities to update my user password database?
Does NetMAX support YP (Yellow Pages) and NIS/NIS+ (Network Information Services)?
Can I create more swap space on my NetMAX?
After configuring a second Ethernet interface, one of my Ethernet interfaces seems to stop working.
My SMC EtherPower (DEC 21041A) Ethernet card doesn't work!
I'm having problems installing LILO from SCSI, help!
Why can't my ISA card with a non standard address be detected?
Why is LILO incorrectly detecting IDE drives in the BIOS table?
My Adaptec 2940UW controller isn't working right. What's wrong?
Why is my IDE hard drive experiencing timeouts?
How do I set up my Diamond Video card for XWindows?
Booting NetMAX gives you "LI" and hangs.
How do I get my PCI modem to work with NetMAX?
Problems with RH6.1 on Supermicro P6 motherboards
When using Dialpad.com through my NetMAX Fire Wall, I can't hear the remote end of the connection.
I can't get the "external" NIC on my NetMAX machine to connect to my ISP and the Internet.
Why is my FreeBSD NetMAX machine detecting more devices than I have?
How do I change the IP address of my NetMAX machine?
Do changes made from the command line automatically appear in NetMAX?
How do I enable telnet on my NetMAX machine?
How do I change the hostname of my machine?
How do I change the IP address(es) on my NetMAX machine?
DSL/Modem and NetMAX

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux   2.0.37

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux   2.0.37 - 4.0x

Applies to: NetMAX Free BSD Bld475
            NetMAX Linux 2.0.37 - 4.0x

Applies to: NetMAX Free BSD Bld475
            NetMAX Linux 2.0.37

  1.  Select Install on Selected Hard Disk from the NetMAX Remote Installer 
  2.  Make sure to select the Enable Large SCSI Translation option. 

address-suppressed

Applies to: NetMAX Free BSD Bld475
            NetMAX Linux 2.0.37

    You did not append the 5150 Port to the IP address. 
    The NetMAX is not turned on. 
    The NetMAX is not plugged into the network. 
    You have a problem with the Ethernet connection. 
    The NetMAX may not have finished booting 

Applies to: NetMAX Free BSD Bld475
            NetMAX Linux 2.0.37 - 4.0x

Applies to: NetMAX Free BSD Bld475
            NetMAX Linux 2.0.37 - 4.0x

Applies to: NetMAX Free BSD Bld475
            NetMAX Linux 2.0.37 - 4.0x

Applies to: NetMAX Free BSD Bld475
            NetMAX Linux 2.0.37 - 4.0x

Applies to: NetMAX Free BSD Bld475
            NetMAX Linux 2.0.37 - 4.0x

Applies to: NetMAX Free BSD Bld475
            NetMAX Linux 2.0.37 - 4.0x

1. For NetMAX 2.x. From the Unix command line, type: "ifconfig -au". On the first line of output there should be a "flags" field, look for "MULTICAST" as one of the flags.
2. For NetMAX 3.x - 4.0x. From the command line, type: "ifconfig -a". Find the proper NIC (usually eth0 or eth1), and look at the fourth line down. These are the flags for that interface. See if "MULTICAST" is one of them.

Applies to: NetMAX Free BSD Bld475
            NetMAX Linux 2.0.37 - 4.0x

Applies to: NetMAX Free BSD Bld475
            NetMAX Linux 2.0.37 - 4.0x

Applies to: NetMAX Free BSD Bld475 
            NetMAX L2.2Pv3.x - 4.0x

Yes. To create more swap space on your NetMAX, perform these commands as "root".

1. Make sure you have enough space on /var (your system disk): df -k/var/swap

2. dd if=/dev/zero of=/var/swap/swap0 bs=1m count=5 The number "5" is how many megabytes of swap to add.

3. echo "/dev/vn0 /var/swap/swap0 swap" >> /etc/vntab If you do this more than once, use "vn1" the next time, "vn2" the third time, etc.

4. Add this line to the end to the /etc/rc.local file: /bin/test -r /etc/vntab && /usr/sbin/vnconfig -ae

It will be used automatically when the NetMAX boots. To enable it immediately, do "vnconfig -ae".

*** For Linux versions L2.2Pv3.x - L2.4P4.0x****

To create more swap space run these commands as root user.

1. touch /var/swapme

2. dd if=/dev/zero bs=1024k count=(RAM size) of=/var/swapme

Where (RAM size) is the amount of RAM currently installed.
For example if your system has 128Mb of RAM then: dd if=/dev/zero bs=1024k count=128 of=/var/swapme

3. mkswap /var/swapme

4. swapon /var/swapme

5. Add this line to the end of /etc/rc.d/rc.local: swapon /var/swapme This will enable the new swap file each time your NetMAX reboots.
address-suppressed

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x
      

    Change the IP assignment of one of the Ethernet interfaces so that it 

    Here's an example:
    BAD:
      Ethernet interface    IP address       Netmask
      xl0                   192.168.0.1      255.255.255.0
      xl1                   192.168.0.2      255.255.255.0
    Interface xl0 is on the network 192.168.0/255.255.255.0, and so is xl1.

    CORRECT:
      Ethernet interface    IP address       Netmask
      xl0                   192.168.0.1      255.255.255.0
      xl1                   192.168.1.1      255.255.255.0
    Interface xl0 is on the 192.168.0/255.255.255.0 network, and xl1 is on the 

                  NetMAX BLD475 

For current users, the fix should be to put the following line into /etc/rc.conf:

  ifconfig_de0="media 10baseT/UTP"

  network_interfaces="de0 generic lo0"

Or request an update to the 3.3 FreeBSD kernel.
address-suppressed

Now, try reinstalling LILO (or NetMAX/Linux) without the IDE disk. Works just fine!

Once you have LILO installed correctly on the SCSI disk, you can reattach the IDE disk and LILO will continue to work OK.

If you have a SCSI and an IDE drive, and tell the BIOS to boot SCSI first, LILO will have a problem when installing NetMAX/Linux. It won't install correctly. It will try to install on the SCSI disk (i.e. it leaves the IDE disk alone, as it should), but the install fails. You have to deattach the IDE disk in order to get LILO to install on the SCSI disk.
address-suppressed

                  NetMAX Linux RH52P v2.0 

   LILO: linux ETHER1=smc-ultra,0x300,10

See the advanced configuration information on your NetMAX installation CD-ROM.
address-suppressed

                  NetMAX Linux RH52P v2.0 

Users who do not have LILO already installed AND have more than one hard drive on their system should read the following information.

The LILO installer (/sbin/lilo), as of version 21, does not correctly determine the number of IDE drives installed in your system's BIOS: it will use the number of IDE drives that the Linux system detects in order to determine the BIOS device number to boot off of. This BIOS device number gets written to a boot block on your hard drive.

So, if you are installing LILO (the NetMAX installer does), and you have more than one drive in your system, you may encounter difficulties if you are installing LILO onto drives other than the first IDE drive.
For example, if you have two drives, one IDE and one SCSI, and you want to install LILO and boot off of the SCSI drive, then you will have to have turned off or unplugged the IDE drive when the system was last booted, so the LILO installer will not count the IDE drive as a BIOS drive. Then, in order to boot off of the SCSI drive, you will have to disable the IDE drive (not the controller!) in the system's BIOS, and enable the SCSI controller's BIOS.
As another example, if you have two IDE hard drives, and you want to install LILO and boot off of the second IDE hard drive, then you will have to have turned off or unplugged the first IDE drive when the system was last booted, so the LILO installer will not count the first IDE drive as a BIOS drive. Then, in order to boot off the second IDE drive, you will have to disable the first IDE drive (not the controller!) in the system's BIOS.

There are alternatives to these methods, if you wish to read the LILO version 21 documentation, located at:

  ftp://tsx-11.mit.edu/pub/linux/packages/lilo/lilo-21.tar.gz
    in the lilo/README file

                  NetMAX FBSD32P v2.0
                  NetMAX FBSD33P v2.0
                  NetMAX BLD475

The EZXconfig setup does not work with the aforementioned card.

In order to setup XWindows using this video card, a little extra effort is required. You must run XF86setup instead of EZXconfig. Configure your mouse so you can manuver through the interface easier. Click on the 'Diamond Stealth 64 Video VRAM (TI RAMDAC)' entry, and do a detailed setup of the card. The chipset you should choose is 'S3_Generic'. The clockchip and the RAMDAC are both probably 'TI3026', but look at the TI chip on your card to make sure.
address-suppressed

1) If SCSI, toggle the value of "Large Hard Drive (> 1 Gb) Translation".

2) If IDE, try setting the "Mode", using the BIOS setup, of the boot drive to "LBA", and also try "CHS".
address-suppressed

1. Install setserial.

You can install setserial from Home|Services|Package Management

Click on ADD, select the category Applications/System, check the box next to setserial, and click on CONTINUE.

2. Configure Modem - (configure per manufacturers instructions see below)

3. Setup Modem in NetMAX Interface

From Home|Network|Interfaces click on the pencil next to ttySx (where x is the serial port that is detected with the modem)

Click on the SELECT button next to Current Configuration, check the box next to the "Generic 115200", then click on the pencil next to this modem and go to the Intialization Tab.

Click on the pencil next to the initialization sequence and edit it to read ATZ

Click on STORE, then SELECT, then STORE, then COMMIT, and commit your changes.

To our knowledge, this is the only PCI modem that Linux supports.
address-suppressed

1. Ensure that you are running the latest version of NetMAX, or have installed the "Port Forwarding" update available at ftp://ftp.netmax.com
2. In your Fire Wall configuration, you'll need to enable UDP: 51200, 51201, and TCP: 51210
3. Setup Port Forwarding (Traffic Rerouting) for these ports in Home|Network|Traffic Rerouting.

1. Go to Network->Interfaces->Edit Interface
2. Change the NetMAX to 128.0.0.0 and click Store
3. Click the Edit button to return to the Edit Interface screen
4. Add the new IP addresses to the list of IPs and click Store
5. Go to Network-Routing
6. Change the IP address of your default router to its new value and click Store
7. If your DNS servers are also changing, then navigate to Network->DNS
8. Change the DNS IP addresses to their new values and click Store
9. Go to Network->Domains
10. Change the IP ranges on your domains to the new IP range and click Store
11. Go to Network->Naming
12. Change the IP addresses associated with your hostnames to their new IP addresses and click Store
13. Go back to Network->Interfaces->Edit Interface
14. Remove your old IP addresses
15. Change your netmask back to its correct value
16. Store and Commit the changes
17. Physically plug your NetMAX into the new device (cable modem, router, etc...) if necessary
18. After waiting an appropriate amount of time (a few minutes), log into the NetMAX interface and test that everything is working properly
19. If you are still having problems, give us a call and we'd be happy to help out.

No.  

In fact, such changes may later be overwritten by NetMAX.

Since a NetMAX administrator may wish to configure specific
options from the command line, we have provided a tool to 
protect the command line changes from being overwritten by NetMAX.

In the /etc directory, there is a file called commit.conf.
Use this file to tell NetMAX not to modify specific files and/or directories.

The syntax of this file is explained withing /etc/commit.conf.

1. Edit the file: /etc/xinetd.d/telnet
2. Change "disable = yes" to "disable = no"
3. Restart xinet.d. This is most easily done by going to Services->FTP, and without changing anything, choose Store, then choose Commit.

1. Access the NetMAX interface.
2. Select Home | Network | Naming
3. Fill in the appropriate information (host name, domain name, IP address, etc.).
4. Ensure that the hostname you want is at the top of the list of hostnames by moving it up or down if necessary.
   address-suppressed

1. Go to Network->Interfaces->Edit Interface
2. Change the NetMAX to 128.0.0.0 and click Store
3. Click the Edit button to return to the Edit Interface screen
4. Add the new IP addresses to the list of IPs and click Store
5. Go to Network-Routing
6. Change the IP address of your default router to its new value and click Store
7. If your DNS servers are also changing, then navigate to Network->DNS
8. Change the DNS IP addresses to their new values and click Store
9. Go to Network->Domains
10. Change the IP ranges on your domains to the new IP range and click Store
11. Go to Network->Naming
12. Change the IP addresses associated with your hostnames to their new IP addresses and click Store
13. Go back to Network->Interfaces->Edit Interface
14. Remove your old IP addresses
15. Change your netmask back to its correct value
16. Store and Commit the changes
17. Physically plug your NetMAX into the new device (cable modem, router, etc...) if necessary
18. After waiting an appropriate amount of time (a few minutes), log into the NetMAX interface and test that everything is working properly
19. If you are still having problems, give us a call and we'd be happy to help out.

Answers in this category:
How do I avoid losing data in volumes?
Define terms used below in "Volume Messages" (also see the Glossary in the QuickStart Guide).
I got the error message, "During reboot, a NetMAX formatted disk 'disk_name' (disk_label) has been detected, an attempt will be made to rebuild any volumes".
I got the error message, "During reboot, a non-NetMAX formatted disk 'disk_name' has been detected".
I got the error message, "The transferred disk 'disk_name' backup configuration could not be extracted. Volumes for this disk cannot be rebuilt".
I got the error message, "Configuration files from the backup configuration for disk 'disk-name' could not be extracted. Volumes for this disk cannot be rebuilt".
I got the error message, "During reboot, the volume 'volume_name' was detected, an attempt will be made to rebuild and mount this volume".
I got the error message, "This volume 'volume_name' will be renamed to 'volume_name#' ".
I got the error message, "During reboot, volume 'volume_name' could not be accessed because disk(s) from the volume configuration were not present".
I got the error message, "During reboot, the volume 'volume_name' (a Mirror) could not be rebuilt because disk(s) from the volume configuration were not present. An attempt will be made to rebuild one half of the mirror".
I got the error message, "During reboot, the volume 'volume_name' (a Mirror) could not be mounted because the file system consistency check failed. An attempt will be made to rebuild one half of the mirror".
Why did my "reset security permissions" command also reset the permissions on paths other than the one I selected?
Error message, "During reboot, the volume 'volume-name' (a Mirror) could not be mounted because the file system consistency check failed. An attempt will be made to rebuild one half of the mirror".
Error message, "During reboot, the volume 'volume-name' (a Mirror) was successfully downgraded to a [Stripe | Normal] volume".
"The previously damaged volume 'volume-name' is now mounted but downgraded. The downgraded volume is functioning normally".
"The volume 'volume-name' is now mounted but downgraded. The downgraded volume is functioning normally".
"The previously damaged volume 'volume-name' is now mounted and functioning normally".
"The volume 'volume-name' is mounted".
"During reboot, the volume 'volume-name' (a Mirror) could not be successfully downgraded. This volume is damaged and cannot be currently used. Consult Troubleshooting in the NetMax QuickStart Manual."
"During reboot, file system consistency check for volume 'volume-name' failed, this volume will not be remounted, please review the log file 'logfile URL'."
What is the disk rescue procedure?
Do I need to check volume names before installing a NetMAX on a system with NetMAX formatted disks with volumes already on them?
Home path share doesn't always show up on the share list, using Windows95 or NT.
When I create a folder on a netatalk/afpd volume, I get an "Access Denied" error, but the folder is created.
What type and level of RAID support is provided?
I cannot access one of my volumes.
How can I retrieve information from the "system" volume (/var) of a hard drive that had a NetMAX FreeBSD BLD475 system installed on it but is no longer used as my NetMAX?
How do I mount a non-NetMAX hard drive as a volume?
How do I setup volumes with an Adaptec 2100S SCSI RAID card?
How do I add additional hard drives to my Internet Server Suite, FireWall Suite or Webserver?

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Rebuild a volume - This is the process of piecing together parts of the volume, from different disk locations, into readable form. Every volume is rebuilt each time the NetMAX is rebooted.

Mount a volume - The process of mounting makes the volume accessible to the user.

Transferred hard disk - A hard disk is transferred if it was attached to a NetMAX, formatted by that NetMAX, then removed from that original NetMAX and attached to another NetMAX.

Reconfigure - This is when the method for storing the data on the volume is modified from one type to another. Volume types are normal, mirror, stripe, and noncontiguous.

Downgraded - A volume is downgraded when a mirrored volume is reconfigured to a normal or a stripe. A two-disk mirror would be downgraded to a normal, while a four or more disk mirror would be downgraded to a stripe. A user can choose to downgrade a working mirror for more useable disk space, and the NetMAX may downgrade a damaged mirror if one half of the mirror cannot be mounted. Volume types (normal, mirror, stripe, and noncontiguous) are described in more detail in online help.

Imaged Disk - This refers to the disk imaging for Toshiba Magnia drives. Since the Magnia does not have a CD-ROM drive, the disk must be imaged directly by us or Toshiba in order for NetMAX to be installed.
address-suppressed

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - NetMAX 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

If you don't, then setting permissions on "MainPath" will overwrite the permissions on "SubPath" and any other paths that point to sub directories under "/MyVolume".
address-suppressed

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.03

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

             NetMAX Linux 2.0.37

        Shut down the NetMAX and the hard disk. 
        Check the hard disk cables to make sure they are securely attached. 
        Turn the hard disk on again. 
        Reboot the NetMAX. 

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37

NetMAX BLD475

Free BSD NetMAX BLD475 provides software RAID Level 0 (striping), as well as software RAID Level 1 (mirroring). The DPT RAID IV controllers are supported, which provide hardware controlled RAID 0, 1, and 5 (striping with rotating parity). In addition, the DPT RAID IV controllers support RAID 10 and RAID 50.

The DPT RAID V controllers are not supported.

Adaptec RAID controllers are not supported (i.e. the Adaptec 131 or 7880). However, they are supported as normal SCSI controllers.

NetMAX RH52Pv2.0

The Linux version of NetMAX RH52Pv2.0 supports software RAID levels 0, 1, and 5. Please see our Hardware RAID article for information on hardware RAID.

NetMAX L2.2Pv2.x (or later)

The newer versions of NetMAX still support software RAID levels 0, 1, and 5, however, you can not include the system drive (the drive the OS is installed on) in the RAID.

IMPORTANT NOTE: CONFIGURING ANY TYPE OF RAID ON A NETMAX SYSTEM REQUIRES MORE THAN ONE HARD DISK DRIVE.
address-suppressed

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
            

1. Create a directory in the /var/mnt directory called 'MyDisk' (or whatever you wish to call it), with the full path '/var/mnt/MyDisk'.
2. Mount the disk. (ex: mount -t fstype /dev/hdX /var/mnt/MyDisk)
3. In the NetMAX interface, select Home | Sharing | File Sharing | Home Paths. Then, create a new path for this hard drive. Please note that once on the general tab for Paths, you cannot select the directory for the path, so you must type it in by hand. For example, type into the Path field '/MyDisk', or for any subdirectory, it could be '/Mydisk/Subdirectory'. Choose what is needed or setup owners or file permissions from the Security page.
4. Store and commit. The disk will then be shared.
5. To make this permanent, add your disk as an entry in /etc/fstab.

These steps might not be necessary once the operating system recognizes the SCSI devices as in the Red Hat 6.x systems.

Make sure that you read the man pages for fstab (man fstab) before editing it.
address-suppressed

How do I add additional hard drives to my Internet Server Suite, FireWall Suite or Webserver?

In order to add drives to your NetMAX server your NetMAX product must have volume management.

These NetMAX products do not include volume management.

Internet Server Pro Suite
Internet Server Suite
Webserver
Firewall Pro Suite
Firewall suite

You must purchase a product with volume management in order to add additional hard drives to the above products.

The products with the volume management feature are:

FileServer
Professional Suite

For more information on these products please go to our Products page.

When you recieve your volume management capable NetMAX product add it's features to your existing NetMAX server by adding it's license number using License Management.

Once you have added the new license number you need to click Approve then Commit your changes.

When the commit completes go to | Home | Sharing | File Sharing and click on the Volumes tab.

In volumes click on the Create button.

Give the volume a name then click on the Select button to select the new hard drive.

Select the drive you would like to add and click Return.

Select what type of drive this will be from the drop down menu. For size give the amount of space you would like to use for that volume.

Now you have all of the basic information you need to create a new volume on an additional hard drive. You may add drive quotas by clicking on the Quotas tab.

Store and Commit your changes. When the commit completes you will be able to use the space on your additional hard drive.
address-suppressed

Answers in this category:
How do I see all the users in a group?
Why are some newsgroup users unable to post or retrieve new message from their group?
Can I add an external user to provide them space on our website without giving them access to any File Sharing Paths?
All I see are dots in single user mode!
Why is my grace period 'none' when I have more days left?
When a user runs an exec'd process, why does that user process not show in the user reports?
Are passwords limited to 8 characters?
I manage my users from the console, why am I unable to change a password?
How can I import users into NetMAX?
How can I use a secondary volume for my user's home directories?

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

You can include additional users indirectly by including other groups (shown on the Groups tab), but selection boxes for these users will not become checked after doing so.

If you wish to see a complete list of all groups that a user has inherited, edit the user and go to the Groups tab. The table at the bottom of the screen displays the groups that this user has inherited.
address-suppressed

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

1. From Home|Users|Defaults|Home Path, set the permissions for all users to "Other" with no read or write access. This does not have to be recursive. If this was not your default when you setup any new user, then you must go to the command line on your NetMAX and do the "chmod" yourself. Changes to the user defaults only occur when new users are added.

2. Create the new (web only) user with no login access, give them a home directory, and put them only in a new group (you might name it "External"). Remove them from the default group "Staff" (or whatever you setup as the default group).

3. For users web home pages to work (if enabled), from the command line, enter "chmod o+x" (oh plus ex) to set "Other" to Execute.

4. Thru Home|Sharing|File Sharing|Path (edit)|Security, change the external security settings on the paths security settings to be owned by "NetAdmin/Staff", and set the permissions to Owner Read/Write, Group Read/Write, and Other None.

5. Edit the file "/etc/ftpusers" and put the new (web only) user in it. This will disallow the new user access via ftp.

6. Commit the NetMAX changes.
address-suppressed

Also, once the hard limit has been reached, if you try to remotely copy and paste files (like from a Windows interface) it will fail once it has reached the hard limit, displaying a disk full popup. When the screen is refreshed, it will display that the paste succeeded, however the file is truncated.
address-suppressed

Applies to: NetMAX Free BSD Bld475
            NetMAX Linux 2.0.37 - 4.0x

1. Install a second hard drive in the NetMAX machine.
2. Boot up the machine and log into the NetMAX interface.
3. Go to Home->Sharing->File Sharing->Volumes->Create
4. Specify a Name and Description, and choose the new hard drive from the list of devices.
5. Store and Commit
6. Go to Home->Users->Users->Defaults->Home Path and change the Home Path Root Location to the new volume you created.
7. Click on the OK button.
8. You will now be able to create users with home paths on the secondary volume.

Answers in this category:
During an upgrade commit, do slaves update as well?
How do I distribute NetMAX's across a network?
"NetMAX Master was unable to commit posted by NetMAX Master"

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

      users 
      machines 
      machine groups 
      domains 
      password policies 

      user defaults 
      user groups 

    1.   Temporarily define the NetMAX master as a slave. 
    2.   One by one, define each slave as a master and perform a commit,
         thereby copying its user and machine list to all other machines. 
    3.   Redefine the NetMAX master and perform a commit. 

                  All versions of NetMAX 

"NetMAX Master was unable to commit posted by NetMAX Master"

This issue will be corrected in a future update. For now, the only option is to make sure slaves are not already committing when a commit is run on the master.
address-suppressed

Answers in this category:
My NetMAX will not boot off of the CD.
I cannot boot from the NetMAX boot floppy.
My NetMAX cannot find a compatible Ethernet card.
My NetMAX tells me I do not have enough memory (RAM).
I do not know which IP address to give the NetMAX.
What do I do when I hear the NetMAX beeping at me about once every five seconds?
The NetMAX is waiting for an IP address (it is beeping), and I have pinged it, but it does not respond.
"No keyboard attached, press F1 to continue" error message appears.
"Not a NetMAX CD-ROM" error message appears.
"Cannot find NetMAX CD-ROM" error message appears.
My NetMAX stops responding because it goes to sleep.
"Floppy version does not match CD-ROM version" error message appears.
"Cannot find FTP site" error message appears.
"No hard disk available" error message appears.
"Not enough space" error message appears.
Onto which hard drive do I install NetMAX?
The installation pauses at .03-.05% during system extraction.
My browser says "document contains no data".
"Host is not responding" browser error.
The install message tells me to remove the CD-ROM and floppy but I cannot get the CD-ROM drive open.
What do I enter for default router?
What do I enter for Netmask?
I closed my browser by accident. How do I get back to the installation?
"Cookie not found" error message appears.
"Lost connection to server" error message appears.
Is a netmask always required when user is prompted to provide an IP address from the console during install or upgrade?
The NetMAX software finds an Ethernet card, but on the console I keep seeing "xxx device timeout". What does this mean?
I'm having trouble entering my NetMAX License Number.
What multi-port serial cards are supported by NetMAX?
I am having a problem with a 16650 serial chip
What is the /netmask option?
Installation onto non-primary hard drive: Installation Fails (RH52Pv2.0)
The boot floppy that came with L22Pv2.2 causes version errors.
Can I use the Overlay Install Method to install NetMAX over an existing Red Hat system?
Problems booting LILO with large (20+GB) IDE hard drives.
How do I use a driver diskette for my unsupported devices?
How do I create a NetMAX Installation CD from the netmax.iso?
How do I register and activate my NetMAX Software?

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

NetMAX version 2.x - 3.x

NetMAX version 4.0x

            NetMAX Linux 2.0.37 - 3.x

1. Your boot floppy is damaged. Try making another floppy (see the FAQ, "How do I make a new boot floppy?" in the "All Versions" section). Make sure to use a new 1.44MB 3.5" floppy and make sure you copy from the same NetMAX version as you want to boot.

2. Some of your hardware is set up differently from the NetMAX software expectations. Reboot using the floppy again, and use the Advanced Configuration described in Appendix A of the NetMAX QuickStart Guide.

3. Your PC's BIOS (Basic Input Output System) is set so that your machine does not boot off of a floppy. Consult your computer's documentation for controlling the BIOS settings.
address-suppressed

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

NetMAX version 3.x

NetMAX version 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

If you own or have already established a block of IP addresses provided by your ISP, select one of those.

Otherwise, you can use any of the predesignated non-routable IP numbers detailed below. A non-routable address is an address that cannot access the Internet directly, but is sufficient for setting up an internal network. If you want to access the Internet, your ISP will provide you with an address to use in addition to the non-routable IP numbers. You can then use the NetMAX as an "address translator" to provide the other machines on your network with access to the Internet, provided that the NetMAX is used as your Internet access point.

Remember that you can always change your IP address at a later time.

Blocks of non-routable IP addresses to choose from:

10.0.0.1 to 10.255.255.254 with a Netmask to 255.0.0.0, resulting in more than 16 million usable addresses.
192.168.0.1 to 192.168.255.254 with a Netmask to 255.255.0.0.

DO NOT USE 10.0.0.0, 10.255.255.255, 192.168.0.0, or 192.168.255.255.
address-suppressed

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to: All versions of NetMAX

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 3.2

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 and earlier

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

For NetMAX 2.x

For NetMAX 3.x

For NetMAX 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 and older

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 3.0

address-suppressed

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 3.1

http://NetMAXIP:5150/

address-suppressed

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 3.0

For all other Ethernet cards: The default media selection (10BaseT, AUI, or ThinkNext [10Base2]) which is set up in your Ethernet cards PROM may not have been detected correctly. Use your Ethernet card's configuration software to insure that the media selection is correct.
address-suppressed

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.x - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37

The proper form for the entry is:

  192.168.0.1/255.255.255.0
    or
  192.168.0.1/24
    or
  192.168.0.1/0xffffff00

Solutions: 1) If SCSI, go to SCSI BIOS and set the boot drive to the installed drive

OR

2) Run the CD in Repair Mode, and install a boot manager onto the primary drive.
address-suppressed

If a boot floppy was included, please don't use it, as it was a packaging mistake.

If you can't boot from the CD, please put your L22Pv2.2 CD in a workstation and read the INSTALL.HTM for instructions on making a boot floppy.

The L22Pv2.1 Linux version or the L22Pv2.2 Linux version of NetMAX can be installed over an existing Red Hat 6.1 system, but you'll need to answer "Y" to the question "Would you like to install the NetMAX kernel?"

No other version of Red Hat or NetMAX can support an Overlay Installation.

This information assumes that you have NOT upgraded the version of the Linux kernel that comes with your Red Hat installation.

Before you do an overlay installation, you may want to first consider whether you actually need to do an overlay installation, because it does make it quite a bit more difficult to administer your NetMAX product if you do an overlay installation.

You may want to look over the instructions for the Overlay Installation Method in the Installation Manual. If you look at the Post Configuration section, you will notice that you will have to manually maintain the files that NetMAX is allowed to overwrite when doing an Overlay Installation.
address-suppressed

LI

You may have a BIOS that does not properly handle large IDE hard drives. The manufacturer of the drive should have instructions for resolving such situations. Usually there is a specific drive geometry (cylinders heads and sectors per track) that you can configure manually in your BIOS to solve this problem. Once the BIOS is configured properly and the NetMAX system boots you are done (you do NOT need to install any drivers or software provided by the manufacturer).

You can usually see how the Linux OS is seeing the hard drive's geometry during installation by following these commands:

1. From the console, boot from the installation CD-ROM.
2. When it starts asking for the IP type (static, DHCP, None), hit CTRL-C.
3. Enter: chroot /CDROM/NETMAX and press ENTER.
4. You should see a "#" prompt.
5. Enter: fdisk -l /dev/hda and press ENTER.

Another way is to cat /proc/ide/hda/geometry

Note: The manually configured drive geometry will usually define a small drive this is OK once the system has booted the full drive capacity will be available.
address-suppressed

Adding kernel module devices is done similar to using the conf.modules file in Linux. You will need to create a DOS formatted floppy with the kernel module on it along with a file with the name of each module to load in the order that you want it loaded.

Step 1: Acquire a kernel module driver for your device from your hardware manufacturer or reseller. The NetMAX verion L22Pv3.2 has a 2.2.18 Linux kernel. That information may help you to select the appropriate driver.

Step 2: Format a DOS dikette (1.44MB format floppy with FAT-16), and copy the kernel module files onto the diskette (the .o files). You will probably want to do this on a windows machine.

Step 3: Next, you'll need to create a text file with UNIX end of line characters that has the name of each module that you want to load on a seperate line. The name of the file should be "modules" and placed in the main directory along with the drivers. For example, your disk might contain a new tulip driver (tulip.o) and a compaq driver (cpqarray.o). You might create your modules file to contain the following two lines:

tulip.o
cpqarray.o

It may be easier to get UNIX end of line character (nl as opposed to cr,lf) by using a HEX editor (intead of a regular text editor like notepad). Or even easier would be to mount the floppy on a Linux machine and create the file in vi.

mount -t msdos /dev/fd0 /mnt
vi /mnt/modules
umount /mnt

Step 4: When booting from the CDROM or boot floppy during installation, there will be a boot prompt where you will have 30 seconds to type something in or the default kernel will be loaded. This prompt will say "Wait 30 seconds for automatic boot or press ENTER to continue immediately". At this prompt, type the following:

linux driver

Step 5: You will be prompted for the driver diskette with "Please insert the UNSUPPORTED MODULES FLOPPY into the drive and press Enter". At this time, insert the floppy that you made and press the ENTER key.

The NetMAX will load your drivers, or give you warning or error messages stating the nature of the problem loading the drivers, then request for you to remove the driver diskette.

Step 6: Return to your Installation Instructions as provided in the Manual.

Step 7: If the driver you installed was for a hard disk drive controller, you will probably want to add this module to /etc/rc.sysinit to be loaded every time on reboot, as this is not yet done automatically.

To do this, copy the kernal module device driver into the /lib/modules/2.2.18/block directory and run the depmod command:

depmod -a

Now add lines similar to the following in your /etc/rc.sysinit file under the "# Add raid devices" section. For this example, the name of our driver is cpqarray.o

if [ -f /lib/modules/2.2.18/block/cpqarray.o ]; then
        action "Starting up Compaq Controller." /sbin/modprobe cpqarray
fi

Also, note that some drivers get updated from time to time to support more devices. If the driver is already on the CD, you will not be able to use the driver diskette method to load a newer copy of it. There are work arounds for some hardware issues. Please see the NetMAX user forums for more information on these.

Note that the simplest method is often to purchase hardware that is on our compatibility lists in the first place. This can save a great deal of time and effort compared some trying to get certain unsupported hardware devices working. The method above will not work for all hardware.

1. Purchase the downloadable version of the NetMAX product you would like.
2. Download the file netmax.iso to your local hard drive. Simply click on the link to initiate this process.
3. You will now need a CD burning program, a CD burner, and a blank CD to create the installation disk. There is a list of programs compatible with the .iso format at the bottom. Note that there may be programs not listed that will work.
4. Install and run the CD burning program.
5. Choose to create a CD from an image file. This procedure will vary from one program to the next, but all programs should accomplish the same task.
6. After going through the procedure specific to your CD burning software, choose to burn the CD.
7. When you are finished, label the disk NetMAX Installation CD.
8. You may now boot your computer off the CD to initiate the installation process.

• Nero Burning ROM
• Padus Disk Juggler
• Clone CD with Virtual Clone Drive
• Gear Pro for Linux

1. Navigate to: https://www.netmax.com/order/support/support.cgi
2. Click on the link to create a new user if you have never done so before.
3. Fill out the form with your information and your product's information.
4. The license number will be that which you received when you purchased your product.
5. The activation key can be found in the NetMAX interface. Log in to the Interface, and navigate to Home|System|License Management. The eight character activation key will be located at the bottom of the "Currently Installed License Numbers" frame.
6. Keep this screen in NetMAX open for the final step of the activation process.
7. Double check your e-mail address to ensure that it is entered correctly, and click the register button.
8. The registration activation code will then be sent to the e-mail address you specified.
9. On the License Management screen of the NetMAX Interface, click the pencil in front of the product you are activating.
10. Enter the Registration Activation Code from your e-mail into the blank spot in the table.
11. If you have multiple products, log in to the support database with your new account. Use the "Create Product" button to repeat this process for all your products.
12. When all products have been registered and have their registration activation codes entered, click on the Approve button in the NetMAX Interface.
13. Click on the Commit All button, and wait for the status bars to finish. When this process is complete, your NetMAX will be ready to go.

Answers in this category:
Do I have enough available disk space to upgrade?
I want to change my hardware configuration and upgrade the software. What now?
Are entries in my commit.conf file protected during an upgrade?
Why do I get an error message when I try to upgrade?
What will happen if I install a boot manager on a headless server?
How do I upgrade a NetMAX BLD475 kernel to support a new hardware device?
What is the proper form for entering an IP address when prompted to do so during installation?
How do I upgrade 3.x versions of discontinued products, to version 4.0x?

Applies to Netmax FreeBSD Bld475
           NetMAX Linux   2.0.37 - 3.x

When doing an upgrade from CD-ROM, the size needed will be the size of the upgrade image. This size can be obtained from the CD by looking at the size of the file /var/upgrade/netmax.general.cpio.gz, if it is a general upgrade. If it is a build-specific number, the file to get the size will be /var/upgrade/netmax.build.number.cpio.gz.

If doing an FTP upgrade, the size can be obtained by looking at the web site information about upgrades, and getting the size needed to perform the upgrade. For an FTP upgrade, the size needed will be twice that of the upgrade image.
address-suppressed

Applies to NetMAX FreeBSD Bld475
           NetMAX Linux   2.0.37 - 4.0x

Applies to NetMAX FreeBSD Bld475
           NetMAX Linux   2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD BLD475

Once you have received a new kernel, it must be copied (uploaded) to the NetMAX server. The kernel may be uploaded using the files manager interface (Home|Personal|<path>|UPLOAD). "Root Access" must be enabled on the server, which can be set up via Home|Users|Root Access. Remember to COMMIT the changes.

Telnet into the NetMAX from your client machine. The user account must be a "Network Administrator" account, otherwise the user will not be able to "su" to root. If you choose to allow "Domain/Hostname Access" in root access, you will be able to telnet directly as the user "root" using the password you have enabled. Otherwise, once the network administrator has logged on via telnet, type the command "su" and press enter. This command will prompt you for a password; enter the "root" password entered in the "Root Access" page.

The first step is to make a copy of the current kernel, in case there is a problem. It is also possible to use the Repair facility to correct any problems automatically.

Type the following commands (all are followed by pressing enter) - case is important:
chflags noschg /kernel
cp -p /kernel /kernel.old

Now, replace the current kernel with the one you have recently uploaded to the NetMAX server. <path> is the location within the file system where you uploaded the file:
cp <path>/kernel /kernel
rm /var/db/kvm_kernel.db

You're done. Now the server must be rebooted:
sync
/sbin/reboot

Once the system comes up successfully, the new kernel will have any additional hardware support. If there are any problems, contact NetMAX Technical Support.
address-suppressed

The proper form for the entry is:

  192.168.0.1/255.255.255.0
    or
  192.168.0.1/24
    or
  192.168.0.1/0xffffff00

• NetMAX Internet Server Suite
• NetMAX File Server
• NetMAX Firewall Suite
• NetMAX Internet Server ProSuite
• NetMAX Web Server
• NetMAX Firewall

1. Purchase the necessary license in the NetMAX store.
2. For NetMAX Firewall and NetMAX Firewall Suite version 3.x, you will need to purchase NetMAX Firewall ProSuite version 4.0x.
3. For NetMAX File Server, NetMAX Internet Server ProSuite, and NetMAX Web Server 3.x, you will need to purchase NetMAX Professional Suite version 4.0x.
4. After you obtain the license number for the software you purchased, remove the current license number for your product. Do this in System -> License Management.
5. Next, add the new license number you purchased in License Management.
6. You should now be able to upgrade using the CD you purchased (or downloaded and burned). Simply follow the normal upgrade procedure in the manual from here on out.

Answers in this category:
Can share names contain spaces?
Why does the mail message reporting the amount of data backed up on my machine appear to report more bytes than the data would account for?
I am not getting an email notification that the Backup System is backing itself up.
Why are hardlinks ignored during backup, and an alert message not generated?
When trying to restore to my Windows machine from the NetMAX FileServer, the restore fails on some directories.
I have multiple archive devices, can I use NTFS's ability to stream to multiple files to increase the speed of my backups?
My Tape Backups are failing, what can I try?
Why aren't my subdirectories being backed up by FileServer? Why are my subdirectories symlinks?
What constitutes a backup device, or why are there no backup devices when I try to view them?
Why am I getting the error "no tape in drive" when doing backups, even though there is a tape in the drive?
How would NetMAX recommend making a backup of our configuration?
What is the recommended way to perform an emergency backup?
Does NetMAX support backups to network volumes or a secondary hard drive?
Overview of backing up and recovering your NetMAX server.
I manually saved my configuration by backing up /var/conf. How do I properly restore it?
Restore a configuration floppy

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

You can use these commands to rewind, tar to, rewind, and tar from the tape (logged in as root):

/usr/netmax/bin/mt -f /dev/st0 rewind
tar -cvf /dev/st0 /etc/services
/usr/netmax/bin/mt -f /dev/st0 rewind
tar -tvf /dev/st0

If your tape drive is functioning from the command line, then NetMAX should have no problem accessing it as well.

The only difference between these commands and what NetMAX does, is that NetMAX will also run some commands to position the tape.

If you are using a brand new tape, with nothing on it, then you will need to check the box that says "Start at beginning of tape".

If you don't do that, and you have a blank tape, then NetMAX will fail at positioning the tape (going to the end of data on the tape and then backing up two).

If your tape drive does not support the repositioning commands:

/usr/netmax/bin/mt -f /dev/st0 rewind
/usr/netmax/bin/mt -f /dev/st0 eod
/usr/netmax/bin/mt -f /dev/st0 bsf 2

Then you will always want the check box checked.
address-suppressed

Therefore, the actual directory or file must be chosen in order to back it up.

For example,:

By default, the NetMAX file server creates a symbolic link "/var/mnt/Users" that points to "/var/mnt/System/Users."
This is the location where users' files are stored.

In order to backup the users' directories, you must choose to backup /var/mnt/System/Users.
address-suppressed

If you have one of these devices and it is not being detected, make sure that you have properly configured your SCSI chain:

    Ensure that there are no duplicate device Ids.
    Ensure that the chain is properly terminated.

Also, make sure that the power to your backup unit is plugged in and that the tape unit is on.
address-suppressed

This allows backup of configuration to a floppy disk.

Should the server's drive fail, it will be possible to reinstall the NetMAX software on a fresh drive and use the Repair Facility to restore configuration from the floppy.

The Repair Facility can be accessed (after reinstall) by booting from the installation CD-ROM.

Use the "Remote Installation Method"- repair cannot accessed from the "Console Installation Method."
address-suppressed

1. Do not select your own paths to store operational data. By default NetMAX stores it all under /var/mnt/System (the system volume), which is what you want.
2. Make a Configuration Backup Floppy from Home|Services|Configuration.
3. Backup the System volume.
4. You probably also want to backup any other volumes that you may have mounted.

In the event that you need to restore, you should:

1. Correct the problem that caused the failure (i.e, replace the failed hard disk drive)
2. Reinstall NetMAX.
3. Recreate any additional volumes that you may have mounted before the system failure.
4. Restore your configuration from floppy. (There are instructions on how to do this in your user manual.)
5. Restore the System volume from backup.
6. You probably also want to restore the data on any additional volumes from backup.
7. Reboot.

Overview of Backing up and Restoring Data using NetMAX

Date: 4/17/01
Revised: 7/14/03

Requirements:

• A SCSI tape drive and appropriate tape media.
• A 3 1/2" high-density diskette.
• NetMAX system CDROM.

Backing Up The NetMAX Server

In order to successfully recover your NetMAX server from a system failure you must have a good backup. Here is a procedure for properly backing up your NetMAX server. Note that there are many valid backup procedures. The following procedure is by no means the only way to back up a NetMAX, however it is the method we recommend.

Backup Administration

Remember that recovering from a catastrophic system failure begins with regular administration of your backup system and process. This includes:

1. Scheduling backups - Schedule backups on a regular basis. Typically this should be performed on a daily basis during a time when the system is least active.
2. Rotation of tapes - Develop a tape rotation scheme that employs multiple tapes. A good choice is a separate tape for each day of the week for a minimum of two weeks. Have 12 additional tapes to rotate in at the end of each month and rotate the last tape of the month off-site for safe keeping. We recommend storing full backups on a separate tape from the differential backups, but you may use the same tape.
3. Monitoring backups and alerts - Monitor backup report logs to ensure that backups are being performed properly.
4. Testing the backups periodically - Setup a regular routine of performing a test restore to ensure that a backups are actually working properly.
5. Care of tape devices - Clean tapes drives on a regular basis according to the manufacturers recommendations and replace worn tapes.
6. Keep your NetMAX CDROM, configuration backup floppy, and backup tapes in a safe and secure place. Another good idea for backups is to rotate a set or two of backup tapes and diskettes off site. In most cases this place is another building with a fireproof safe. By taking this step you will be able to recover your system should your NetMAX server be met with a catastrophic end (fire, tornado, earthquake, nuclear missile attack, etc...).

Backing Up The NetMAX Server

1. Your NetMAX system CDROM - To quickly restore the basic static system.
2. Configuration Backup - To restore the configuration settings of the NetMAX.
3. Backup Tapes of Data - To restore your valuable data.

The Backup Process

1. First backup your system configuration to a backup configuration floppy through the NetMAX interface.

   • Insert a formatted 3.5 inch high density diskette in your floppy drive.
   • Go to Home|System|Configuration. The screen will list your floppy drive device. Select Continue. When the message on the screen updates to "Ready to backup configuration" select Continue again to begin the backup process.
   • Note: Make sure to backup your configuration regularly! You should back up your configuration any time you make a system change. Remember if you backup your system regularly your restoration will be closer to your current system. It is also a good idea to rotate backup diskettes so that if something doesn't work correctly you can restore from a prior configuration backup.
   • You can also make this Configuration Backup Floppy from the command line using the following command:

     /usr/netmax/bin/floppy_backup.pl -b -d /dev/fd0

2. Use NetMAX's backup function to store critical information and data for later retrieval if required.
   • Go to Home|Services|Backup and configure the backup utility to store the directory /var/mnt/System and all subdirectories it contains.
   • This directory tree contains the users home directories, the Web directories and any other data information you may have stored on your NetMAX server system volume. If you know specifically what directories you will be using to store custom data (for example, only web sites), then you may choose those specific directories. Its always better to back up more than you need than to miss something though.
   • Note: Make sure that "Start at beginning of tape" is selected the first time you back up. This is necessary for proper recovery.
   • Also configure the backup utility to store the directory /var/conf and all subdirectories it contains. This directory tree stores all configuration data for the NetMAX server. It shouldn't be needed if you have a proper configuration back up floppy, but it can't hurt to have this data backed up in more than one place.
   • Note: Double check your backup configuration to make sure that you are backing up these two directories:

     • /var/mnt/System
     • /var/conf
   • In order to backup another hard drive (volume) you will need to backup an additional directory.

     • The additional directory you need to backup is:

       /var/mnt/(volume name)

     • Where (volume name) is the name you gave to your NetMAX hard drive.
     • For example if you created a volume called "secondhd" configure the backup utility to additionally backup the directory /var/mnt/secondhd.
   • Again, double check that you have selected "Start from beginning of tape."

System Recovery

How to fully recover a NetMAX server from a complete failure.

To do this you need:

1. Your NetMAX system CDROM - To quickly restore the basic static system.
2. Current Configuration Backup - To restore the configuration settings of the NetMAX.
3. CURRENT Backup Tapes of Data - To restore your valuable data.

Recovery Process

The following process requires that you backed up your system by following the backup tips above. Additionally it assumes that the current hardware and network setup is identical to the hardware and network which created the backup. In other words only the data on the drive has changed.

1. Install NetMAX using your NetMAX CDROM. Make sure to use the same IP address as before.
2. After installation you will be able to recover your previous configuration.
   • Reboot using your NetMAX CDROM or a boot floppy and proceed to do a repair. For more information on doing a repair consult your manual.
   • From the repair options select Restore and follow the instructions given to restore your configuration from your configuration backup diskette.

     If you had applied patches or upgrades before you made the Configuration Backup Floppy, the version on the CD may not match the version on the floppy. In this case, you will want to apply all of the patches and upgrades to bring your NetMAX up to the version that you used to make the floppy. Then restore the configuration from the floppy with the following command:

     /usr/netmax/bin/floppy_backup.pl -r -d /dev/fd0

3. After you have restored your configuration you are ready to restore data from your tape backup.
   • Put the most recent full backup tape in the tape drive.
   • Before restoring your backed up files re-catalog your tape.
   • After NetMAX has been reinstalled and the configuration has been restored using the backup configuration diskette, put your backup tape in your tape drive.
   • Log into your NetMAX interface and go to: Home | Services | Backups.

     • Click on the Catalog button.
     • Make sure that your tape drive is selected in the device drop down menu.
     • Click the "OK" button.
   • Once the re-cataloging has completed you may continue with your restoration.
   • Go to Home | Services | Backup and click Restore.
     • Restore your backup of:

       • /var/mnt/System/
       • /var/conf
       • /var/mnt/(volume name) (if applicable)

   • If you have differential tapes, repeat this process for each differential going from oldest to newest. If the differentials were stored on the same tape, the backup system will automatically restore the newest version of each file.
   • Now that you have recovered your Web, User etc. data and your system configuration you need commit the system.
     • If your commit button is not blinking you can force a commit by going to Home|Services|Mail and clicking the Store button.

4. After the commit has completed you will be back up and running with the same files and settings from the last time you backed up your system.

Special Circumstances Recovery Method

If you try to restore from tape backup and keep getting the message "verifying tape id" or "locating archive" try the following steps:

For this procedure you must be logged into the command line of NetMAX as root user. You must also have the most recent full backup in the tape drive. This should only be tried as a last resort.

**This procedure assumes that there is enough space available to restore files from backup.

1. First the tape in the drive must be rewound. Use this command to do so.

   • /usr/netmax/mt -f /dev/nst0 rewind
2. After the tape has rewound (the prompt reappears) you can recover your data from the tape drive. In this procedure you will restore the data to the directory from where it was backed up.

   • First you need to change directory to the root directory:

     • cd /
3. From the root directory you will recover the NetMAX configuration files as well as all data from /var/mnt/System (user, web, applications, etc.) Run this command to begin recovery:

   • dd if=/dev/st0 bs=10240 | gunzip | tar -xvf -
4. Now that you have recovered all of the stored NetMAX files you will need to run a few commands to get the system back to the state it was at when it was backed up.

   • cd /var/conf/sdb
   • find .-type f -exec touch {}/;
   • parse
   • pmake commit

• After you run the last command your system will be fully recovered. At this point you may continue use of your NetMAX server.

1. Move all files in the /var/conf directory to a temporary backup directory.
2. Restore /var/conf from your backup into the now empty /var/conf directory. The method of restoring will vary depending on whether you backed up to tape or to a floppy.
3. Make sure you are logged in as root at the command line.
4. Type:
   find /var/conf/sdb -type f -exec touch {} \;
5. Next, type:
   parse pmake commit

Answers in this category:
Why can't I save a link to a document by using the "Save Link As..." option?
What happened to my symbolic links in /etc for the db versions of the password files?

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

If you wish to save a file to your local computer, first click the link to the file. The document should appear in a new window. If your browser knows how to handle a particular format (i.e., text, jpeg, pdf), it will display the file and you can use the File|Save menu within your browser. If your browser is unable to handle a document, your browser should ask you if you wish to save it at that time.
address-suppressed

Answers in this category:
The NetMAX bar at the top of the screen has turned red.

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Answers in this category:
I am trying to print to a password-protected Windows network print spool from a client and it fails to print.
When printing from Windows NT (or Windows 95) using an HP Laser Jet IIISi or HP LaserJet IIISi Post Script printer, it prints [LaserJet Data] at the top of the page, and does not complete the print job.
I am unable to print to a Windows printer.
I have configured a network printer using LPR and am unable to print to it.
I'm having a problem when printing to printer connected to the parallel port.
When using NetMAX as a print server, how do I stop the banner page from printing?

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  All versions of NetMAX

The fix is to set Windows to use a generic PostScript driver, NOT an HP-printer PostScript driver (as most of them will include this PCL header to switch it to PostScript). You might try using a more generic PostScript printer driver, like the Apple LaserWriter II NT Driver.
address-suppressed

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

The work-around is to log into your NetMAX machine, become root, and edit the file /usr/netmax/etc/rc.d/lpd.sh and add the following line after the initial comments:

/usr/sbin/lptcontrol -p -d /dev/lpt0

This command switches the parallel port to polled mode.

This only applies to the FreeBSD FBSD33Pv2.0 version of NetMAX.
address-suppressed

More than likely your printer is currently configured to always print banner pages.

If you are not getting a banner page when printing from your other print servers, or printing directly from your clients, it is because those clients/servers must be specifically telling the printer to not print the banner page that it would otherwise print.

The NetMAX Interface does not include the feature of allowing you to tell the printer to not print a banner page.

Please review the manual for your printer for instructions on how to disable the banner page.

For most HP printers with an MIO internal print server or HP JetDirect print server, you can telnet to the print server's IP and disable it remotely. Otherwise, you may need to disable it through the buttons and menus on the printer itself.
address-suppressed

Answers in this category:
When I log into the NetMAX console using 'L', I am immediately returned to the console status screen.
What version of the X Server comes with NetMAX?
When I log into the NetMAX console using X (Start X-session), both KDE and Netscape complain that they are unable to write configuration files.
What is the proper way to logically shutdown my NetMAX server? Can I just use the shutdown, halt, or reboot commands?
Why does "locate" no longer work from the command line?
Why can I not start any X applications, after the initial commit, when installing from an X console?
How do I change my default X-Windows Desktop?

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Always using these commands to shutdown your NetMAX machine from the command line will ensure a logical shutdown by checking for a commit in progress and terminating daemons nicely, among other things.

The easiest way to shutdown your server, is through the NetMAX interface. From Home|Shutdown the system can be halted by using the "Immediate Shutdown" button, and it can be rebooted by using the "Immediate Restart" button. It is strongly recommended that a user halt or reboot the NetMAX from the NetMAX interface.

The Toshiba Magnia SG10 and SG20 can be easily shutdown using the buttons on the front of the appliance. Press the power button once. The LCD screen will ask if you are sure you want to shut down. Press the power button again. This will initiate the software shutdown process. Note that shutting down using this method is the same as using the NetMAX interface. Never unplug a Magnia before shutting down using one of these two methods.
address-suppressed

• Install all files required by the desktop environment. This can be done through the NetMAX package management utility.
• Change the sim link to startx:
  ls -l `which startx`
  ln -sf startx.orig /usr/X11R6/bin/startx
  (replace the path to startx with what the first command returns)
• Exit the X windows environment and log into the shell.
• Type switchdesk GNOME (replace GNOME with the desktop of choice)
• Log in to X Windows again.

Answers in this category:
Why can't I send an email to an IP address, for example, to an email address of yoohoo@192.168.10.1?
Can I use "webmaster" or "faq" as a functioning email alias?
How do I allow users to execute programs in their .forward file?
Why am I having a problem when FTPing through my NetMAX FireWall?
What email aliases are set up by default, and how can I modify them?
Why are my mail aliases not working?
I'm having problems with my IMAP server. It's not saving any mail.
Why isn't Sendmail running on my NetMAX machine?
How do I allow anyone to relay email through my NetMAX WebServer/Professional?
Why doesn't my Windows95/98 machine talk to the network time server?
My WebServer/Internet Server/Professional users no longer receive email.
Why isn't ProFTPD starting after upgrading to L22Pv31p1?
Why are FTP downloads from my NetMAX being corrupted?
Why is there a delay when my email clients connect to the POP/IMAP server on the NetMAX?
How do I SSL enable POP3?
Why are my mail aliases not working?
How do I set up a catch-all mail alias?
What happens when I click "Send" in my mail client?
How do I set up an autoresponse when users are on vacation?
How can I limit the maximum size of a single email message? (Maximum SMTP size)

Applies to:
            NetMAX FreeBSD Bld475
            NetMAX Linux 2.0.37 - 3.x

This can also be done for other fixed aliases in this file.
address-suppressed

For NetMAX 2.x and earlier

For NetMAX 3.x - 4.0x

            All Linux versions of NetMAX
            IPChains is specific to NetMAX 2.x - 3.x.
            NetMAX 4.0x uses IPTables

Active FTP

A normal (active) FTP session typically starts with an FTP client initiating the control connection from a high numbered port to TCP port 21 of the FTP server.

All commands and replies are sent over this control connection.

When a file is requested, the FTP server initiates a data connection from the adjacent port (its default data port, TCP port 20) to the FTP client on the data port.

By default, the data port of the FTP client is the same high numbered port that the control connection originated from.

This data connection is used for transfering files, which includes the ascii sending of directory listings.

So, before sending a request for a file transfer, the FTP client starts listening on this port for the data conenction.

                ------------                -------------
                |          |  FTP Commands  |           |
                |   FTP    | -------------> |    FTP    |
                |  CLIENT  |   FTP Replies  |  SERVER   |
                |          |                |           |
                |          |      Data      |           |
                |          | <------------- |           |
                |          |   Connection   |           |
                ------------                -------------

Upon file transfer completion the data connectin closes and a new one is created for every additional file transfer.

The FTP client can specify for the FTP server to connect to a data port other than the default port by issuing a PORT command. A lot of FTP clients now a days automatically issue a PORT command because they want to specify which port the data connection should go to.

Passive FTP

In passive mode FTP, the FTP client sends the PASV command, which tells the FTP server to listen for a data connection instead of initiating one. However, the PASV command also results in a request for the FTP server to specify a different default data port.

So if the PASV commands is used, it's possible for the data connection to be initiated from a different high numbered port on the ftp client to a different high numbered port on the FTP server.

                ------------                -------------
                |          |  FTP Commands  |           |
                |   FTP    | -------------> |    FTP    |
                |  CLIENT  |   FTP Replies  |  SERVER   |
                |          |                |           |
                |          |      Data      |           |
                |          | -------------> |           |
                |          |   Connection   |           |
                ------------                -------------

FTP Clients behind the firewall.

So, when using a packet filtering firewall (such as NetMAX FireWall), the following rules must be added to allow FTP clients behind the firewall to access FTP servers on the external network (Internet):

Action	Type	From Address	Mask	Port	To Address	Mask	Port	Direction	SYN	Notes
accept	tcp	Network IP		1025-65535	any		21	output		Allow control traffic/connection out
accept	tcp	Network IP		1025-65535	any		20	output		Allow data traffic out
deny	tcp	any		21	Network IP		1025-65535	input	Y	Block incoming connections with control source port
accept	tcp	any		21	Network IP		1025-65535	input		Allow control traffic in
deny	tcp	any			Network IP		6000-6009	input		Protect Xwindows ports
accept	tcp	any		20	Network IP		1025-65535	input		Allow data traffic in

If using passive mode (which is more secure), you would need the following rules:

Action	Type	From Address	Mask	Port	To Address	Mask	Port	Direction	SYN	Notes
accept	tcp	Network IP		1025-65535	any		21	output		Allow control traffic out
accept	tcp	Network IP		1025-65535	any		1025-65535	output		Allow data traffic/connection out
deny	tcp	any			Network IP		1025-65535	input	Y	Block incoming connections
accept	tcp	any		1025-65535	Network IP		1025-65535	input		Allow control/data traffic in

We assume here that you have more than one FTP client behind your firewall. If you only have one, you can specify an IP address instead of using "Network IP" (for additional security).

Of course, when you're doing IP NAT (Network Address Translation) on your NetMAX FireWall, it's a completely different story. If your FTP client is behind the NAT, you need to use passive mode FTP, because you can't realistically setup a port forwarding rule to allow the FTP server to make the data connection in through the NAT to an unknown high numbered port.

And even if you're doing passive mode FTP, you'll have to keep your FTP transfers short, because the control connection is going to time out (because ip masquerading connections timeout after 15 minutes by default if there is no activity on them) before the data connection is finished transfering the file, which will effectively kill your transfer.

So, if you keep your FTP transfers under 15 minutes and use passive mode, you should be able to use the following rules to allow FTP through your NAT and packet filtered firewall.

Action	Type	From Address	Mask	Port	To Address	Mask	Port	Direction	SYN	Notes
accept	tcp	Network IP		1025-65535	any		21	output		Allow control traffic out
accept	tcp	Network IP		1025-65535	any		1025-65535	output		Allow data traffic/connection out
deny	tcp	any			Network IP		1025-65535	input	Y	Block incoming connections
accept	tcp	any		1025-65535	Network IP		1025-65535	input		Allow control/data traffic in

FTP Server behind the firewall.

If you have your FTP server behind a packet filtering firewall (such as NetMAX FireWall), you will need the following rules to allow ftp transfers through the firewall:

Action	Type	From Address	Mask	Port	To Address	Mask	Port	Direction	SYN	Notes
accept	tcp	Network IP		21	any		1025-65535	output		Allow control traffic out
accept	tcp	Network IP		20	any		1025-65535	output		Allow data traffic out
accept	tcp	any		1025-65535	Network IP		21	input		Allow control traffic/connection in
deny	tcp	any			Network IP		20	input	Y	Block incoming connections to data port
accept	tcp	any		1025-65535	Network IP		20	input		Allow data traffic in

To allow for passive mode FTP, you would also need the following rules (which are not recommended, because they open up your firewall for access to high numbered ports):

Action	Type	From Address	Mask	Port	To Address	Mask	Port	Direction	SYN	Notes
accept	tcp	Network IP		1025-65535	any		1025-65535	output		Allow data traffic out
deny	tcp	any			Network IP		6000-6009	input		Protect Xwindows ports
accept	tcp	any		1025-65535	Network IP		1025-65535	input		Allow data traffic/connection in

We assume here that you have more than one FTP server behind your firewall. If you only have one, you can specify the IP address, instead of using "Network IP" (for additional security).

Of course, when you're doing IP NAT (Network Address Translation) on your NetMAX FireWall, it's a completely different story. If your FTP server is behind the NAT, you need to use normal (active) mode FTP, because you can't realistically setup a port forwarding rule to allow the FTP client to make the data connection in through the NAT to an unknown high numbered port. You also need to setup port forwarding (Traffic Rerouting on your NetMAX FireWall Suite) to forward TCP port 21 to your FTP server.

And even if you're doing normal mode FTP, you'll have to keep your FTP transfers short, because the control connection is going to time out (because ip masquerading connections timeout after 15 minutes by default if there is no activity on them) before the data connection is finished transfering the file, which will effectively kill your transfer.

Adjusting the TCP timeout for your NAT:

One way to help the situation when doing FTP through a NAT, is by optimizing the timeouts of your IP masquerading.

From the command line, you can type the following:

ipchains -M -S 7200 10 160

Where 7200 is the number of seconds (120 minutes) for the TCP timeout, 10 is the number of seconds for the TCP timeout (after receiving a FIN), and 160 is the number of seconds for the UDP timeout.

Also, you can enable hash marks in your FTP client, if it supports it.

ip_masq_ftp Kernel Module:

L2.2Pv3.x of the NetMAX FireWall comes with the ip_masq_ftp kernel module installed, which "fixes" the problems with having an FTP client behind an IP NAT. This module is a work around for the limitations of IP NAT and FTP.

• It checks incoming packets for replies to outgoing PASV commands. If it sees one, it sets up a new masquerade entry for the outgoing data connection rather than letting the normal ip_masq logic set up the entry when the first data packet is sent. It does this just so it can set a special pointer in the data connection entry pointing at the control connection entry. The ip_masq code uses this pointer to reset the timeout for the control connection when there is activity on the data connection. This prevents the control connection from being deleted during a long data transfer.
• It checks outgoing packets for PORT commands, which mean the masqueraded client is telling the external server to open a data connection. If it sees one, it sets up a new masquerade entry as if the connection were being opened from the masq side, and re-writes the PORT command packet to specify the masq box's IP address and the selected masq port number. That way the incoming data packet will look like a reply to a previous outgoing packet, and the ip_masq code will know what to do with it. And of course the new entry for the data connection is linked to the control connection so it will be kept alive.

Limitations of ip_masq_ftp:

• Your FTP client can't use the default data port, but must instead use the PORT command to specify a different data port when doing active mode FTP.
• Only works when connecting to FTP servers on the standard port 21.
• It is not orthogonal, so it only helps if the FTP client is behind the NAT, and not if the FTP server is behind the NAT.

Notes:

If you want to connect to an FTP site by its domain name instead of by its IP address, you may also need to open up DNS ports. This article is not intended to cover DNS.

The ip_masq_ftp kernel module comes with the L2.2Pv2.2 product as well, but is not installed by default. To install it, you need to edit the /etc/rc.d/rc.sysinit file, and add the following lines above the other modprobe commands:

# Insert ip_masq_ftp so that passive mode for a ftp client is not needed.
modprobe ip_masq_ftp

So your rc.sysinit file should now look like this:

<--SNIP-->
        fi
fi

# Insert ip_masq_ftp so that passive mode for a ftp client is not needed.
modprobe ip_masq_ftp

# Probe for a IBMPC parallel port
modprobe parport_pc 2>/dev/null
modprobe lp 2>/dev/null

<--SNIP-->

Update: The 4.0 and 4.01 versions of NetMAX use the Linux 2.4 kernel and netfilter. The modules to enable this are slightly different, and are also not installed by default.

modprobe ip_conntrack_ftp
modprobe ip_nat_ftp

The above two lines can be added to the /etc/rc.firewall.local script to run after each firewall commit and reboot.

NetMAX 4.02 enables these modules by default, if you have IP NAT enabled on an interface under Home|Network|Interfaces.

These modules add packet editors to your TCP stack. So that each TPC packet is scanned for PORT FTP commands so that they can be rewritten and tracked in the packets. It is recommended that you don't enable these modules unless you are doing NAT and active mode FTP is required. They will cause a slightly higher CPU load.

Sources:

ip_masq_ftp Release Notes, RFC 959
address-suppressed

adm, bin, daemon, games, gopher, halt, hostmaster, lp, man, mail, news, nobody, operator, photo-user, shutdown, sync, system, toor, uucp, usenet, webmaster, netmax, anonymous, ftp, manager, dev_null

After you edit this file, you must commit your changes by forcing the mail committer to run by going to Home|Services|Mail. Click STORE (no configuration changes are required). Click COMMIT in the green Command Panel. Lastly, click on the smaller COMMIT button in the Input Frame.

In NetMAX 4.0x, the webmaster alias can no longer be edited in this way. It has been removed from the aliases file, as it can now be configured through the NetMAX interface.
address-suppressed

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 3.x

If you have more than 112 users in a mail alias, try reducing the number of users in that alias. A work-around is to make an alias that points to more aliases. For example, to have the alias "all" point to 200 users, use three aliases: "allpart1" points to the first 100 users, "allpart2" points to the second 100 users, and "all" is addressed to "allpart1@yourdomain.com" and "allpart2@yourdomain.com".
address-suppressed

Versions L2.2Pv2.x

To make your mail server an open relay (a potential target for spammers):

Edit the /etc/sendmail.cf file and comment out the following line:

R$*                    $#error $@ 5.7.1 $: "550 Relaying denied"

So when you're done, it should read:

#R$*                    $#error $@ 5.7.1 $: "550 Relaying denied"

You'll also want to add this file to the /etc/commit.conf file so that NetMAX doesn't overwrite this customization.

Edit the /etc/commit.conf file to contain the following line:

skip /etc/sendmail.cf

After you edit this file, you must commit your changes by forcing the mail committer to run by going to Home|Services|Mail. Click STORE (no configuration changes are required). Click COMMIT in the green Command Panel. Lastly, click on the smaller COMMIT button in the Input Frame.

Versions L2.2Pv3.x

To make your mail server an open relay (a potential target for spammers):

Edit the /etc/sendmail.cf file and comment out the following lines:

R     $#error $@ 4.7.1 $: "450 Relaying temporarily denied. Cannot resolve PTR record for " $&{client_addr}
R     $#error $@ 5.7.1 $: "550 Relaying denied. IP name possibly forged " $&{client_name}
R     $#error $@ 5.7.1 $: "550 Relaying denied. IP name lookup failed " $&{client_name}
R$*                    $#error $@ 5.7.1 $: "550 Relaying denied"

So when you're done, it should read:

#R    $#error $@ 4.7.1 $: "450 Relaying temporarily denied. Cannot resolve PTR record for " $&{client_addr}
#R    $#error $@ 5.7.1 $: "550 Relaying denied. IP name possibly forged " $&{client_name}
#R    $#error $@ 5.7.1 $: "550 Relaying denied. IP name lookup failed " $&{client_name}
R$*                     $:  $&{client_name}
# pass to name server to make hostname canonical
R $* $~P             $:  $[ $1 $2 $]
R$* .                   $1                      strip trailing dots
R                    $@ RELAYFROM
R $=w                $@ RELAYFROM
R $* $=R                     $@ RELAYFROM
R $*                 $: $>LookUpDomain <$1>  <$1> <+Connect>
R $*             $@ RELAYFROM
R<$*> <$*>              $: $2

# anything else is bogus
#R$*                     $#error $@ 5.7.1 $: "550 Relaying denied"

You'll also want to add this file to the /etc/commit.conf file so that NetMAX doesn't overwrite this customization.

Edit the /etc/commit.conf file to contain the following line:

skip /etc/sendmail.cf

After you edit this file, you must commit your changes by forcing the mail committer to run by going to Home|Services|Mail. Click STORE (no configuration changes are required). Click COMMIT in the green Command Panel. Lastly, click on the smaller COMMIT button in the Input Frame.
address-suppressed

net time \\netmax /set

Issuing this command on a Windows95/98 machine uses file and print sharing services to access a windows proprietary time server. It does not use the Internet standard NTP (Network Time Protocol) service that is running on your NetMAX.

Although Windows95/98 does not come with an NTP client, there are freely available ones that you can find and download on the Internet.
address-suppressed

This may be followed by an error during a commit of "Mail spool no longer under the NetMAX server's control".

The problem is that after using your NetMAX CD to perform a Repair, a symbolic link to the location of the mail spool is broken.

To recreate this link, please type the following from the command line, logged in as root:

ln -s /var/mnt/System/Mail /var/spool/mail

Upon investigation, we have decided to remove this package from Package Management, and the FTP site.

The RPM has been reported to disable FTP, and to disable VPN communications.

If you have downloaded this RPM, please follow this procedure to return your system to its original (Pre-updated) state:

From the NetMAX interface, edit the file BUILD in the root of the filesystem.
Change the contents of this file to contain 120820801.120823250.120827737
DO NOT press enter at the end of this line.
Save the file.

Now run the repair from a NetMAX L2.2Pv3.1 CD.
See "Completing the NetMAX Remote Installer > Repair Mode" in the NetMAX QuickStart Guide.

After the repair is complete, reboot the NetMAX and remove the CD. Ensure that all system functions are operating properly.

We are sorry for any inconvenience that this mistake has caused our customers. The development team is currently working on getting the update patches fixed, thoroughly tested,  and returned to Package Management and the FTP site so that our customers can benefit from these updates.
address-suppressed

This problem is resolved in ProFTPD 1.2.2rc2.

To upgrade your ProFTPD daemon to the current version, download the 1.2.2rc2 or later tarball from ProFTPD's web site.

Normally you will then need to ungzip, untar, and compile the program and replace your proftpd binary with the one you just compiled. A typical session would go like this (logged in as root):

gzip -d proftpd-1.2.2rc2.tar.gz

tar -xvf .tar

cd proftpd-1.2.2rc2

./configure --prefix=/usr/netmax --datadir=/var/conf/proftpd --sysconfdir=/var/conf/proftpd --sharedstatedir=/var/conf --localstatedir=/var/conf --with-modules=mod_l
inuxprivs:mod_quota:mod_ratio:mod_ldap --with-includes=/usr/netmax/include --with-libraries=/usr/netmax/lib

make

cp /usr/netmax/sbin/proftpd /usr/netmax/sbin/proftpd.old

cp -f proftpd /usr/netmax/sbin/

address-suppressed

1. Your email client (such as Netscape Communicator, Eudora, Outlook, or Outlook Express) initiates a TCP connection to the IP address of the POP/IMAP server that you have specified.

   NOTES: If your email client is set up to connect to a machine by hostname (instead of by IP address) here is where your first delay might be encountered, because the email client must resolve the name to it's IP address. Usually this will be answered immediately though, or not at all. So this might be the problem if you are unable to connect to the email server at all, but most likely is not the problem if you do connect to it eventually.

   When checking email that resides on the NetMAX, or using the SMTP server on your NetMAX, all of your email clients on the Internet should connect to a hostname that resolves to your NetMAX's external IP address, or you can specify the IP address instead of a hostname. All of your internal email clients (behind the same NAT that the email server is behind), should use a hostname that resolves to the internal IP address of the NetMAX, or you can specify the IP address instead of a hostname.

2. The sendmail email server on the NetMAX notes the IP address that the email client is connecting from.
3. The email server spends 30 seconds attempting a reverse domain name lookup to see what name that IP address reverse resolves too.

   NOTES: This is usually where the delay is caused, because when the NetMAX attempts to resolve that IP address to a name, it doesn't resolve. The main reasons why this happens are:

   1. The NetMAX's DNS server is not set to use the InterNIC. If you don't tell the NetMAX to use specific DNS servers for name resolution, you can set it to use the InterNIC by checking the box under Home|Network|DNS (provided that you have a NetMAX product that provides DNS services).
   2. The NetMAX's DNS resolver is not set to use the correct name servers. If your NetMAX is not a DNS server that is using the InterNIC, you must tell it what Domain Name Servers to use when it needs to resolve names. This is usually your ISP's nameservers. This is configured under Home|Network|DNS.
   3. The nameserver responsible (based on InterNIC records) for providing reverse resolution for that specific IP address is not answering requests at that time. This can be blamed on the ISP that owns that IP address space.
   4. The nameserver responsible (based on InterNIC records) for providing reverse resolution for that specific IP address doesn't exist, or isn't configured correctly. This can be blamed on the ISP that owns that IP address space.

      NOTES: But the NetMAX is responsible for this IP address (based on InterNIC records)? Then you don't have the latest version of the NetMAX (some earlier versions didn't set up reverse entries correctly), the NetMAX hasn't really been deligated responsiblity for reverse name resolution for that address space with InterNIC's records, or you haven't entered those IP addresses for the hosts into Home|Network|Machines under the appropriate domain.

      If the IP addresses are INTERNAL (private/non-routeable) IP addresses, and the NetMAX is responsible for reverse DNS, make sure that you are at the latest version, that you have a domain under Home|Network|Domains that contains the INTERNAL network, and that the IP addresses are entered with a hostname under Home|Network|Machines under that domain.

      What if some other machine is assigning my INTERNAL machines with IP addresses dynamically? Then that machine should do the reverse DNS for those IPs, because there's no way you're going to be able set up the NetMAX to do it, unless you want to get rid of that DHCP server and use the DHCP services on your NetMAX (if you have a NetMAX product that includes the DHCP services).

4. A connection is allowed after the reverse name lookup times out, or after a reply is successfully received.
5. The email client authenticates by providing it's username and password.
6. If authentication is successful, new email is downloaded (for POP), or new headers are downloaded (for IMAP), or the email is sent (if using SMTP and relaying is allowed from that IP or domain).

NOTES: Although this is now commonly referred to as "reverse DNS", there is no reverse mapping done, so the term is a misnomer. The resolution from IP address to name is handled in the same way as the resolution from name to IP address. The only difference is that the lookup is done on the IN-ADDR-ARPA infrastructure domain instead of the top level domain.
address-suppressed

Follow these steps to SSL enable POP3:

• Log in with root access.
• Make a directory for the certificates: mkdir /usr/netmax/certs
• Copy the admin.pem certificate:       cp /var/conf/ssl/admin.pem /usr/netmax/certs/ipop3sd.pem
• Copy pop3 to pop3s:       cp /etc/xinet.d/pop3 /etc/xinet.d/pop3s
• Edit the pop3s file changing all instances of pop3 to pop3s
• Restart the xinetd service:       service xinetd restart
• Test it by typing:       telnet localhost 995
• You should get a message about the escape character.

address-suppressed

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

If you have more than 112 users in a mail alias, try reducing the number of users in that alias. A work-around is to make an alias that points to more aliases. For example, to have the alias "all" point to 200 users, use three aliases: "allpart1" points to the first 100 users, "allpart2" points to the second 100 users, and "all" is addressed to "allpart1@yourdomain.com" and "allpart2@yourdomain.com".
address-suppressed

Explanation of a Catch-All Alias

• Users:
  • jeff
  • bill
  • fred
• Aliases:
  • support (goes to jeff)
  • help (goes to bill and fred)

• Users:
  • jeff
  • bill
  • fred
• Aliases:
  • jeff (goes to jeff)
  • bill (goes to bill)
  • fred (goes to fred)
  • support (goes to jeff)
  • help (goes to bill and fred)

How to Create a Catch-All Alias

Caveats to setting up a Catch-All Alias

1. The local SMTP receives outbound messages.
2. The destination address is analyzed.
3. The SMTP server checks for the DNS mail exchanger (MX) record of the domain in the destination address. This points to to SMTP server that handles inbound messages for the destination email address.
4. The message is sent to the destination SMTP server.
5. If there is a problem, either the SMTP will hold on to the message and try to retransmit later, or it will bounce and a bounce notification will be send to the originator of the message.
6. If there are no problems, the SMTP server will usually pass the message off to a special program called the "delivery agent."
7. The delivery agent's ultimate goal is to get the message into the mailbox of the recipient. Sometimes, however, the delivery agent will perform other steps like content-filtering or auto-responding, which may involve passing the message to other programs before final delivery.

Follow these steps to limit the maximum size of email messages:

• Log into the NetMAX interface as an administrative user.
• Access HOME|Services|Mail
• Specify the maximum message size (in bytes) for Maximum Message Size (bytes)
  Notes: If you specify a value of 0 then there will be no limit at all.
  This can lead to problems where someone sends a message that is too big for the amount of RAM in your NetMAX server.
  This leads to crashes and unpredictable behavior.

address-suppressed

Answers in this category:
How do I set up SSI (Server Side Includes)?
How do I enable CGI applications with the .pl extension?
How do I setup multiple web sites on my NetMAX Web Server Product?
For what Certificate Authorities can NetMAX create a Certificate Signing Request for SSL?
When I try to setup multiple web sites, get "The IP for this host name is already used in an IP based Virtual Host".
How do I enable the FrontPage server extensions to handle form submission webbots?
UID of user "nobody" changes when upgrading to L2.4Pv4.0x
How do I use CGI on my website?

Method 1

For this method, we're going to create an .htaccess file to each directory where we want to execute SSI. Because we're going to be using an .htaccess file, we need to allow this file the override the default settings:

1. From Home|Services|WWW, click on the WEB SITES tab, click on the pencil next to the appropriate web site, click on the OPTIONS tab, then ensure that the "Enable CGI Execution" and "Enable .htaccess to Override Defaults" checkboxes are checked.
2. Click on RETURN, then STORE, then COMMIT, and commit your changes.
3. Next, you'll need to create a file named .htaccess in the directory where you want to execute SSI. The file should contain the following line:

   XBitHack on

4. Set execute permissions on the HTML document that contains the SSI.

The "XBitHack on" directive tells the server to treat each executable file in the directory as a server-parsed-html file.

Method 2

For this method, we'll setup a specific mime type that will tell the WebServer to treat as server-parsed-html.

1. From Home|Services|WWW, click on the WEB SITES tab, click on the pencil next to the appropriate web site, click on the OPTIONS tab, then enxure that the "Enable CGI Execution" checkbox is checked.
2. From Home|Services|WWW, click onthe MIME TYPES tab, click on CREATE, and create the following Mime Type:

   Extension: shtml
   MIME Type: text/x-server-parsed-html
   Local Execution Method: None

3. Click on RETURN, then STORE, then COMMIT, and commit your changes.

4. Create your HTML documents that contain SSI with the .shtml extension.

Notes for both methods: If you are an advanced Apache user, then it is important to note that checking the "Enable CGI Execution" checkbox actually adds the ExecCGI and Includes Options. Also, because the webserver runs as nobody, you'll need to ensure that your cgi's are executable by the nobody system user.
address-suppressed

From Home|Services|WWW click on the pencil next to the mime type for the cgi extension and add the pl extension so that the extension now reads:

Extension: cgi pl
MIME Type: application/x-httpd-cgi

Note: That's a space between cgi and pl.

Then click on Store then Commit and commit your changes.

As always, the .pl file will need to have permissions set so that the web server can run the program.
address-suppressed

IP Based virtual hosting

Important Note: RH52Pv2.0 and L22Pv2.x only support IP based virtual hosting. This means that each web site (domain name) has to have it's own IP address.

To add multiple IP's and setup web sites for them, please do the following:

1. Add additional IP addresses to your network adapter from Home|Network|Interfaces click on the pencil next to your network adapter, add additional IP addresses, STORE, and COMMIT your changes.
2. Add the additional domain names from Home|Network|Domains. You need to at least enter the Domain Name and Primary IP Address for the domain. You can click on the "?" for help on filling this form out. After you add all of the domains, click on STORE, and COMMIT your changes.
3. Add host names for the additonal domain names from Home|Network|Naming. You'll probably want to add names like www.domainname.com for each IP address. After you add all of the host names, click on STORE, and COMMIT your changes.
4. From Home|Services|WWW you should be able to click on the WEB SITES tab and add a web site for each www.domainname.com that you set up in step 3. Make sure and specify a different "Path" for each one. You'll probably want to put all of the paths parallel to each other.

        |--- /log       |--- /PublicFTP           |--- /domainname1
   /var |--- /mnt ------|--- /System ---|--- /Web |--- /domainname2
        |--- /preserve  |--- /Web                 |--- /domainname3
   

   If you have L22Pv3.x, you'll want to select "IP" for "Web Site Host Method".

   When you're done adding your web sites, click on STORE, and COMMIT your changes.

5. You'll probably want to setup a username for the webmaster of each domain name and set their home directory to be the "Path" to the web site. That way each user can ftp/telnet in and edit the documents that they're responsible for.
6. If you are using the mail server on your NetMAX and have both domain names (and their MX record) pointing to the NetMAX then each user (Home|Users|Users) will actually be able to receive email at any of the domain names associated with the NetMAX machine.

   So the user john would receive email at john@domainname1.com and/or john@domainname2.com. It would be up to john on which domain of the two he wanted to have people send his email to. He could use both if he wanted.

   You will need to make sure that the check box for "Include all domains for this NetMAX" is checked under the ROUTE tab from Home|Services|Mail if you don't want to have to send your mail to john@www.domainname1.com. You can click on the "?" for help when in that area for more information.

   In RH52Pv2.0 and L22Pv2.x, you can only setup email aliases for the primary domain name. In L22Pv3.x, you can setup virtual email aliases for each seperate domain name.

Name Based Virtual Hosting

Important Note: L22Pv3.x supports both IP based, and name based virtual hosting. This means that each web site (domain name) does not need to have its own IP address, because multiple web sites can be hosted on each IP address.

To add multiple IP's and setup web sites for them, please do the following:

1. When setting up your first web site under Home|Services|WWW, you will want to select "Name" for the "Web Site Host Method", if you are going to do name based virtual hosting.
2. To add addtional web sites, you'll need to add the additional domain names from Home|Network|Domains. You need to at least enter the Domain Name and Primary IP Address for the domain. You can click on the "?" for help on filling this form out. After you add all of the domains, click on STORE, and COMMIT your changes.
3. Add host names for the additonal domain names from Home|Network|Naming. You'll probably want to add names like www.domainname.com for each IP address. After you add all of the host names, click on STORE, and COMMIT your changes.
4. From Home|Services|WWW you should be able to click on the WEB SITES tab and add a web site for each www.domainname.com that you set up in step 3. Make sure and specify a different "Path" for each one. You'll probably want to put all of the paths parallel to each other.

        |--- /log       |--- /PublicFTP           |--- /domainname1
   /var |--- /mnt ------|--- /System ---|--- /Web |--- /domainname2
        |--- /preserve  |--- /Web                 |--- /domainname3
   

   Ensure that you select "Name" for the "Web Site Host Method."

   When you're done adding your web sites, click on STORE, and COMMIT your changes.

5. You'll probably want to setup a username for the webmaster of each domain name and set their home directory to be the "Path" to the web site. That way each user can ftp/telnet in and edit the documents that they're responsible for.
6. If you are using the mail server on your NetMAX and have both domain names (and their MX record) pointing to the NetMAX then each user (Home|Users|Users) will actually be able to receive email at any of the domain names associated with the NetMAX machine.

   So the user john would receive email at john@domainname1.com and/or john@domainname2.com. It would be up to john on which domain of the two he wanted to have people send his email to. He could use both if he wanted.

   You will need to make sure that the check box for "Include all domains for this NetMAX" is checked under the ROUTE tab from Home|Services|Mail, if you don't want to have to send your mail to john@www.domainname1.com. In L22Pv3.1, this check box is called "Consider all mail local for this domain" and is located under the MAIL tab in Home|Network|Domains. You can click on the "?" for help when in that area for more information.

   Virtual email aliases can be created for each domain name available on the NetMAX.

128i Ltd. (New Zealand)
BelSign NV/SA
CertiSign Certificadora Digital Ltda.
Deutsches Forschungsnetz
Entrust.net Ltd.
Equifax Inc.
GlobalSign NV/SA
IKS GmbH
ISAKMP Test CA
NLsign B.V.
TC TrustCenter (Germany)
Thawte Consulting
Verisign, Inc.
Verisign, Inc. Test CA

address-suppressed

1. IP Based Web Hosting
2. Name Based Web Hosting

You can not have a combination of the two on the same IP.

You probably already have a website setup for IP.

All you need to do is edit the "Web Site Host Method" for the site, and change it from IP to Name, and then you can create additional Name based web sites on the same IP.
address-suppressed

Emailing the form submissions in NetMAX 3.x and earlier.

Here are the steps that you must take to configure the sending of mail for the FrontPage server extensions for old versions of NetMAX.

Login as root and edit the /var/local/frontpage/version4.0/frontpage.cnf file to contain the following entries:

SendmailCommand:/usr/sbin/sendmail %r
MailSender:frontpage@yourdomain.com

The other option would be to add these lines:

SMTPHost:127.0.0.1
MailSender:frontpage@yourdomain.com

The MailSender address will be used if the from address is not specified in the form. These settings will be used for all virtual hosts as well.

To use different settings for different hosts, instead of editing the frontpage.cnf file, you would edit the .cnf file for each virtual host in the /var/local/frontpage directory.

You will want to read the knowledge base article at:

http://www.netmax.com/fom/cache/266.html

Saving the form submissions to disk

If you are saving form submissions to a file with a webbot, ensure that the directory that you're saving to is writeable by the user "nobody", and that the file already exists and is writeable by the user "nobody". FrontPage expects the file to already be there, and will not create it.

Helpful Notes

(You only need to do the following if you are going to copy your FrontPage created documents over from a Microsoft website, instead of publishing them, like you're supposed to. If you use FrontPage to publish your site to the NetMAX, you do not need to do this!)

In order for the NetMAX to handle the Microsoft FrontPage HTML markups just like a Microsoft FrontPage enabled web server, it only takes a two-line modification to the FrontPage root web's ".htaccess" file. If you have problems publishing your FrontPage documents, or to avoid having to create the form submission save-to files, you can try the following.

The HTML files need to be parsed by "/_vti_bin/shtml.exe" in order for the webbot markups to function as they would on a "normal" FrontPage enabled server. If the HTML pages are not put through "shtml.exe", then the webbot markups are not processed, and the web page will not displayed as intended.

In the FrontPage root's directory (like /var/mnt/System/Web/external) there should be a ".htaccess" file. Add these two lines at the end:

    AddType application/frontpage htm html
    Action  application/frontpage /_vti_bin/shtml.exe

This will make all ".htm" and ".html" files be passed through "/_vti_bin/shtml.exe", which will parse the FP webbot markups, making the NetMAX web server act just like a standard Microsoft FrontPage enabled web server.

SERIOUS DRAWBACK: Since we told Apache to send *all* HTML files through the external CGI script, accessing any HTML file will cause the "shtml.exe" program to be executed. This could seriously slow down the system during a period of time when there are a lot of HTML files being accessed.

Recommended solution: Instead of parsing all "htm" and "html" files for FrontPage webbots, pick another file name extension, like "fphtml", to parse for webbots. In this case, the .htaccess additions mentioned above should be changed to be:

    AddType application/frontpage fphtml
    Action  application/frontpage /_vti_bin/shtml.exe

Note that we do not recommend running the FrontPage server extensions due to multiple security problems associated with them. We can not provide support beyond ensuring that you have enabled FrontPage in the NetMAX Interface. If enabled for a web site, Microsoft's FrontPage Server Extensions for UNIX should be installed as instructed by Microsoft.

http://support.microsoft.com/support/default.asp?SD=SO&PR=fp2000

address-suppressed

For compatibility reasons, we have changed the UID to match the one that RedHat's apache RPMs use. This may cause problems when upgrading a NetMAX that already has web sites configured on it with web documents or directories owned by the user.

To resolve any issues after an upgrade, you may need to run this command as root:

find / -uid 65534 -exec chown nobody {} \;

CGI (Common Gateway Interface) is a great technology for making websites more interactive. A CGI script is a program which is used to generate and customize HTML output or for processing of forms and user data. An example CGI script is included at the bottom of this article.

To enable CGI execution on your website, follow these steps:

1. Log into the NetMAX interface as an administrative user
2. Access HOME|Services|WWW
3. Click Create to make a new website, or the pencil icon to edit an existing website
4. Supply the proper path and hostname information on the Aliases Tab
5. Click the OPTIONS tab
6. Ensure that Enable CGI Execution is checked.
7. You may also wish to change the Default File to the name of your CGI app, i.e. index.cgi
8. Store and Commit the changes

This will cause your NetMAX server to treat any file whose name ends in ".cgi" and is marked as executable to be run from anywhere within the path specified in step 4 (including subdirectories) as CGI applications.

Please note that CGI scripts are programs that run on your server. This means that you should be sure that any CGI applications you choose to implement are secure and do not have any undesired side effects. CGI applications will be run as the user "nobody" by default, so they won't likely be able to damage the system, but any directories and or files accessible to the "nobody" user are accessible by CGI programs as well.

For this reason, it is common practice to put all cgi applications under a common directory which is separate from your usual web content. This directory is typically called "cgi-bin." To achieve maximum security, administrators should put the cgi-bin directory in a completely separate directory space. To accomplish this, disable CGI execution on the main site, create the cgi-bin directory in a separate directory space and add a new site by following the instructions above with one key exception: in the box labelled "URL Path" specify /cgi-bin. This means that the URL to the example CGI would become http://www.mynetmax.net/cgi-bin/index.cgi instead of http://www.mynetmax.net/index.cgi.

Answers in this category:
When viewing a NetMAX table using Unix Netscape, it is difficult for some users to see which checkboxes are checked.
Internet Explorer keeps giving me "Browser Cookie Error" and the NetMAX interface says "Login Disabled because your browser does not have cookies enabled properly!".
Why does nothing happen when I set up a users web page with .htaccess override?
How can I tell how many bits of encryption my browser supports?

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.03

The second problem is that is does not get the the user's .htaccess file, and that is because of the configuration setup in /var/conf/users/apache/access.conf. In the Directory directive is has AllowOverride None, which makes it unable to get to the user's .htaccess.

This appears to happen on linux and freebsd.

Updated 7/16/99, JAH

It appears that is a Apache security issue. When using the Directory directive and trying to match for a regular expression, it appears to ignore the .htaccess file in that directory. This is true for user web pages, but also it is true a regular web site was matched as a regular expression. But, seeing that for the regular web sites we give the absolute path, .htaccess works fine.

Please install the update package RH52Pv2.0U1.
address-suppressed

Answers in this category:
Is the WinChip-200 compatible with NetMAX?
Can I use my General Instruments SB1000 one-way cable modem with NetMAX Fire Wall?
How do I get NetMAX to use all of my memory (RAM) if it is't automatically detected?
Why does the NetGear FA-310 card not work with my NetMAX Linux RH52Pv2.0?
Why does my Intel Ethernet Pro 100 NIC stop responding and give me the "eth0: Too much work to do at interrupt, status=0x4050" error?
Does NetMAX FileServer/Professional support IDE tape backup devices?
Does NetMAX support hardware level RAID?
I keep getting a message saying there are no rx buffers and/or no resources for my Intel EtherExpress Pro card. What's wrong?
Are USB keyboards compatible with NetMAX?
I upgraded to NetMAX 4.04 and my SCSI RAID controller (or Wireless Card) stopped working. How can I fix this?

In order for the NetMAX to recognize it, you must set up the SB1000 driver. This requires configuring Linux's Plug-and-Play (PnP) system. The simple method, which should work for most installations, is to:

• Obtain a "root" shell on your NetMAX. Use "telnet" to log in as an administrator, and then "su".
• Type the following command:

  /sbin/pnpdump -c | /bin/sed -e 's;(CHECK);;' > /etc/isapnp.conf
  

• It is extremely important to check the resulting /etc/isapnp.conf file to make sure that the GIC board has the correct IO 0 BASE, IO 1 BASE, and INT 0 IRQ values. If you have the Microsft Windows drivers installed, then you can use the System Control Panel to determine the correct values for these parameters. Also check this file for conflicting IO and IRQ parameters regarding other devices that the PnP setup software ma have found.
  
  
• Type the following command:

  echo "sb1000" >> /etc/netmods.list
  

  (note that there are two ">" characters)
  
  
• Reboot your NetMAX for the changes to take effect.

After setting up the dial-out modem, visit the Home -> Network -> Routing page and set the Default Router to the dial-out modem you just configured (ttyS#).

Then visit the Home -> Network -> DNS page and set the Allowed to use InterNIC checkbox, so your NetMAX can resolve names on the Internet.

Lastly, Commit all of these changes.

The next time your NetMAX needs to access the Internet, it should automatically dial your Cable service provider.

address-suppressed

RAM

It will ask you if the amount of memory you currently have is correct. Answer n, and it will ask you how much you really have.

You'll have to reboot to get the OS to pick up the changes.

We have found that Linux has a problem finding the memory in some hardware configurations.

Also, you can specify how much memory you have at the Linux boot prompt. When you reboot your NetMAX machine, you should get the Linux boot prompt for 30 seconds at the console. At this prompt type:

linux mem=###M

Where ### is the amount of memory in megabytes. For example, if you have 128M of memory, and the machine is only recognizing 64M, you would type:

linux mem=128M

You would add this line to the /etc/conf.modules file:
options eepro100 max_interrupt_work=40
The variable 40 is just an example, max_interrupt_work uses 20 by defaults. The variable should be determined on a case by case basis.

Note: If you use a number which is to high it potentially could slow down your network traffic.
address-suppressed

However, there is a way to add an IDE tape drive from the command line. Here are the instructions:

1. Add the line "insmod ide-tape" (without the quotes) to the /etc/rc.d/rc.local file.
2. Add the tape entry in the /etc/devs.conf file.

   An example is given in the file for reference:

   #[TapeDrive]
   #st0=SCSI Tape 1 <-sample scsi drive line
   

   A sample of what you might enter:

   [TapeDrive]
   ht0=IDE Tape 1
   

3. Reboot or run /usr/netmax/etc/rc.d/Devs.first (for 3.x products) or /etc/init.d/netmax_devs (for 4.x products)

You should now see the drive in the interface, under backup devices.

NOTE: This is for reference only as we can only support the interface. Any command line instructions are done at your own risk.
address-suppressed

NetMAX can be installed on a hardware level RAID if:

1. The hardware level RAID is transparent to the OS (operating system).
2. The RAID controller appears to the OS as one of the supported SCSI cards.
3. The RAID controller shows the system drives to the OS with the standard sdX naming schemre.

Most hardware level RAID systems come with a DOS bootable floppy that you use to manage the hardware level RAID, and then you install the OS on the "system" drives that you have created.

It is probably much easier to install NetMAX on a supported SCSI adapter, install the SCSI drivers (and management software if available) for your RAID adapter, and then mount and use the RAID as additional filespace/volumes.
address-suppressed

The following messages are usually caused by an Intel Ethernet Express Pro 100 card sharing an IRQ with other devices:

eth0: card reports no RX buffers.
eth0: card reports no resources.

If you have one of these cards and this problem exists you will need to go through the BIOS to force this card to use a unique IRQ.

If you have two of these cards installed and this problem exists try replacing one of the cards with another NIC (check our compatibility list.) If this does not work make sure that this card is using unique IRQ through your BIOS. For more assistance, refer to the manual included with the network card, or to the manufacturer's website.

1. Log in to the NetMAX Interface as the administrative user.
2. In the Files Manager, navigate to the /usr/netmax/etc/rc.d directory. Click on root to begin navigating there.
3. Remove the Devs.first file by placing a check in the box, clicking on Actions, and choosing to "Delete" the file.

Answers in this category:
Why does it take so long for Windows File Sharing changes made on the NetMAX to take effect?
Why are my shareable directories (using NFS) not writeable?
The permissions and exports for removable devices are incorrect.
Can I share a hard drive that already has data on it, but not make it into a NetMAX volume?
When a user moves from one primary group into another, does the group setting on his files change automatically?
Why did I get a "Group is not committed" error when I set up a new share?
How do my Windows(CIFS) clients access the NetMAX's shares?
Can my NetMAX act as an NT PDC or an NT Member Server?
Why do my Windows users get "invalid password" errors when attempting to fileshare?
How can I share the drive on my Windows machine with Linux?

/var/mnt/System/tmp 192.168.0.1/255.255.255.128(no_root_squash)

to read:

/var/mnt/System/tmp 192.168.0.1/255.255.255.128(rw,no_root_squash)

You will also need to edit the /etc/commit.conf file so that the /etc/exports file will not be overwritten by commits issued in the NetMAX interface. You would need to add the following line to this file:

skip /etc/exports

address-suppressed

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

Applies to:  NetMAX FreeBSD Bld475
             NetMAX Linux 2.0.37 - 4.0x

This is because if the group is specified for a path, and then after that group is deleted before the commit, the path will no longer have a valid group with which to associate.
address-suppressed

All other products create a volume named "System" by default, but do not enable file sharing on the entire volume. Rather, it will create a Path in this volume named "Web", and another one named "PublicFTP" (WebServer products only) that has both Macintosh(AppleShare) and/or Windows(CIFS) filesharing enabled if the NetMAX finds that it is in a Windows workgroup and/or in an Apple Talk Zone.

For your Windows clients to access shares on a Windows Network using CIFS, they must be using TCP/IP. Your Windows clients need to have the TCP/IP protocol setup on their ethernet NIC (Network Interface Card) and have "Client for Microsoft Networks" and "File & Printer sharing for Microsoft Networks" bound to the TCP/IP protocol.

There are basically two methods for CIFS clients to find shares on a Windows network. One is the broadcast method, and the other method is by using a WINS server.

Broadcast Method

When using the broadcast method, each machine on the network that has shares, will advertise these shares on the IP network's broadcast address on UDP ports 137 and 138 approximately every 12 minutes. Although a client's shares are broadcast throughout the entire IP network, only the master browser actually uses this information. The master browser's job is to maintain the browse list of shares, and provide it to clients on the network that request it. There must be a master browser for each windows workgroup on an IP network in order for machines and shares in that workgroup to appear in the "Network Neighborhood". Windows 95, Windows 98, and Windows ME machines are only capable of acting as a master browser for their workgroup if they have file and print sharing service enabled.

If your NetMAX is running product version 3.1p2 or earlier, it is not capable of acting as the master browser for your network. This means that the NetMAX is not responsible for making shares available in your client's Network Neighborhood. You are responsible for ensuring that you make a master browser available for each workgroup on each network, in these instances if your clients need to browse the network.

Because it is possible to have CIFS (Common Internet File System) clients on the same logical network while seperating them with routers that do not pass on IP broadcasts (such as a VPN over the Internet), it is recommended that all machines in a Windows network be on the same physical network.

Although "Client for Microsoft Networks" is not enabled on most Windows machines by default. After enabling it, the broadcast method is the default browsing method that is used.

WINS Service

To allow network browsing between networks, a WINS server must be implemented. A master browser must still be set up for each workgroup for each network, but these master browsers can synchronize with a central WINS server.

You can enable your NetMAX server to act as a WINS server from Home|Sharing|Windows on the current version. Because a WINS Server must be the master browser for the workgroup that it is located in, when NetMAX is configured to be a WINS server, it also raises its OS level to force the outcome of all master browser elections in its favor. Which means that the NetMAX should force itself as the master browser for its workgroup on its network. Because of this, you should not set up NetMAX as a WINS server on the same domain that a Windows NT PDC or BDC reside in. If it is necessary to have a WINS server on these domains, it is recommended that you use the Windows NT machine as the WINS server.

When using a WINS server, there should be one, and only one WINS server, and every single machine that will partake in windows file and printer sharing should be configured to use the WINS server for NetBIOS name resolution.

The WINS server itself should not use a WINS server. Although Windows NT machines are capable of synchronizing multiple WINS servers for an even bigger Windows network, the protocols used have not been made available to the public and so your NetMAX is not capable of performing this function.

Accessing Shares on NetMAX

This section does not cover browsing. You will want to implement a method of browsing in order to use these instructions.

In order for your clients to see the NetMAX in their "Network Neighborhood", the clients must utilize the same master browser or WINS server.

To actually connect to the shares on the NetMAX, you must authenticate yourself on the network. This is done by logging into "Client for Microsoft Networks" with the same username and password as your account on the NetMAX. You can not access the NetMAX's shares without having a username and password on it. The NetMAX is not capable of authenticating against an NT PDC (acting as an NT Member Server) or acting as a PDC.

To administer your shares (create,edit,delete), you can access the file sharing menu from Home|File Sharing.

Common Issues Encountered with the CIFS Protocols

1. If your NetMAX is not acting as a WINS server, it will not partake in browser elections. This means that, unless you have another dedicated master browser for your network such as another SAMBA server or a Windows NT machine, one of your clients is likely to become the master browser. Because a lot of clients don't stay powered up, this may cause problems connecting to shares, and acquiring browse lists should the machine that was the master browser no longer be available.

2. If you have no machines that have "File and Print Sharing" enabled, you may not even have a machine acting as a master browser. If you have more than one client machine with the capability of acting as a master browser, it is possible that both machines will continue to have elections throughout the day to determine which one should act as the master browser. Because most clients running the same Windows OS will have the same OS level, it is possible for the master browser to switch throughout the day, causing delays when accessing shares becuase of the need for the clients to locate the new master browser.

3. If one client was acting as the master browser, and all the clients are turned off, if the one that was acting as the master browser is not turned on first, then the other machines will no longer know where to find the master browser. This will cause you to have to wait for elections to again be initiated and for a master browser to be determined before you will be able to browse the network.

4. If a client is acting as a master browser for a domain, it is possible that the client will not allow the other clients to resolve NetBIOS names, where as a Windows NT server, or a SAMBA server would have a guest account so that anyone on the same network would be authorized to resolve NetBIOS names. Therefore, if a client becomes the domain master browser, it may be necessary to connect to the shares via IP address instead of by NetBIOS name.

   To assist with this, you can make your NetMAX the master browser. Since it should be available more than most clients, this would be a very good idea. Although this can not be done from the NetMAX Interface for versions prior to L22Pv31p3, you can add the following lines to /var/conf/samba/smb.conf

   preferred master = yes
   os level = 65
   

   You will then want to see the article here.

   After protecting your custom changes, you will want to restart SAMBA. The easiest way to do this, may be to restart your NetMAX.

5. If your master browser is a SAMBA server or a Windows NT server, it is entirely possible for it to be acting as a router and have NICs located on more than one IP broadcast network. If this happens, it is possible for two master browsers, even though they're on different networks, to initiate an election. This will result in there not being a master browser for one of the networks. The L22Pv31p1 version of NetMAX and earlier do not let you specify which network card to run file sharing on. It is therefore not recommended to use the NetMAX as a WINS server if it is located on more than one network (possibly acting as a router). Most NetMAX FireWall implementations make the external NIC reside on their ISP's network, and there are often going to be uncontrollable parameters, including foreign NT servers, PDCs, WINS servers, and competing master browsers.

   To help with this issue, a firewall rule could be placed on the NIC that you don't wish to be the master browser on. The "Block all file sharing services" common firewall rule should be sufficient if you have at least L22Pv30.

6. Windows filesharing or browsing does not work through an IP NAT.

1. Act as master browser for a workgroup on a network (will be added).
2. Choose which NIC to run file sharing on (will be added).
3. Act as master browser and the WINS server (currently available).
4. Do not partake in browser elections (default behavior of NetMAX currently).
5. Utilize a WINS server (currently available).
6. Specify WINS server configuration to clients with DHCP server (current status unknown).

IMPORTANT NOTE:The /var/log/log.nmb log file will prove to be invaluable at assisting you to diagnose your Windows Network browsing issues. This article does not attempt to cover Active Domain Controllers.

However, this may not limit you, if you have the knowledge to configure Linux and samba to enable this functionality without using the NetMAX Interface.

We recommend going to Samba's website at http://www.samba.org for additional information on configuring samba.
address-suppressed

The user name and password must be the same on both the Windows machine and the NetMAX machine
to access the NetMAX from a Windows machine's Network Neighborhood.

NOTE: Another possible cause for this message is that the Windows machine may not be
encrypting passwords by default.

Experienced system administrators can try the following tasks to fix this situation.

Note, however, that modifications to the System Registry can cause Windows machines
to become inoperable if a mistake is made.

Anyone not familiar with editing the Windows Registry should not edit the Registry.

If you aren't scared off yet, do the following:

To verify this setting, access Start->Run on the Windows machine.
Enter regedit in the dialog box and press Enter.

For Win95 or Win98:

    Access HKEY_LOCAL_MACHINE->System->CurrentControlSet->Services->VxD->VNETSUP
    in the left pane.

   Create a "dword" in the right pane called "Enable PlainTextPassword".

   Assign a value of "0" to the "EnablePlainTextPassword" key.

Close regedit and reboot the Windows machine.

For Windows 2000

Access HKEY_LOCAL_MACHINE->SYSTEM->CurrentControlSet->Services->LanmanWorkStation->Parameters
in the left pane.

   Create a "dword" in the right pane called "Enable PlainTextPassword".