Error Extendido 65
Contents |
von GoogleAnmeldenAusgeblendete FelderNach Gruppen oder Nachrichten suchen
Boot Disk Creation I'm ripping my hair out on this one, and if anyone can offer a suggestion, I'm all ears. I'm attempting to boot a Dell GXxxx workstation with Dos6.22 and the MS network client software, which is all properly configured to run TCP/IP with DHCP. It boots, starts up, and I have network access from the DOS prompt. I can use the NET USE command to map a drive letter to the NTFS share I established on my 2K3 server. The user account was created especially for this and granted full control https://groups.google.com/d/topic/microsoft.public.win3x_wfw_dos/pLbEG2xfRYk to the share, and the directory. I map the drive, change to it, and I can see the contents by typing DIR. I can even successfully execute programs from the share. When I try to write to the share, however, I get EXTENDED ERROR 65, which Googles out to mean network access denied. I've tried different shares, I've tried different user accounts, I've even tried mapping a http://www.itninja.com/question/boot-disk-problem-error-65 share on my production box. Everything I've tried has worked exactly as I expected, with the exception of the Extended Error 65. To further debug this, I've tried several different models of Dell GX (260, 270, 280) all with the same results. Can anyone here recommend or suggest a step I may have missed, or a spot to look? Thank you so much. You can email me direct at mark.weston@telus.com or weston54@yahoo.com, or even call (416) 279-7518. Thank you very much, and have a super day. Mark Weston 0 Comments [ + ] Show Comments Comments Please log in to comment Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable. Answers 0 I know you said you set full access for your share, but have you gone back to double check your effective permissions? Default share perms on 2000 server are full/everyone, but not so on 2003. Craig --<>. Answered 05/26/2005 by: craig16229 Please log in to comment Please log in to comment Answer this question or Comment on this question for clarity AnswerSubmit Don't be a Stranger! Sign up today to participate, stay informed, earn poin
a mounted filesystem http://support.novell.com/docs/Tids/InfoDocument/1002350.html to the screen or copying a file from a mounted filesystem (E:) to a workstation drive (C:), a flashing cursor will appear on the screen. To get back to the DOS prompt from this state, the ctrl break keys needs to dos error be hit. Then, the message " read fault error reading drive e: " appears on the screen. When attempting to copy a file from a local drive (C:) to a mounted filesystem (E:), instead, the error message " extended error 65, dos error codes 0 files copied " appears. Solutions Setting the /R and /W parameters to 1024 from 4096 on the LWPNFS.COM driver in the AUTOEXEC.BAT resolved the problems. document Document Title: Read fault error or Extended error 65 Document ID: 1002350 Creation Date: 25Mar1995 Modified Date: 02Jul1995 Revision: 1 Novell Product Class:End of Life (EOL) 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.