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.