SOSS may fail to bind to the network sockets it requires to to its NFS Kernel drivers.
This can be resolved by opening the device manager, under view, select show hidden devices, under Non-Plug and play drivers, locate and disable nfssvr and rpcxdr.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
sorry...
**SOSS may fail to bind to the network sockets it requires when the Windows 2003 SR2 NFS service has been installed
This can be resolved by opening the device manager, under view, select show hidden devices, under Non-Plug and play drivers, locate and disable nfssvr and rpcxdr.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It's no start on Win2003
Send message
H:\>sossnt.exe -console
SOSS v3.4 3 Mar 93 (compiled Jan 22 2006)
Starting net services at Fri Apr 13 09:38:38 2007
starting port mapper
starting mountd daemon
bind() failednet daemon error: mount daemon
P.S. WinNFSd not start also
SOSS may fail to bind to the network sockets it requires to to its NFS Kernel drivers.
This can be resolved by opening the device manager, under view, select show hidden devices, under Non-Plug and play drivers, locate and disable nfssvr and rpcxdr.
sorry...
**SOSS may fail to bind to the network sockets it requires when the Windows 2003 SR2 NFS service has been installed
This can be resolved by opening the device manager, under view, select show hidden devices, under Non-Plug and play drivers, locate and disable nfssvr and rpcxdr.
You can also run soss as
sossnt.exe -console -vvv
to get additional debugging information