Does the OES client support IPv6? We are about to move our environment over to IPv6 but we still use the OES client on Windows WS to access NSS shares on OES2018 servers. Is there any problem with the OES client working on top of IPv6?
Just for my own information, does this mean you are also disabling IPv4 entirely? I've seen environments with both protocols and not noticed any problems, but that could easily be because everything was also using IPv4 as needed.
-- Good luck.
If you find this post helpful and are logged into the web interface, show your appreciation and click on the star below.
If you want to send me a private message, please let me know in the forum as I do not use the web interface often.
In article <firstname.lastname@example.org>, Dchunt wrote: > Is the idea to do away with the OES client and use CIFS instead for > Windows WS connecting to an OES 2018 server?
I wouldn't say that as all the hooks supporting IPv6 appear to be there. I think it is something that just needs to be testing, and of course it would be nice for something official on that support of IPv6 and in looking for that I see IPv6 support going back over 13 years ago on NetWare for NCP, but strangely nothing on the topic of IP versions in the current docs. I will do some prodding. In the mean time, has anyone actually played with it? Certainly this would be easy to test some in a lab where all IPv4 is removed.
> Is the idea to do away with the OES client and use CIFS instead for > Windows WS connecting to an OES 2018 server?
The plan is not "you must drop Client for Open Enterprise Server and use CIFS access", although we do indeed want the CIFS access to also be an option for achieving the networking goals of your business.
Truthfully I do not know which if any of the CIFS access options (Novell CIFS, SAMBA, Domain Services for Windows, etc.) support IPv6 at this time. Someone more familiar with OES Server and the CIFS services would have to confirm that point.
Currently the hard-stop limitation for Client for Open Enterprise Server is that NCP does not support IPv6 at this time. Many things about OES and the underlying SLES platform do support IPv6, of course. (LDAP, DNS, the TCPIP stack itself, etc.)
But neither "NCP" nor "NCP access to eDirectory" have IPv6 support at this time. Therefore neither does the Client for Open Enterprise Server support NCP or NCP access to eDirectory over IPv6 at this time.
Although IPv6 for NCP and NCP access to eDirectory has been acknowledged on the OES roadmap for several years, it has not been committed to have any implementation target date yet.
In article <email@example.com>, Alan Adams wrote: > Although IPv6 for NCP and NCP access to eDirectory has been > acknowledged on the OES roadmap for several years, it has not been > committed to have any implementation target date yet.
Perhaps time to push this a bit more now as the world keeps shifting towards IPv6
Dan, since you are closer to a customer who is wanting to go this way, how about creating the Idea and posting it here so that we can all vote for it, that customers are actually starting to move that way. https://ideas.microfocus.com/MFI/novell-oes/