NT Service 1.5 Bug - FS231 Errors (Networking Products)
At 19 APR 2000 08:54:45AM [url=http://www.sprezzatura.com" onMouseOver=window.status=Click here to visit our web site?';return(true)]The Sprezzatura Group[/url] wrote:
After hours chasing down an inability to log into AREV/OI due to an FS231 error we were able to establish that the NT Service only uses the first 12 letters of the share name in attempts to communicate. If your share name is ] 12 characters attempts to connect will fail with an FS231 error.
The fix is simple - rename your share if corporate policy allows. If it doesn't then wait for a bug fix…
World Leaders in all things RevSoft
At 19 APR 2000 10:36AM Stephen S. Revelation wrote:
Sprezz Group,
It's true. I have put this 'bug' into our SPR (Software Problem Report, for the unaware) database.
-Stephen
At 28 APR 2000 05:33PM Darrell Latta wrote:
Thanks for the hard work Sprezz Grp (and sharing the results of course). This was the Exact problem of a previous post of mine. After reading your entry, changed the length of the share name and everything worked perfectly.
Interesting note, when mapping my drive under Win98 (while I was testing) it even warned me the some DOS products may not work if I proceeded with the mapping sharename of greater than 12 characters. Guess we should actually heed these little warnings from time to time.
Thanks again!!
Darrell…