|
|
|
| My network currently consists of 400 client computers and 6 servers. Half of the client computers are NetWare clients and the other half are Windows NT clients. 1 of the 6 servers is running Windows NT Server 4.0. All of the other servers are running NetWare 3.12. Currently, none of the NetWare clients can access the Windows NT server.
What soultion should I implement to allow the NetWare clients to access resources on the Windows NT servers?  | |
|
|
| Tech Ranger 2003-12-16, 5:35 am |
| What do you mean by Netware Clients? | |
| azimuth40 2003-12-16, 3:07 pm |
| quote:
Originally posted by Tech Ranger
What do you mean by Netware Clients?
Windows server calls them CAL's. Traditionally a Client was a TSR or equavalent VxD that allowed you to hook to a Netware server. In DOS it used to be in the autoexec.bat file. Microsoft origially wrote their own for windows because they thought Novell was taking too long and trying to punish or take unfair advanatage of them. Imagine that. 
There are Netware clients for each type of OS that can hook to netware so basically client means computer as in the term client/server architecture. FPNW lets Windows Servers understand the systems logged onto Netware as their primary server.
Adding Netware into a forrest is not the right term FPNW kind of lets Windows Server emulate a Novell Server. | |
| Tech Ranger 2003-12-16, 8:28 pm |
| quote:
Originally posted by azimuth40
Windows server calls them CAL's. Traditionally a Client was a TSR or equavalent VxD that allowed you to hook to a Netware server. In DOS it used to be in the autoexec.bat file. Microsoft origially wrote their own for windows because they thought Novell was taking too long and trying to punish or take unfair advanatage of them. Imagine that.
There are Netware clients for each type of OS that can hook to netware so basically client means computer as in the term client/server architecture. FPNW lets Windows Servers understand the systems logged onto Netware as their primary server.
Adding Netware into a forrest is not the right term FPNW kind of lets Windows Server emulate a Novell Server.
I know that. He seemed to be using the term as if a Novell Client is an OS. He wants to connect his "Novell Clients" to his NT Server. This is what doesn't make sense to me. If he has a MAC OS or a Windows OS ws, why use the Novell redirector to access NT resources? That is why I asked what he means by a Novell Client. The scenario doesn't make sense. | |
| azimuth40 2003-12-17, 1:55 am |
| quote:
Originally posted by Tech Ranger
I know that. He seemed to be using the term as if a Novell Client is an OS. He wants to connect his "Novell Clients" to his NT Server. This is what doesn't make sense to me. If he has a MAC OS or a Windows OS ws, why use the Novell redirector to access NT resources? That is why I asked what he means by a Novell Client. The scenario doesn't make sense.
I am rusty on the history now but I believe it is because access is not bi-directional. I believe it works like this but I could be wrong. Log into a windows server first as your primary connect and with the windows client for netware you can see both types of resources. However if you use the software from Novell and log into a Novell server first then you cannot see Windows resources. Microsoft's solution was to make the Windows servers look like Novell servers so that the Novell supplied software is fooled.
Novell uses their client to forcefully limit the number of systems that can connect. As I recall part of the fight was that when Microsoft wrote their own it circumvented Novell's logon limit security. They kind of placed obstacles in each others way until Microsoft did the emulation thing.
It has been a long while since I have been at that level with Windows and Novell so if I am wrong maybe someone will correct the paths. I think that the problem is that it is such an old version of Netware. Newer versions may more peacefully co-exist |
|
|
|