×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




Mark,
the name of the userprofile must match the name of that user in Win9x / NT
either locally or in the domain, if there is one.
I meant this match, when talking about "synchronising", this is a manual 
process.
There is no "additional" logic like a second name for this purpose ...

Regards from Germany, Philipp

P.S.: IF you had an NT domain controller AND win nt integration on your
AS/400, THEN you could enroll AS/400 users in the domain user database
automatically. But this is another story, if you are interested ...  :-)

"M. Lazarus" schrieb:

> Philipp,
>
> At 6/7/02 05:06 PM, you wrote:
> >the network client code of  Windows 9x and ME always uses the
> >username of your first login to the machine/network itself to authorize
> >on further connections. There is no way to change this behaviour, you
> >cannot supply a different username to connect to another (netbios-) resources
> >like you were able with Win NT or W2K.
> >You got to synchronize your usernames on the windows machines with
> >the names on the AS/400.
>
>   Is there an additional user ID / password when connecting via Netserver
> or do the usual *USRPRF's apply?
>
>   -mark
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.