PC NetLink 1.1 Issues

The known issues with PC NetLink are listed in the following section.

PC NetLink is also referred to as SunLink Server.

Windows NT 4.0 with Solstice Network Client 3.x Causes A PC NetLink NT Printer Share to Fail

Windows NT 4.0 with Solstice Network Client 3.x causes a PC NetLink NT Printer Share to fail and displays the following error message: Printer driver for Windows NT 4.0 x86 could not be installed. This function is only valid in Windows NT mode.

Workaround: Share PC NetLink printers from an NT 4.0 system that does not have Solstice Network Client 3.x (SNC) installed on it. The SNC 3.x NT systems will be able to see the Printer shares and install the printer locally without difficulty.

To check the presence of SNC 3.x on an NT 4.0 system, open Services in the Network dialog box in the Control panel. If Network Services lists "Solstice NFS Client" and/or "Solstice File Sharing" entries, then SNC 3.x is installed on that system. If necessary, remove SNC 3.x through the Add/Remove Programs() function in the Control Panel.

SunLink Server Manager Will Not Use A Secondary WINS Server if the Primary WINS Server is Still Functioning

Unlike a native Windows NT environment, the SunLink Server program will not use a secondary WINS server if the primary WINS server is still functioning. If a SunLink Server computer is functioning as the primary WINS server, and attempts to locate a resource that does not exist in its WINS database, the SunLink Server NetBIOS will not automatically consult the secondary WINS server for that resource. In this regard, a SunLink Server computer configured as a primary WINS server does not behave in the same way as a native Window NT primary WINS server.

Workaround: This issue will not become a problem for most environments. To preclude this from becoming a problem, either point all servers that need to communicate with each other to the same primary and secondary WINS servers, or replicate all WINS servers.

The passwd2sam -m Used on a BDC Causes Problems

When used on a BDC, the passwd2sam -m option may:

• Give programming type error messages.

• Create users' directories without permissions.

• Create users' directories in uppercase.

These problems do not occur when the command is used on a PDC.

Workaround: Do not use the passwd2sam -m on a BDC.

Using SunLink Server Software and Microsoft Terminal Server Together Causes Synchronization Problems

If SunLink Server software and Microsoft Terminal Server are used together in a domain, domain synchronization problems will occur. When both these tools are used in a domain, user's Terminal Server configuration parameters will not be synchronized.

Workaround: Install SunLink Server software in a separate "resource" domain that trusts another "account" domain.

Auto-mounted Solaris Home Directories Are Not Always Automatically Available to Windows NT Clients

The following description and workaround is intended for experienced Solaris system administrators only.

Solaris home directories that are stored remotely are ordinarily mounted automatically when users need to access their accounts. The current release of SunLink Server is not able to provide automatic access from Windows NT clients to Solaris home directories that are not stored on the SunLink Server system. However, home directories that are stored on the same system as the SunLink Server program are available to Windows NT clients.

The reason for this is that the autofs file system monitors all attempts to access directories, and if the file system is not accessed within a default period of five minutes, the file system becomes unmounted. Therefore, if a net share operation is performed on /home and then the share is connected from the client, the access to the home directory will be unmounted. This is because the autofs daemon does not detect that the user is accessing the directory from the Windows client system.

Workaround: Change the auto-mount master map entry for /home from --nobrowse to --browse so that SunLink Server can see the subdirectories of /home.

PC NetLink Must be Installed in English Locale

When installing PC NetLink on a system running the Solaris operating environment in a European language, the graphical interface of PC NetLink will appear in the corresponding language, but none of its functionality will be available.

Workaround: Before using PC Netlink, open a terminal window and set the locale to English. Then start the graphical interface of PC NetLink from the terminal window.