Accessing the server and shares

• Can't start server

• Can't access server

• Invalid file format when starting Profile Editor

• Can't start the Profile Editor

• PC access to VisionFS

• Server not in any workgroup

• Account not authorized to log in

• Not browsable means not active in Windows 95

• Problems reconnecting at logon on Windows NT 4

• Access Denied dialog or no share listings

• Find Computer fails

• Restarting server can cause errors

Can't start server

If you encounter one of the following errors when starting VisionFS, this indicates a NetBIOS port conflict:

   Another program is using TCP port 139.
   Another program is using UDP port 138.
   Another program is using UDP port 137.
   A socket is still in use, attempting 30 retries........................
   session/bindfailed
   Failed to bind to socket address *:139: bind(4,*:139): (125) Address
   already in use
   Failed to open UDP port 137: bind(5,132.147.209.37:137): (125) Address
   already in use
   The server won't run unless this address/port combination is available.

The most likely problem is that SCO Advanced File and Print Server is running over NetBIOS on the UNIX server.

To allow VisionFS to start, you must stop NetBIOS, as well as rename the NetBIOS startup script to prevent it from being run automatically when the system reboots.

Log in as root on the UNIX server and enter the following commands:

net stop server
/etc/netbios stop
cd /etc/rc2.d
mv S74netbios s74netbios

Now you should be able to start VisionFS.

If SCO NetBIOS over TCP/IP isn't running, but there's still a NetBIOS port conflict, see ``Other file and printer sharing programs or NBT applications''.

Can't access server

Verify that VisionFS is installed and running on the UNIX server:

1. Log in as root on the UNIX server.

2. Use the status option of the visionfs(1M) command.

If VisionFS is not installed, see ``Setting up''.

If VisionFS is installed, but the server is not running, use the visionfs start command to start VisionFS.

If VisionFS is installed and the server is running, but the Windows client cannot see the server, see ``PC access to VisionFS''.

Invalid file format when starting Profile Editor

On Windows 95 or Windows NT 4, if the Profile Editor gives an error ``Invalid file format'' and doesn't start, another program might have installed an old version of the file vsvbx.vbx in the PC's Windows system directory. This file is used instead of the Profile Editor's own version of vsvbx.vbx, stored in the same folder as profedit.exe.

To run the Profile Editor, first map a drive to the visiontools share on the server.

Can't start the Profile Editor

If you can't start the VisionFS server or Profile Editor, the profile might be corrupt, or a VisionFS Administrator might have accidentally changed some settings that mean you are no longer allowed to access the Profile Editor.

To fix a profile, use the setup option of the visionfs(1M) command.

PC access to VisionFS

To access a VisionFS server, Windows needs to use standard networking software, the same as it can use to access other Windows PCs on the network.

Windows for Workgroups requirements

• Support for Microsoft Windows Networks. To check, open Windows Setup, click Change Network Settings on the Options menu, and click Networks.

• Microsoft TCP/IP. See ``Installing Microsoft TCP/IP''.

Windows 95 requirements

• Client for Microsoft Networks. To check, open Windows Control Panel, double-click Network, and look in the list under The Following Network Components are Installed.

• TCP/IP. See ``Installing Microsoft TCP/IP''.

Windows NT requirements

• NetBIOS Interface and Workstation services. To check, open Windows Control Panel, and double-click Network. On Windows NT 3.51, look in the Installed Network Software list. On Windows NT 4, look in the list on the Services tab.

• TCP/IP Protocol. See ``Installing Microsoft TCP/IP''.

Installing Microsoft TCP/IP

To access a VisionFS server, PCs must use TCP/IP as one of their transport protocols.

• For Windows 95 and NT, a TCP/IP protocol stack is provided with the operating system.

• For Windows for Workgroups, you can install the protocol stack provided on the Microsoft web site, www.microsoft.com.

To install Microsoft TCP/IP on Windows 95

1. Open Windows Control Panel and double-click Network.

2. Click Add. Click Protocol, and then click Add.

3. In the Manufacturers list, click Microsoft. In the Network Protocols list, click TCP/IP. Click OK to return to the Configuration tab.

4. In the network components list, click TCP/IP and then click Properties.

5. Fill in the required details in the Properties dialog box.

To install Microsoft TCP/IP on Windows NT 4

1. Open Windows Control Panel, double-click Network, and then click the Protocols tab. The dialog box shows the installed protocols.

2. Click Add.

3. In the Network Protocols list, click TCP/IP Protocol, and then click OK.

4. Windows NT Setup displays a message asking if you want to use DHCP to dynamically provide an IP address. If DHCP is in use at your site, click Yes, and you can ignore step 7 in these instructions. Otherwise, click No.

5. Windows NT Setup displays a message asking for the full path to the Windows NT distribution files. Provide the appropriate location, and click Continue. All necessary files are copied to your hard disk.

6. Click Close.

7. Fill in the required details in the Microsoft TCP/IP Properties dialog box.

To install Microsoft TCP/IP on Windows NT 3.51

1. Start Control Panel from the Main group in Program Manager.

2. Double-click the Network icon.

3. Click Add Software. In the Network Software list, click TCP/IP Protocol And Related Components, and then click Continue.

4. Check the options for the TCP/IP components you want to install.

