lanmanserverdrivers are up and running.
hdwwiz.exeThe Hardware Wizard will come up:
lanmanserverdriver for all interfaces. By delaying the startup of the
lanmanserverdriver and by installing a
portproxyrule we can circumvent this. This section explains how to do this:
sc config lanmanserver start= demandNOTE the space after the
portproxyrule to reroute TCP port 445 to a port of our choosing. For this tutorial, I choose 44445:
netsh interface portproxy add v4tov4 listenaddress=10.255.255.1 listenport=445 connectaddress=10.255.255.1 connectport=44445IMPORTANT NOTES:
listenaddressis the address of the Loopback adapter configured in the section earlier
connectaddressmust be identical to the
listenaddress=127.0.0.1does not work. Believe me, I've tried.
portproxyrule is persistent, so there should be no need to repeat this step after a reboot.
portproxywas applied successfully by checking the open ports on the system. Type in the command console
netstat -an | find ":445 "You should see something like
TCP 10.255.255.1:445 0.0.0.0:0 LISTENINGIf you see '
0.0.0.0:445' instead then the 'portproxy' rule was not applied correctly.
sc query smb sc query lanmanserverThe 'SMB' and 'LanmanServer' drivers should be in the state Running. If they are not, then follow these steps to create a task using the Task Schedule to start them at system startup.
portproxymethod: it is no longer possible to use local shares on the computer while this rule is active.
login.nikhef.nl. Choose host login2.nikhef.nl and protocol SSH.
login2.nikhef.nland press OK.
login.nikhef.nland press OK.
smbdriver by typing
sc config lanmanserver start= autoNOTE the space after the
portproxyrule by typing
netsh interface portproxy delete v4tov4 listenaddress=10.255.255.1 listenport=445
Device Managerby typing
devmgmt.mscExpand the 'Network Adapters', right-click on Loopback adapter and select Uninstall.