Troubleshooting

Novell NetWare Servers Can't Be Found

I have installed a NetWare client, but version 2.x NetWare servers do not appear under Entire Network in My Network Places.

Windows might not have correctly identified the Ethernet frame type used by these earlier NetWare versions. In Network and Dial-Up Connections, open the Local Area Connection properties. Select NWLink IPX/SPX Compatible Protocol, and open Properties. Under Frame Type, change the setting from Auto to 802.3.

If you have NetWare version 3 or higher servers on the network, you should configure them to use 802.3 framing in addition to the default Ethernet_II.

Can't Attach to NetWare Servers

I'm using the Microsoft Client but can't connect to some NetWare servers running version 3 or higher; my password is rejected.

Have the NetWare administrator enable unencrypted passwords on these servers. The Microsoft client can't send encrypted passwords to NetWare servers. (The Novell client does not have this problem.)

Banner and/or Blank Pages Are Printed on NetWare Printers

When I send printer output to Novell printers, banner pages are printed at the beginning of my print jobs, and/or blank sheets are printed at the end.

Open the CNSW Control Panel applet, and uncheck Print Banner Pages and Add Form Feed.

Some Computers Are Missing from Entire Network

My list of Computers Near Me is incomplete under Entire Network in My Network Places.

The network has elected a browser master that doesn't have all the protocols used by Windows networking computers on your LAN. This is a random selection, so be sure to install and bind the same set of protocols on every workstation in your LAN.

Carriage Returns and Line Feeds Are Mangled

When plain-text files are sent from UNIX machines to my printers using lpr and Print Services for UNIX, carriage returns and line feeds are mangled. Line feeds are inserted where just carriage returns were present.

When it's receiving plain ASCII text for printing, the TCP/IP Print Server replaces both LF (line feed or newline) and CR (carriage return) characters with a carriage return/line feed pair. This messes up print jobs that wanted to overprint lines using just a carriage return.

You can disable the translation of both newlines and carriage returns, or just of carriage returns, by adding a value to the Registry.

For instructions and warnings about using the Registry Editor, p. 1259.

Use the Registry Editor called Regedit to find the key HKEY_LOCAL_MACHINE\ System\CurrentControlSet\Control\Print\Printers\printername\PrinterDriverData, where printername is the name of the shared printer the UNIX user is using.

To prevent the TCP/IP Print Server from replacing either CR or NL with CR+LF, follow these steps:

1.	Select key PrinterDriverData and choose Edit, New, DWORD Value. Enter the name Winprint_TextNoTranslation, and set the value to 1.
2.	To prevent the server from replacing CR with CR+LF but still replace LF with CR+LF, add the DWORD value Winprint_TextNoCRTranslation with the value 1.
3.	After making either of these additions, go to Computer Management, view Services, right-click TCP/IP Print Server, and select Restart.

Some Windows XP printer drivers do not correctly implement overprinted lines. You might find that the lines are now correctly stacked on top of each other, but only the text from the topmost line is visible. You might need to use the binary mode flag (-o l) in your lpr command and add a form feed to the end of your file.

If you later decide to undo the Registry change, you can remove the value item or set its value to 0, and then restart the service.

Can't Run Macintosh Application Concurrently

When a Macintosh application is installed on a shared folder stored on a Windows XP, NT, or Server 200x, an Unable to Open File error occurs on Macintoshes when more than one Macintosh user attempts to run the application concurrently.

Some Macintosh programs fail to open their application executable files in the proper file sharing mode. You can patch the problem by using a resource editor program on the Macintosh; just follow these steps:

1.	Obtain a copy of ResEdit. An excellent resource (pun intended) for all things resource related is ResExcellence (www.resexcellence.com). There, you can download a copy of ResEdit as well as gain helpful resource editing skills through the huge collection of step-by-step projects. For novice users, a better program is FileBuddy from SkyTag (www.skytag.com).
2.	Start ResEdit or FileBuddy. Select Get Info from the File menu. In the dialog that appears, you can select the application.
3.	Put a check in the Shared check box.
4.	If you're using ResEdit, quit the application and choose Yes to save the changes. In FileBuddy, click OK.

CAUTION

Resource editing on a Macintosh is as risky as Registry editing in Windows. Always make a copy of whatever file you're going to edit before making changes, and never throw out an original, even if it seems that your modified version works like a charm.

Macintosh Files Have Lost Application Associations

After a shared file has been edited by a Windows user, when Macintosh users open the file, the Macintosh Finder says it can't find the application required to open the document.

The file's resource fork was stripped out when the file was edited in Windows, so the file's Type and Creator codes are missing. The Macintosh user can drag the file and drop it onto the application's icon or manually locate the application. When the Macintosh user saves the file, the association will be restored for future edits.

The Type and Creator codes can also be set using a Macintosh resource editor, as described previously. However, resource editing is tricky and best not done unless it's an emergency.

NOTE

Type and Creator codes are case sensitive. MSWD is not the same as MsWd or mswd. Case can often cause confusion if you must restore the codes if they were stripped on a trip through Windows or DOS.