Virtual CD Server - Axonix

Known Conflicts

Banyan Vines
The Virtual CD Server can operate in a multi-protocol network in conjunction with Banyan Vines. The Virtual CD Server must be accessed using one of three protocols: SMB/TCP-IP, NCP/IPX or HTTP/TCP-IP. It is possible to add the Virtual CD Server to a Banyan Vines network that has no file server. A network client utility (embedded in Windows95) must be active on each workstation. The Virtual CD Server will then emulate either a Novell or NT server.

Novell
If the Client for NetWare Networks is loaded in a server-less environment, the Virtual CD Server will appear in Network Neighborhood as a Novell 3.12 server with the server name of Vision_xxxxx_NW. The bindery of the Virtual CD Server is used to create users and define user rights.

NT
If the Client for Microsoft Networks is loaded in a server-less environment, the Virtual CD Server will appear in Network Neighborhood as an NT server with the server name of Vision_xxxxx. A static IP address must be established for each workstation and the Virtual CD Server. The Domain name of the server must be changed to match the workgroup name. The bindery of the Virtual CD Server is used to create users and define user rights.

In rare occasions the server does not automatically appear in Network Neighborhood. If this happens select the Find Computer option from the Windows Start menu. Enter the Virtual CD Server name and click Find Now. After the server is located it will also appear in Network Neighborhood.

Microtest DiscPort
The latest version of Microtest DiscView management software (v5.51a) is the only Y2K compliant DiscView release. This version of the software conflicts with the Virtual CD Server by calling out to all servers to discover which server has the DiscPort NLMs/drivers loaded. The software cannot discover if the Virtual CD Server, which can emulate both Novell and NT servers, contains these elements. This causes the DiscView software to hang, and may corrupt the DiscPort CDROMS volume.

Novell Environment Solution
The Virtual CD Server can be modified to emulate an NT server, not a Novell server. The DiscView software is then modified to search only for Novell servers; bypassing the Virtual CD Server.

The Virtual CD Server must be running software version 4.10c (or higher). A mini network of just the Virtual CD Server and one PC workstation must be created to allow for the initial modifications. This may be done using a crossover cable or by attaching both devices to a hub with no other connections.

1. Boot the Virtual CD Server and the workstation. Make sure that the TCP/IP protocol stack is loaded on the workstation, a static IP address is provided for the workstation, and that the Client for Microsoft Networks is also loaded. This does not need to be the Primary Network Login, but must be loaded. At this time please note the workgroup name of the workstation.
2. Load the CDVision Administrator utility onto the workstation.
3. Set the IP Address for the Virtual CD Server.
4. Disable the Novell NCP Protocol of the Virtual CD Server.
   1. Open Network Neighborhood.
   2. Open the Virtual CD Server.
   3. Open the Admin folder.
   4. Open the server.ini file. If no extensions are displayed in the window the .ini file icon looks like a notepad with a yellow gear on it.
   5. Scroll down to the [Server] section of the file.
   6. Edit the NCPProtocolActive line to read NCPProtocolActive=No
   7. Scroll down to the [Protocol] section of the file.
   8. Delete the line referencing the NCP protocol. This should be the second protocol listed.
   9. Edit the third line to reflect its new status as the second protocol. The finished section should look like this:

      Protocol1=smb.dll,SMB Protocol
      Protocol2=http.dll,HTTP Protocol

   10. Save and close the server.ini file. The NetWare NCP Protocol has just been disabled.
5. Reboot the Virtual CD Server. It is now accessible only as an NT server.

On the workstation that had the DiscView management utility loaded there is an .ini file that the program uses to determine what type of servers to poll when searching for NLMs. To exclude NT servers from this polling apply the following steps.

1. Open the C:\WINDOWS directory.
2. Open the discview.ini file.
3. Scroll to the [State] section.
4. Edit the DiscoverSystems line to read DiscoverSystems=2
5. Save and close the file.

After both systems have been modified the Virtual CD Server may be attached to the full Novell network.

1. Each workstation must have the TCP/IP protocol stack loaded and a static IP address.
2. If the Virtual CD Server is not visible in Network Neighborhood, it may be necessary to use the Find Computer function to discover the system, and then map to the Virtual volume.
3. The administrator's workstation must have the CDVision Tools utility loaded. To reduce the amount of time spent searching for the Virtual CD Server edit the cdcmdr.ini file.
   1. Open the Windows Explorer.
   2. Open the C:\WINDOWS directory.
   3. Open the cdcmdr.ini file.
   4. Edit the file to look like the following example, replacing the Vision_xxxxx with the name of your Virtual CD Server

      [Init]
      AutoSearchServers=0
      [SMB SERVERS]
      Server1=VISION_xxxxx

NT Environment Solution
If the DiscPort is used in an NT environment, the Virtual CD Server must be forced to emulate a Novell server only. Follow the steps above, with the following alterations:

1. The workstations must be loading the Microsoft Client for Novell Networks, and the IPX/SPX protocol stack.
2. The Virtual CD Server server.ini file will be modified to disable the SMB protocol (Microsoft network protocol). Leave the NCP (Novell network protocol) active. The Virtual CD Server does not need to have an IP address.
3. The discview.ini file is modified to search only for NT servers, excluding the Virtual CD Server, by setting DiscoverSystems=1
4. If the cdcmdr.ini file is modified, the heading for the list of Virtual CD Servers is [NCP SERVERS]