Both Samba and IBM LAN use net.exe as 'major' command. This needs to be fixed somehow.

[Silvan Scherrer]

A solution could be to create a wrapper net.exe that analyzes the parameters passed to it and select which net.exe was intended based on that. Hardly foolproof, this could be sort of a fix for many of the annoyances.

Another solution would be to simply rename the Samba version of net.exe (which would at least break the documentation)

One way or the other, this problem needs to be resolved.

[Silvan Scherrer]

it's not decided who has to do the workaround. we might look at that issue somehow in the future, but it has absolutely no priority

[Herwig Bauernfeind]

As people who install Samba (either server or client) hardly will be interested in IBM net.exe I'd suggest to do a check in the Samba installers to detect whether IBM net.exe is found in PATH before Samba net.exe and if so rename IBM net.exe to ibmnet.exe. Alternatively a simply warning abut the situation could be thrown.

On the other hand renaming Samba net.exe would be awful lot of work in GUI tools and scripts, so I am not willing to to this. Note however, that neither scripts nor tools rely on PATH to find their net.exe (they will take it from the very same directory where smbd.exe (server wise) and smbclient.exe (client wise) is found.

So having the Samba directory added to the end of the PATH will eliminate most problems.

[Silvan Scherrer]

this will be solved as soon as we have the rpm version of samba. in latest rpm was a scheme for duplicate names introduced.