Novell Error 8801
Site Leaders Articles Blogs What's New? FAQ Advanced Search Forum PRODUCT RELATED DISCUSSIONS FILE & NETWORKING SERVICES Open Enterprise Server OES: Platform Independent OES: Client - Windows Error 8801. You can view the discussions, but you must login before you can post. Click the LOGIN link in the forum header to proceed. To start viewing messages, select the forum that you want to visit from the selection below. If this is your first visit, be sure to check out the FAQ by clicking the link above. Results 1 to 2 of 2 Thread: Error 8801. Thread Tools Show Printable Version Subscribe to this Thread… Display Switch to Linear Mode Switch to Hybrid Mode Threaded Mode Threaded View 10-Nov-2005,08:39 AM #1 Admin NNTP User Error 8801. Hi. I have computers that should be able to login to network with both lan and wlan connections. With lan connection everything works fine. However, when login with wlan no mappings are done in login script. Get error 8801 on every drive, but login is successful. Manual map works fine after the computer logs on. Could SLP be the problem? When will the PC get in contact with the DA? Should I use IP addresses instead of servernames in login script? Or is thee any other parameter I could use on the client to fix this problem? The reason why I dont want to use IP addresses is because we are running cluster services, and would be able to use failover. Reply With Quote « Previous Thread | Next Thread » Bookmarks Bookmarks Twitter Facebook Google Digg del.icio.us StumbleUpon Posting Permissions You may not post new threads You may not post replies You may not post attachments You may not edit your posts BB code is On Smilies are Off [IMG] code is Off [VIDEO] code is Off HTML code is Off Forum Rules Contact Us Micro Focus Discussion Forums Archive Privacy Statement Terms of Service Top All times are GMT +1. The time now is 11:37 PM. © 2016 Micro Focus
Business Suite Novell Clients Formerly TID 2937150 goal Documentation of 88xx error codes symptom What is the meaning of error codes returned on the client in the http://support.novell.com/docs/Tids/Solutions/10058471.html range of 0x8800 - 0x88ff (Decimal range from 34816 - 35071) fix This information is from SDK14, and is not necessary giving remedies, but just a 'developers' explanation of the error. 0x8800 https://www.suse.com/support/kb/doc?id=7016351 errors are returned by the local shell, i.e. the request has never been seen by the fileserver at all! Hex Dec Constant: Description 0x8800 0 SHELL_ERROR 0x8800 0 VLM_ERROR 0x8800 0 novell error ALREADY_ATTACHED: Attempted to attach to a server with a valid, existing connection. 0x8800 0 NWE_ALREADY_ATTACHED: Attempted to attach to a server with a valid, existing connection. 0x8801 1 INVALID_CONNECTION: Request attempted with invalid or nonattached connection handle. 0x8801 1 NWE_CONN_INVALID: Request attempted with invalid or nonattached connection handle. 0x8802 2 DRIVE_IN_USE: OS/2 only. (NOT USED). 0x8802 2 NWE_DRIVE_IN_USE: OS/2 only. (NOT USED). novell error 8801 0x8803 3 CANT_ADD_CDS: Attempted to map a drive but was unable to add a new current directory structure. 0x8803 3 DRIVE_CANNOT_MAP 0x8803 3 NWE_DRIVE_CANNOT_MAP: Attempted to map a drive, but was unable to add new current directory structure. 0x8804 4 BAD_DRIVE_BASE: Attempted to map a drive using an invalid path specification. 0x8804 4 NWE_DRIVE_BAD_PATH: Attempted to map a drive using an invalid path specification. 0x8805 5 NET_READ_ERROR: Attempt to receive from the selected transport failed. 0x8805 5 NET_RECV_ERROR: Attempt to receive from the selected transport failed. 0x8805 5 NWE_NET_RECEIVE: Attempt to receive from the selected transport failed. 0x8806 6 UNKNOWN_NET_ERROR: Network send attempted with a nonspecific network error. 0x8806 6 NWE_NET_UNKNOWN: Network send attempted with a nonspecific network error. 0x8807 7 SERVER_INVALID_SLOT: Attempted a server request using an invalid server connection slot. 0x8807 7 BAD_SERVER_SLOT: Attempted a server request using an invalid server connection slot. 0x8807 7 NWE_SERVER_BAD_SLOT: Attempted a server request using an invalid server connection slot. 0x8808 8 NO_SERVER_SLOTS: Attempted to attach to a server with no connection slots available 0x8808 8 NWE_SERVER_NO_SLOTS: Attempted to attach to a server with no connection slots availab
2 for Windows" / "Client for Open Enterprise Server" patches and fixes × × Sorry for the inconvenience Our new site design is only available in English right now. Go to the previous site to read in my language Stay here and read in English × Give Us Feedback Got some feedback about the website? Let us know so we can fix it. For support information, please visit Support. Sales:+972-54-314-33-64 Support:420-28-408-4051 Connect with us Feedback Form We adapt, you succeed. Read Privacy Policy Required Fields* X SUSE Support My Favorites Close Please login to see your favorites. Bookmark Email Document Printer Friendly Favorite Rating: History of "Novell Client 2 for Windows" / "Client for Open Enterprise Server" patches and fixesThis document (7016351) is provided subject to the disclaimer at the end of this document. Environment Novell Client 2 for WindowsClient for Open Enterprise Server 2 SP4 (IR4) Resolution The following is a list of published fixes for Novell Client 2 for Windows, most recent to oldest:Novell Client 2 SP4 for WindowsClient for Open Enterprise Server 2 SP4 (IR4)(16Sep2016):1. Applications may not see a truncated file as 0 bytes in length when File Caching is enabled. (Bug 994451)2. Unused portions of the application's read buffer could be written to when reading sizes greater than 64KB. SeeTID 7017908. (Bug 991544)3. Applications enumerating folders with a large number of files or subdirectories may omit some entries. SeeTID 7017895. (Bug 990529)4. Updated the Micro Focus logo mark and images to reflect updated corporate branding.(Bug 989796)5. Provided customization for system tray and shell extension icon using INSTALL.INI. SeeTID 7018057. (Bug 989780)6. Windows 10 Build 10240 (July 2015 TH1) or Build 14393 (July 2016 RS1) Secure Boot configurations fail to boot. SeeTID 7017838. (Bug 988795)7. After reboot, the system default logi