5. Windows NT Setup displays a message asking for the full path to the Windows NT distribution files. Provide the appropriate location, and click Continue. All necessary files are copied to your hard disk.

6. In the Installed Network Software list, click TCP/IP Protocol and then click Configure.

7. Fill in the required details in the TCP/IP Configuration dialog box.

To install Microsoft TCP/IP on Windows for Workgroups

1. In Program Manager, open the Network group, and double-click Network Setup.

2. Click Drivers.

3. Click Add Protocol.

4. Click Unlisted or Updated Protocol, then click OK.

5. Type the path to the directory containing Microsoft TCP/IP. Then click OK.

6. Click OK. The files are copied to the PC's disk.

7. Click Microsoft TCP/IP-32 3.11b, and click Setup.

8. Fill in the required details in the Microsoft TCP/IP Configuration dialog box.

Server not in any workgroup

If the VisionFS server doesn't appear in any workgroup, the Windows or UNIX network settings might be wrong.

Check that the subnet mask is the same on the Windows clients and the UNIX server. See ``Checking your PC and UNIX broadcast addresses''.

For now, type \\server\share explicitly rather than browse the network.

Checking your PC and UNIX broadcast addresses

VisionFS uses NetBIOS naming, which broadcasts names using the UNIX server's broadcast address. It's important that this broadcast address is correct, or the VisionFS server won't appear in workgroups.

On your UNIX server, you can use the visionfs netinfo command to display information about the network interfaces. This command will tell you if your UNIX server seems to be using an incorrect broadcast address or subnet mask.

Windows works out the broadcast address based on the subnet mask. Most sites use a Class C subnet mask even if they have a Class B network. However, Windows defaults the subnet mask based on the class of network. This means you might need to change subnet masks of 255.255.0.0 (Class B network) to 255.255.255.0 (Class C network).

The UNIX server and your PCs must use the same broadcast address. Some flavors of UNIX (for example, SunOS) use the wrong broadcast address by default. See the ifconfig(1Mtcp) manual page to find out how to set broadcast addresses and subnet masks.

Account not authorized to log in

Windows NT 4.0 Service Pack 3 by default doesn't allow the use of unencrypted passwords. This results in an error message ``The account is not authorized to log in from this station'' when a user tries to access a VisionFS server that is using unencrypted passwords.

To fix the problem, either stop using unencrypted passwords to authenticate users, or do the following:

1. On Windows NT, run Registry Editor.

2. From the HKEY_LOCAL_MACHINE subtree, go to the following key:
   
   \system\currentcontrolset\services\rdr\parameters

3. Click Add Value on the Edit menu and add the following:
   
   Value Name: EnablePlainTextPassword
   Data Type: REG_DWORD
   Data: 1

4. Click OK, quit Registry Editor, then shut down and restart Windows NT.

Not browsable means not active in Windows 95

In Windows 95 Explorer, if you configure a share to be not browsable, using the box on the General tab of the share's properties, then it is also not active -- Windows won't let you connect to the share, even if you know its name. This is a problem with Windows 95.

However, you can access the share from DOS, for example by mapping a drive. Windows Explorer on Windows NT 4 does not have this problem.

Problems reconnecting at logon on Windows NT 4

If you're having problems with the Reconnect at Logon box on Windows NT 4 in domains, you should switch to VisionFS (encrypted) passwords, or use another VisionFS server (in VisionFS password mode) or Windows NT server for authentication, and use the same passwords for Windows and VisionFS.

Access Denied dialog or no share listings

When you click a VisionFS server in the Connect Network Drive dialog of File Manager or Print Manager, Windows might display an Access Denied dialog or not list the resources on the server.

On Windows for Workgroups, this is because Windows has tried to authenticate you on the VisionFS server using your Windows password, and this has failed because your Windows password is different from your password for accessing the VisionFS server.

On Windows NT 3.51, the cause is one of the following:

• VisionFS is using UNIX (unencrypted) passwords, and Windows has not tried to authenticate you.

• Your Windows password and your password for accessing this VisionFS server are different.

Both versions of Windows have generated an error rather than prompt you for the correct password. This is a Windows problem.

To connect a network drive, type the server and share names in the Path box, in the form \\server\share.

To connect a network printer, first connect a network drive using the above solution. You can disconnect the drive afterwards.

Find Computer fails

In Windows 95 and NT 4, you can click Find Computer on the Start menu to locate computers on the network.

On Windows 95, this can sometimes fail to locate a VisionFS server. This happens if you haven't connected to the VisionFS server in that Windows session, and Windows hasn't cached your password for the VisionFS server, and your Windows password is different from your password for accessing the VisionFS server.

Windows NT 4 successfully locates VisionFS servers in Find Computer.

In Windows 95, clicking Run on the Start menu and typing \\server works more reliably than searching for a computer named server in the Find Computer dialog.

Restarting server can cause errors

Restarting the VisionFS server can cause problems for users because some Windows programs can't cope if the server restarts while they are using it, and will display error dialogs.

This typically affects programs accessing the server heavily, such as Setup programs. Don't restart the server while a user is running a Setup program. Use the Profile Editor to see who's connected to a server before restarting it.

Database programs normally require you to re-open the database.