9 replies
by shanghai sam
by pierrejamme
by shanghai sam
by dlafrombois
This first answer is completely wrong. In fact Microsoft requires unique CAL's for each of their products, irrespective of where they run. For example, a Exhanger server requires (1) cal for exchange and (1) for NT/2000. However, I believe that if you use NT, 2000, or XP clients they include an NT license.
What Answer #1 was referring to was a product Novell sells called Netware for NT. This product enable your Novell users to be authenticated to the NT domain without managing two different users accounts.
by shanghai sam
by erikdr
Well, back to basics.
1) If you want to use NT as file server (not appserver), then indeed individual connections from workstations would be the first that come to mind. And with all Windows versions, they DO require separate CAL's - they aren't included in the purchase of NT, W2K etc.
Note that you'd have separate userid/password for NT apart from NW5!
2) Indeed answer 1. replies to the wrong question - the Novell client for NT is a _client_ and does not allow NT shares to be published on NetWare. However the trick itself can be done, with a tool called NDS for NT. With this one, NT shares can be integrated with NDS and can be mounted on the Novell server. (Which then saves you the Microsoft CAL's). However this mounting is badly documented and not the main reason for using NDS for NT (that is for integrating appservers and single signon). The other way round, NT as the main server and itself mounting NetWare volumes, is done more frequently - it uses Microsoft GSNW. However it istricky with read-write traffic, sometimes the cache on NT gets updated and the NW master not yet.
Hope this helps,
- The Netherlands
by shanghai sam
by ldc6205
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending