Groupwise Error 8503
Novell GroupWise 5.2 Novell GroupWise 16 bit Client symptom Error: 8503 trying to connect to post office in direct mode using vlms. Error: 8503 Error: Could not connect to the specified network address. Either the server is down, the network is slow, or an invalid address and port combination was specified. Error only occurred with workstations running vlms. Customer could not connect to the post office in direct mode. cause Invalid WINSOCK.DLL file in the C:\WINDOWS directory. Even though the customer is accessing GroupWise in direct mode, GroupWise still needs to load a valid WINSOCK.DLL file. If it cannot find it or it is incompatible with the version of dos requesters being used, the 8503 error will occur. You can get the WINSOCK.DLL file off of your Microsoft Windows 95 CD. fix Get a valid WINSOCK.DLL file and put it in the C:\WINDOWS directory 1. Find all occurrences of WINSOCK.DLL in the search paths, then remove all of them 2. Download the TCP16.EXE file from the support connection. 3. Extract file into the directory that contains the NET.CFG and the vlms. 4. Add this path to the search drive list. (Or you can extract the TCP16.EXE into a current search path) document Document Title: Error: 8503 trying to connect to post office in direct mode using vlms. Document ID: 10010088 Solution ID: 4.0.20836.1675983 Creation Date: 23Jun1998 Modified Date: 28Mar2002 Novell Product Class:Groupware 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.
remote Mailbox folder Cannot log in to the gateway. Check the gateway login ID... Cannot log in to the gateway. Check the gateway login password... LDAP failure detected Required information is missing from the connection Some setup files are missing The following information necessary to run GroupWise against... The master GroupWise system is unable to process a request... The master GroupWise system is unable to process your current... This item uses a custom view that was not retrieved... This transmission cannot be completed due to network problems Unable to create folder {file_name.ext} could not be opened as a modem script http://support.novell.com/docs/Tids/Solutions/10010088.html file {file_name.ext} failed to open NOTE:This guide does not include a comprehensive list of all possible GroupWise client error messages. It lists error messages for which solutions are readily available from GroupWise engineers and testers. You can search the Novell Support Knowledgebase to locate additional solutions documented by Novell Support as specific customer issues have been resolved. A previous request to retrieve items has not been completed Source: GroupWise http://www.novell.com/documentation/groupwise2012/gw2012_guide_tsh1/data/a3wyycs.html Windows client; Remote mode. Possible Cause: Because requests sent to the master GroupWise system are processed and then returned to your Remote mailbox, there are times when your Remote mailbox waits for responses from the master system. If this is the case, making a new request will duplicate the response that is returned from the previous request, resulting in wasted transmission time and, possibly, long-distance charges. Action: If you need a new request because of differing date ranges or item filtering, click Yes to confirm that an additional request is required. Otherwise, click No so the outstanding request will be processed completely before another request is issued. Cannot access your Master Mailbox Source: GroupWise Windows client; Remote mode. Possible Cause: For GroupWise to access your Master Mailbox remotely, GroupWise must give your Master Mailbox password to the master GroupWise system. Otherwise, access is denied without the appropriate password. Action: Run GroupWise before leaving your office, then set a password on your Master Mailbox. Action: If you are already away, have someone at your office set a password for you. Then, specify that password in Remote Options. Action: The administrator can reset the password for a user in ConsoleOne. See Creating or Changing a Mailbox
services 890A Cannot listen on specified port 890B Cannot accept incoming connection 890F Connection no longer valid 8910 TCP/IP read failed on an established connection 8911 Cannot write on connection 8912 Cannot read on http://www.novell.com/documentation/groupwise2012/gw2012_guide_tsh1/data/b4k0vaw.html connection; timed out 8913 Cannot write on connection; timed out 8915 The server or the client machine is running out of memory 8916 Cannot use TCP/IP services 8917 TCP/IP name lookup failed 8918 UDP send http://novell.support.groupwise.6x.clients.narkive.com/ojdmUr72/proxy-error-8503 failed 8919 Attempt to bind to a non-existent IP address 891A TCP/IP data is not ready for reading 891B No SSL certificate supplied 891C Bad SSL certificate 891D Bad SSL private key or password 891E Insufficient groupwise error memory for SSL 891F Invalid SSL certificate 8920 SSL certificate and private key do not match 8921 SSL accept failure 8922 SSL connect failure 8923 Insufficient memory for SSL 8924 SSL handshake timeout failure 8925 Connection refused 8926 Unknown host 8927 Host not reachable NOTE:This guide does not include a comprehensive list of all possible GroupWise error codes. It lists error codes for which solutions are readily available from GroupWise engineers groupwise error 8503 and testers. You can search the Novell Support Knowledgebase to locate additional solutions documented by Novell Support as specific customer issues have been resolved. 8901 Cannot use TCP/IP services Source: GroupWise engine; TCP/IP communication. Explanation: A fundamental TCP/IP call failed. Possible Cause: TCP/IP services couldn’t be used. It is possible that TCP/IP is loaded incorrectly on this server. Possible Cause: Cannot load WINSOCK (Windows only), or the WINSOCK that did load is not supported. DNS is not loaded and you are trying to resolve DNS names. Action: Correctly configure TCP/IP on the server. 8902 Cannot load TCP/IP services Source: GroupWise engine; TCP/IP communication. Explanation: TCP/IP load failed because a required file was missing. Possible Cause: Unable to load TCP/IP services because one or more of the required files is missing: winsock.dll, wsoc32.dll, or tcpip.nlm. Action: Make sure that you have the required files, and that they are in the search path. Action: Correctly configure TCP/IP on the server. 8903 Cannot use TCP/IP services Source: GroupWise engine; TCP/IP communication. Action: See 8901 Cannot use TCP/IP services. 8906 Cannot use TCP/IP services Source: GroupWise engine; TCP/IP communication. Action: See 8901 Cannot use TCP/IP services. 8907 Cannot use TCP/IP services Source: GroupWise engine; TCP/IP communication. Action: See 8901 Cannot use TCP/IP services. 8908 Canno
issues with proxy but the users in the field are.In the field they are on Cable or DSL, they use the full client (notremote setup) where they make an IP connection to the POA. They canproxy to mailboxes that are on their own Post Office no problem, butwhen they have to proxy to a mailbox on another Post Office that get the8503 error. Could not connect to the specified network address. Eitherthe server is down, the network is slow or an invalid address and portcombination was specified.The server we are trying to make the proxy connection to is up and nothaving any issues. Also if they go through WebAccess and use the proxyfeature there is no problem, they can attach to the mailbox.There are no POP3 or IMAP4 limitations for any of these users.Any thoughts on where I should start to look to resolve this problem?Thanks, Danita Zanre 2005-03-09 15:33:48 UTC PermalinkRaw Message Barbara,Post by Barbara GenslingerThey canproxy to mailboxes that are on their own Post Office no problem, butwhen they have to proxy to a mailbox on another Post Office that get the8503 error. Could not connect to the specified network address.That's because the redirection tables for GW POs are most assuredly to non-routeable (private) IP addresses. Look at the "proxy port" information in ConsoleOne for a possible solution.--Danita ZanreNovell Volunteer Sysopwww.caledonia.net/iris.html Barbara Genslinger 2005-03-09 19:03:14 UTC PermalinkRaw Message You are correct, the redirection table is only internal IP's. I added the external IP as a Proxy Server and used Port 1677 as the internet proxy client/server port. The changes appear inthe redirection table but I still can not attach via the client in the field.I only have 1 public IP which is the one they are using in the field to connect. Can I place this IP in the Proxy Server field of all the POA's? And will it make a difference anyway sincethey connect via TCP/IP to the server with the public IP and the account we want to proxy to is on a different box?Basically all remote users are on PO1 (208.x.x.x aka 10.1.x.x) the mailbox they need to proxy to is PO5 with only a 10.11.x.x address. All Client server ports are 1677 since the POA's