This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Using Astaro v5 in a Netware Environment

I am working now for a college that uses Netware 6 and eDirectory (NDS) that uses LDAP. The college is looking for a new Proxy Server product as their Surf Control is about to expire.

The issue is that they need Astaro's proxy to link in with the eDirectory tree

Is this possible? Has anyone used Astaro and Netware 6 before? If so what are the issues?? If any?

Also where is the best place to obtain Astaro price info??

Cheers

This thread was automatically locked due to age.

Parents

0 VelvetFog over 21 years ago

Another alternative for connecting ASL and NetWare NDS together, is by running Novell's RADIUS server.

However, the Novell RADIUS server does not ship with NetWare. It can be found on Novell's BorderManager installation CD.
Cancel
Vote Up 0 Vote Down

Cancel
0 Mike_H over 21 years ago in reply to VelvetFog

Andy

Cheers for this. Do we have any info on getting the user authentication working? is it in the manual?
Cancel
Vote Up 0 Vote Down

Cancel
0 Simon Shaw over 21 years ago in reply to Mike_H

People still use Netware ???!!! [:O]
Cancel
Vote Up 0 Vote Down

Cancel
0 Mike_H over 21 years ago in reply to Simon Shaw

I know I was shocked when I started. I have only been here two weeks
Cancel
Vote Up 0 Vote Down

Cancel
0 ReD-MaN over 21 years ago in reply to Mike_H

Netware is still flying along ... I have used ASL in a Netware 6 environment.. but it was a while ago and since then have lost the docs on how I did it....it did work very nicely though.. pretty similar in setup as compared to ADS.
Cancel
Vote Up 0 Vote Down

Cancel
0 StephaneGROBETY over 21 years ago in reply to Simon Shaw

Actualy, I replaced our two Border manager servers with ASL and I can tell you that it really was a releife.

That being said, theonly point where Novell far surpassed Astaro was the VPN client: Until version 3.7 of the client, it was perhapse uggly, but it was easy to install by the end user and free (something you can't say about Astaro).
Cancel
Vote Up 0 Vote Down

Cancel
0 Mike_H over 21 years ago in reply to StephaneGROBETY

Fulgan

Have you still got notes on how you got the users on the NDS or eDirectory as they call it to auth with Astaro?
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Mike_H over 21 years ago in reply to StephaneGROBETY

Fulgan

Have you still got notes on how you got the users on the NDS or eDirectory as they call it to auth with Astaro?
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 StephaneGROBETY over 21 years ago in reply to Mike_H

The reason why I didn't explain how to connect Astaro to the NDS you the details is because I don't do it.

We've dropped Netware completely and BM was the last piece that used the NDS.

That being said, what exactly are you looking for ? What I've seen in the Astaro config is pretty straightforward LDAP syntax. I would fill in in the following way:

LDAP Type: Novell
Unique User Attribute: cn
IP address:
TCP port: 389
Bind DN: cn=, cn=Users, dc=yourcompany, dc=com
Base DN: dc=yourcompany, dc=com
password:

"" here should reference the user name of some Novell user authorized to make LDAP queries. The "Bind DN" parameter should be the complete LDAP path of this user. The Base DN should reference either your full domain or the full path of the branch where users authorized to log in are stored.

I hope it clarifies things for you
Cancel
Vote Up 0 Vote Down

Cancel
0 Mike_H over 21 years ago in reply to StephaneGROBETY

Cheers Fulgan
Cancel
Vote Up 0 Vote Down

Cancel
0 Brent_Gay over 20 years ago in reply to Mike_H

Also keep in mind that the ASL queries the LDAP directory in plain text. I ran into a situation where the Novel server was set to accept only TLS/SSL connections and it would not work. Check out this for more info.
Cancel
Vote Up 0 Vote Down

Cancel