Choose your language
Back to startpage






Fusion95 Frequently Asked Questions (FAQ)

Last updated: 8 December 2010


Contents

  1. Windows 7
  2. Windows VISTA
  3. Windows XP
  4. Windows 2000 and Windows ME
  5. Wide Area Networks
  6. Password Encryption
  7. Adding additional UNIX Printer Clients
  8. File name upper, lower or mixed case
  9. Tuning SCO OpenServer 5 for large Fusion95 systems
  10. Windows 2000 8.3 filenames.
  11. Basic Problem Determination Guide
  12. PCserve - file & printer server - problem determination and reporting
  13. F95ADMIN - problem determination and reporting
  14. Smbprtup - printer client - problem determination and reporting


Windows 7

NOTE! Windows 7 clients are currently not supported.
Problem: Loading .EXE programs from a Fusion95 mapped drive does currently not work.

In order to connect Windows 7 clients, you must change the default authentication level to work as in XP:

Windows 7 Pro and higher:
Click 'Start button (lower left corner)'
in the "Search programs and files" input field, type 'secpol.msc'
Select
 -Local policies
  -Security Options
   Network Security:
    Lan Manager Authentication Level: "Send LM and NTLM - use NTLMv2-session security if negotiated"
   Click OK.


Windows 7 Home:
The Home edition of Windows 7 does not have the 'secpol.msc'. Edit the registry using 'regedit' as follows: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\LMCompatibilityLevel
If it doesn't already exist, create a DWORD value named
LmCompatibilityLevel
Set the value to 1

Send LM & NTLM - use NTLMv2 session security if negotiated: Clients use LM and NTLM authentication and use NTLMv2 session security if the server supports it; domain controllers accept LM, NTLM, and NTLMv2 authentication. The reson for this registry change is that Microsoft decided to change the default authentication protocol in later versions of Microsoft Windows Operating system.


Windows VISTA

In order to run Windows VISTA clients, you must change the default authentication level to work as in XP:
Click 'Run'
type 'secpol.msc'
Select
 -Local policies
  -Security Options
   Network Security:
    "Send LM and NTLM - use NTLMv2-session security if negotiated"
   Click OK.


Windows XP

In order to run Windows XP clients, you must be running Fusion95 version 6.


Windows 2000 and Windows ME

In order to run Windows 2000 or Windows ME clients, you must be running version 5.04 or later of Fusion95.


Wide Area Networks

Fusion95 can be used in a Wide Area Network, Internet or Intranet environment. The WAN can be private and/or public and consist of any type of link from low-speed dial-up to high-speed leased lines.

The main difference between accessing Fusion95 on a WAN compared to a LAN is the address resolution scheme. In order to access a server via TCP/IP the client needs to be able to resolve the server name into a TCP/IP address.

On a LAN, a broadcast is sent to the NetBIOS name server to resolve a server name to an IP address. This is transparent; it doesn't need to be configured. On a WAN, the broadcast packets are not routed and therefore another method must be used.

To the top

Wide Area Networks - Accessing a remote Fusion95 server

Methods to resolve addresses on a WAN depend upon the client software, the following are available in Windows95:

  1. Read the local LMHOSTS file.
  2. Read a remote LMHOSTS file on a central server.
  3. Ask a Windows Name Server (WINS).
  4. Ask a Domain Name Server (DNS).

Note that this section has nothing "specifically" to do with Fusion95; exactly the same rules would apply even if you were connecting to a Windows server.

Use a local LMHOSTS file

The following LMHOSTS file could be used in a client PC to resolve the addresses for a number of remote servers:

  192.0.0.1 RS6000 #PRE
  192.0.0.10 POWERPC #PRE
  192.0.1.11 M88K #PRE
  192.0.1.12 APRIL #PRE

Note that on some clients (e.g. NT) you can specifically enable/disable LMHOSTS look-ups using the TCP/IP properties settings.

Use a remote LMHOSTS file

Putting the LMHOSTS file onto a server rather than onto every client, greatly reduces maintenance time. The following LMHOSTS file could be used in a client PC to point to an LMHOSTS on a remote server to be used to resolve addresses:

  192.0.0.1 RS6000 #PRE
  #INCLUDE \\RS6000\DISK\LMHOSTS

