TOPIC
This Read Me document contains late-breaking information about Open Transport compatibility, add-on software, and solutions to known problems with third-party software. For instructions about how to use the Open Transport control panels (AppleTalk and TCP/IP), see the Open Transport User's Guide. For additional technical information about Open Transport, see the "Open Transport Technical Info" file that came with Open Transport.
DISCUSSION
Tips for SLIP and PPP Configurations Some MDEVs are known to be incompatible with other MDEVs. If you experience problems, remove unused MDEVs so that only the MDEVs you need are installed on your computer at a given time. If you still encounter problems, you may have to reduce the number of MDEVs installed to one to prevent conflicts. Users who dial into a TCP/IP network or Internet Service Provider (ISP) may have been assigned a router (gateway) address that is not a part of their local subnet. This was an accepted but technically invalid configuration for MacTCP. Open Transport users should not enter a value for the router address or subnet mask; Open Transport/TCP generates correct values for these fields automatically. In unusual circumstances, these supplied values can be overridden using the Administration mode of the TCP/IP control panel. If BootP is used over SLIP or PPP for interface configuration, and if BootP returns additional default router addresses, Open Transport will automatically add those addresses to the list of default routers. When Open Transport is installed on a computer that previously had MacTCP configured for a server configuration, the initial configuration method‹the selection in the "Configure" pop-up menu in the TCP/IP control panel‹is set for the use of a BootP server. This default may not be the appropriate choice for you; please verify. If your computer was previously configured for MacTCP "server" addressing and you experience connection difficulties using PPP or SLIP after installing Open Transport, follow these steps: 1. Open the TCP/IP control panel. 2. Choose Using PPP Server or Using SLIP from the Configure pop-up menu. 3. Close the TCP/IP control panel, and save changes when prompted. 4. Try connecting again. If your computer was previously configured for MacTCP "manual" addressing and you experience connection difficulties using PPP or SLIP after installing Open Transport, follow these steps:
2. Choose Manual from the Configure pop-up menu. 3. Verify that the correct IP address is entered in the Address field. 4. Close the TCP/IP control panel, and save changes when prompted. 5. Open the configuration utility supplied with your SLIP or PPP software, and verify that it also reflects the correct IP address in the appropriate location. Refer to the documentation supplied with your SLIP or PPP software for further information on how to enter an IP address, and how to save an updated configuration. 6. Try connecting again. Known Limitations and other issues The AppleTalk control panel displays separate printer and modem ports on the PowerBook 190. LocalTalk will only work correctly when the modem port is selected in the AppleTalk control panel. The software that dims the screen of PowerBook Duo computers when the PowerBook is docked and idle is not compatible with Open Transport. Use a third-party screen saver in place of the Apple-provided module. In some cases, on a PowerBook 190 configured to use the Infrared Port in the AppleTalk "Connect via" pop-up menu, networking services may become disabled following a sleep/wake or restart. If this happens, try putting the computer to sleep and waking it up again, or use the AppleTalk control panel to temporarily select the modem/printer port before switching back to the infrared port. On a IIfx or a Quadra 950, Open Transport can only use the "compatible mode" setting in the Serial Switch control panel. Do not use the "faster mode" setting with LocalTalk. On 68030 and 68040 computers, changes in AppleTalk configurations can cause systems running Meeting Maker 3.5 or 3.5.1 to crash. This can occur when changing AppleTalk links, turning AppleTalk off, or bringing ARA connections up or down. This problem will occur on classic networking as well. Apple is working with ON Technology to resolve this problem. Open Transport generally requires more memory (RAM) than MacTCP. To conserve memory, you might try some of the following: When TCP/IP is set to "Load only when needed" (in the control panel's Options window), the first TCP/IP application opened will cause Open Transport to load into memory. Some older applications do not cause Open Transport to load, and then report errors similar to those encountered when MacTCP is not installed. If this is a problem, turn off the "Load only when needed" option (open the TCP/IP control panel and click the Options button, then click the "Load only when needed" checkbox to remove the X) and restart your computer. The TCP/IP control panel is able to obtain and utilize multiple gateway and name server addresses from DHCP and BootP servers. However, it will currently display only the first one. This should be addressed in a future release. Generally, you should turn on the "Load only when needed" option in the TCP/IP control panel when using a modem. If TCP/IP is always loaded ("Load only when needed" is not checked), your modem may attempt to initiate a dialup connection at startup. Some MDEVs require more system heap memory than is available at startup, which may cause the computer to hang. Also, some Internet service providers charge by connect time, so you may be charged for the connection, even if you were not using it. If you use MacSLIP, you should likewise not configure the MacSLIP control panel to initialize MacSLIP at system startup time. As stated above, this may require more system heap memory than is available at startup, which may cause the computer to hang. If you are experiencing problems when using MacSLIP with virtual memory on, increasing your virtual memory size may give you better results. (Use the Memory control panel to increase virtual memory.) Some MacTCP-based applications will not function correctly unless the MacTCP DNR file is in its original location at the root level of the System Folder. You should only specify use of 802.3 framing in the TCP/IP control panel if you have been directed to do so by your network manager, or if you are sure that all other stations on your network segment, including your IP router(s), are also configured to use 802.3 and not Ethernet version 2.0 framing. Claris Emailer version 1.1 v3 or later and Claris Emailer Lite version 1.1 v4 or later is compatible with Open Transport 1.1.2 and later. Earlier versions of Claris Emailer may not be compatible with Open Transport's "Load only when needed" configuration option. If you experience a system crash 2-3 minutes after quitting Emailer, turn off the "Load only when needed" option. (Open the TCP/IP control panel and click the Options button, then click the "Load only when needed" checkbox to remove the X.) The current version of the MacTraceRoute Ethernet LAP does not work on computers running Open Transport. NFS/Share versions 1.4.4 or later are compatible with Open Transport. When using Netware Client version 5.11 configured for NetwareIP service, the first login may yield a Netware Configuration error message. To avoid this error, open the NetwareIP control panel and change the value under Domain SAP Server (DSS) Retry Attempts from 1 to 2. You can also change Open Transport TCP/IP control panel to always load TCP/IP into memory (open the TCP/IP control panel, click the Options button, and click the "Load only when needed" box to remove the X). eXodus 5.2.2 and later are compatible with Open Transport. Versions of Anarchie prior to 1.6 have a data corruption problem when used with Open Transport. Make sure you are using Anarchie 1.6 or later. If an Apple Remote Access (ARA) user is on a non-routed, extended (Ethernet) network, and there are devices on the local network with the same network number as devices on the remote network, the user will not be able to see the local devices. This problem can be fixed by installing a router. Another workaround is to clear the PRAM on the ARA computer. (Hold down the Command, Option, and PR keys simultaneously while starting up the computer). Clearing PRAM causes the computer to start up with a new network number, which should not conflict with the remote network number. Daemon 1.0.0 & Daemon Killer 1.0 are not compatible with Open Transport. MudDweller 1.2 is not completely compatible with Open Transport. You can open new connections, but the ³reconnect² choice does not work correctly. The system will crash during launch of NetPresenz if Open Transport TCP/IP is configured to use MacIP and the selected zone has no MacIP server. Current versions of VersaTerm SLIP are not compatible with Open Transport. Problems can occur with old versions of the KeyServer package from Sassafras Software when TCP/IP is configured to "Load only when needed" (in the control panel's Options window). Contact Sassafras for the latest revisions at < http://www.sassafras.com >. To use the CSI Hurdler serial card with Open Transport, contact CSI to get a copy of their preference file patch. This will enable the card to be compatible with Open Transport 1.1.2. |
||||||
| Document Information | |
| Product Area: | Communications-Networking |
| Category: | Open Transport |
| Sub Category: | General Topics |
Copyright © 2000 Apple Computer, Inc. All rights reserved.