How to Enforce Static IP address for all user accounts including guest

On my computer I need to have a guest account. The problem is that other computers on this network connected to the internet via my computer so my computer needs to have static IP address of 192.168.0.1 but when Guest account is logged in my system forgets the static IP address I have set in my other admin account. I am not even sure that LAN is connected when the Guest account logs in.

My admin account is logged in and locked so I suppose all programs and settings there should still be working.

How do I make sure that my ethernet settings are working the same way for guest account too. I am not worried about Guest account being able to access the local network.

Devices get IP's not accounts!!

192.168.0.1 is usually a default gateway address not a machine address...unless you've changed you modems configs around?

192.168.0.0 is your LAN Network Address
192.168.0.1 is your Default Gateway Address.
192.168.0.2 would be the 1st available IP assigned by your modem (DHCP)

You say other machines connect through yours to access the net??
Expand on that please.

here is the scenario

We have three computers

connected with a router.

One of the computer accesses the internet with an EVDO USB Wireless Modem.

That computer has the ip address 192.168.0.1 because it acts as the default gateway for all other machines on the computer. Other machines have automatically assigned ips like 192.168.0.2, 192.168.0.3

Now the first machine with the internet access needs to have its ip fixed or else other computers will not be able to access the internet. However the problem on that machine is that it has a guest account. When the guest account logs in the network access disconnects. Even though the admin ID is still logged in on the machine and locked.

Now I want to set up that no matter which account logs in or whatever happens. the static ip address for that machine remains the same all the time.

Well I'm not exactly sure how the wireless modem is configured (through windows or through proprietary software), but when the connection's alive you should still see it in the network and sharing center through windows. This is what you would do:

When the connection is live
1. Start>(search for)"sharing">click "network and sharing center" from the results>in new window, click "change adapter settings" from the left pane
2. Find the EVDO USB connection, right-click and hit properties
3. Click on the networking tab, and click "internet protocol version 4 (tcp/ipv4)
4. Go back to start>(search for)cmd>click cmd
5. In the new commandline window, type in "ipconfig /all" and scroll through the results until you find the EVDO adapter and it's IP info
6. in the TCP/IPv4 window you opened in step 3, click "use the following IP address" button, and type in the gateway, subnet and dns addresses (if available) you found in the commandline window. In the "IP Address:" bar, that's where you type in 192.168.0.1
7. Click okay, okay, and that's it. You should now have a static IP permanently configured for your USB adapter.

I'm assuming this walkthrough may not be so helpful since it sounds like your USB modem is acting as a router too, so you'll probably have to configure the DHCP and static settings from whatever software you had to install to get other machines to connect to it. What's the software you're using?

If the modem uses the gateway of 192.168.0.1 it's not a modem at all, instead it's one of those modem/router combo's and it sounds like the OP has that plugged into another router.

This certainly isn't a proper way to set up any type of reliable network.

Setting up a static IP won't fix an incorrectly set up network.

I'm imagining it's:

A dongle that plugs into a desktop/laptop. No other routers involved, it's just a hotspot. Uses software to tell devices it's a wireless router, and kablowy... that's it. My IPv4 walkthrough I'm assuming is totally useless because this isn't just a modem, as you said it's probably a hotspot+modem device. But yes, many manufacturer-specific apps and Windows communication glitches could easily warrant a forced static internal address, especially if the client that's getting assigned by the local hotspot is also pulling double duty as the gateway for other devices. I don't think we've got enough info to make that call yet, but there are definitely times when a dynamic OR static changeover will fix a network.

Setting up static IP's is child's play but that isn't really the issue here.

The issue is that the hardware for this network is not set up properly in the first place. This will only lead to problems further down the line.

In my opinion the modem/router combo thingy needs to be removed and replaced with a standard modem before this network has any chance of working like it should. I'd personally never try building a reliable network starting with one of those modem/router combo's. And disabling DHCP on the modem/router might work but I'd still never do it that way.