Failed to Initialize AppleTalk – Error

1 Star2 Stars3 Stars4 Stars5 Stars
Loading...
  • Product:
    ExtremeZ-IP
  • Version:
    All
  • Document Type:
    Info
  • Revised:
    3/17/2009
  • Reviewed:
    3/31/2006

Summary:

Describes how to handle the error from ExtremeZ-IP “Failed to initialize Appletalk support (10049). The ExtremeZ-IP server will not appear in the Chooser”

Description:

When the ExtremeZ-IP service starts up, you may see an error message in the Event Viewer that says “Failed to initialize AppleTalk support (10049). The ExtremeZ-IP server will not appear in the Chooser”.

In order to have ExtremeZ-IP servers appear in the Mac OS 9 Chooser, you need to have the AppleTalk protocol installed on the server. If you are receiving an error message of “Failed to Initialize AppleTalk support,” the most likely cause is that the AppleTalk protocol is not installed on the server. Although AppleTalk is certainly not required to use ExtremeZ-IP if you have Mac OS 9 clients connecting to your server, you may want to enable it. The AppleTalk protocol can be enabled on all Microsoft server operating systems. However although Windows 2000 Professional shipped with AppleTalk, Microsoft did not include it with Windows XP Pro.

If you choose not to or cannot install the AppleTalk protocol, you can prevent the “Failed to Initialize AppleTalk” error from appearing, by unchecking the “Register file server on AppleTalk” checkbox on the Settings tab of the ExtremeZ-IP administrator. Because the server name will not be broadcast in the Chooser, Mac OS 9 users should connect to the server via the IP address or hostname.

An alternative to using the AppleTalk protocol for server discovery is to use the TCP/IP protocols SLP (accessible via the Network Browser on Mac OS 9, or “Connect to Server” dialog in Mac OS X), or Rendezvous (accessible via the “Connect to Server” dialog on Mac OS X).

Tags: