can any one explain how i connect NT server 4 to Novell version 4.11. I was told to Install NDS4NT. As I am a beginner I have no Idea where to start. Lawnboy gave the answer but do not know how to contact him. Any help would be gratefull and a contact address if I can not understand the Instruction or get stuck.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
How to Connect NT to Novell
- Thread starter printer1
- Start date
Gateway Service for NetWare (GSNW). Included with Windows NT Server, GSNW lets Windows NT Server act as a gateway to a NetWare network, allowing you access to all the resources on a NetWare server. Windows NT Workstation-based clients can access NetWare resources using TCP/IP, the native network communication protocol for Windows NT. In addition, GSNW allows Windows NT Server-based network clients to access files on a NetWare server without requiring a NetWare client redirector on an IPX/SPX protocol stack (such as NWLink). . These efficiencies reduce the administrative load for each client and improve network performance.
GSNW also supports Novell's NetWare Directory Services (NDS) navigation, authentication, printing, and login scripts. This support allows NetWare clients to take advantage of the Windows NT Server platform and still retain fully functional access to their NetWare 4.x servers via the Windows NT Server gateway. Lastly, GSNW lets a machine running Windows NT Server act as a communications server to a NetWare network, re-sharing the network connections from the NetWare server. So, for example, you can use Windows NT Server Remote Access Service to access NetWare server resources.
U can add this service from network properties and then u have to make trust between both the servers by assgining an account to act as a trust account.
GSNW also supports Novell's NetWare Directory Services (NDS) navigation, authentication, printing, and login scripts. This support allows NetWare clients to take advantage of the Windows NT Server platform and still retain fully functional access to their NetWare 4.x servers via the Windows NT Server gateway. Lastly, GSNW lets a machine running Windows NT Server act as a communications server to a NetWare network, re-sharing the network connections from the NetWare server. So, for example, you can use Windows NT Server Remote Access Service to access NetWare server resources.
U can add this service from network properties and then u have to make trust between both the servers by assgining an account to act as a trust account.
LawnBoy
MIS
- Mar 12, 2003
- 2,881
Best place to start would be They have an excellent support knowledge base there, fully searchable. I personally have not used NDS4NT, but I know several SysAds who have with good results.
Don't know about GSNW, but I hesitate to use MS-ware anywhere near my Novell tree. BTW, NetBeui is the "native" network protocol for NT.
There is a "Novell: Netware 5" discussion group here on Tek-Tips with some great expertise. I know you're running NW4, but you can probably get your questions answered there.
I would have answered sooner if you had replied to my post...
Don't know about GSNW, but I hesitate to use MS-ware anywhere near my Novell tree. BTW, NetBeui is the "native" network protocol for NT.
There is a "Novell: Netware 5" discussion group here on Tek-Tips with some great expertise. I know you're running NW4, but you can probably get your questions answered there.
I would have answered sooner if you had replied to my post...
nds4nt has been replaced by account management
been along time since i've played with netware 4.11 but the nds4nt is pretty straight forward and means that all your nt accounts and netware accounts are syncronised and you can also connect to whatever shares you need on the nt boxes through the netware script. i current run account management 2.1 on netware 6.
gnsw is very ltd as it's really just one connection that everyone is piggy backing on to. it also doesnt really recognise nds - it makes and utilises a bindery connection and is limitied to ipx (not a prob in 4.11 as it's really stuck in ipx land as well but for 5 and 6 you want ip only)
if you install nds4nt on -
then verify ds is in healthy state and everything is in time sync
install onto pdc - MAKE SURE YOU DONT put a repica onto the nt server - if you do i would remove replica from this
install onto all bdc's
20 mins later your finished
go into nwadmin - create a user or go to existing user and you will see domain access and then you add them to nt groups - and if user doesnt exist in nt it will create him with these groups
been along time since i've played with netware 4.11 but the nds4nt is pretty straight forward and means that all your nt accounts and netware accounts are syncronised and you can also connect to whatever shares you need on the nt boxes through the netware script. i current run account management 2.1 on netware 6.
gnsw is very ltd as it's really just one connection that everyone is piggy backing on to. it also doesnt really recognise nds - it makes and utilises a bindery connection and is limitied to ipx (not a prob in 4.11 as it's really stuck in ipx land as well but for 5 and 6 you want ip only)
if you install nds4nt on -
then verify ds is in healthy state and everything is in time sync
install onto pdc - MAKE SURE YOU DONT put a repica onto the nt server - if you do i would remove replica from this
install onto all bdc's
20 mins later your finished
go into nwadmin - create a user or go to existing user and you will see domain access and then you add them to nt groups - and if user doesnt exist in nt it will create him with these groups
- Status
Similar threads