Using the above LMHOSTS file would introduce a single-point-of-failure into your WAN. If the server RS6000 was not operational then it would not be possible for the client PC's to access the WAN; even if the server they wanted to access was operational. In order to provide redundancy, alternate servers can be specified. In the following example, if server RS6000 was not available then the alternate server APRIL would be used to resolve the addresses.

  192.0.0.1 RS6000 #PRE
  192.0.1.12 APRIL #PRE
  #BEGIN_ALTERNATE
  #INCLUDE \\RS6000\DISK\LMHOSTS
  #INCLUDE \\APRIL\DISK\LMHOSTS
  #END_ALTERNATE

Use a WINS

A WINS can be used to resolve addresses. Care must be taken to have multiple WINS so as to not  introduce a single-point-of-failure into your WAN. WINS will only run in a Windows NT server. WINS is only available to Windows95 and Windows NT clients as standard; an upgraded redirector (VREDIR.386) for WfW is available on the Windows NT server CD-ROM.

Use a DNS

A DNS can be used to resolve addresses. Care must be taken to have multiple DNS so as to not  introduce a single-point-of-failure into your WAN. DNS will run in a wide range of machines including Windows, UNIX and AIX.

Use a mixture of the above

It is not necessary to just use one of the methods above; they can be used in combination. For example if all methods are implemented, a Windows NT workstation will resolve names in the following order:

  1. NetBIOS name cache.
  2. Windows Name Server (WINS).
  3. LAN Broadcast.
  4. LMHOSTS file.
  5. HOST file.
  6. Domain Name Server (DNS).

Testing name resolution

The Windows nbtstat command can be used to test name resolution. It can be run twice, first with the -A option and then with the -a option. Both commands should give the same result. If the first command works, but the second doesn't, then name resolution in the Windows PC has not been correctly configured. The following command will obtain the adapter status from the node with the IP address specified...

  NBTSTAT -A 192.0.0.1

Using the -a option together with the server's node name will cause Windows to resolve the name to an IP address and then obtain the adapter status from that node...

  NBTSTAT -a RS6000

Note: the options are case sensitive.

Use the IP address instead of the server's name

In Windows98 and later versions of Windows95 and NT it is possible to specify the IP address instead of the node name when you map a drive. This bypasses the whole name resolution mechanism. Thus...

  NET USE U: \\192.0.0.1\ACCOUNTS

can be used instead of...

  NET USE U: \\RS6000\ACCOUNTS To the top

Wide Area Networks - Printing from Fusion95 to a remote printer

The Fusion95 printer client will first use broadcasts to obtain the IP address of the printer server. If Fusion95 and the printer server do not reside on the same broadcast network (e.g. separated by a WAN), then Fusion95 will not be able to find the printer server using this method. The Fusion95 printer client will then search the DNS and/or the /etc/hosts file to attempt to find a matching name, even checking for all upper or all lower case.

In order to print to a remote printer from the Fusion95 printer client you should add the printer server's name and IP address to the /etc/host file on you Fusion95 UNIX machine or configure the DNS used by UNIX to provide the IP address of the remote printer server.

The "Printer on local LAN" configuration option for the printer client is normally set to yes. It should be set to no if the printer is on a node outside of the current broadcast network (i.e. accessed via a router but not if accessed via a bridge). In this case Fusion95 will not attempt to broadcast to locate the printer but instead go directly to the DNS and/or the /etc/hosts file. This will remove an overhead of 10 seconds.

To the top

Wide Area Networks - Configuring ports in a firewall router

If your WAN uses a firewall or router that restricts certain TCP and UDP sockets then you have to make sure that you open the ports required by Microsoft Networking so that a PC client can access the Server.

For Microsoft Networking you should open ports 137, 138 and 139 for both TCP and UDP. These are often defined as follows:

netbios-ns  137/tcp # NETBIOS Name Service
netbios-ns  137/udp # NETBIOS Name Service
netbios-dgm 138/tcp # NETBIOS Datagram Service
netbios-dgm 138/udp # NETBIOS Datagram Service
netbios-ssn 139/tcp # NETBIOS Session Service
netbios-ssn 139/udp # NETBIOS Session Service

Note that this section has nothing "specifically" to do with Fusion95; exactly the same rules would apply even if you were connecting to a Windows server.

To the top

Password Encryption

Fusion95 version 4 supports Windows password encryption over the LAN.

The following Microsoft clients have a default configuration that requires the server to support encrypted passwords over the LAN.

Fusion95 version 3 does not support Windows password encryption (it only supports UNIX password encryption) and thus requires plain text passwords to be enabled in these Windows platforms. The next three sections describe how to enable plain text passwords in each of these clients.

Fusion95 version 4 does support Windows password encryption, and thus it is not normally necessary to enable plain text passwords in the above clients. However it may still be desirable to enable plain text passwords if Unix-Level security and UNIX password encryption (by setting secmode=1 in the pcserve.ini file) is to be used instead of Windows password encryption. A better solution is to change to User-Level security (by setting secmode=3 in the pcserve.ini file) and use Fusion95's User Database rather than the /etc/passwd file in which case Windows password encryption is supported.

To the top

Password Encryption - Windows NT 4.0 with SP3

Note: this is not normally required for Fusion95 version 4. It is however required for Fusion95 version 3.

Connecting to SMB/CIFS servers (such as Fusion95 and LAN Manager for UNIX) with a plain text password fails after upgrading to Windows NT 4.0 Service Pack 3.

This is because the SMB redirector in Service Pack 3 handles passwords differently than previous versions of Windows NT. Beginning with Service Pack 3, the SMB redirector will not send a plain text password unless you add a registry entry to enable unencrypted passwords.

This applies to both NT Server and NT Workstation.

This will cause an error such as:
SYSTEM ERROR 1240: The account is not authorized to logon from this station

Resolution

To enable plain text passwords, modify the registry in the following way:

WARNING: Make sure you know how to run the registry editor correctly. Using it incorrectly can cause serious problems.

  1. Run Registry Editor (REGEDT32.EXE).
  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.
  4. Add the following:
    Value Name: EnablePlainTextPassword
    Data Type: REG_DWORD
    Data: 1
  5. Click OK and then quit Registry Editor.
  6. Shut down and restart Windows.

More Information

For more information see the Microsoft Knowledge Base article: Q166730.

For more information about Window NT, Service Pack 3 and The Registry see the relevant Microsoft documentation.

To the top

Password Encryption - Windows95 with VREDIR update (VRDRUPD.EXE)

Note: this is not normally required for Fusion95 version 4. It is however required for Fusion95 version 3.

Connecting to SMB/CIFS servers (such as Fusion95 and LAN Manager for UNIX) with a plain text password fails after upgrading Windows95 with Microsoft's VRDRUPD.EXE update.

This is because the new SMB redirector handles passwords differently. With this update, the SMB redirector will not send a plain text password unless you add a registry entry to enable unencrypted passwords.

Resolution

To enable plain text passwords, modify the registry in the following way:

WARNING: Make sure you know how to run the registry editor correctly. Using it incorrectly can cause serious problems.

  1. Run Registry Editor (REGEDIT.EXE).
  2. From the HKEY_LOCAL_MACHINE subtree, go to the following key:
    /HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/VxD/VNETSUP
  3. From the Edit menu, select:
    New - DWORD
  4. Rename the entry to:
    EnablePlainTextPassword
  5. Set its value to:
    1
  6. Click OK and then quit Registry Editor.
  7. Shut down and restart Windows.
To the top

Password Encryption - Windows98

Note: this is not normally required for Fusion95 version 4. It is however required for Fusion95 version 3.

Connecting to SMB/CIFS servers (such as Fusion95 and LAN Manager for UNIX) with a plain text password fails from Windows98.

This is because the SMB redirector, by default, requires passwords to be encrypted. With this version of Windows, the SMB redirector will not send a plain text password unless you add a registry entry to enable unencrypted passwords.

Resolution

To enable plain text passwords, modify the registry in the following way:

WARNING: Make sure you know how to run the registry editor correctly. Using it incorrectly can cause serious problems.

  1. Run Registry Editor (REGEDIT.EXE).
  2. From the HKEY_LOCAL_MACHINE subtree, go to the following key:
    /HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/VxD/VNETSUP
  3. From the Edit menu, select:
    New - DWORD
  4. Rename the entry to:
    EnablePlainTextPassword
  5. Set its value to:
    1
  6. Click OK and then quit Registry Editor.
  7. Shut down and restart Windows.
To the top

Password Encryption - Windows 2000

Note: this is not normally required for Fusion95 version 4, and running Windows 2000 clients with earlier versions of Fusion95 is not recommended

Connecting to SMB/CIFS servers (such as Fusion95 and LAN Manager for UNIX) with a plain text password fails from Windows 2000.

