S
Sailor
Guest
I am trying to disable loopback adapeter with a shutdown script. It appears
that when the script is running the network adapter is not found or it
doesn't even disable it. I can enable and disable the adapter without any
problems when I have not requested a shutdown. It appears that the network
adapter information is all "gone" and not available anymore when the OS
shutdown / reboot routine has started.
Is there some other place I can to get this accomplished earlier before the
network information is gone?
e:
cd \jobs\reboot
date /t >reboot.txt
time /t >>reboot.txt
echo disabling loopback>>reboot.txt
netsh interface set interface "LoopBack" DISABLED
This is Windows 2003 SP2.
The reason we do this is because during startup the network metric is not
correct, making it not available on the backbone (it has another connection
to the ineternet). We tried changing network order, but this has no effect.
So, if there's another option,I'd like to hear it (we're not allowed to hard
code a metric in).
that when the script is running the network adapter is not found or it
doesn't even disable it. I can enable and disable the adapter without any
problems when I have not requested a shutdown. It appears that the network
adapter information is all "gone" and not available anymore when the OS
shutdown / reboot routine has started.
Is there some other place I can to get this accomplished earlier before the
network information is gone?
e:
cd \jobs\reboot
date /t >reboot.txt
time /t >>reboot.txt
echo disabling loopback>>reboot.txt
netsh interface set interface "LoopBack" DISABLED
This is Windows 2003 SP2.
The reason we do this is because during startup the network metric is not
correct, making it not available on the backbone (it has another connection
to the ineternet). We tried changing network order, but this has no effect.
So, if there's another option,I'd like to hear it (we're not allowed to hard
code a metric in).