Member Avatar for johnroach1985

Hi there. In a day I have to connect to a lot of networks and each network has its own setting. Each time I have to re-configure my Windows Vista Home Edition IP confiugrations which is both slow and quite annoying. Thus I decided to write a program in C# (since it is the easiest programming language ever! :) ). So the way it will work is that; I will right click an icon on my icon tray. There there will be a "add connection setting" button. From there I will be able to create a connection setting with its IP,DNS (primary and secondary),Gateway and subnetmask settings. And if I ever need to switch to that connection I will only need to right click and choose the connection settings.

Now to the problem I face; How do I change these settings in Vista through C#? And how do I make sure I don't get some "permission" problem? And what will be the best way to store these settings?


I thank you for your help in advance
Cheers!

  • 3 Contributors
  • 3 Replies
  • 359 Views
  • 7 Hours Discussion Span
  • Latest Post Latest Post by johnroach1985

Dani AI

Generated

Two practical routes for automating IP/DNS/gateway/subnet switching on Vista are WMI (managed) and invoking netsh (command-line). and rightly pointed to existing examples; the notes below clarify trade-offs, privilege handling, profile storage, and quick troubleshooting so the solution works reliably for 's tray-menu workflow.

WMI (System.Management + Win32_NetworkAdapterConfiguration) is the most direct managed approach: identify the adapter (by Index or Description), set static address/gateway/DNS via the relevant methods, and check returned status codes. Advantages: fine-grained control and single-process managed code. Caveats: calls require administrative privileges, the WMI service must be healthy, and adapter identifiers must match exactly. Implement retry logic and check return codes; a brief connectivity disruption during apply is normal.

Invoking netsh from an elevated process is simpler to implement and easy to debug from a shell. Example netsh commands (illustrative):

netsh interface ip set address "Local Area Connection" static 192.168.1.50 255.255.255.0 192.168.1.1 1
netsh interface ip set dns "Local Area Connection" static 8.8.8.8

Run netsh elevated from C# with ProcessStartInfo and Verb = "runas" (UseShellExecute = true) so UAC prompts for elevation when needed.

Privilege and storage recommendations: require Administrator via manifest for the applying process or implement a small elevated helper/service to perform changes. Store profiles as JSON or XML under %LocalAppData%\AppName for per-user profiles or %ProgramData%\AppName for machine-wide profiles (avoid writing to Program Files at runtime). Include a “revert to DHCP” profile and validate results with an ipconfig check after changes.

Quick troubleshooting checklist: confirm exact adapter name or index, ensure WMI service is running, log WMI return codes and netsh stderr, test changes in a VM or spare machine, and always provide an undo path to restore connectivity.

Recommended Answers

All 3 Replies

Member Avatar for privatevoid

Is this of any use to you?

Member Avatar for johnroach1985

Thank you all.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.