This is because the SMB redirector, by default, requires passwords to be encrypted. With this version of Windows, the SMB redirector will not send a plain text password unless you add a registry entry to enable unencrypted passwords.

Resolution

To enable plain text passwords, modify the registry in the following way:

WARNING: Make sure you know how to run the registry editor correctly. Using it incorrectly can cause serious problems.

1. Run Registry Editor (REGEDIT.EXE).
2. From the HKEY_LOCAL_MACHINE subtree, go to the following key:
/HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/LanmanWorkStation/Parameters
3. From the Edit menu, select:
New - DWORD
4. Rename the entry to:
EnablePlainTextPassword
5. Set its value to:
1
6. Click OK and then quit Registry Editor.
7. Shut down and restart Windows.

To the top

Adding additional UNIX Printer Clients

When Fusion95 is installed it will automatically configure 8 printer clients called lprt00 through lprt07. The following procedure can be used to configure additional printer clients lprt08 and upwards.

Start-up Script

The start-up script (/usr/fusion95/f95start) must be modified to start the correct number of printer daemons. Change one line of the script as follows:

SMBP=0
while [ $SMBP != 8 ]
do

The while loop is processed once for each printer. Change the number to the new number of printer clients to be supported:

SMBP=0
while [ $SMBP != 9 ]
do

This will now loop and create 9 printer clients.

Create an lp model

An 'lp' model must be created for each printer. This should be created in the /usr/fusion95 catalog by copying the script for lprt00.

# cd /usr/fusion95
# cp lprt00 lprt08

Create an lp printer

An 'lp' entry must be created for each printer. This is platform dependant.

AIX 4 and AIX 3.2.5

# mkque -qlprt08 -a"up = TRUE"
# mkquedev -qlprt08 -dlprt08 -a"file = FALSE" -a"backend =/bin/sh /usr/fusion95/lprt08"

SCO Open Server 5 and SCO 3.2 and M88K 3.2

# /usr/lib/lpadmin -plprt08 -mfusion95 -D"Fusion95 SMB printer client 08" -onobanner -v/dev/null -h
# enable lprt08
# accept lprt08

SCO Unixware 7

Note that while not required, the lpadmin -A option might be useful (e.g. -A mail). This controls Alerts when printing problems occur. See the Unixware lpadmin(1M) manual page for more details.

# mknod /dev/lprt08 p
# /usr/sbin/lpadmin -plprt08 -mstandard -D"Fusion95 SMB printer client 08" -onobanner -o"stty='clocal -onlcr'" -v/dev/lprt08
# /usr/bin/enable lprt08
# /usr/lib/accept lprt08
# rm /dev/lprt08

Generic UNIX System V Release 4

# /usr/sbin/lpadmin -plprt08 -mfusion95 -D"Fusion95 SMB printer client 08" -onobanner -v/dev/null -h
# enable lprt08
# accept lprt08

Digital UNIX (DEC OSF/1)

# mkdir /usr/spool/lpd/lprt08
# echo "lprt08|LPRT08| :\
:af=/usr/adm/lpacct:\
:lf=/usr/adm/lperr:\
:lp=/dev/null:\
:mx#0:\
:if=/usr/fusion95/lprt08:\
:pl#66:\
:pw#80:\
:sd=/usr/spool/lpd/lprt08:\
:xf=/usr/lbin/xf:" >> /etc/printcap

Data General UNIX

# /usr/sbin/lpadmin -plprt08 -mstandard -D"Fusion95 SMB printer client 08" -onobanner -v/dev/lprt08 -h
# enable lprt08
# accept lprt08

HP-UX 10

# /usr/lib/lpshut
# touch /dev/lprt08
# /usr/lib/lpadmin -plprt08 -mdumb -v/dev/lprt08 -h
# /usr/bin/enable lprt08
# /usr/lib/accept lprt08
# rm /dev/lprt08
# /usr/lib/lpsched -v

HP-UX 9

# /usr/lib/lpshut
# /usr/lib/lpadmin -plprt08 -mfusion95 -v/dev/null -h
# /usr/bin/enable lprt08
# /usr/lib/accept lprt08
# /usr/lib/lpsched -v

To the top

File name upper, lower or mixed case

Windows 32 - CIFS protocol

When using the CIFS protocol, usually on Windows 95, 98, NT 4, 2000 & later workstations, the following applies:

