|
Home > Archive > CNE > November 2002 > network+ student needs help
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
network+ student needs help
|
|
| thecomeons 2002-11-19, 2:14 pm |
| okay, so maybe this isn't the correct forum, but i just fancied getting the answer from people who may have had actual experience with netware than those studying network+.
okay, this is what i believe to be true, so correct me if i'm wrong.
win9x uses microsoft client for netware networks and it only works with nwlink (m$ ipx/spx compatable protocol) and needs to use novell's client32 to use tcp/ip and nds from the netware server.
winnt uses client services for netware which only works with nwlink and needs client32 to use tcp/ip and nds from the netware server.
with win2k i am stuck. i assume it is the same as winnt, but i would like to think that m$ would have come up with a newer version of the nt client that could access netware's tcp/ip and nds.
am i wrong?
thanks in advance. | |
| darthw 2002-11-19, 4:17 pm |
| Per the Microsoft knowledgebase article number 222059:
quote:
Both GSNW and CNSW require the IPX protocol for connectivity to NetWare networks because until recently, the IPX protocol was necessary for connectivity to NetWare resources. NetWare 5 provides support for native IP. GSNW and CSNW were written prior to the release of NetWare 5.
So, preferably, you would want the latest version of the Novell Client to access Netware on IP and NDS, or eDirectory.
Without doing any research to verify my answer, I'm pretty sure you cannot access NDS using the Microsoft Client for Netware, rather you have to have the Novell client. I believe the Microsoft Client for Netware will only allow IPX mode to a specific server, rather to the Bindery, or a server running Bindery Services. I'm not sure on this for W2K or XP as I have had limited exposure to these in a Novell environment thus far. |
|
|
|
|