Connecting to NT 4.0 thru Novell

[bstites]

I'm probably making this harder than what it really is... sigh. I've just reinstalled NT on one of our servers and made it a PDC. All of our authentication (and email) is done thru Novell servers...so users connect there first... (and I know NOTHING about Novell). However, when users access their files on the NT server, I also want them to be authenticated with NT and follow the user account policies that have been set up. I can get access to the NT server by setting up a share by mapping a drive to it, but only if I set up passwords to NOT expire... which I don't want.

Also, I can see the Novell servers on the NT server, but I cannot see the NT server on any of the Novell clients (I don't have anything to do with administering the Novell servers). To connect the clients I have to enter the TCP/IP address in the folder name of "Map Network Drive"... I cannot see it thru Network Neighborhood... nor by using the Server Name.

I hope this makes sense. I'm at a loss as to where to go now. Thanks for your help! X-)

 

[Guest_imported]

You have a number of problems. First let's take a look at the Novell authentication on NT. There is a product called NDS for NT 2.0 which you load on the NT PBC and any BDC. I don't think Novell sells it any more and have moned on to a product called NDS Corporate Edition. I do use NDT for NT and it works quite well for account and password syncronization between NetWare and NT. I haven't use the NDS Corp. Edit. yet (got to bite the bullet some day. Hope it won't go off.) so I can't give you any hints on it. As with all Novell products, read as much as you can find about them first, as mistakes with them will bite you on the ass pretty bad.

Your second part of your problem sounds like you have not put the NT server in your DNS or WINS or HOST file. You need some reference to the server so the client can find it. This is a reference between it's common name (also know as the NetBIOS name), and it's IP address. If you don't have a DNS or WINS server running (and why not with a WINS server) then put a reference to the NT server in the HOST file located in C:\WINNT\system32\drivers\etc

It's pretty straight forward to modify the host file.

Good luck.

 

[Jpoandl]

What OS is the client machines using (Win9x,NT, 2k)?

An easy way to be able to authenicate to both NetWare and NT/2000 is load both clients on the client workstations. In other words, make sure that the Windows 9x/NT workstations have the Microsoft Client and the Netware client loaded. Configure the Microsoft client to log into an NT domain and configure the Netware client to log into the Netware tree.

The client would probably have to have more than one protocol loaded. This would depend on what protocols are being used in your environment. A few years back, Netware used IPX/SPX. The Microsoft version of this protocol is called NWLINK. However, more recently NetWare added support for TCP/IP. Microsoft prefered protocol is TCP/IP although many people still use NEtBUIe.

Hope some of this helps.. Joseph L. Poandl
MCSE 2000

 

[Jpoandl]

It sounds that your NT server already has both clients running. I say this because you indicated that you can see your NT and NetWare servers from the NT server. This server either simply has the NetWare client loaded on it....or it may have the GateWay services loaded on it.

If you provide more details about your environment, I'm sure we could help...

(If you load both client pieces on your client machines....then make sure that you enter a domain name on the client to log on to. Check LOG ON TO DOMAIN.) Joseph L. Poandl
MCSE 2000