Unlike, UNIX, the Windows operating system does not support multiple files in the same directory with the same file name but in different cases. For example FILENAME.TXT, filename.txt and FileName.Txt would be allowed in the same directory on a UNIX machine but not in a Windows machine. To avoid confusing Windows clients, you should not have multiple files with the same name in UNIX directories shared using Fusion95.

File Open / Search
File opens or searches from Windows 32 clients are not case sensitive. Fusion95 will search the directory for the first file with the requested name, regardless of case, and open that file for the Windows machine.

File Create
The action performed by Windows 32 file creates, depends on the setting on the filename= parameter in the pcserve.ini file.

Setting filename=3 causes file to be created with the name specified at open time - allowing upper or lower or mixed case file names.

Setting filename=15 causes file names to be created in the case specified when the disk is shared (by pcconfig or f95admin) - either all upper or all lower.

The default value in Fusion95 version 5 is filename=3. To be compatible with older versions of Fusion95 and force the case to either all lower or all upper you might want to change to filename=15 in the pcserve.ini file.

Windows 16 - SMB protocol

When using the SMB protocol, usually on old Windows 3.1 workstations, the following applies:

File names can be either in all upper case or all lower case. The case of the file names is determined when the disk is shared (by pcconfig or f95admin). Files with mixed case names, can never be seen, opened or created.

File Create
When files are created, the name will always have the case specified regardless of the case specified by the client.

File Open / Search
When files are opened/searched, file names containing letters other than the case specified will be ignored.

To the top

Tuning SCO OpenServer 5 for large Fusion95 systems

Fusion95 uses one Semaphore Undo Structure per user. For large systems running on SCO OpenServer 5 it may necessary to tune the SEMMNU kernel parameter and increase its value. It is suggested that this value be set to ten (10) more than the number of Fusion95 users.

SCO documented the maximum value of SEMMNU as 100. Which of course would never be enough for any large system. But they also have the "secret documentation" which says the maximum is 32000. This you can find at:

http://www.sco.com/cgi-bin/ssl_reference?104877

Most modern UNIX systems allocate these Semaphore Undo Structures dynamically from available kernel memory, and thus no kernel tuning is required. Even SCO have started allocating them dynamically in UnixWare 7 and removed SEMMNU.

To the top

Windows 2000 8.3 filenames.

Filenames with an MS-DOS 8.3 format (i.e. the name part is max 8 characters and the extention part is max 3 characters) are mapped to all upper case so that they appear to be MS-DOS filenames. All other filenames retain their format.

It is possible to stop these filenames from being "forced" to upper case. To do so, set dontmangle8dot3=0 in the file pcserve.ini in the /usr/fusion95/cfg directory. You have to restart Fusion95 to make the change take effect.

Here is also the explanation of the keyword, that you can also add to the file. 

*****************************
* Eight Dot Three Filenames *
*****************************
;
; dontmangle8dot3=
;
; When set to one, all file names with 8.3 format are treated as DOS
; filenames regardless of case.
;
; The default is:
;
; dontmangle8dot3=1
;
dontmangle8dot3=0

To the top  

Basic Problem Reporting Guide

The following are the basic steps for customers and resellers to take when experiencing problems in F95ADMIN.

Check that Fusion95 Starts

A. Run the command /usr/fusion95/f95check to determine that all processes are running. This should produce output like...

# /usr/fusion95/f95check

Checking F u s i o n 9 5
         ===============

Network node name: POWERPC
* Fusion95 SMB/CIFS File Server running
* Fusion95 WfW beacon running using domain/workgroup name: WORKGROUP
* Fusion95 NetBIOS Name Service running
* Fusion95 SMB Printer Client running

