Groupwise Error 8909
disconnected from the server Error 8909. Error: 8908 Users are getting disconnected when trying to open GroupWise cause Packet receive buffers was set very low. fix Referred to TIDs Performance, Tuning and Optimization 2943356 and 2943472Physical Packet Receive BuffersReceive buffers are used to store incoming packets from each of the networks attached to a NetWare server. The Maximum Physical Receive Packet Size should be set according to the kind of network it is on. In most cases, this is 1524 bytes for Ethernet segments, 4540 bytes for Token-Rings and FDDI and 618 bytes for Arcnet and LocalTalk. These values are taken from the "Novell BorderManager Installation and Setup" manual, the chapter on "Installing Novell BorderManager", page 9. Certain products installed have specific requirements in which you will need to refer to your manuals for instructions.A good rule of thumb for the minimum packet receive buffers setting is approximately 2-3 receive buffer for each connection and maximum packet receive buffers to 4000 (or any higher value). Also, check the No ECB (Event control block) Available Count information in the LAN/WAN Information option in MONITOR.NLM. These messages indicate that the server was unable to acquire sufficient packet receive buffers, usually called event control blocks (ECBs). Running out of ECBs is not a fatal condition. Servers that run for several days where high loads occur in peaks might exceed the set maximum number of ECBs, causing the system to generate ECB system messages. If these situations are caused by occasional peaks in the memory demand, you should probably maintain your current maximum ECB allocation and allow the message to be generated at those times. On the other hand, if your server memory load is very high and you receive frequent ECB allocation errors, you should probably set your maximum ECB allocation higher. Use the following SET command in the AUTOEXEC.NCF file: SET MAXIMUM PACKET RECEIVE BUFFERS = number Note that the memory allocated for ECBs cannot be used for other purposes. The minimum number of buffers available for the server can also be set in the STARTUP.NCF file with the following command: SET MINIMUM PACKET RECEIVE BUFFERS = number.If the current Packet Receive Buffers rises above the minimum set level after the server has been up for a period of time, set the minimum Packet Receive Buffers to the current level. document Document Title: Clients get disconnected from the server Error 8909. Document ID: 10011290 Solution ID: 4.0.1443234.2203944 Creation Date: 25Jun1999 Modified Dat
Favorite Rating: Error: Unable to connect to send, Link blocked (8909). When the MTA is down (Last modified: 20Mar2003) This document (10016088) is provided subject to the disclaimer at the end of this document. fact Novell GroupWise 5.5 Novell GroupWise Internet Agent Post office link to domain is TCP/IP Domain and Post Office are on the same server symptom Error: Unable to connect to send, Link blocked (8909). When the MTA is down Error: http://support.novell.com/docs/Tids/Solutions/10011290.html 8909 Cannot send Internet mail fix Change the Post Office links from TCP/IP to UNC in the Link Configuration Tool:1. Highlight the Domain object in GroupWise View of the appropriate NWAdmin2. Right click on the object and select Link Configuration3. In the Link Configuration Tool select View | Post Office Links 4. Double click on the link that http://www.novell.com/support/kb/doc.php?id=10016088 needs to be changed5. Click on the pull down arrow next to Protocol and select UNC6. Ensure the UNC Path is correct7. Click on OK8. Exit the Link Configuration tool and save your changes9. The MTA should cycle through a restart automatically10. Ensure that the Post Office opens on the restart of the MTA disclaimer The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information. Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information. Document ID: 10016088 Solution ID: 4.0.48697198.2304439 Creation Date: 03Sep1999 Modified Date: 20Mar2003 NovellGroupware Did this document solve your problem? Provide Feedback © Micro Focus Careers Legal close Feedback Print Full Simple Request a Call Follow Us Facebook YouTube Twitter LinkedIn Newsletter Subscription RSS
Favorite Rating: Error 8909 while loading POA after changing the Server IP AddressThis document (7000974) is provided subject to http://www.novell.com/support/kb/doc.php?id=7000974 the disclaimer at the end of this document. Environment Products:Novell NetWare 6.0Novell http://www.primarycomputer.net/english/gw5.5/admin/tb1085xx.htm NetWare 6.5Novell GroupWise 6.5Novell GroupWise 7Configuration:POA object contains the correct IP AddressPOA startup file contains the correct the IP Address Situation Error 8909 while loading POAClient/Server setting in the POA log file displayswrong or previousIP addressMTA shows the POA as closedPOA not loading with proper settingsPOA not groupwise error loading after changing the server IP address Resolution Switch to thePost Office Agent(POA) screen and press F7 key to exit the POA.Switchto Message Transfer Agent (MTA)screen and press F7 key to exit the MTA.Type "inetcfg" without quotes at server system console and press Enter. This will open Internetworking Configuration window.Scroll down to Boardsand pressEnter.Check the number of boards connected to groupwise error 8909 the server, note down the name and the name of the driver used by thatboard.Press ESC key to exit the board options to reach the Internetworking Configuration window.Scroll toProtocolsand press Enter and look for the protocols that are in enabled status. TCP/IP should be enabled.Press ESC key to exit Protocol options to switch back tothe Internetworking Configuration window.Scrollto Bindings option and make sure that the bindings are enabled. Check the IP binding whether proper IPaddress is bound to that card or not. If the IP address bound to the card is not correct then follow the sub steps listed below:Press Enter key. It will open an another small window"Binding TCP/IP to a LAN Interface".From herechange the IP address bound to that network card. Press Enter key and it will allowto change the IP address.Enter thecorrect IP address and press ESC key. Select YES to save the configuration.Press ESC key to exit Binding options to switch back to thethe Internetworking Configuration window.Scroll downto Reinitialize System option and pressEnter.SelectYes to re-initialize the system.Type "edit autoexec.ncf" at the S
packet contained invalid identifier 8563 Client/server request packet contained invalid identifier 89xx TCP/IP Communication 8901 Cannot use TCP/IP services 8902 Cannot load TCP/IP services 8903 Cannot use TCP/IP services 8906 Cannot use TCP/IP services 8907 Cannot use TCP/IP services 8908 Cannot connect to specified address 8909 Cannot use TCP/IP services 890A Cannot listen on specified port 890B Cannot accept incoming connection 890F Connection no longer valid 8910 Cannot read on connection 8911 Cannot write on connection 8912 Cannot read on connection; timed out 8913 Cannot write on connection; timed out 8916 Cannot use TCP/IP services 8Fxx Server Toolkit 8F03 Invalid configuration option 8502 Cannot initialize protocol SourceGroupWise engine; general communication. ExplanationCannot open protocol. Possible Cause(s)Cannot initialize protocol. It is possible that TCP/IP is not correctly loaded on this machine. Possible Cause(s)Cannot load Winsock (Windows only) or the version of Winsock that did load is not supported. DNS is not loaded and you are trying to resolve DNS names. Action(s)Configure TCP/IP on the workstation correctly. 8503 Cannot connect to specified IP address SourceGroupWise engine; general communication. ExplanationCannot open connection to specified address. Action(s)Check the IP address for the POA. See Use Client/Server Access to Post Office in Chapter 3: Reconfigure the POA in Book 2: Post Office Agent in the Agent Configuration Guide. Action(s)Check the status of the POA server and the load on the network. 8509 Cannot access TCP/IP services SourceGroupWise engine; general communication. ExplanationTCP/IP bind failed. Possible Cause(s)TCP/IP is not loaded on the workstation or is not loaded correctly. The TCP port is already in use by another process. Action(s)Configure TCP/IP on the workstation correctly. If this error occurs on a NetWare server, make sure you have the latest version of the TCPIP NLM. For technical services and file updates, see Novell Support Connec