DOS, IPX & NW6

spara

unread,

Oct 31, 2003, 7:58:27 PM10/31/03

to

Just upgraded from NWSB4.2 to SBS6. Have similar problem to JeffB in earlier
post.
In NW4.2 we used to be able to logout and login from a DOS window in WIN98.
We used this for automated logging in and running batch files at night for
various file maintenance work.
With NW6, once logged out, we can't login from a DOS window. DOS report F:
as invalid drive.
If workstation is logged in via Windows, then it is possible to login from a
DOS window as another user.
I don't think it is a rights issue since even Admin cannot login.
There was a mention about the SYS volume being NSS which it is but I am able
to login if a user is already logged in as I explained.
Any thoughts ?

Joe

Sandy

unread,

Oct 31, 2003, 8:50:06 PM10/31/03

to

Joe, this looks like it is a rights issue.

Make [Public] a trustee of Sys:Login with Read and File Scan [RF] rights,
and it should be fine.

BTW this 'problem' first appeared when people added Long name space to the
Sys volume (for example if starting to use Java on NetWare 4.11).
NetWare internally allowed [Public] access to Sys:Login if the client was
using DOS name space to access the Sys volume.
I don't think this internal 'exception' is even in NSS.

-Sandy

"spara" <!@!.!> wrote in message
news:TyDob.1768$kW3...@prv-forum3.provo.novell.com...

Joe G

unread,

Nov 3, 2003, 7:11:12 PM11/3/03

to

Thanks Sandy
That did the trick
On NW4.11 I had long name space on the SYS volume but did not have this
problem
Joe

"Sandy" <Sandy@_No.Spam> wrote in message
news:ijEob.1763$5N5...@prv-forum2.provo.novell.com...

Sandy

unread,

Nov 4, 2003, 8:29:47 AM11/4/03

to

Glad to help.

I first saw this problem on NetWare 4.11 with Windows NT 4 Workstations.

The only reason I can think of why it wasn't a problem for you is if you are
using Windows 9x, since that is really DOS (unlike NT), and always uses DOS
namespace in a DOS window.

-Sandy

Barry St.John

unread,

Nov 6, 2003, 10:31:12 AM11/6/03

to

In article <A8Cpb.3019$5N5...@prv-forum2.provo.novell.com>, Joe G wrote:
> On NW4.11 I had long name space on the SYS volume but did not have this
> problem

It's nothing to do with the name spaces. It has to do with NW6 not
automatically assigning rights to SYS:LOGIN the way previous versions of
NetWare did. That's because NetWare 6 doesn't support a DOS client
(officially) so there no need for those default read and find rights to
SYS:LOGIN.
--

-Barry. [Novell Support Forum SysOp]

Sandy

unread,

Nov 6, 2003, 5:49:46 PM11/6/03

to

Hi Barry,

it kind-of-does. The old Sys:Login exception (and it was not a real trustee
assignment) was only in the traditional file system and only if using DOS
name space.

As you said because the DOS clients are no longer officially supported, that
exception was never put in the NSS code, and since NW6.x allows Sys to be an
NSS volume, we can get this situation with old DOS clients.

Still, an easy fix to add the right trustee to Sys:Login.

-Sandy

"Barry St.John" <Chicago...@CompuDONTServeBUGME.com> wrote in message
news:VA.000013a...@compudontservebugme.com...

Barry St.John

unread,

Nov 7, 2003, 3:15:04 PM11/7/03

to

I understand that, but NSS is not a name space. Joe's comment was with
regard to long name space, which has nothing to do with the SYS:LOGIN
rights.

Sandy

unread,

Nov 7, 2003, 9:43:24 PM11/7/03

to

Yeah, that was because I went on about history with NW4.11, NT clients and
why this also happened when long name space was added to the Sys volume on a
NW4.11 server.

-Sandy

"Barry St.John" <Chicago...@CompuDONTServeBUGME.com> wrote in message

news:VA.000013b...@compudontservebugme.com...