B. If one or more of the processes has not started, check the contents of the /usr/fusion95/*0.log files. They may contain useful information for problem resolution, and should be forwarded to support for examination.

C. One reason that Fusion95 might not start is that another program is using the IP sockets needed by Fusion95. These are sockets 137, 138 and 139. These could already have been taken if another RFC NetBIOS was already running by mistake in the Fusion95 machine. This could show up in the /usr/fusion95/*0.log files as the error message "bind failed".

A machine with an RFC NetBIOS already running will show something like the following network status.

# netstat -na | grep 13[789]
tcp   0   0   *.137   *.*   LISTEN
tcp   0   0   *.138   *.*   LISTEN
tcp   0   0   *.139   *.*   LISTEN
udp   0   0   *.137   *.*
udp   0   0   *.138   *.*
udp   0   0   *.139   *.*
#

A machine with NO RFC NetBIOS already running will return no tcp or udp information in the network status.

# netstat -na | grep 13[789]
#

To the top

Check the PC to Fusion95 Connectivity

A. From UNIX run the ping command to determine that the PC can be seen.

# ping 10.0.0.212
PING 10.0.0.212 (10.0.0.212): 56 data bytes
64 bytes from 10.0.0.212: icmp_seq=0 ttl=255 time=1 ms
64 bytes from 10.0.0.212: icmp_seq=1 ttl=255 time=1 ms
64 bytes from 10.0.0.212: icmp_seq=2 ttl=255 time=1 ms
64 bytes from 10.0.0.212: icmp_seq=3 ttl=255 time=1 ms
64 bytes from 10.0.0.212: icmp_seq=4 ttl=255 time=1 ms

--- 10.0.0.212 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 1/1/1 ms

B. From the PC run the ping command to determine that UNIX can be seen.

C:\WINDOWS>ping 10.0.0.210

Pinging 10.0.0.210 with 32 bytes of data:

Reply from 10.0.0.210: bytes=32 time<10ms TTL=255
Reply from 10.0.0.210: bytes=32 time=1ms TTL=255
Reply from 10.0.0.210: bytes=32 time=1ms TTL=255
Reply from 10.0.0.210: bytes=32 time=1ms TTL=255

Ping statistics for 10.0.0.210:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms

C. From Fusion95, check the configuration of TCP/IP and RFC NetBIOS.

# /usr/fusion95/nbns -z
nbns - Fusion95 NetBIOS Name Server
Version 4.04 - 4 Aug 2000 - Copyright 1994-2000 April System Design
SMB Server Configuration:
....Node Name: POWERPC
....Domain Name: WORKGROUP
....localhost: 127.0.0.1

Building NetBIOS Name Table:
....Name 0 <POWERPC        > 20 ( FAEPFHEFFCFAEDCACACACACACACACACA)
....Name 1 <POWERPC        > 00 ( FAEPFHEFFCFAEDCACACACACACACACAAA)
....Name 2 <WORKGROUP      > 00 ( FHEPFCELEHFCEPFFFACACACACACACAAA)
....3 names in NetBIOS Names Table

Running on the following networks....
  Interface    IP Address    Network Mask    Broadcast Address
        en0    10.0.0.210    255.255.255.0   10.0.0.255

Verify that the Node and Domain (or Workgroup) names are correct.

Verify that the localhost IP address is correct.

Verify the IP address on which Fusion95 is running is correct.

Verify the IP network mask, and thus the broadcast address of the network on which Fusion95 is running is correct. The network mask (and thus the broadcast address) should be the same for all machines connected to the network. Unless going through a router - the PC and the Fusion95 machine MUST have the same network address, network mask and broadcast address. If this is NOT correct it might still be possible for the PC to access the resources on the Fusion95 machine, but the Fusion95 machine will probably not appear in the PC's Network Neighborhood.

D. From the PC run the nbtstat command to determine that UNIX can be seen. Run nbtstat with both the -A (upper case) option followed by the IP address of the Fusion95 machine and the -a (lower case) option followed by the name of the Fusion95 machine.

C:\WINDOWS>nbtstat -A 10.0.0.210

       NetBIOS Remote Machine Name Table

  Name               Type        Status
---------------------------------------------
POWERPC       <20>  UNIQUE      Registered
POWERPC       <00>  UNIQUE      Registered
WORKGROUP     <00>  GROUP       Registered

MAC Address = D2-00-00-0A-00-00

C:\WINDOWS>nbtstat -a POWERPC

       NetBIOS Remote Machine Name Table

  Name               Type        Status
---------------------------------------------
POWERPC       <20>  UNIQUE      Registered
POWERPC       <00>  UNIQUE      Registered
WORKGROUP     <00>  GROUP       Registered

MAC Address = D2-00-00-0A-00-00

Both of the above command should produce the same output. If the first finds the Fusion95 machine while the second fails to do so then there is probably a problem with name resolution. This is often caused by operating through a router (for example over a Wide Area Network) without being properly configured.

If name resolution is thus suspected:

E. In the PC using the Control Panel, check that the Microsoft Network Client is installed and has been bound to TCP/IP. Make sure that you have logged on via Microsoft Networking.

F. In the PC start an MS-DOS command prompt and verify that the NET command can see the shared resources on the Fusion95 server.

C:\WINDOWS>net view \\powerpc
Shared resources at \\POWERPC

Sharename    Type       Comment
---------------------------------------
COLORLJ1     Print
COLORLJ2     Print
GUARDIAN     Disk       /G
HOME         Disk       /home
LASER        Print
TMP          Disk       /tmp
VAR          Disk       /var
WEBDEV       Disk       /webdev
The command was completed successfully.

An error 53 returned by this comamnd indicates that the specified server name cannot be found. If name resolution problems have been suspected in the previous step, this will probably be the result here. To confirm this (on modern Windows operating systems) the name of the Fusion95 can be replaced in the NET command by its IP address:

C:\WINDOWS>net view \\10.0.0.210
Shared resources at \\10.0.0.210

Sharename    Type       Comment
---------------------------------------
COLORLJ1     Print
COLORLJ2     Print
GUARDIAN     Disk       /G
HOME         Disk       /home
LASER        Print
TMP          Disk       /tmp
VAR          Disk       /var
WEBDEV       Disk       /webdev
The command was completed successfully.

G. Still in the PC's command prompt, verify that the NET command can be used to map a shared disk resources on the Fusion95 server.

C:\WINDOWS>net use t: \\powerpc\tmp
The command was completed successfully.

To the top

Check how Fusion95 appears in the Network Neighborhood browse list

A. Because of the way the browsing works in Microsoft Networks, it might take a short time before a newly started server appears in the Network Neighborhood browse list.

B. A Microsoft Networking Browser Server must be running in order for machines to appear in the Network Neighborhood browse list. Make sure you have at least one Windows machine in the network configured as a file and print server.

C. Confirm that the domain or workgroup name of the browse server is the same as the name configured in Fusion95. The f95check command will show the domain/workgroup name being used by Fusion95.

# /usr/fusion95/f95check

Checking F u s i o n 9 5
         ===============

Network node name: POWERPC
* Fusion95 SMB/CIFS File Server running
* Fusion95 WfW beacon running using domain/workgroup name: WORKGROUP
* Fusion95 NetBIOS Name Service running
* Fusion95 SMB Printer Client running

D. Confirm that Fusion95 node can see the master browse server for the configured domain/workgroup. The Fusion95 nbas program can be used for this purpose.

# nbas -m WORKGROUP
nbas - Fusion95 RFC NetBIOS Adapter Status
Version 4.04 - 4 Aug 2000 - Copyright 1994-2000 April System Design

                  ------ ADAPTER STATUS ------

          Remote IP Address : 10.0.0.214
  Adapter Node Name/Address : 00 50 04 87 AC 24

                  --- 10 NAMES in name table ---

 1 "APRIL          "     Server
 2 "APRIL          " 00  Redirector
 3 "WORKGROUP      " 00  Workgroup Group Name
 4 "INet~Services  " 1C  Primary Domain Controller Group Name
 5 "IS~ADMIN......." 00  Redirector
 6 "APRIL          " 03  Messages
 7 "WORKGROUP      " 1E  Browser Server Group Name
 8 "SQLSERVICE     " 03  Messages
 9 "WORKGROUP      " 1D  Master Browser Server
10 "..__MSBROWSE__." 01  Group Name

E. Create a trace file to enable support to deterimine that Fusion95 is broadcasting its name for addition to the browse list. The trace.txt output from this file should be sent to support.

# cd /usr/fusion95
# ./wbeacon -dWORKGROUP -tnC12>&1 | tee trace.txt

To the top

PCserve - file & printer server - problem determination and reporting

The following are hints for customers and resellers with problems in the file & printer server - pcserve. This section is a follow on from the previous "basic" section. If the server appears to have started but does not seem to be operating correctly, creating a trace as described below can help support staff to determine the problem.

If you are running through a router, read the "Wide Area Networks" chapter in this document. The Password Encryption chapter may also be of interest if you are having problems with authentication.

Obtain a trace

Problems can often be speedily resolved with the help of a trace file. It is however occassionally the case that creating a trace file does not reproduce the problem, but even then the trace is of use in allowing support personnel to see the client and server configuration.

To obtain a trace from pcserve, do the following.

  1. cd /usr/fusion95
  2. cp f95start f95trace
  3. vi f95trace
    Edit the line containing:
      TRC_SRV=" "
    so that it says:
      TRC_SRV=" -o3 "
    Note that you might be asked to specify a number other than 3 by support.
  4. Disconnect all users and then stop the server by running:
    ./f95stop
  5. Start the server with trace enabled by running:
    ./f95trace
    This will cause trace output to be written to pcserve0.log
  6. Connect from the PC, and run the software causing the problem.
  7. Stop the server by running:
    ./f95stop
  8. Save the trace file created:
    cp pcserve0.log trace.log
  9. Restart the server without trace by running:
    ./f95start
  10. Send the created trace file to support, it may be a good idea to compress it if it is large.
To the top

F95ADMIN - problem reporting

The following are hints for customers and resellers reporting problems in F95ADMIN.

Determine F95ADMIN version

Please report which version of F95ADMIN you are running. To do this:

Run the latest F95ADMIN

Make sure that the F95ADMIN you are running is the latest version. The latest version of F95ADMIN is available for download.

Create a trace

If upgrading to the latest version doesn't fix the problem, create a log file to help us trace the problem. Do the following:

Edit the file called f95admin.ini in the C:\Windows catalog. It should look something like...

  [config]
  usedisk=Z:
  search=2
  servername=HIMALAYA
  domainname=

Add the line...

  log=1

So the file looks like...

  [config]
  usedisk=Z:
  search=2
  servername=HIMALAYA
  domainname=
  log=1

Now restart, F95ADMIN and run so as to reproduce your problem. This will create a f95admin.log file in the C:\Program Files\Fusion95 catalog.

Reporting the problem

Please send us the following information to help us resolve your problem...

Note:

The directory names C:\Windows and C:\Program Files\Fusion95 might vary on different Windows systems depending on which language version you are running and whether the installation defaults were chosen. In the above, we used the values for a default installation on an English Windows.

To the top

Smbprtup - printer client - problem determination and reporting

The following are hints for customers and resellers with problems in the printer client - smbprtup.

If you are running through a router, read the "Wide Area Networks " chapter in this document, the section entitled "Printing from Fusion95 to a remote printer " is specifically of interest.

Obtain a trace

Problems can often be speedily resolved with the help of a trace file. It is however occassionally the case that creating a trace file does not reproduce the problem, but even then the trace is of use in allowing support personnel to see the client and server configuration.

To obtain a trace from smbprtup, run the following.

# cd /usr/fusion95
# ls -l | ./smbprtup -nt -ccfg/lprt00.cfg2>&1 | tee trace.txt

Email the output (trace.txt) to support together with a full description of the problem.

Connection Problems

Problems which cause smbprtup to fail when it attempts to connect to the server with the shared printer resource are often caused by the name conflicts or wide-area networking problems.

  1. Check that the server name and printer name are valid and that they can be reached from a PC.
  2. Sometimes adding the name and ip address of the printer server to the /etc/hosts file on the UNIX machine resolves the problem.

To verify the configuration, run the smbprtup with the -v option.

# cd /usr/fusion95
# ./smbprtup -v -ccfg/lprt00.cfg

An error will be reported if the configuration fails to veify, otherwise the command prompt will be displayed.

Security Problems

Problems which cause smbprtup to fail when it attempts to map the shared printer resource are often caused by the security settings on the server to which the printer is attached. Common causes are that the password and username (if required) configured for the smbprtup printer client using smbprt.sh or fusion menu do not match those on the printer server:

  1. The printer is on a share-level server and the password configured is wrong.
  2. The printer is on a user-level server and the username/password configured is not a valid account
  3. The printer is on a user-level server and the username/password configured is an account which does not have network access rights to the printer.

Open Problems

Problems which cause smbprtup to fail when it attempts to open the spool file are often caused by the spooling options settings on the server to which the printer is attached.

This is often caused by a Windows spool server not correctly supporting RAW printing when configured for EMF spooling. To check this, look at the printer spooling configuration, in the Windows machine. To do this, go to:

  1. Start Menu
  2. Settings
  3. Printers
  4. Right click on the printer and select Properties

In Windows98 and Windows95:

  1. Details Tab
  2. Spool Settings

In Windows NT:

  1. General Tab
  2. Print Processor

In Windows 2000:

  1. Advanced Tab
  2. Print Processor

Check the configuration.

  1. Make sure that "Spool data format" is set to "RAW" instead of "EMF".

Note:

In the above examples lprt00 is used. You will need to change the number to that of the printer client causing the problem.

To the top

 

© Copyright 2004-2017 Developed by April System Design