iliriyan
asked on
programing
Disabling a NIC
how to disable a nic interface by a small program written on any programing language
probably a small script or so
how to disable a nic interface by a small program written on any programing language
probably a small script or so
Rather vague, doncha know? How's about:
Answer: Call ShutDown
Answer: Call ShutDown
(note also, platform dependencies involved)
This can often be done at the hardware level, but that is NIC dependent, i.e., the method to disable will vary widely.
Doing it in software is OS dependent. Even within the Windows family, the method of disabling varies.
Do you want to do this for a particular box or for whatever box the program is running on, regardless of NIC model and OS?
Doing it in software is OS dependent. Even within the Windows family, the method of disabling varies.
Do you want to do this for a particular box or for whatever box the program is running on, regardless of NIC model and OS?
ASKER
in a box where the program will shutdown and start the NIC
on OS windows.
on OS windows.
> in a box where the program will shutdown and start the NIC on OS windows.
This is generally not available where requirements involve heterogenous Windoze environments. Namely, before the Windows UI is sufficiently stable for user access, the stack (including NIC) also has to be stable, a networking prerequisite if you will. Thus, all the times peole experience messages such as "you must shutdown (or restart) computer to complete the process". Even newer OS, where there are times that the messagebox does not appear, there are substantial networking needs that still require the reboot (not just a logoff) to complete the rebuilding process.
Depending on application need, this is possible, where several restrictions can be applied to requirements. But in general, not all that feasible. Also has many OS dependencies, so any desire for cross platform compatibility must head to back-burner.
This is generally not available where requirements involve heterogenous Windoze environments. Namely, before the Windows UI is sufficiently stable for user access, the stack (including NIC) also has to be stable, a networking prerequisite if you will. Thus, all the times peole experience messages such as "you must shutdown (or restart) computer to complete the process". Even newer OS, where there are times that the messagebox does not appear, there are substantial networking needs that still require the reboot (not just a logoff) to complete the rebuilding process.
Depending on application need, this is possible, where several restrictions can be applied to requirements. But in general, not all that feasible. Also has many OS dependencies, so any desire for cross platform compatibility must head to back-burner.
> "program will shutdown and start the NIC"
Answer: Call ShutDown /Restart
Answer: Call ShutDown /Restart
ASKER
does not works mate
?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
not bad
i have don it
with one two three and go
i have don it
with one two three and go
? (thanx)
Good Fortune! :)
Good Fortune! :)
ASKER