Networks·41,469 discussions

NDS Citrix Metaframe Login

Locked

Newly created users can no longer get an NDS connection to our Netware 5 server through GSNW. This was working fine before, but now the only available way to log into Netware is via Preferred Server. Since the server is in a different container thanmany of the users, we can’t log them into Netware at all (since GSNW doesn’t see the other containers in bindery mode). We aren’t using Client 32 for NT and have no plans to since it has worked fine without it in the past.

Topic

NDS Citrix Metaframe Login

In reply to NDS Citrix Metaframe Login

Try adding a bindery context on your server to the container where your users are. You can use servman, edit autoexec.ncf, or type from the server prompt to change the bindery context. You can have multiple bindery contexts. Example for setting from server prompt, use semicolon to separate contexts.

SET BINDERY CONTEXT = OU.OU.OU.O;OU.OU.O

NDS Citrix Metaframe Login

In reply to NDS Citrix Metaframe Login

NDS Citrix Metaframe Login

In reply to NDS Citrix Metaframe Login

A neat solution to this is to implement Novells NDS eDirectory (formerly NDS4NT). By doing this you get full NDS-support and may administer the domain from NWADMIN. You don’t have to think about binderycontexts or use that somewhat limited GSNW. Costly? Yes, but very usefull in a mixed NT and Netware enviroment. We use it at several customers, low TCO and high performance, leaving the IT-dept. time to do what they are supposed…

Good luck

/Magnus

NDS Citrix Metaframe Login

In reply to NDS Citrix Metaframe Login

I found the solution from Microsoft’s site. Seems like creating users through NWADMIN on a workstation with Client 3.2 caused the problem. It’s solved. Thanks anyway.

[Author]

Replies